Hi folks,
The user manual says "ask for help here after you've done an erase_flash", so here goes :-)
I'll get into the dev stuff later but at this stage I'd appreciate it if you could share how I can get the OVMSv3 firmware re-installed on the module after the flash has been erased.
thanks,
Jan
Jan,
download the three .bin files from here:
https://ovms.dexters-web.de/firmware/ota/v3.1/edge/
Then do:
esptool.py --chip esp32 --port /dev/ttyUSB0 --baud 921600 --before "default_reset" --after "hard_reset" write_flash -z --flash_mode "dio" --flash_freq "40m" --flash_size detect 0x1000 bootloader.bin 0x10000 ovms3.bin 0x8000 partitions.bin
…replacing the port by your USB device.
Regards,
Michael
Hi Michael,
Thanks for the quick response!
Jan
Hi Michael,
Sorry to bother you...
Is it possible to determine the size of the current firmware and copy that off the OVMS v3 module?
Something along the lines of:
esptool.py -p /dev/ttyUSB0 -b 115200 read_flash 0x1000 0x7000 bootloader.bin 0x8000 0x8000 partitions.bin 0x10000 ????? ovms3.bin
For bootloader.bin and partitions.bin it's easy to find the max size (so I assume that is what one should use?). Not sure what to pick for ovms3.bin though.
I'd like to make a copy of the current firmware, then erase the flash, then muck around with firmware, and once I'm done playing put it all back together to what it was.
kind regards,
Jan
kind regards,
Jan
Yes, you can use read_flash to read the firmware off the module (as well as configuration area, etc). The different offsets and sizes of the different partitions are shown in the partitions.csv file (source of partitions.bin):
https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3/blob/ma...
Alternatively, you can just grab the entire 16MB of flash from offset 0.
Regards, Mark.