-
-
Searching on the esprino site for that device code comes up with
http://www.espruino.com/ILI9163
So looks like you could use that library
-
Article on espruino and @Gordon in make magazine...
Maker Pro News: An Open Hardware Exposé, Changes at TechShop, and More
http://makezine.com/2017/06/13/maker-pro-news-open-hardware-expose-changes-techshop/ -
-
@Gordon
The other option would be to add ble support to the Linux build and run that on a pi 3? -
-
-
This might help.
It runs a background service that makes Bluetooth appear to chrome as web Bluetooth.
http://forum.espruino.com/conversations/305246/#comment13648705 -
-
-
The default firmware for the ESP32 is setup to use an FAT files system on the last 1 Mb of the flash memory. To use and SPI SD card, you would need to do a custom build of the firmware, and turn of the FlashFS option. You can use SPI for other devices with the stock firmware
https://github.com/espruino/Espruino/blob/master/boards/ESP32.py#L35
'FILESYSTEM', 'FLASHFS' ],
Would need to be changed to:
'FILESYSTEM', # 'FLASHFS' ],
and the firmware rebuilt. Then an external SD card could be used.
-
@Gordon
Looks like there is an issue here:http://www.espruino.com/json/ESPRUINOBOARD.json
"libraries": [ "NET", "GRAPHICS", "NEOPIXELHASHLIBFILESYSTEM" ],
-
It should be there:
https://github.com/espruino/Espruino/blob/master/boards/ESPRUINOBOARD.py#L40What does
var fs=require('fs')
show? -
-
-
-
I'm having the same problem. If I type this into the console in the IDE:
You need to enter this on the right hand side of the ide, so that the module can be loaded onto the board.
If you enter it on the left side, you will get that message.
edited by Gordon - I think you got the sides switched over :)
-
-
@AlessioBacin
The ESP8266 port does not have the TLS component compiled in that is required for https. There is not enough free memory for the buffers required. You reduce the number of jsvars and compile this in, but depending on how complex your code is, you might not have enough space left to do what you want to achieve.You could use a http to https proxy service as a helper.
The ESP32 build has enough resources, so that https:// works.
I think this could be related to the address of functions getting called from an earlier version of the firmware. If flash and blank out the code area, and then upload your code again, it might all go away...
Sorry, can't recall the address to flash too.