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

mfg: account for updated bootloader path in mfg command #440

Merged
merged 1 commit into from
Jul 20, 2021

Conversation

vikrant-proxy
Copy link
Contributor

Bootloader binaries seem to have moved to app/@mcuboot, which causes mfg command to fail, see #439. This PR attempts to account for this change.

Copy link
Contributor

@vrahane vrahane left a comment

Choose a reason for hiding this comment

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

This does look fine to me. I will let it get reviewed by others as well since we do not want this to be a compatibility breaking change for others.

@vrahane vrahane merged commit 9009682 into apache:master Jul 20, 2021
@marcoNexion
Copy link

Hi, after pulling this commit I've a compatibility issue. Since my own bootloader (a stub) is located in the bootloader area and not dependent of @mcuboot.
Do I need to change my bsp.flash_map when bootloader is not based on mcuboot ?

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.

3 participants