I had been playing with that as I kept getting WebIDE syntax errors R-Hand editor side, and wondered, as no one had success in either of the other forum links if one or the other was a typo.
>SPI: {
"_options": { "sck": D14, "miso": D12, "mosi": D13 }
}
Uncaught Error: RFM69 not found
at line 1 col 58
...row Error("RFM69 not found");b.w(47,85);if(85!=b.r(47))throw...
^
in function called from system
{
"spi": SPI: {
"_options": { "sck": D14, "miso": D12, "mosi": D13 }
},
"cs": D15, "rst": D16, "freq": 915 }
>
The "RFM69 not found" error seems to be from ~L080:
The part I'm still struggling with is that in order to get a correct syntax check, I need to use
the NodeMCU.Dx format, I seem to get errors, as it might just be that those GPIO pin designations just don't exist for the D1 mini. Is it ESP8266, ESP32, RFM69, or Espruino under the hood?
Still searching for the Git source that might explain the NodeMCU.Dx mapping to see if limitations exist there.
AFAIK, on the ESP8266, only some pins are truly general purpose input and output pins. Lots have restrictions either during boot, or don't behave nicely either as input or output. Nodemcu.D8 == GPIO15 might be one of those pins, but not certain about it...
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
It appears we were updating at the same time. . . .
Good catch @AkosLukacs!
I had been playing with that as I kept getting WebIDE syntax errors R-Hand editor side, and wondered, as no one had success in either of the other forum links if one or the other was a typo.
But, with a bit of fiddling,
'cs' and 'rst' are now recognized.
The "RFM69 not found" error seems to be from ~L080:
The part I'm still struggling with is that in order to get a correct syntax check, I need to use
the NodeMCU.Dx format, I seem to get errors, as it might just be that those GPIO pin designations just don't exist for the D1 mini. Is it ESP8266, ESP32, RFM69, or Espruino under the hood?
Still searching for the Git source that might explain the NodeMCU.Dx mapping to see if limitations exist there.