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

Expander cannot be flashed #53

Closed
falkoschindler opened this issue Jul 9, 2024 · 2 comments · Fixed by #56
Closed

Expander cannot be flashed #53

falkoschindler opened this issue Jul 9, 2024 · 2 comments · Fixed by #56
Assignees
Labels
bug Something isn't working
Milestone

Comments

@falkoschindler
Copy link
Collaborator

Currently there is an issue flashing the expander, causing it to crash with a backtrace. We assume the problem is due to a different partition table in version 0.1.12. So when updating an expander from some version like 0.1.5 to 0.1.11, it works well. But upgrading to 0.1.12 fails.

Maybe we can make CONFIG_PARTITION_TABLE_OFFSET an optional parameter for core.flash() to work around these edge cases. Or we describe how to OTA-update the expander in the readme. As long as we don't change the partition table in the near future, a temporary fix might be good enough.

@falkoschindler falkoschindler added the bug Something isn't working label Jul 9, 2024
@falkoschindler
Copy link
Collaborator Author

Or we describe how to OTA-update the expander in the readme.

We noticed that this is not an option, because the firmware on the expander doesn't know the ota() command. So we need to fix the flash() command to work with arbitrary partition tables on the target ESP.

@JensOgorek
Copy link
Contributor

Fixed with PR: #56

@falkoschindler falkoschindler linked a pull request Jul 15, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants