Can the GUI be updated to use the latest esptool? #2
Comments
|
Attempted to follow more closely the instructions of https://github.com/sparkfun/SparkFun_RTK_Firmware/blob/main/docs/firmware_update.md with some success but the GUI does not. Cloning https://github.com/espressif/esptool.git and running esptool from that with chip_id I get: Where it is written in firmware_update.md: esptool.exe --chip esp32 --port COM6 --baud 921600 --before default_reset --after hard_reset write_flash -z --flash_mode dio --flash_freq 80m --flash_size detect 0x1000 ./bin/RTK_Surveyor.ino.bootloader.bin 0x8000 ./bin/RTK_Surveyor_Partitions_4MB.bin 0xe000 ./bin/boot_app0.bin 0x10000 ./RTK_Surveyor_Firmware_vxx.bin I have transliterated that to instead run the following: confirmed via serial output: ...and so that seems to be functional. Does esptool for the GUI need to be updated? Aside I had to pull in |
|
Hi @eshattow , Apologies for the inconvenience and your long history of wrestling with RTK updates on Linux. Thank you for the detective work. If esptool v4.7 fixes this issue then we will absolutely update the GUI to match. I'm looking at it now. Best wishes, |
|
Hi @eshattow , I'm struggling with this... I've created a new v1.6.0 branch. In there, I've deleted the old copy of I'm on Windows. If I run
But if I run the executable created by the workflow, it fails silently at "Uploading stub...":
Interestingly, if I leave the executable open, and re-run the uploader locally, it then fails at the same place. But starts working as soon as I close the executable. Something is being loaded differently between the two environments. I suspect (py)serial, but I don't yet know how to prove that or correct it. Thanks for the pointer about I don't think this is related to this issue, but it could be. I'll have to give up on this for now and will come back to it on Monday. More later, |
|
I now suspect this is caused by |
|
Ah. Cancel that. I now suspect it is because it can't find stub_flasher_32.json. I bet that isn't being added to the pyinstaller installer...? |
|
The same issue is described here: espressif/esptool#208 (comment) OK. I'm giving up on this. Sorry! Generating a self-consistent GUI executable seems very difficult with esptool ~4.6.2. You can download the GUI source here: https://github.com/sparkfun/SparkFun_RTK_Firmware_Uploader/archive/refs/heads/v1.6.0.zip |
PaulZC
changed the title
|
Note: esptool 4.7.0 released upstream a couple weeks ago. |
PaulZC
changed the title
|
Thanks for the heads-up @eshattow Humm... I wonder if there is a sneaky way to add the stub_flasher json files to the pyinstaller installer? |
|
Hi @eshattow , I've made some progress with this: I have it working nicely on Windows; I can't get it to work on macOS; and I don't have a Linux machine to test it on. There were two 'tricks' to get it running on Windows:
This works on Windows, but fails on macOS. It appears that the esptool pyc still can't find the stub_flasher json files. Best wishes, |
|
RTK Surveyor 4MB is attached and powered on. $ ./RTKUploader.linux Choose Firmware File Browse to /tmp/SparkFun_RTK_Firmware_Binaries.git/RTK_Surveyor_Firmware_v4_0.bin Upload Firmware |
|
That's great - looks like it is working nicely!? I'm not sure where all of those warnings are coming from. My Linux Fu is weak.... |
|
Well, that turned into quite an adventure. I couldn't get the uploader to work on MacOS due to - I thought - it not being able to find the stub_flasher json files. Turns out it was just the baud rate. As soon as I dropped to 460800, everything started working... Please see: https://github.com/sparkfun/SparkFun_RTK_Firmware_Uploader/releases/tag/v1.6.0 Enjoy! Closing... |
From RTK Firmware Uploader v1.5.2 when used with RTK_Surveyor_Firmware_v3_10.bin:
I've tried all three listed baud rates (115200, 460800, 921600) but the outcome is the same. See sparkfun/SparkFun_RTK_Firmware#361 and sparkfun/SparkFun_RTK_Firmware#266 it is the same hardware. Is there no way to do this with the GUI?
Additionally I tried:
The text was updated successfully, but these errors were encountered: