boards: nordic: nrf54h20dk iron board MCUBoot support #88298
Conversation
|
Hello @nordic-mik7, and thank you very much for your first pull request to the Zephyr project! |
github-actions
bot
requested review from
anangl,
jaz1-nordic,
kl-cruz,
magp-nordic,
masz-nordic and
nika-nordic
Provide proper adaptions as bootloader ROM offset, flash load offset and dts definitions for the nRF54H20 iron board to make it ready for the MCUBoot bootloader. Signed-off-by: Michal Kozikowski <[email protected]>
nordic-mik7
force-pushed
the
dev/ironboard_mcuboot_rom_offset
branch
from
4cf4c1e to
2c20897
Compare
nordic-mik7
changed the title
github-actions
bot
requested review from
de-nordic,
kartben,
nashif and
nordicjm
| # Copyright (c) 2025 Nordic Semiconductor ASA | ||
| # SPDX-License-Identifier: Apache-2.0 | ||
|
|
||
| config SMP_SVR_NRF54H20_SAMPLE | ||
| bool | ||
| default y if SOC_NRF54H20_CPUAPP | ||
| select EXPERIMENTAL | ||
|
|
||
| source "Kconfig.zephyr" |
There was a problem hiding this comment.
It was requested to deliver this sample as experimental.
| # If cpusec_cpuapp_ipc node is present in dtc, it automatically enables canonical ZCBOR encoding. | ||
| # Canonical ZCBOR encoding needs legacy RC behaviour to work with mcumgr-client and other PC tools. | ||
| # When tools are updated, this can be removed. | ||
| CONFIG_MCUMGR_SMP_LEGACY_RC_BEHAVIOUR=y |
There was a problem hiding this comment.
I don't follow this, this hasn't been a problem with any other board and has not been set for others in years, even when used with that garbage tool does not refer to the go tool. If there is a problem with a tool, report it to the tool author. Gold standard is AuTerm, if it works with that then other tools are broken.
There was a problem hiding this comment.
nrf54h20 IPC communication with secdom enforced canonical ZCBOR encoding so far. Canonical ZCBOR is not working with AuTerm unless we use legacy RC codes. This CONFIG is set here to indicate that if we enable IPC node for nrf54h20 in the future, legacy RC behavior must be set.
There was a problem hiding this comment.
I have an nrf5340dk here with this sample, CONFIG_ZCBOR_CANONICAL=y and CONFIG_MCUMGR_SMP_LEGACY_RC_BEHAVIOUR=n using AuTerm 0.35a and MCUmgr is working perfectly over the UART so if it doesn't work for you on nrf54h20 then would suggest trying an nrf52/nrf53 dev board and if that works, indicates there is an issue with something else
There was a problem hiding this comment.
removed it. You are right, it seems that there were some issues related to IPC itself in previous Ironside SDFW. To be investigated, currently IPC with secdom is turned off.
Adding sample configuration for nRF54H20dk 'iron' board. Signed-off-by: Michal Kozikowski <[email protected]>
nordic-mik7
force-pushed
the
dev/ironboard_mcuboot_rom_offset
branch
from
c83e43b to
e30da54
Compare
| slot0_partition: partition@3c000 { | ||
| label = "image-0"; | ||
| reg = <0x3c000 DT_SIZE_K(400)>; | ||
| }; | ||
|
|
||
| slot1_partition: partition@6E000 { | ||
| label = "image-1"; | ||
| reg = <0x6E000 DT_SIZE_K(400)>; |
There was a problem hiding this comment.
I guess the size of these partitions was supposed to be 200 kB, not 400.
|
Please do not review this PR, write your comments in #88576 The author of this PR is out of office, and we do not have write access to his fork. |
Provide proper adaptions as bootloader ROM offset, flash load
offset and dts definitions for the nRF54H20 iron board to make it
ready for the MCUBoot bootloader.
Adding smp_svr sample configuration for nRF54H20dk 'iron' board.