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

MCUBoot doesn't jump to primary slot if secondary slot is unavailable #2219

Open
td-frosik opened this issue Feb 26, 2025 · 5 comments
Open

Comments

@td-frosik
Copy link

I have the secondary slot placed in the external flash. I would like the MCUBoot to jump to the application in the primary slot even if the external flash is damaged or unavailable.

Could you add configuration option to ignore error from opening the secondary slot flash area?

@nordicjm
Copy link
Collaborator

If the secondary device is not available then the device/hardware is faulty, the abort of booting is intentional

@td-frosik
Copy link
Author

It would be better to have an option to start the application in the primary slot which is valid and be able to send the information about external flash error to cloud or wherever it's needed.

@nordicjm
Copy link
Collaborator

It would be better to have an option to start the application in the primary slot which is valid and be able to send the information about external flash error to cloud or wherever it's needed.

You could probably do this in MCUboot already with a hook and returning dummy empty data if the device is not present

@td-frosik
Copy link
Author

Could you show me some example that explains how it can be done?

@nordicjm
Copy link
Collaborator

In https://github.com/mcu-tools/mcuboot/tree/main/boot/zephyr the hooks_sample.c file, there is a Kconfig for enabling hooks

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

2 participants