For a day or so, V3.0 is released.
We've been waiting long time for this step.
My plan now is, to get Espruino running with actual sources, which are
There are some restrictions like
Once this upgrade to V3.0 is done and works fine, next steps are
Please take my plan as starting point only.
Any comments, especially from guys (hopefully) involved, are welcome.
This sounds great - thanks! I don't think OTA works on ESP32 at the moment, so I wouldn't waste time worrying about it.
I imagine most users would prefer BLE to the extra few vars given the choice, and memory usage isn't such a nightmare now it's reasonably easy to upload code directly to flash.
Your right - the ota stuff was never completed.
My two cents worth... this is a possible plan
At this stage I'm not sure if the esp32 ble branch builds if the BLE Makefile flags are off?
I believe we should offer a build without BLE, as the increased RAM usage and power requirements might not suit everyone.
Or the other options to offer two firmware - one with BLE and one without?
How does this sound?
sounds ble-eding good ;-)
@Wilberforce, thanks for your feedback
I’ve started an issue page here - it’s probably best to track there.
I have done a pull request on the master branch which updated the compiler. This is done in the provision script.
Will add more answers to your questions today.
At this stage I still can't get a build running, as it's expecting the psram, and that not available on the standard boards. I need to get the build working with a standard board and v3 before we can move on...
I've got a plain build with v3 and 4000 vars booting. Please see the github post above.
Next step is to update the build tools so this can be part of master, then look at bring in the Bluetooth
Hi! I've tried to build ESP32 branch, and I have no success.
First of all, I have found that 'source scripts/provision.sh ESP32' (as in docs) gets app and esp-idf from master branch of EspruinoBuildTools while code uses newer version already. I have corrected it to get ESP32 branch.
Then I have got an error about unknown gcc option '-mfix-esp32-psram-cache-issue'. After removing it from makefile (in any case I have no board with psram) I have all files compiled. But at linking stage I have got "undefined reference to `esp_ble_gap_set_security_param'" error.
While I think the build will not work without the call, I have commented all calls of esp_ble_gap_set_security_param() to look for next stop. It is "cp: cannot stat '/home/serge/Projects/ESP32/Espruino/app/build/partitions_espruinoBLE.bin': No such file or directory"
My build commands are:
source scripts/provision.sh ESP32
make clean && BOARD=ESP32 DEBUG=1 USE_BLUETOOTH=1 make
Sorry - this stuff is in flux at the moment. I have created a new branch to resolve the issues, then will push once all the testing is done. This branch updates the tool chain and solves all the issues you are seeing.
I then have the task to merge the two branches into master...
Can you wait a bit longer?
If it is firmware you want to try with Ble compiled, I can provide a link for that.
Thank you. My idea is to transfer Puck.JS BLE-MQTT bridge from Raspberry-like system to ESP32 and use one of public MQTT services with it. It may be cheap and simple solution.
@JumJum published a build here:
You will need to use all bin files, as the partition table is different. Please note that it will be changing from what is in the firmware linked above. You might want to do a flash erase.
If you do get a puck linked to the esp32 as a bridge, please start a new topic and share!
Don't worry about formatting, just type in the text and we'll take care of making sense of it. We will auto-convert links, and if you put asterisks around words we will make them bold.
For a full reference visit the Markdown syntax.
© Espruino, powered by microcosm.
Report a problem