Skip to content

bootloader-fw-link: Use RAM to communicate #1423

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

NickeZ
Copy link
Collaborator

@NickeZ NickeZ commented Apr 22, 2025

Instead of writing to non-volatile storage between mcu resets, write to a well-known location.

RAM is random after hardware reset, but does not get cleared on MCU reset.

Instead of writing to non-volatile storage between mcu resets, write to
a well-known location.

RAM is random after hardware reset, but does not get cleared on MCU
reset.
@NickeZ NickeZ force-pushed the nickez/auto-enter-in-ram branch from c018ffc to bf840c2 Compare April 22, 2025 22:08
}
}
// After reset we prefer to stay in bootloader
auto_enter = sectrue_u32;
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The factory-setup could also just erase the first 8 bytes of itself when it is done, making it unbootable (and thus the bootloader would not try to boot it).

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

Successfully merging this pull request may close these issues.

1 participant