You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working with an ESP32-S3 core on a project where I need to flash three .bin files, all over 1MB, to three separate locations in memory. Currently, the write_bin_to_flash method forces the device to reboot after each method call (link), which causes a communication failure error when I try to write at the next location.
I am looking for the ability to specify that the device should only restart after the last call to write_bin_to_flash. I would assume this would require a new parameter.
The text was updated successfully, but these errors were encountered:
Hi! I've just implemented #561, which might help here (although it might not be a full solution, I think). You could use --after no-reset or --after no-reset-no-stub to avoid the reset after every write. I'd appreciate it if you could give it a try.
Thanks for your work on the project!
I'm working with an ESP32-S3 core on a project where I need to flash three
.bin
files, all over 1MB, to three separate locations in memory. Currently, thewrite_bin_to_flash
method forces the device to reboot after each method call (link), which causes a communication failure error when I try to write at the next location.I am looking for the ability to specify that the device should only restart after the last call to
write_bin_to_flash
. I would assume this would require a new parameter.The text was updated successfully, but these errors were encountered: