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: Alignments needed for devices without erase #85620

Closed

Conversation

de-nordic
Copy link
Collaborator

MCUboot support for devices without erase may require additional alignment in Zephyr.

@zephyrbot
Copy link
Collaborator

zephyrbot commented Feb 11, 2025

The following west manifest projects have changed revision in this Pull Request:

Name Old Revision New Revision Diff
mcuboot zephyrproject-rtos/mcuboot@346f737 (main) zephyrproject-rtos/mcuboot@f2b6def (upstream-sync) zephyrproject-rtos/mcuboot@346f7374..f2b6def9
trusted-firmware-m zephyrproject-rtos/trusted-firmware-m@2f13847 (main) zephyrproject-rtos/trusted-firmware-m#120 zephyrproject-rtos/trusted-firmware-m#120/files

DNM label due to: 1 project with PR revision

Note: This message is automatically posted and updated by the Manifest GitHub Action.

@zephyrbot zephyrbot added manifest manifest-mcuboot DNM (manifest) This PR should not be merged (controlled by action-manifest) labels Feb 11, 2025
MCUboot support for devices without erase may require additional
alignment in Zephyr.

Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
The commit brings TrustedFirmware-M version that provides
flash_area_get_sector function required by MCUboot.

Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DNM (manifest) This PR should not be merged (controlled by action-manifest) manifest manifest-mcuboot manifest-trusted-firmware-m
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants