pycom-fwtool-cli flash command using .tar.gz vs .elf file
I took a look at this -> Re: Using pycom-fwtool-cli, but still have questions.
What am I missing where flashing with this tool where the repo publishes .elf files, but this tool takes either a .tar.gz or a binary file & partition combo?
FYI here's the output of my pycom-fwtool-cli which is different (newer?) than the documentation.
user@host# pycom-fwtool-cli -p /dev/ttyACM0 flash -f LoPy4-application.elf-0x00000.bin -h usage: pycom-fwtool-cli flash [-h] [-t TAR] [-f FILE] [--secureboot] [-p PARTITION] optional arguments: -h, --help show this help message and exit -t TAR, --tar TAR perform the upgrade from a tar[.gz] file -f FILE, --file FILE flash binary file to a single partition --secureboot Flash Encrypted binaries if avialable -p PARTITION, --partition PARTITION The partition to flash (all, fs, nvs, factory, secureboot, bootloader, partitions, otadata, fs1, ota_0, config)
I've figured out the esptool.py elf2image part ... but what partition do I need to use to get the latest firmware on here.
Hopefully I'm missing something, and making this too difficult? Thoughts?
esptool.py elf2image LoPy4-application.elf
I've been trying various things, so I'm not sure the state of my flash is ok, namely I get this on the console:
rst:0x10 (RTCWDT_RTC_RESET),boot:0xb (HSPI_FLASH_BOOT) flash read err, 1000 ets_main.c 371 ets Jun 8 2016 00:22:57 rst:0x10 (RTCWDT_RTC_RESET),boot:0xb (HSPI_FLASH_BOOT) flash read err, 1000 ets_main.c 371 ets Jun 8 2016 00:22:57