Porting our board from ncs sdk 2.6.1 to 3.2.1

[C.Thilo]

Hi

I'm currently in the middle of porting our board from nrf sdk 2.6.1 to nrf sdk 3.2.1.

I made it so far, that the correct dts are used, but somehow the build process seems not to see, that our board is based on the nrf5340 soc.

During sysbuild (whatever that is) it recognizes the dependency as the entries are correct in
build/zephyr/.config:

SB_CONFIG_BOARD="panngmodule"
SB_CONFIG_BOARD_REVISION=""
SB_CONFIG_BOARD_PANNGMODULE=y
SB_CONFIG_BOARD_PANNGMODULE_NRF5340_CPUAPP_NS=y
SB_CONFIG_BOARD_QUALIFIERS="nrf5340/cpuapp/ns"
SB_CONFIG_SOC="nrf5340"
SB_CONFIG_SOC_SERIES="nrf53"
SB_CONFIG_SOC_FAMILY="nordic_nrf"
SB_CONFIG_SOC_FAMILY_NORDIC_NRF=y
SB_CONFIG_SOC_SERIES_NRF53X=y
SB_CONFIG_SOC_NRF5340_CPUAPP=y
SB_CONFIG_SOC_NRF5340_CPUAPP_QKAA=y

But when the normal build for our project starts, the dependency to the SOC is missing.

Our Kconfig.panngmodule looks exactly like that one of NRF5340DK, except of the Board "prefix"

config BOARD_PANNGMODULE
	select SOC_NRF5340_CPUAPP_QKAA if BOARD_PANNGMODULE_NRF5340_CPUAPP
	select SOC_NRF5340_CPUAPP_QKAA if BOARD_PANNGMODULE_NRF5340_CPUAPP_NS
	select SOC_NRF5340_CPUNET_QKAA if BOARD_PANNGMODULE_NRF5340_CPUNET

So where would I need to search for?

[C.Thilo]

Ok. I though it ignores it. But the real problem were some proj.conf entries which are not working anymore.

The multicore build changed, right?
At least the previously working build with 2.6.1, MCUBoot and rpmsg 802154 via child_image folder are is not working anymore.

Both bootloader and the rpmsg image for CPUNET are not build anymore.
I guess, I need to look deeper into the sysbuild of zephyr. Is this the multi core build nowadays?

Cheers,
Thilo

[Vidar Berg]

Hello,

You are on the right track. I also recommend you go through the following migration documents which explain the new HW model and the multi image (sysbuild) support introduced in SDK v2.7.0:

- https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_sysbuild.html

- https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_hwmv2.html

Best regards,

Vidar

[C.Thilo]

Hi Vidar

Thank you for the links!
Will look into it!

Kind regards,
Thilo

[C.Thilo]

Hi Vidar

Do you have by any chance a migration guide for the partitionmanager? 

We used to use a pm_static.yml across multiple projects running on the same board, so one one bootloader fits all and we could update the one app or the other.

Any hints how we can get this to work again?

Thanks!

Cheers,
Thilo 

[Vidar Berg]

Hi Thilo,

You should be able to use the same pm_static.yml as before. Are you seeing any build errors, or is it simply not being picked up by the build? Is the file located in the project root?

Cheers,

Vidar

[C.Thilo]

Hi Vidar,

Here my current sysbuild.conf perhaps it is a part of the problem.

SB_CONFIG_BOOTLOADER_MCUBOOT=y
SB_CONFIG_MCUBOOT_MODE_SINGLE_APP=y

SB_CONFIG_NETCORE_802154_RPMSG=y

SB_CONFIG_PARTITION_MANAGER=y

pm_static.yml is located in the root of the project and was always magically picked.

We use a single slot for the application and have b0n for the netcore and of course the netcore app itself. Thats why we have the SB_CONFIG_MCUBOOT_MODE_SINGLE_APP in sysbuild.conf
and in the prj.conf of mcuboot I added:

CONFIG_SINGLE_APPLICATION_SLOT=y
CONFIG_MCUBOOT_GENERATE_UNSIGNED_IMAGE=y

My build currently tells me, that the slot0_parition is missing:

CMake Error at /media/data/projects/pan-ng/ZephyrSDK/zephyr/cmake/modules/extensions.cmake:3880 (message):
  required nodelabel not found: slot0_partition
Call Stack (most recent call first):
  CMakeLists.txt:554 (dt_nodelabel)

 
I'm unsure if it is because we have no slot0_parition in the dts, as we used the pm_static.yml way and dts definition were ignored anyway, so we removed them.

And the other problem is, that we use unsigned images but mcuboot wants a key file:

MCUBoot bootloader key file: /media/data/projects/pan-ng/ZephyrSDK/bootloader/mcuboot/root-rsa-2048.pem
CMake Warning at CMakeLists.txt:442 (message):
  WARNING: Using default MCUboot signing key file, this file is for debug use
  only and is not secure!

But good to now, that the pm_static.yml can still be used.

Cheers,
Thilo