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 link into code-partition #14566
Comments
I would introduce Kconfig property:
And use it for conditional assignment to Then Mcuboot project should then select just select |
Can you confirm that this affects other boards? |
I confirm that this is issue for other boards as well. |
I mentioned this to @carlescufi a while back on Slack. I was having a problems getting binaries built from Zephyr to have the correct flash offset settings. I eventually got it to work by manually specifying how I wanted mcuboot built:
Using this method, I was able to take the .hex file directly and place it on the board using the nRF-Connect GUI tool for Linux. |
@mike-scott Thanks for post this workaround. |
@nvlsianpu : Could you do a PR with your proposed solution? I'm not familiar enough with these symbols to review unfortunately. |
mcu-tools/mcuboot#445 |
Objective of the path is to allow to select by the application to link into the chosen code-partition. Introduced USE_CODE_PARTITION will be set by bootloader project. fixes zephyrproject-rtos#14566 Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
Objective of the path is to allow to select by the application to link into the chosen code-partition. Introduced USE_CODE_PARTITION will be set by bootloader project. fixes #14566 Signed-off-by: Andrzej Puzdrowski <andrzej.puzdrowski@nordicsemi.no>
mcuboot doesn't link into code-partition despite it is chosen.
To Reproduce
build mcuboot against nrf52840_pca10059 zephyr target or any else target which has shifted code-partition.
Expected behavior
linking into code partition.
Impact
mcuboot will not work on XIP target which has mcuboot partition started at offset different than Zero.
Environment
mcuboot issue
mcu-tools/mcuboot#444
The text was updated successfully, but these errors were encountered: