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

Define communication between bootloader and booted image #204

Closed
d3zd3z opened this issue Feb 5, 2018 · 3 comments
Closed

Define communication between bootloader and booted image #204

d3zd3z opened this issue Feb 5, 2018 · 3 comments
Milestone

Comments

@d3zd3z
Copy link
Member

d3zd3z commented Feb 5, 2018

In order for the application to know how to perform an upgrade, it needs to know certain information from the bootloader, at a minimum, a version number. It would be better, however, for this information to be closer to the information needed to convey (upgrade type, slot information, etc).

Implement a mechanism to communicate this information between the bootloader and the running app.

@d3zd3z d3zd3z added this to the 1.2.0 milestone Feb 5, 2018
@d3zd3z
Copy link
Member Author

d3zd3z commented Feb 5, 2018

Copied from MCUB-17.

@nvlsianpu
Copy link
Collaborator

@utzig utzig modified the milestones: 1.2.0, 1.3.0 Apr 3, 2018
@d3zd3z d3zd3z modified the milestones: 1.3.0, 1.4.0 Jan 18, 2019
@d3zd3z
Copy link
Member Author

d3zd3z commented Nov 27, 2019

I've requested Zephyr: Inter-applications flash_map exchange mechanism be closed, and I'm going to close this as well. If someone finds a need for this, feel free to re-open, but with Zephyr, we seem to do OK by conveying this information through device tree, and the current mechanism.

@d3zd3z d3zd3z closed this as completed Nov 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants