Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to specify whether to reboot after writing bin to flash #497

Open
ajmcquilkin opened this issue Nov 5, 2023 · 1 comment
Open
Labels
enhancement New feature or request

Comments

@ajmcquilkin
Copy link

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, 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.

@jessebraham jessebraham added the enhancement New feature or request label Dec 6, 2023
@SergioGasquez
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

3 participants