Trouble migrating from NCS 2.6 to 2.8

RE: Trouble migrating from NCS 2.6 to 2.8

willdean — Sun, 12 Jan 2025 13:17:18 GMT

Please accept my gratitude for working through this! I have just moved a project from 2.7 to 2.9 and had exactly this problem (among others). Your two weeks (of undoubted misery) was a great benefit to me.

What a shambles this project is. Not sure who the target audience is, but I don't feel like I'm it.

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Fri, 03 Jan 2025 10:45:29 GMT

Running the debugger through the bt_enable code (not fun with the different in-line and macro encapsulations btw...) led me to think that the function hooks for the hci ipc driver are not initialised correctly.

The code has a lot of macros of type DT_HAS_DRIVERxxx, searching the forum found me this post

nrf5340 custom board: bt_hci_core: No HCI driver registered - Bluetooth init failed (err -19)

Although I had a crash rather than a error code, it turned out to be a similar issue.

My DTS from 2.6 had in the chosen section the correct chosen name:

chosen {

...

zephyr,bt-hci = &ipc0; // BAD

zephyr,bt-hci-ipc = &ipc0; // IRRELEVANT

...

};

Turns out that in NCS 2.8, you MUST have the chosen point to the specific bt_hci_ipc0 node:

zephyr,bt-hci = &bt_hci_ipc0;

If you don't set it at all you get the init failed log, if you set it to &ipc0 you will get the core dump (thanks for that).

btw, the chosen name "zephyr,bt-hci-ipc" now appears to be ignored and can be omitted.

The definition of bt_hci_ipc0 is found in zephyr/dts/arm/nordic/nrf5340_cpuapp_ipc.dtsi:

ipc0: ipc0 {

compatible = "zephyr,ipc-openamp-static-vrings";

memory-region = <&sram0_shared>;

mboxes = <&mbox 0>, <&mbox 1>;

mbox-names = "tx", "rx";

role = "host";

status = "okay";

bt_hci_ipc0: bt_hci_ipc0 {

compatible = "zephyr,bt-hci-ipc";

status = "okay";

};

Why the chosen has to point to bt_hci_ipc0 and not ipc0 is completely opaque to me, I can find NO documentation about this in the nordic or zephyr docs.

Also, just for fun, note that the CPUNET dts requires this chosen line:

zephyr,bt-hci-ipc = &ipc0;

and cannot refer to bt_hci_ipc0 as this node does not exist for the CPUNET image build (in nrf5340_cpunet.dtsi there is just ipc0)...

On tyhe positive side, it seems that the NCS 2.6 CPUNET build image will work with the 2.8 CPUAPP image, although I haven't fully tested everything yet due to the need to clean up all the various changes made over the last 2 weeks trying to get this to run....

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Tue, 24 Dec 2024 12:02:31 GMT

Blocking issue for now is that I cannot get the BLE HCI to start without this error:

[00:00:09.128,051] <wrn> app: NetBLE starting....
[00:00:09.134,338] <err> os: ***** USAGE FAULT *****
[00:00:09.139,923] <err> os:   Unaligned memory access
[00:00:09.145,751] <err> os: r0/a1:  0xc8c3b562  r1/a2:  0x601d8767  r2/a3:  0x9939399b
[00:00:09.154,418] <err> os: r3/a4:  0x0002dff5 r12/ip:  0x01010101 r14/lr:  0x0002e01d
[00:00:09.163,085] <err> os:  xpsr:  0x21000200
[00:00:09.168,304] <err> os: Faulting instruction address (r15/pc): 0x00073cde
[00:00:09.176,208] <err> os: >>> ZEPHYR FATAL ERROR 31: Unknown error on CPU 0
[00:00:09.184,082] <err> os: Current thread: 0x20007d60 (sysworkq)
[00:00:09.190,948] <err> os: Halting system

This is as soon as the application calls bt_enable(NULL); The wifi stack is not yet started BTW so shouldn't be causing an issue....

Call stack from the debugger:

arch_system_halt@0x000b59ee (c:\ncs\v2.8.0\zephyr\kernel\fatal.c:30)
k_sys_fatal_error_handler@0x000742d6 (c:\ncs\v2.8.0\zephyr\kernel\fatal.c:44)
z_fatal_error@0x00074378 (c:\ncs\v2.8.0\zephyr\kernel\fatal.c:119)
z_arm_fatal_error@0x0004b594 (c:\ncs\v2.8.0\zephyr\arch\arm\core\fatal.c:86)
z_arm_fault@0x0004bad8 (c:\ncs\v2.8.0\zephyr\arch\arm\core\cortex_m\fault.c:1157)
z_arm_usage_fault@0x0004bbbc (c:\ncs\v2.8.0\zephyr\arch\arm\core\cortex_m\fault_s.S:102)
<signal handler called>@0xfffffffd (Unknown Source:0)
rpmsg_send_offchannel_raw@0x00073cde (c:\ncs\v2.8.0\modules\lib\open-amp\open-amp\lib\rpmsg\rpmsg.c:131)
rpmsg_send@0x0002e01c (c:\ncs\v2.8.0\modules\lib\open-amp\open-amp\lib\include\openamp\rpmsg.h:204)
send@0x0002e01c (c:\ncs\v2.8.0\zephyr\subsys\ipc\ipc_service\backends\ipc_rpmsg_static_vrings.c:525)
hci_core_send_cmd@0x0004ef36 (c:\ncs\v2.8.0\zephyr\subsys\bluetooth\host\hci_core.c:3012)
process_pending_cmd@0x0004ef36 (c:\ncs\v2.8.0\zephyr\subsys\bluetooth\host\hci_core.c:4722)
bt_hci_cmd_send_sync@0x0004f016 (c:\ncs\v2.8.0\zephyr\subsys\bluetooth\host\hci_core.c:422)
common_init@0x0004f0d0 (c:\ncs\v2.8.0\zephyr\subsys\bluetooth\host\hci_core.c:3222)
hci_init@0x0004f0d0 (c:\ncs\v2.8.0\zephyr\subsys\bluetooth\host\hci_core.c:3974)
bt_init@0x0004f0d0 (c:\ncs\v2.8.0\zephyr\subsys\bluetooth\host\hci_core.c:4187)
_netble_start@0x0001396e (c:\work\dev\if-device-nrf53\cc1-med\src\net\netble.c:1338)
_app_event_handler@0x0001396e (c:\work\dev\if-device-nrf53\cc1-med\src\net\netble.c:1446)
event_processor_fn@0x000312b8 (c:\ncs\v2.8.0\nrf\subsys\app_event_manager\app_event_manager.c:190)
work_queue_main@0x00074de8 (c:\ncs\v2.8.0\zephyr\kernel\work.c:688)

I have tried with the prj.conf setup reduced to the minimum:

# BT/BLE config

CONFIG_BT=y

CONFIG_BT_PERIPHERAL=y

but still the same error.

This happens whether using the CPU-NET image from previous 2.6 build, from the current project's hci_ipc v2.8 build, or from the sample 'extended_adv/advertiser' built with v2.8.

hci_ipc.conf:

#
# Copyright (c) 2021 Nordic Semiconductor
#
# SPDX-License-Identifier: LicenseRef-Nordic-5-Clause
#

CONFIG_BT_CTLR_ADV_SET=2
CONFIG_BT_CTLR_ADV_EXT=y
CONFIG_BT_CTLR_DATA_LENGTH_MAX=251
CONFIG_BT_BUF_ACL_RX_SIZE=251
CONFIG_BT_BUF_ACL_TX_SIZE=251
CONFIG_BT_MAX_CONN=1

CONFIG_BT_EXT_ADV=y
CONFIG_BT_EXT_ADV_MAX_ADV_SET=2
CONFIG_BT_DATA_LEN_UPDATE=y
CONFIG_BT_USER_DATA_LEN_UPDATE=y
# added to try to get 2.8 working
CONFIG_IPC_SERVICE=y
CONFIG_MBOX=y
CONFIG_BT_HCI_RAW=y
CONFIG_BT_BUF_CMD_TX_COUNT=10

(I copied in the lines from the advertiser sample to see if that helped, but no...)

The advertiser sample runs OK with the hci_ipc CPU-NET build from its project, but gives:

Bluetooth init failed (err -5)

with either the v2.6 project build CPU-NET, or the v2.8 main project CPU-NET...

(but no memory fault in either case)

Any ideas on what I can try?

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Mon, 23 Dec 2024 15:20:52 GMT

I have posted this as a seperate case together with my 'fix', to check if the change I made is reasonable and reliable or not. Please see:

nrf5340 Anomaly 159 Workaround : not a workaround? Breaks QPSI Flash use on NCS 2.8.0

and give me an opinion.

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Mon, 23 Dec 2024 14:36:27 GMT

[quote userid="134465" url="~/f/nordic-q-a/117362/trouble-migrating-from-ncs-2-6-to-2-8/516111"]

now stuck with external flash access (as FAT32 filesystem) as this happens:

Fullscreen

1
2
[00:00:09.943,542] <err> qspi_nor: nRF5340 anomaly 159 conditions detected
[00:00:09.951,019] <err> qspi_nor: Set the CPU clock to 64 MHz before starting QSPI operation
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

[00:00:09.943,542] <err> qspi_nor: nRF5340 anomaly 159 conditions detected
[00:00:09.951,019] <err> qspi_nor: Set the CPU clock to 64 MHz before starting QSPI operation

and then the filesystem access (ELM) is broken.

This appears to be a 'fix' for anomly 159 (which I was not aware of experiencing). Why does this break FS access? (which stops the app loading the wifi config to test WPA connection!)

[/quote]

Digging into this, the log comes from zephyr/drivers/flasqh/nrf_qspi_nor.c (which uses modules/hal/nordic/nrfx/drivers/src/nrf_qpsi.c). The log is actually just when the code translates the underlying error of NRFX_ERROR_FORBIDDEN into a ECANCELED:

#if NRF53_ERRATA_159_ENABLE_WORKAROUND

case NRFX_ERROR_FORBIDDEN:

LOG_ERR("nRF5340 anomaly 159 conditions detected");

LOG_ERR("Set the CPU clock to 64 MHz before starting QSPI operation");

return -ECANCELED;

#endif

The code in nrf_qspiçnor.c deals with forcing the first condition for the workaround of the anomaly 159 (HCLK_192M divider should be 0), but not the second (CPU clock must be 64HMz ie divider set to 1). And this is what is detected in nrfs_qspi.c :

static bool .qspi_errata_159_conditions_check(void)
{
#if NRF_CLOCK_HAS_HFCLK192M && NRF53_ERRATA_159_ENABLE_WORKAROUND
    if ((nrf_clock_hfclk192m_div_get(NRF_CLOCK) != NRF_CLOCK_HFCLK_DIV_1) ||
        (nrf_clock_hfclk_div_get(NRF_CLOCK) != NRF_CLOCK_HFCLK_DIV_2))
    {
        return true;
    }
    else
#endif
    {
        return false;
    }
}

Given that the flash qspi access already does the job of changing the hclk192M divider before and after access, why doesn't it also change the CPU clock to avoid the issue? Instead it just logs that it detected it and thats why your app is stuffed...

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Mon, 23 Dec 2024 12:04:54 GMT

Update:

- updated app code to deal with I2S and PDM API breaking changes

- updated BLE code to deal with removal of bt_read_static_address()

The build now completes in child_image mode (sysbuild is for another day).

Subsequently testing the generated image:

- increased system heap size from 70kB to 100kB to deal with increased malloc demands (probably wpa_supplient)

- increased syswordq stack size from 4kB to 8kB to avoid stack overflow

- disabled BLE as this crashes when calling bt_enable(NULL).

 [00:01:32.781,463] <err> os: ***** BUS FAULT *****
[00:01:32.786,865] <err> os:   Precise data bus error
[00:01:32.792,602] <err> os:   BFAR Address: 0xb722ca38
[00:01:32.798,522] <err> os: r0/a1:  0xb722c9b4  r1/a2:  0x3fa470b8  r2/a3:  0x6a22f762
[00:01:32.807,189] <err> os: r3/a4:  0x0002e335 r12/ip:  0x01010101 r14/lr:  0x0002e35d
[00:01:32.815,826] <err> os:  xpsr:  0x21000200
[00:01:32.821,044] <err> os: Faulting instruction address (r15/pc): 0x00075c16
[00:01:32.828,948] <err> os: >>> ZEPHYR FATAL ERROR 25: Unknown error on CPU 0
[00:01:32.836,822] <err> os: Current thread: 0x20007ba0 (sysworkq)
[00:01:32.843,688] <err> os: Halting system

I cannot find what causes this yet - the debugger shows its in the hci_init(). This worked fine on 2.6. Removed any shared ram/HCI partition stuff but no difference...I have tried updating the CPU-NET image with the new build in case not compatible but no difference.... (hoping that this is not necessary as this will make DFU for my existing devices hard as hadn't got CPU-NET update to work yet with mcuboot...)

Any ideas?

- got wifi to run (but not sure if its working properly as can't config it) after changing the DTS setup

- now stuck with external flash access (as FAT32 filesystem) as this happens:

[00:00:09.943,542] <err> qspi_nor: nRF5340 anomaly 159 conditions detected
[00:00:09.951,019] <err> qspi_nor: Set the CPU clock to 64 MHz before starting QSPI operation

and then the filesystem access (ELM) is broken.

This appears to be a 'fix' for anomly 159 (which I was not aware of experiencing). Why does this break FS access? (which stops the app loading the wifi config to test WPA connection!)

So now I have 2 blocking runtime issues (bt_enable() crash, QPSI 'fix breaks file system).

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Fri, 20 Dec 2024 16:16:14 GMT

[quote userid="107683" url="~/f/nordic-q-a/117362/trouble-migrating-from-ncs-2-6-to-2-8/515973"]I'm not 100% sure, but this might be a child image/sysbuild rooted issue, i.e that CONFIG_DISK_DRIVER_FLASH should be present within mcuboot.conf as well as within prj.conf[/quote]

Well, currently I'm just building in child image mode (I know the sysbuild is breaking with a failure to find some partition stuff anyway).

And mcuboot seems to build ok for the CPUNET image, and also should not access the external flash as a 'disk' anyway.

So I'm pretty sure its because the DTC is not generating the DT_HAS_ZEPHYR_FLASH_DISK_ENABLED

I put in the DTS:

&mx25r64 {

partitions {

compatible = "fixed-partitions";

#address-cells = <1>;

#size-cells = <1>;

fatfs_partition: partition@0 {

label = "storage";

reg = <0x00000000 0x00600000>;

};

/ {

msc_disk0 {

compatible = "zephyr,flash-disk";

partition = <&fatfs_partition>;

disk-name = "NAND";

cache-size = <4096>;

};

Which appears to have fixed it! (to be tested once I have an actually running image)

So now... the build breaks because

1/ the nrfx I2S API has been updated with breaking changes (to v3.7.0?)

2/ The nrfx PDM API has been updated with breaking changes...

[quote userid="107683" url="~/f/nordic-q-a/117362/trouble-migrating-from-ncs-2-6-to-2-8/515973"]As mentioned I will be out of office for a while now, and I wish you good luck if you'll keep working until I'm back. I will pick up the case(s) on the 6th of January.[/quote]

Well, I hope the entire support isn't just you? Some of us have projects to deliver, and so far this migration has cost me a full week and its not done yet...

RE: Trouble migrating from NCS 2.6 to 2.8

AHaug — Fri, 20 Dec 2024 15:15:47 GMT

Just saw your latest reply, so reposting.

[quote user="BrianW"]

It seems this is due to having this in prj.conf:

CONFIG_NRF_WIFI_PATCHES_BUILTIN=y

[/quote]

Ah, I'll use this sample as a comparison basis myself then, since it might be more relevant to the audio sample.

One thing that might be the reason for the errors you saw is if you're using the regular build or "build with pristine" actions in the extension. Sometimes these configure or build with artifacts from your previous build remaining (can't quite explain it, but the short explanation is "pristine" is not the same as "delete the previous build and build fresh with new configurations"). As a sanity check for those types of error I typically remove the build folder before building the project.

[quote user="BrianW"]CONFIG_NRF_WIFI_PATCHES_BUILTIN=y[/quote]

I'm not 100% sure, but this might be a child image/sysbuild rooted issue, i.e that CONFIG_DISK_DRIVER_FLASH should be present within mcuboot.conf as well as within prj.conf

It could also be that something is missing w.r.t how the flash device is listed https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/services/storage/disk/access.html (this is just throwing a link I've seen elsewhere in somewhat similar error messages at the problem and I've not verified that it's working. Hopefully it might be something else than a wild guess, but let me know if it was helpful)

[quote user="BrianW"]We'll see if any of this actually works once I get the build to fully complete![/quote]

Glad to hear that atleast those two warnings were resolved!

[quote user="BrianW"]CONFIG_NRF_WIFI_PATCHES_BUILTIN=y[/quote]

I can't quite see why the Kconfig would cause configuring issues, but if I should guess it might be due to it not knowing where to place the files in the memory map. This config is not present in wifi/sta by defualt? https://github.com/nrfconnect/sdk-nrf/blob/main/samples/wifi/sta/prj.conf

As mentioned I will be out of office for a while now, and I wish you good luck if you'll keep working until I'm back. I will pick up the case(s) on the 6th of January.

Kind regards,
Andreas

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Fri, 20 Dec 2024 15:06:00 GMT

So, wrt the build failing at the CMake config step, which is due to this error (in build/cc1-med/CMakeFiles/CMakeError.log):

[quote userid="134465" url="~/f/nordic-q-a/117362/trouble-migrating-from-ncs-2-6-to-2-8/515814"]

Its failing to link a cmake tool?

c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.exe: c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/lib\libc.a(lib_a-exit.o): in function `exit':

exit.c:(.text.exit+0x34): undefined reference to `_exit'

collect2.exe: error: ld returned 1 exit status

[/quote]

It seems this is due to having this in prj.conf:

CONFIG_NRF_WIFI_PATCHES_BUILTIN=y

WTF is pretty much all I can say.

This is very frustrating to find this kind of issue, which has wasted 2 days of my time to hunt down...

Lets see if any of the wifi stuff works when it finally builds...

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Fri, 20 Dec 2024 13:55:46 GMT

[quote userid="107683" url="~/f/nordic-q-a/117362/trouble-migrating-from-ncs-2-6-to-2-8/515896"]

BrianW said:
2/ a more serious looking warning, but related (as far as I can tell) to dts definitions in the SDK

This warning seems to be interesting as it is not present in the default audio application configuration (and in neither of the other samples I've built to test).

[/quote]

This was down to having the gpio definition for the I2S amp's 'enable' input (/SDMODE on the MAX device)) inside the i2s0 node.Once i moved it out to be a seperate node

i2s_sdmode: sdmode {

compatible = "nordic,gpio-pins";

gpios = <&gpio1 14 GPIO_ACTIVE_HIGH>; // P1.14

};

then the warning went away....

[quote userid="107683" url="~/f/nordic-q-a/117362/trouble-migrating-from-ncs-2-6-to-2-8/515896"]

BrianW said:
3/ enabling the PDM driver

Looks to me that this has changed from _PDM to _PDM0 in 2.8.0: https://docs.nordicsemi.com/bundle/ncs-2.8.0/page/kconfig/index.html#CONFIG_NRFX_PDM0

[/quote]

Ok, the error goes away with this name change.

We'll see if any of this actually works once I get the build to fully complete!

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Fri, 20 Dec 2024 13:25:46 GMT

thanks for the info above. Its true the jump 2.6->2.7/2.8 is very hard, especially due to the zephyr updates, and lacking a set of detailled release notes that show exactly what is been deleted/updated/added doesn't help.

My strategy since yesterday is that I have started with the wifi/sta sample prj.conf (which doesn't build completely but gets past the config step to actually compile source files), and worked forwards from that... somehow this has resolved the CMake ld error, but I have no idea why.

I hope to get the non-sysbuild working first as ou suggest, but I'm still stuck with a couple of issues

1 points quickly (I hope)

USB FAT32 flash disk operation

warning: DISK_DRIVER_FLASH (defined at drivers/disk/Kconfig.flash:4) was assigned the value 'y' but
got the value 'n'. Check these unsatisfied dependencies: DT_HAS_ZEPHYR_FLASH_DISK_ENABLED (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
DISK_DRIVER_FLASH in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

which leads to:

CMake Warning at C:/ncs/v2.8.0/zephyr/CMakeLists.txt:952 (message):
No SOURCES given to Zephyr library: drivers__disk

Excluding target from build.

What is required to satisfy DT_HAS_ZEPHYR_FLASH_DISK_ENABLED ? (again, this is a change from 2.6)? I have tried the usb disk example from 2.8, but can't work out what the key difference is between the dts files?

thanx

RE: Trouble migrating from NCS 2.6 to 2.8

AHaug — Fri, 20 Dec 2024 11:54:53 GMT

Two more notes:

See https://github.com/nrfconnect/sdk-zephyr/blob/7f8d857bf1f57b07e832d52263beaa23c91fef24/boards/nordic/nrf5340_audio_dk/nrf5340_audio_dk_nrf5340_cpuapp_common.dtsi#L122 w.r.t i2s0 device and how it is set up for the audio dk and https://stackoverflow.com/questions/21871362/how-to-put-comments-in-device-tree-source-files#21892052 w.r.t commenting out lines in dts (which is present within our dts files. Interesting...)

Edit: Never mind the commenting, it is a syntax in dts: https://www.kernel.org/doc/Documentation/devicetree/booting-without-of.txt

Kind regards,
Andreas

RE: Trouble migrating from NCS 2.6 to 2.8

AHaug — Fri, 20 Dec 2024 11:16:39 GMT

Hi,

HWM2

[quote user="BrianW"]I can ignore these, yes?[/quote]

I wouldn't recommend you to ignore any compilation warnings. The warnings you mention are labeled as deprecated.

[quote user="BrianW"]2/ a more serious looking warning, but related (as far as I can tell) to dts definitions in the SDK[/quote]

This warning seems to be interesting as it is not present in the default audio application configuration (and in neither of the other samples I've built to test). Could you add your modification to the i2s0 device within for instance https://github.com/nrfconnect/sdk-nrf/tree/main/applications/nrf5340_audio or any of the other audio samples and see if you're able to force the warning w.r.t address and size from there?

[quote user="BrianW"]3/ enabling the PDM driver [/quote]

Looks to me that this has changed from _PDM to _PDM0 in 2.8.0: https://docs.nordicsemi.com/bundle/ncs-2.8.0/page/kconfig/index.html#CONFIG_NRFX_PDM0

Sysbuild:

I see you've addressed some of the sysbuild questions/uncertainties in the reply following the longer set of sysbuild questions so I'll start there:

[quote user="BrianW"]I'm thinking that with sysbuild the 'main app' prj.conf is NOT merged in with the mcuboot one, so this has to stand on its own?[/quote]

Yes, this is correct. You still need to have a prj.conf for your app. Sysbuild only handles companion images

[quote user="BrianW"]Ok, I see the example has the file called mcuboot.conf, however if I name it that then I get:[/quote]

You can see the structure of sysbuild companion images here as well: https://github.com/nrfconnect/sdk-nrf/tree/main/applications/nrf5340_audio/sysbuild. I'm not sure if my explanation of the structure caused any misunderstandings.

It is unfortunately too many changes simultaneously that causes the build crashes with no useful information you listed in your replies from yesterday.

Here's a breakdown of what I would've done if I were to migrate from 2.6.1 to 2.8.0:

Start with the audio app and montior changes from 2.6.1 to 2.8.0. Pay attention to changes from child_image/ to sysbuild/ as well as the addition to sysbuild.conf together with prj.conf
Compare the board files within said project and the board files for the 5340 in 2.6.1 and 2.8.0. These are the changes w.r.t hwm1 and hwm2 in addition to the migration note for this https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_hwmv2.html
After you've migrated to hwmv2, try to build with "--no-sysbuild". This should allow you to build with child and parent images. This is still supported in 2.8.0, but will not be in 2.9.0.
Resolve any configuration errors and make it compile without sysbuild
Start with migration from child/parent images to sysbuild. Make note of the changes in item 1 and the two links you sent in the start

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_guide_2.8.html

Unfortunately there will be some downtime in the coming weeks due to holidays here in Norway, so activity will be slow on devzone until early Janaury. I'm sorry for not being able to help you pinpoint the migration issues before now but I strongly believe that if you methodically follow the 5 steps I listed you will succeed.

Kind regards,
Andreas

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Thu, 19 Dec 2024 16:54:16 GMT

The full build output:

C:\work\dev\if-device-nrf53>west build --build-dir cc1-med/build cc1-med --board cc2v1/nrf5340/cpuapp --pristine -DBOARD_ROOT=/work/dev/if-device-nrf53
-- west build: making build dir C:\work\dev\if-device-nrf53\cc1-med\build pristine
-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: C:/ncs/toolchains/2d382dcd92/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.8.0/zephyr/.cache
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: cc2v1, qualifiers: nrf5340/cpuapp
Parsing C:/work/dev/if-device-nrf53/cc1-med/Kconfig.sysbuild
Loaded configuration 'C:/work/dev/if-device-nrf53/cc1-med/build/_sysbuild/empty.conf'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/sysbuild.conf'
Configuration saved to 'C:/work/dev/if-device-nrf53/cc1-med/build/zephyr/.config'
Kconfig header saved to 'C:/work/dev/if-device-nrf53/cc1-med/build/_sysbuild/autoconf.h'
--
   *****************************
   * Running CMake for mcuboot *
   *****************************

Loading Zephyr default modules (Zephyr base).
-- Application: C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr
-- CMake version: 3.21.0
-- Using NCS Toolchain 2.8.20241106.194216054162 for building. (C:/ncs/toolchains/2d382dcd92/cmake)
-- Found Python3: C:/ncs/toolchains/2d382dcd92/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.8.0/zephyr/.cache
-- Zephyr version: 3.7.99 (C:/ncs/v2.8.0/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: cc2v1, qualifiers: nrf5340/cpuapp
-- Found host-tools: zephyr 0.16.8 (C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.8 (C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/2d382dcd92/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")

-- Found BOARD.dts: C:/work/dev/if-device-nrf53/boards/infrafon/cc2v1/cc2v1_nrf5340_cpuapp.dts
'label' is marked as deprecated in 'properties:' in C:/ncs/v2.8.0/zephyr/dts/bindings\audio\nordic,nrf-pdm.yaml for node /soc/peripheral@50000000/pdm@26000.
'label' is marked as deprecated in 'properties:' in C:/ncs/v2.8.0/zephyr/dts/bindings\i2s\nordic,nrf-i2s.yaml for node /soc/peripheral@50000000/i2s@28000.
-- Generated zephyr.dts: C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/dts.cmake
CMake Warning at C:/ncs/v2.8.0/zephyr/cmake/modules/dts.cmake:389 (message):
  dtc raised one or more warnings:

  <stdout>: Warning (avoid_unnecessary_addr_size):
  /soc/peripheral@50000000/i2s@28000: unnecessary #address-cells/#size-cells
  without "ranges" or child "reg" property

Call Stack (most recent call first):
  C:/ncs/v2.8.0/zephyr/cmake/modules/zephyr_default.cmake:133 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:12 (find_package)


Parsing C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr/Kconfig
Loaded configuration 'C:/work/dev/if-device-nrf53/boards/infrafon/cc2v1/cc2v1_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/sysbuild/mcuboot/prj.conf'
Merged configuration 'C:/ncs/v2.8.0/nrf/subsys/partition_manager/ext_flash_mcuboot_secondary.conf'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/.config.sysbuild'
Configuration saved to 'C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/.config'
Kconfig header saved to 'C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/include/generated/zephyr/autoconf.h'
-- Found GnuLd: c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
-- Setting build type to 'MinSizeRel' as none was specified.
MCUBoot bootloader key file: /work/dev/if-device-nrf53/keys/bootloader_priv-ecdsa256.pem
-- Configuring done
-- Generating done
-- Build files have been written to: C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot
--
   *****************************
   * Running CMake for hci_ipc *
   *****************************

Loading Zephyr default modules (Zephyr base).
-- Application: C:/ncs/v2.8.0/zephyr/samples/bluetooth/hci_ipc
-- CMake version: 3.21.0
-- Using NCS Toolchain 2.8.20241106.194216054162 for building. (C:/ncs/toolchains/2d382dcd92/cmake)
-- Found Python3: C:/ncs/toolchains/2d382dcd92/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.8.0/zephyr/.cache
-- Zephyr version: 3.7.99 (C:/ncs/v2.8.0/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: cc2v1, qualifiers: nrf5340/cpunet
-- Found host-tools: zephyr 0.16.8 (C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.8 (C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/2d382dcd92/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")

-- Found BOARD.dts: C:/work/dev/if-device-nrf53/boards/infrafon/cc2v1/cc2v1_nrf5340_cpunet.dts
-- Generated zephyr.dts: C:/work/dev/if-device-nrf53/cc1-med/build/hci_ipc/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/work/dev/if-device-nrf53/cc1-med/build/hci_ipc/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: C:/work/dev/if-device-nrf53/cc1-med/build/hci_ipc/zephyr/dts.cmake
Parsing C:/ncs/v2.8.0/zephyr/Kconfig
Loaded configuration 'C:/work/dev/if-device-nrf53/boards/infrafon/cc2v1/cc2v1_nrf5340_cpunet_defconfig'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/sysbuild/hci_ipc/prj.conf'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/build/hci_ipc/zephyr/.config.sysbuild'
Configuration saved to 'C:/work/dev/if-device-nrf53/cc1-med/build/hci_ipc/zephyr/.config'
Kconfig header saved to 'C:/work/dev/if-device-nrf53/cc1-med/build/hci_ipc/zephyr/include/generated/zephyr/autoconf.h'
-- Found GnuLd: c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
-- libmetal version: 1.6.0 (C:/ncs/v2.8.0/zephyr/samples/bluetooth/hci_ipc)
-- Build type:
-- Host:    Windows/AMD64
-- Target:  Generic/arm
-- Machine: arm
-- Looking for include file stdatomic.h
-- Looking for include file stdatomic.h - found
-- open-amp version: 1.6.1 (C:/ncs/v2.8.0/modules/lib/open-amp/open-amp)
-- Host:    Windows/AMD64
-- Target:  Generic/arm
-- Machine: arm
-- C_FLAGS :  -Wall -Wextra
-- Looking for include file fcntl.h
-- Looking for include file fcntl.h - found
-- Setting build type to 'MinSizeRel' as none was specified.
-- Configuring done
-- Generating done
-- Build files have been written to: C:/work/dev/if-device-nrf53/cc1-med/build/hci_ipc
--
   *****************************
   * Running CMake for cc1-med *
   *****************************

Loading Zephyr default modules (Zephyr base).
-- Application: C:/work/dev/if-device-nrf53/cc1-med
-- CMake version: 3.21.0
-- Using NCS Toolchain 2.8.20241106.194216054162 for building. (C:/ncs/toolchains/2d382dcd92/cmake)
-- Found Python3: C:/ncs/toolchains/2d382dcd92/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.8.0/zephyr/.cache
-- Zephyr version: 3.7.99 (C:/ncs/v2.8.0/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: cc2v1, qualifiers: nrf5340/cpuapp
-- Found host-tools: zephyr 0.16.8 (C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.8 (C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/2d382dcd92/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")

-- Found BOARD.dts: C:/work/dev/if-device-nrf53/boards/infrafon/cc2v1/cc2v1_nrf5340_cpuapp.dts
'label' is marked as deprecated in 'properties:' in C:/ncs/v2.8.0/zephyr/dts/bindings\audio\nordic,nrf-pdm.yaml for node /soc/peripheral@50000000/pdm@26000.
'label' is marked as deprecated in 'properties:' in C:/ncs/v2.8.0/zephyr/dts/bindings\i2s\nordic,nrf-i2s.yaml for node /soc/peripheral@50000000/i2s@28000.
-- Generated zephyr.dts: C:/work/dev/if-device-nrf53/cc1-med/build/cc1-med/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/work/dev/if-device-nrf53/cc1-med/build/cc1-med/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: C:/work/dev/if-device-nrf53/cc1-med/build/cc1-med/zephyr/dts.cmake
CMake Warning at C:/ncs/v2.8.0/zephyr/cmake/modules/dts.cmake:389 (message):
  dtc raised one or more warnings:

  <stdout>: Warning (avoid_unnecessary_addr_size):
  /soc/peripheral@50000000/i2s@28000: unnecessary #address-cells/#size-cells
  without "ranges" or child "reg" property

Call Stack (most recent call first):
  C:/ncs/v2.8.0/zephyr/cmake/modules/zephyr_default.cmake:133 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:8 (find_package)



warning: NRF_SECURITY (defined at C:/ncs/v2.8.0/nrf\subsys\nrf_security/Kconfig:32) was assigned the
value 'n' but got the value 'y'. See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NRF_SECURITY and/or look up NRF_SECURITY in
the menuconfig/guiconfig interface. The Application Development Primer, Setting Configuration
Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful too.


warning: DISK_DRIVER_FLASH (defined at drivers/disk/Kconfig.flash:4) was assigned the value 'y' but
got the value 'n'. Check these unsatisfied dependencies: DT_HAS_ZEPHYR_FLASH_DISK_ENABLED (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_DISK_DRIVER_FLASH and/or look up
DISK_DRIVER_FLASH in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.


warning: Deprecated symbol MBEDTLS_LEGACY_CRYPTO_C is enabled.


warning: Experimental symbol WIFI_READY_LIB is enabled.


warning: Experimental symbol WIFI_NM_WPA_SUPPLICANT is enabled.


warning: Experimental symbol WIFI_NM_WPA_SUPPLICANT is enabled.


warning: Experimental symbol NRF_WIFI_RPU_RECOVERY is enabled.


warning: Experimental symbol POSIX_ASYNCHRONOUS_IO is enabled.


warning: Experimental symbol POSIX_DEVICE_IO is enabled.


warning: Experimental symbol POSIX_FD_MGMT is enabled.


warning: Experimental symbol POSIX_MULTI_PROCESS is enabled.


warning: Experimental symbol POSIX_REALTIME_SIGNALS is enabled.


warning: Experimental symbol POSIX_SIGNALS is enabled.


warning: Experimental symbol NET_SOCKETS_SERVICE is enabled.

Parsing C:/ncs/v2.8.0/zephyr/Kconfig
Loaded configuration 'C:/work/dev/if-device-nrf53/boards/infrafon/cc2v1/cc2v1_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/prj.conf'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/build/cc1-med/zephyr/.config.sysbuild'
Configuration saved to 'C:/work/dev/if-device-nrf53/cc1-med/build/cc1-med/zephyr/.config'
Kconfig header saved to 'C:/work/dev/if-device-nrf53/cc1-med/build/cc1-med/zephyr/include/generated/zephyr/autoconf.h'
-- Found GnuLd: c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
=========== Generating psa_crypto_config ===============
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_SPM: False
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_C: True
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER: False
Backup: CONFIG_MBEDTLS_PLATFORM_SETUP_TEARDOWN_ALT: False
Backup: CONFIG_MBEDTLS_THREADING: False
Backup: CONFIG_MBEDTLS_THREADING_ALT: True
=========== Checkpoint: backup ===============
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_SPM: False
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_C: True
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER: False
Restore: CONFIG_MBEDTLS_PLATFORM_SETUP_TEARDOWN_ALT: False
Restore: CONFIG_MBEDTLS_THREADING: False
Restore: CONFIG_MBEDTLS_THREADING_ALT: True
=========== End psa_crypto_config ===============
=========== Generating psa_crypto_library_config ===============
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_C: True
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER: False
Backup: CONFIG_MBEDTLS_PSA_CRYPTO_SPM: False
Backup: CONFIG_MBEDTLS_USE_PSA_CRYPTO: False
Backup: CONFIG_MBEDTLS_PLATFORM_PRINTF_ALT: False
Backup: CONFIG_MBEDTLS_THREADING: False
Backup: CONFIG_MBEDTLS_THREADING_ALT: True
=========== Checkpoint: backup ===============
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_C: True
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_KEY_ID_ENCODES_OWNER: False
Restore: CONFIG_MBEDTLS_PSA_CRYPTO_SPM: False
Restore: CONFIG_MBEDTLS_USE_PSA_CRYPTO: False
Restore: CONFIG_MBEDTLS_PLATFORM_PRINTF_ALT: False
Restore: CONFIG_MBEDTLS_THREADING: False
Restore: CONFIG_MBEDTLS_THREADING_ALT: True
=========== End psa_crypto_library_config ===============
CMake Error at C:/ncs/v2.8.0/zephyr/cmake/modules/extensions.cmake:695 (add_custom_target):
  add_custom_target cannot create target
  "gen_nrf70_bin_inc_77552e44891130fb8290820867cdfb8b" because another target
  with the same name already exists.  The existing target is a custom target
  created in source directory "C:/ncs/v2.8.0/zephyr/drivers/wifi/nrfwifi".
  See documentation for policy CMP0002 for more details.
Call Stack (most recent call first):
  C:/ncs/v2.8.0/nrf/subsys/net/lib/nrf70_fw_ext/CMakeLists.txt:45 (generate_inc_file_for_target)


-- libmetal version: 1.6.0 (C:/work/dev/if-device-nrf53/cc1-med)
-- Build type:
-- Host:    Windows/AMD64
-- Target:  Generic/arm
-- Machine: arm
-- Looking for include file stdatomic.h
-- Looking for include file stdatomic.h - found
-- open-amp version: 1.6.1 (C:/ncs/v2.8.0/modules/lib/open-amp/open-amp)
-- Host:    Windows/AMD64
-- Target:  Generic/arm
-- Machine: arm
-- C_FLAGS :  -Wall -Wextra
-- Looking for include file fcntl.h
-- Looking for include file fcntl.h - found
-- Setting build type to 'MinSizeRel' as none was specified.
CMake Warning at C:/ncs/v2.8.0/zephyr/CMakeLists.txt:952 (message):
  No SOURCES given to Zephyr library: drivers__disk

  Excluding target from build.


CMake Warning at C:/ncs/v2.8.0/zephyr/CMakeLists.txt:952 (message):
  No SOURCES given to Zephyr library: drivers__pwm

  Excluding target from build.


-- Including signing script: C:/ncs/v2.8.0/nrf/cmake/sysbuild/image_signing.cmake
CMake Warning at C:/ncs/v2.8.0/zephyr/CMakeLists.txt:2134 (message):
  __ASSERT() statements are globally ENABLED


-- Configuring incomplete, errors occurred!
See also "C:/work/dev/if-device-nrf53/cc1-med/build/cc1-med/CMakeFiles/CMakeOutput.log".
See also "C:/work/dev/if-device-nrf53/cc1-med/build/cc1-med/CMakeFiles/CMakeError.log".
CMake Error at cmake/modules/sysbuild_extensions.cmake:514 (message):
  CMake configure failed for Zephyr project: cc1-med

  Location: C:/work/dev/if-device-nrf53/cc1-med
Call Stack (most recent call first):
  cmake/modules/sysbuild_images.cmake:20 (ExternalZephyrProject_Cmake)
  cmake/modules/sysbuild_default.cmake:20 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  C:/ncs/v2.8.0/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)


-- Configuring incomplete, errors occurred!
See also "C:/work/dev/if-device-nrf53/cc1-med/build/CMakeFiles/CMakeOutput.log".
←[91mFATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\2d382dcd92\opt\bin\cmake.EXE' -DWEST_PYTHON=C:/ncs/toolchains/2d382dcd92/opt/bin/python.exe '-BC:\work\dev\if-device-nrf53\cc1-med\build' -GNinja -DBOARD=cc2v1/nrf5340/cpuapp -DBOARD_ROOT=/work/dev/if-device-nrf53 '-SC:\ncs\v2.8.0\zephyr\share\sysbuild' '-DAPP_DIR:PATH=C:\work\dev\if-device-nrf53\cc1-med'
←[0m

The CMakeError.log:

Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler: C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe 
Build flags: 
Id flags:  

The output was:
1
c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.exe: c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/lib\libc.a(lib_a-exit.o): in function `exit':
exit.c:(.text.exit+0x34): undefined reference to `_exit'
collect2.exe: error: ld returned 1 exit status


Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
Compiler: C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe 
Build flags: 
Id flags:  

The output was:
1
c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.exe: c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/lib\libc.a(lib_a-exit.o): in function `exit':
exit.c:(.text.exit+0x34): undefined reference to `_exit'
collect2.exe: error: ld returned 1 exit status

Its failing to link a cmake tool?

exit.c:(.text.exit+0x34): undefined reference to `_exit'

collect2.exe: error: ld returned 1 exit status

The only other error I see is this:

CMake Error at C:/ncs/v2.8.0/zephyr/cmake/modules/extensions.cmake:695 (add_custom_target):
add_custom_target cannot create target
"gen_nrf70_bin_inc_77552e44891130fb8290820867cdfb8b" because another target
with the same name already exists. The existing target is a custom target
created in source directory "C:/ncs/v2.8.0/zephyr/drivers/wifi/nrfwifi".
See documentation for policy CMP0002 for more details.
Call Stack (most recent call first):
C:/ncs/v2.8.0/nrf/subsys/net/lib/nrf70_fw_ext/CMakeLists.txt:45 (generate_inc_file_for_target)

but this seems to be linked to the nrf70 wifi stuff? Maybe no link to the cmake error?

I also see this:

warning: DISK_DRIVER_FLASH (defined at drivers/disk/Kconfig.flash:4) was assigned the value 'y' but
got the value 'n'. Check these unsatisfied dependencies: DT_HAS_ZEPHYR_FLASH_DISK_ENABLED (=n).

which makes me wonder why it can't find the flash disk definition in my DTS? What exactly does the DT_HAS_... macro look for? I have defined

zephyr,flash-disk = &mx25r64;

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Thu, 19 Dec 2024 16:43:23 GMT

after finding the fix for the CONFIG_FLASH for the sysbuild, it also stops at this step. Can you explain why, given it seems to be using all the elements from the correct toolchain?

Without a fix for this I am completely blocked.

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Thu, 19 Dec 2024 16:24:52 GMT

[quote userid="134465" url="~/f/nordic-q-a/117362/trouble-migrating-from-ncs-2-6-to-2-8/515567"]It seems it doesn't like something about the flash driver? But this worked fine in 2.6... and also I don't get this error if using child_images build system...[/quote]

After diving into a maze of nasty twisty little KConfig dependancies, it seems this is because I need CONFIG_FLASH=y in the sysbuild/mcuboot/prj.conf. Previously this was configured just in the main prj.conf for the project.

I'm thinking that with sysbuild the 'main app' prj.conf is NOT merged in with the mcuboot one, so this has to stand on its own?

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Wed, 18 Dec 2024 17:25:46 GMT

And, as I said, with the old childimage system it gets further thru the config process (does the CPUNET, and mcuboot, then gets (I assume) to app), and it stops with this:

-- Target:  Generic/arm
-- Machine: arm
-- Looking for include file stdatomic.h
-- Looking for include file stdatomic.h - found
-- open-amp version: 1.6.1 (C:/ncs/v2.8.0/modules/lib/open-amp/open-amp)
-- Host:    Windows/AMD64
-- Target:  Generic/arm
-- Machine: arm
-- C_FLAGS :  -Wall -Wextra
-- Looking for include file fcntl.h
-- Looking for include file fcntl.h - found
-- Setting build type to 'MinSizeRel' as none was specified.
CMake Warning at C:/ncs/v2.8.0/zephyr/CMakeLists.txt:952 (message):
  No SOURCES given to Zephyr library: drivers__disk

  Excluding target from build.


CMake Warning at C:/ncs/v2.8.0/zephyr/CMakeLists.txt:952 (message):
  No SOURCES given to Zephyr library: drivers__pwm

  Excluding target from build.


CMake Warning at C:/ncs/v2.8.0/zephyr/CMakeLists.txt:2134 (message):
  __ASSERT() statements are globally ENABLED


CMake Deprecation Warning at C:/ncs/v2.8.0/nrf/cmake/partition_manager.cmake:32 (message):


            ---------------------------------------------------------------------
            --- WARNING: Child and parent image functionality is deprecated   ---
            --- and should be replaced with sysbuild. Child and parent image  ---
            --- support remains only to allow existing customer applications  ---
            --- to build and allow porting to sysbuild, it is no longer       ---
            --- receiving updates or new features and it will not be possible ---
            --- to build using child/parent image at all in nRF Connect SDK   ---
            --- version 2.9 onwards.                                          ---
            ---------------------------------------------------------------------
Call Stack (most recent call first):
  C:/ncs/v2.8.0/zephyr/cmake/modules/kernel.cmake:255 (include)
  C:/ncs/v2.8.0/zephyr/cmake/modules/zephyr_default.cmake:142 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:8 (find_package)


-- Found partition manager static configuration: C:/work/dev/if-device-nrf53/cc1-med/pm_static.yml
Partition 'mcuboot' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_pad' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_primary_app' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_primary' is not included in the dynamic resolving since it is statically defined.
Partition 'nvs_storage' is not included in the dynamic resolving since it is statically defined.
Partition 'mcuboot_secondary' is not included in the dynamic resolving since it is statically defined.
Partition 'pcd_sram' is not included in the dynamic resolving since it is statically defined.
Partition 'rpmsg_nrf53_sram' is not included in the dynamic resolving since it is statically defined.
-- Configuring incomplete, errors occurred!
See also "C:/work/dev/if-device-nrf53/cc1-med/build/CMakeFiles/CMakeOutput.log".
See also "C:/work/dev/if-device-nrf53/cc1-med/build/CMakeFiles/CMakeError.log".
←[91mFATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\2d382dcd92\opt\bin\cmake.EXE' -DWEST_PYTHON=C:/ncs/toolchains/2d382dcd92/opt/bin/python.exe '-BC:\work\dev\if-device-nrf53\cc1-med\build' -GNinja -DBOARD=cc2v1/nrf5340/cpuapp -DBOARD_ROOT=/work/dev/if-device-nrf53 '-SC:\work\dev\if-device-nrf53\cc1-med'
←[0m

and in ther cc1-med/build/CMakeFiles/CMakeError.log it says:

Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler: C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe 
Build flags: 
Id flags:  

The output was:
1
c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.exe: c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/lib\libc.a(lib_a-exit.o): in function `exit':
exit.c:(.text.exit+0x34): undefined reference to `_exit'
collect2.exe: error: ld returned 1 exit status


Compiling the CXX compiler identification source file "CMakeCXXCompilerId.cpp" failed.
Compiler: C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe 
Build flags: 
Id flags:  

The output was:
1
c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.exe: c:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/lib\libc.a(lib_a-exit.o): in function `exit':
exit.c:(.text.exit+0x34): undefined reference to `_exit'
collect2.exe: error: ld returned 1 exit status

I don't understand?

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Wed, 18 Dec 2024 16:46:56 GMT

Now for sysbuild with mcuboot. btw, if I build without sysbuild (build.sysbuild=False), then the KConfig part gives some warnings buit gets further. With sysbuild, it breaks at the KConfig checking stage.

[quote userid="107683" url="~/f/nordic-q-a/117362/trouble-migrating-from-ncs-2-6-to-2-8/515543"]What you previously had within <your_project>/child_images/mcuboot.conf is now present within <your_project>/sysbuild/mcuboot.conf [/quote]

Ok, I see the example has the file called mcuboot.conf, however if I name it that then I get:

CMake Error at C:/ncs/v2.8.0/zephyr/cmake/modules/extensions.cmake:2861 (message):
  No prj.conf file(s) was found in the
  C:/work/dev/if-device-nrf53/cc1-med/sysbuild/mcuboot folder(s), please read
  the Zephyr documentation on application development.

So I will name it prj.conf.

[quote userid="107683" url="~/f/nordic-q-a/117362/trouble-migrating-from-ncs-2-6-to-2-8/515543"]Do you have SB_CONFIG_BOOTLOADER_MCUBOOT=y within sysbuild.conf or is it just within sysbuild/mcuboot.conf?[/quote]

In sysbuild.conf :

# MCU boot config now handled by sysbuild
SB_CONFIG_BOOTLOADER_MCUBOOT=y
#SB_CONFIG_MCUBOOT_BOOTLOADER_MODE_SWAP_WITHOUT_SCRATCH=y
#SB_CONFIG_MCUBOOT_GENERATE_UNSIGNED_IMAGE=y

SB_CONFIG_NETCORE_HCI_IPC=y
#SB_CONFIG_NETCORE_APP_UPDATE=y
SB_CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y
SB_CONFIG_BOOT_SIGNATURE_KEY_FILE="/work/dev/if-device-nrf53/keys/bootloader_priv-ecdsa256.pem"
#CONFIG_MCUBOOT_SIGNATURE_KEY_FILE="/work/dev/if-device-nrf53/keys/bootloader_priv-ecdsa256.pem"

# nrf7002 firmware handled by sysbuild
SB_CONFIG_WIFI_NRF70=y
SB_CONFIG_WIFI_NRF70_SYSTEM_MODE=y

# todo get dfu packaging to work
#SB_CONFIG_WIFI_PATCHES_EXT_FLASH_XIP=y

# build of dfu packages
#SB_CONFIG_SUPPORT_NETCORE=y
#SB_CONFIG_SECURE_BOOT=y
#SB_CONFIG_SECURE_BOOT_NETCORE=y

#SB_CONFIG_DFU_MULTI_IMAGE_PACKAGE_BUILD=y
#SB_CONFIG_DFU_MULTI_IMAGE_PACKAGE_APP=y
#SB_CONFIG_DFU_MULTI_IMAGE_PACKAGE_NET=y
#SB_CONFIG_DFU_MULTI_IMAGE_PACKAGE_WIFI_FW_PATCH=y

#SB_CONFIG_DFU_ZIP=y
#SB_CONFIG_DFU_ZIP_APP=y
#SB_CONFIG_DFU_ZIP_NET=y
#SB_CONFIG_DFU_ZIP_WIFI_FW_PATCH=y

# put slot2 in external flash
SB_CONFIG_PARTITION_MANAGER=y
SB_CONFIG_PM_MCUBOOT_PAD=0x200
SB_CONFIG_PM_EXTERNAL_FLASH_MCUBOOT_SECONDARY=y

And my sysbuild/mcuboot/prj.conf:

# mcuboot serial recovery makes image too big for flash space... TODO find more space
CONFIG_MCUBOOT_SERIAL=n
CONFIG_BOOT_SERIAL_CDC_ACM=n
# Enable wait for DFU functionality at boot? 
CONFIG_BOOT_SERIAL_WAIT_FOR_DFU=n
#CONFIG_BOOT_SERIAL_WAIT_FOR_DFU_TIMEOUT=5000

# DFU directly as special USB device? - nO, this required winusb zadig driver which then broke usb FS mounting...
CONFIG_BOOT_USB_DFU_WAIT=n
#CONFIG_BOOT_USB_DFU_WAIT_DELAY_MS=5000
#CONFIG_USB_DEVICE_STACK=y
#CONFIG_USB_DEVICE_PRODUCT="Infrafon CC2-WDD"
# USB VID is MCS electronics, who sell individual PIDs. 0x138F is for CC2 purchases 25/08/2024
#CONFIG_USB_DEVICE_VID=0x16D0
#CONFIG_USB_DEVICE_PID=0x138F
#CONFIG_USB_DRIVER_LOG_LEVEL_ERR=y

CONFIG_BOOT_MAX_IMG_SECTORS=256
CONFIG_FPROTECT=n

# now handled by sysbuild
#CONFIG_BOOTLOADER_MCUBOOT=y
#CONFIG_BOOT_SIGNATURE_TYPE_ECDSA_P256=y
#CONFIG_BOOT_SIGNATURE_KEY_FILE="/work/dev/if-device-nrf53/keys/bootloader_priv-ecdsa256.pem"
#CONFIG_MCUBOOT_SIGNATURE_KEY_FILE="/work/dev/if-device-nrf53/keys/bootloader_priv-ecdsa256.pem"

CONFIG_MCUBOOT_BOOTLOADER_MODE_SWAP_WITHOUT_SCRATCH=y
CONFIG_MCUBOOT_SHELL=n

CONFIG_DEBUG_COREDUMP=n
CONFIG_DEBUG_COREDUMP_BACKEND_LOGGING=n
CONFIG_DEBUG_COREDUMP_MEMORY_DUMP_MIN=n

# Use minimal C library instead of the Picolib
CONFIG_MINIMAL_LIBC=y

CONFIG_DEBUG=n
CONFIG_DEBUG_INFO=n
# all functions in seperate sections so linker can discard unused code
CONFIG_COMPILER_OPT="-Os"
# -fdata-sections -ffunction-sections -Wl,--gc-sections -Wl,--strip-all"
CONFIG_THREAD_NAME=n
CONFIG_THREAD_ANALYZER=n
CONFIG_THREAD_ANALYZER_USE_PRINTK=n
CONFIG_THREAD_ANALYZER_AUTO=n
CONFIG_SYS_HEAP_RUNTIME_STATS=n
CONFIG_INIT_STACKS=n
CONFIG_ASSERT=n
CONFIG_ASSERT_VERBOSE=n
CONFIG_ASSERT_NO_MSG_INFO=y
CONFIG_ASSERT_NO_COND_INFO=y
CONFIG_ASSERT_NO_FILE_INFO=y
CONFIG_STACK_SENTINEL=n
CONFIG_RESET_ON_FATAL_ERROR=y
CONFIG_REBOOT=y

# turn off serial and uart console to save space (later)
CONFIG_CONSOLE=y
CONFIG_CONSOLE_HANDLER=n
CONFIG_SERIAL=y
CONFIG_UART_CONSOLE=y
CONFIG_STDOUT_CONSOLE=y

# turn off log to save image size
CONFIG_LOG=y
CONFIG_LOG_MODE_MINIMAL=y
CONFIG_LOG_MODE_IMMEDIATE=n
#CONFIG_LOG_BACKEND_UART=y
CONFIG_LOG_DEFAULT_LEVEL=3
CONFIG_LOG_PRINTK=n
CONFIG_SHELL=n
CONFIG_SHELL_MINIMAL=n
CONFIG_SHELL_LOG_BACKEND=n

CONFIG_GPIO=n
CONFIG_GPIO_MCP230XX=n

CONFIG_USE_SEGGER_RTT=n
CONFIG_I2C=n
CONFIG_SPI=n

CONFIG_BOOT_BANNER=n
#CONFIG_TIMESLICING=n
#CONFIG_MULTITHREADING=n
CONFIG_TICKLESS_KERNEL=n
CONFIG_TIMEOUT_64BIT=n
CONFIG_NRF_ENABLE_ICACHE=n

This stops "due to Kconfig warnings":

-- west build: making build dir C:\work\dev\if-device-nrf53\cc1-med\build pristine
-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: C:/ncs/toolchains/2d382dcd92/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.8.0/zephyr/.cache
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: cc2v1, qualifiers: nrf5340/cpuapp
Parsing C:/work/dev/if-device-nrf53/cc1-med/Kconfig.sysbuild
Loaded configuration 'C:/work/dev/if-device-nrf53/cc1-med/build/_sysbuild/empty.conf'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/sysbuild.conf'
Configuration saved to 'C:/work/dev/if-device-nrf53/cc1-med/build/zephyr/.config'
Kconfig header saved to 'C:/work/dev/if-device-nrf53/cc1-med/build/_sysbuild/autoconf.h'
--
   *****************************
   * Running CMake for mcuboot *
   *****************************

Loading Zephyr default modules (Zephyr base).
-- Application: C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr
-- CMake version: 3.21.0
-- Using NCS Toolchain 2.8.20241106.194216054162 for building. (C:/ncs/toolchains/2d382dcd92/cmake)
-- Found Python3: C:/ncs/toolchains/2d382dcd92/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.8.0/zephyr/.cache
-- Zephyr version: 3.7.99 (C:/ncs/v2.8.0/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: cc2v1, qualifiers: nrf5340/cpuapp
-- Found host-tools: zephyr 0.16.8 (C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.8 (C:/ncs/toolchains/2d382dcd92/opt/zephyr-sdk)
-- Found Dtc: C:/ncs/toolchains/2d382dcd92/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")

-- Found BOARD.dts: C:/work/dev/if-device-nrf53/boards/infrafon/cc2v1/cc2v1_nrf5340_cpuapp.dts
'label' is marked as deprecated in 'properties:' in C:/ncs/v2.8.0/zephyr/dts/bindings\audio\nordic,nrf-pdm.yaml for node /soc/peripheral@50000000/pdm@26000.
'label' is marked as deprecated in 'properties:' in C:/ncs/v2.8.0/zephyr/dts/bindings\i2s\nordic,nrf-i2s.yaml for node /soc/peripheral@50000000/i2s@28000.
-- Generated zephyr.dts: C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/dts.cmake
CMake Warning at C:/ncs/v2.8.0/zephyr/cmake/modules/dts.cmake:389 (message):
  dtc raised one or more warnings:

  <stdout>: Warning (avoid_unnecessary_addr_size):
  /soc/peripheral@50000000/i2s@28000: unnecessary #address-cells/#size-cells
  without "ranges" or child "reg" property

Call Stack (most recent call first):
  C:/ncs/v2.8.0/zephyr/cmake/modules/zephyr_default.cmake:133 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:12 (find_package)



warning: The choice symbol MCUBOOT_BOOTLOADER_MODE_SWAP_WITHOUT_SCRATCH (defined at
modules/Kconfig.mcuboot:164) was selected (set =y), but no symbol ended up as the choice selection.
See http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MCUBOOT_BOOTLOADER_MODE_SWAP_WITHOUT_SC
RATCH and/or look up MCUBOOT_BOOTLOADER_MODE_SWAP_WITHOUT_SCRATCH in the menuconfig/guiconfig
interface. The Application Development Primer, Setting Configuration Values, and Kconfig - Tips and
Best Practices sections of the manual might be helpful too.


Parsing C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr/Kconfig
warning: FLASH_MAP (defined at subsys/storage/flash_map/Kconfig:10) has direct dependencies FLASH_HAS_DRIVER_ENABLED with value n, but is currently being y-selected by the following symbols:
 - MCUBOOT_DEVICE_SETTINGS (defined at C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr/Kconfig:977), with value y, direct dependencies y (value: y)Loaded configuration 'C:/work/dev/if-device-nrf53/boards/infrafon/cc2v1/cc2v1_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/sysbuild/mcuboot/prj.conf'
Merged configuration 'C:/ncs/v2.8.0/nrf/subsys/partition_manager/ext_flash_mcuboot_secondary.conf'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/.config.sysbuild'


error: Aborting due to Kconfig warnings

CMake Error at C:/ncs/v2.8.0/zephyr/cmake/modules/kconfig.cmake:396 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  C:/ncs/v2.8.0/nrf/cmake/modules/kconfig.cmake:29 (include)
  C:/ncs/v2.8.0/zephyr/cmake/modules/zephyr_default.cmake:133 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:12 (find_package)


-- Configuring incomplete, errors occurred!
CMake Error at cmake/modules/sysbuild_extensions.cmake:514 (message):
  CMake configure failed for Zephyr project: mcuboot

  Location: C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr/
Call Stack (most recent call first):
  cmake/modules/sysbuild_images.cmake:20 (ExternalZephyrProject_Cmake)
  cmake/modules/sysbuild_default.cmake:20 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  C:/ncs/v2.8.0/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
  template/CMakeLists.txt:10 (find_package)


-- Configuring incomplete, errors occurred!
See also "C:/work/dev/if-device-nrf53/cc1-med/build/CMakeFiles/CMakeOutput.log".
←[91mFATAL ERROR: command exited with status 1: 'C:\ncs\toolchains\2d382dcd92\opt\bin\cmake.EXE' -DWEST_PYTHON=C:/ncs/toolchains/2d382dcd92/opt/bin/python.exe '-BC:\work\dev\if-device-nrf53\cc1-med\build' -GNinja -DBOARD=cc2v1/nrf5340/cpuapp '-DBOARD_ROOT=C:\work\dev\if-device-nrf53' '-SC:\ncs\v2.8.0\zephyr\share\sysbuild' '-DAPP_DIR:PATH=C:\work\dev\if-device-nrf53\cc1-med'
←[0m

It seems it doesn't like something about the flash driver? But this worked fine in 2.6... and also I don't get this error if using child_images build system...

Note I have a pm_static.yml to define my partitions as I have an external flash chip also - does this make a difference? (again, all fine on 2.6)

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Wed, 18 Dec 2024 16:30:04 GMT

Hi Andreas

Ok. Lets start with the migration to HWMv2. I have managed to rename/update my board files so that doing west boards can see the board, and that it manages to do the dtc part.

I have 3 issues I think here:

1/ warnings about depreciated labels

-- Found BOARD.dts: C:/work/dev/if-device-nrf53/boards/infrafon/cc2v1/cc2v1_nrf5340_cpuapp.dts
'label' is marked as deprecated in 'properties:' in C:/ncs/v2.8.0/zephyr/dts/bindings\audio\nordic,nrf-pdm.yaml for node /soc/peripheral@50000000/pdm@26000.
'label' is marked as deprecated in 'properties:' in C:/ncs/v2.8.0/zephyr/dts/bindings\i2s\nordic,nrf-i2s.yaml for node /soc/peripheral@50000000/i2s@28000.

I can ignore these, yes?

2/ a more serious looking warning, but related (as far as I can tell) to dts definitions in the SDK

-- Including generated dts.cmake file: C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/dts.cmake
CMake Warning at C:/ncs/v2.8.0/zephyr/cmake/modules/dts.cmake:389 (message):
  dtc raised one or more warnings:

  <stdout>: Warning (avoid_unnecessary_addr_size):
  /soc/peripheral@50000000/i2s@28000: unnecessary #address-cells/#size-cells
  without "ranges" or child "reg" property

Call Stack (most recent call first):
  C:/ncs/v2.8.0/zephyr/cmake/modules/zephyr_default.cmake:133 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:12 (find_package)

The dtsi file that defines the i2s reg and address-cells for the controller is in the SDK: file zephyr/dts/arm/noridc/nrf5340_cpuapp_peripherals.dtsi :

i2s0: i2s@28000 {

compatible = "nordic,nrf-i2s";

#address-cells = <1>;

#size-cells = <0>;

reg = <0x28000 0x1000>;

interrupts = <40 NRF_DEFAULT_IRQ_PRIORITY>;

status = "disabled";

};

My dts just enables it and adds pinctrl definition, as well as a gpio used for the sdmode of the amp.

&i2s0 {

status = "okay";

compatible = "nordic,nrf-i2s";

label="I2S audio out MAX98357A";

pinctrl-0 = <&i2s0_default>;

pinctrl-1 = <&i2s0_sleep>;

pinctrl-names = "default", "sleep";

i2s_sdmode: sdmode {

compatible = "nordic,gpio-pins";

gpios = <&gpio1 14 GPIO_ACTIVE_HIGH>; // P1.14

};

Is there a way for me to 'correct' the warning for the base definition?

3/ enabling the PDM driver

My DTS has the PDM defined as:

&pdm0 {

status = "okay";

compatible = "nordic,nrf-pdm";

label="PDM micro in";

pinctrl-0 = <&pdm0_default>;

pinctrl-1 = <&pdm0_sleep>;

pinctrl-names = "default", "sleep";

pdm_en: en {

compatible = "nordic,gpio-pins";

gpios = <&ioexp0 12 GPIO_ACTIVE_HIGH>; // GPB.04

};

This doesn't cause an issue for the dtc, but I saw a problem for KConfig which didn't like having CONFIG_NRFX_PDM=y (which was ok for v2.6). Do I need to evolve something in the dts to allow me to define the CONFIG to include the PDM driver?

btw, I updated the nrf7002/wifi bits of the DTS, and it now accepts that the DTS has a valid wifi DT to let the wifi stuff in prj.conf be accepted.

thanks

RE: Trouble migrating from NCS 2.6 to 2.8

AHaug — Wed, 18 Dec 2024 15:11:44 GMT

Hi,

I see you've started looking into this quite a bit since yesterday, but I'll start with breaking down the abstraction layer a bit w.r.t sysbuild and the change from using parent/child images. This level of understanding is most likely where you're already at, but I'm doing it to ensure we're on the same page.

In nRF Connect SDK we've previously used the child and parent-image system to manage multi-image builds such as for instance the nRF5340 which has both an image for the application core, for the network core (hci_rpmsg) and in most cases an image for a bootloader (mcuboot). To match what is used in Zephyr, the migration to sysbuild was done and thus in turn deprecating child and parent images in favour of companion images instead. I.e it is as good as the same, but different to comply with the norm in the Zephyr RTOS.

What you previously had within <your_project>/child_images/mcuboot.conf is now present within <your_project>/sysbuild/mcuboot.conf as shown in this sample: https://github.com/nrfconnect/sdk-zephyr/tree/main/samples/sysbuild/with_mcuboot/sysbuild and what you had in prj.conf that is related to adding multi-images is now within sysbuild.conf.

[quote user=""]I created sysbuild.conf (at the root where I run west - is this right?), [/quote]

Yes, this is correct. The second big thing is as you mention sysbuild.conf. Since the build system is changed to use sysbuild, it's now sysbuild that manages your multiple images, and it is within sysbuild.conf you need to add configurations to enable said additional images (such as MCUboot through SB_CONFIG_BOOTLOADER_MCUBOOT=y).

The third big thing that has happened is the migration from hardware model 1 to hardware model 2 (which you've referred to), and the third big thing is the sysbuild.conf

Next to your work from today:

It's a bit hard to separate build logs from questions, could you edit the 3 earliest replies to use "insert -> code" insert for whats from the build log and the rest outside?

[quote user="BrianW"]How can I fix this?[/quote]

Do you have SB_CONFIG_BOOTLOADER_MCUBOOT=y within sysbuild.conf or is it just within sysbuild/mcuboot.conf?

Kind regards,
Andreas

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Wed, 18 Dec 2024 12:05:31 GMT

The kconfig warning that causes trhe mcuboot build to fail is for kconfig setting that are NOT in my sysbuid/mcuboot/prj.conf file :

Parsing C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr/Kconfig
warning: FLASH_MAP (defined at subsys/storage/flash_map/Kconfig:10) has direct dependencies FLASH_HAS_DRIVER_ENABLED with value n, but is currently being y-selected by the following symbols:
 - MCUBOOT_DEVICE_SETTINGS (defined at C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr/Kconfig:977), with value y, direct dependencies y (value: y)Loaded configuration 'C:/work/dev/if-device-nrf53/boards/infrafon/cc2v1/cc2v1_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/sysbuild/mcuboot/prj.conf'
Merged configuration 'C:/ncs/v2.8.0/nrf/subsys/partition_manager/ext_flash_mcuboot_secondary.conf'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/.config.sysbuild'


error: Aborting due to Kconfig warnings

CMake Error at C:/ncs/v2.8.0/zephyr/cmake/modules/kconfig.cmake:396 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  C:/ncs/v2.8.0/nrf/cmake/modules/kconfig.cmake:29 (include)
  C:/ncs/v2.8.0/zephyr/cmake/modules/zephyr_default.cmake:133 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:12 (find_package)

-- Configuring incomplete, errors occurred!

CMake Error at cmake/modules/sysbuild_extensions.cmake:514 (message):
  CMake configure failed for Zephyr project: mcuboot

How can I fix this?

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Wed, 18 Dec 2024 11:37:53 GMT

This error is caused by my board not being migrated to HWMv2 (despite the migration guide here https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/releases_and_maturity/migration/migration_hwmv2.html explicitly stating that OOT boards do not need to be migrated....)

Once the board is fixed up to HWMv2, and the build command references the board as board/soc/variant instead of borad_soc_variant (thanks a lot for a meaningless change...) the 'sta' sample gets a lot further (it now has dependances on LEDs in the DTS it seems)

I also had to update my MCP23017 DTS reference to be compatible="microchip,mcp23017" instead of mcp23xxx to let the DTS compile (why? don't know) for this error:

devicetree error: gpio controller <Node /soc/peripheral@50000000/i2c@9000/mcp23017@20 in 'C:/ncs/v2.8.0/zephyr/misc/empty_file.c'> for <Node /soc/peripheral@50000000/pdm@26000/en in 'C:/ncs/v2.8.0/zephyr/misc/empty_file.c'> lacks binding

Now its:

ioexp0: mcp23017@20 {

status = "okay";

compatible = "microchip,mcp23017";

reg = < 0x20 >;

gpio-controller;

ngpios = < 16 >;

#gpio-cells = < 2 >;

int-gpios = <&gpio1 15 GPIO_ACTIVE_LOW>; // P1.15 interupt from ioexpander

};

in case anyone else gets stuck at this one...

My application build is still broken, due to 'KConfig warnings'. Pity it doesnt say which ones:

warning: BOOT_USB_DFU_WAIT_DELAY_MS (defined at
C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr/Kconfig:759) was assigned the value '5000' but got the
value ''. Check these unsatisfied dependencies: BOOT_USB_DFU_WAIT (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
BOOT_USB_DFU_WAIT_DELAY_MS in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

warning: BOOT_SERIAL_WAIT_FOR_DFU_TIMEOUT (defined at
C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr\Kconfig.serial_recovery:160) was assigned the value
'5000' but got the value ''. Check these unsatisfied dependencies: BOOT_SERIAL_WAIT_FOR_DFU (=n),
MCUBOOT_SERIAL (=n). See
docs.zephyrproject.org/.../kconfig.html and/or
look up BOOT_SERIAL_WAIT_FOR_DFU_TIMEOUT in the menuconfig/guiconfig interface. The Application
Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of
the manual might be helpful too.

warning: USB_DEVICE_PRODUCT (defined at C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr/Kconfig:1014,
subsys/usb/device/Kconfig:37) was assigned the value 'Infrafon CC2-WDD' but got the value 'MCUBOOT'.
See docs.zephyrproject.org/.../kconfig.html and/or look up
USB_DEVICE_PRODUCT in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

warning: BOOTLOADER_MCUBOOT (defined at C:/ncs/v2.8.0/nrf/modules/trusted-
firmware-m\Kconfig.tfm.defconfig:90, modules/Kconfig.mcuboot:13) was assigned the value 'y' but got
the value 'n'. Check these unsatisfied dependencies: (BUILD_WITH_TFM || !MCUBOOT) (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
BOOTLOADER_MCUBOOT in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

warning: LOG_BACKEND_UART (defined at subsys/logging\backends\Kconfig.uart:4) was assigned the value
'y' but got the value 'n'. Check these unsatisfied dependencies: (!LOG_MODE_MINIMAL) (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
LOG_BACKEND_UART in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best PracticesParsing C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr/Kconfig
sections of the manual might be helpful
too.

warning: USB_DEVICE_VID (defined at subsys/usb/device/Kconfig:19) was assigned the value '0x16D0'
but got the value ''. Check these unsatisfied dependencies: USB_DEVICE_STACK (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
USB_DEVICE_VID in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

warning: USB_DEVICE_PID (defined at subsys/usb/device/Kconfig:25) was assigned the value '0x138F'
but got the value ''. Check these unsatisfied dependencies: USB_DEVICE_STACK (=n). See
docs.zephyrproject.org/.../kconfig.html and/or look up
USB_DEVICE_PID in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

waLoaded configuration 'C:/work/dev/if-device-nrf53/boards/infrafon/cc2v1/cc2v1_nrf5340_cpuapp_defconfig'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/sysbuild/mcuboot/prj.conf'
Merged configuration 'C:/ncs/v2.8.0/nrf/subsys/partition_manager/ext_flash_mcuboot_secondary.conf'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/build/mcuboot/zephyr/.config.sysbuild'
rning: The choice symbol MCUBOOT_BOOTLOADER_MODE_SWAP_WITHOUT_SCRATCH (defined at
modules/Kconfig.mcuboot:164) was selected (set =y), but no symbol ended up as the choice selection.
See docs.zephyrproject.org/.../kconfig.html
RATCH and/or look up MCUBOOT_BOOTLOADER_MODE_SWAP_WITHOUT_SCRATCH in the menuconfig/guiconfig
interface. The Application Development Primer, Setting Configuration Values, and Kconfig - Tips and
Best Practices sections of the manual might be helpful too.

warning: The choice symbol USB_DRIVER_LOG_LEVEL_ERR (defined at
subsys/logging/Kconfig.template.log_config:11) was selected (set =y), but no symbol ended up as the
choice selection. See
docs.zephyrproject.org/.../kconfig.html and/or look up
USB_DRIVER_LOG_LEVEL_ERR in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.

warning: FLASH_MAP (defined at subsys/storage/flash_map/Kconfig:10) has direct dependencies FLASH_HAS_DRIVER_ENABLED with value n, but is currently being y-selected by the following symbols:
- MCUBOOT_DEVICE_SETTINGS (defined at C:/ncs/v2.8.0/bootloader/mcuboot/boot/zephyr/Kconfig:977), with value y, direct dependencies y (value: y)

error: Aborting due to Kconfig warnings

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Wed, 18 Dec 2024 09:27:52 GMT

I tried to build the wifi 'sta' sample (copied from the ncs 2.8.0 tree). This fails with the same errors...

C:\work\dev\if-device-nrf53>west build --build-dir wifi_sta_28/build wifi_sta_28 --board cc1medv1_nrf5340_cpuapp --pristine -DBOARD_ROOT=%CD%
-- west build: making build dir C:\work\dev\if-device-nrf53\wifi_sta_28\build pristine
-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: C:/ncs/toolchains/2d382dcd92/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.8.0/zephyr/.cache
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: cc1medv1_nrf5340_cpuapp
Parsing C:/ncs/v2.8.0/zephyr/share/sysbuild/Kconfig
Loaded configuration 'C:/work/dev/if-device-nrf53/wifi_sta_28/build/_sysbuild/empty.conf'
Merged configuration 'C:/work/dev/if-device-nrf53/wifi_sta_28/sysbuild.conf'
Configuration saved to 'C:/work/dev/if-device-nrf53/wifi_sta_28/build/zephyr/.config'
Kconfig header saved to 'C:/work/dev/if-device-nrf53/wifi_sta_28/build/_sysbuild/autoconf.h'
CMake Error at C:/ncs/v2.8.0/nrf/sysbuild/CMakeLists.txt:117 (list):
list GET given empty list
Call Stack (most recent call first):
cmake/modules/sysbuild_extensions.cmake:583 (nrf_PRE_CMAKE)
cmake/modules/sysbuild_extensions.cmake:583 (cmake_language)
cmake/modules/sysbuild_images.cmake:16 (sysbuild_module_call)
cmake/modules/sysbuild_default.cmake:20 (include)
C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
C:/ncs/v2.8.0/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
template/CMakeLists.txt:10 (find_package)

What is not correctly installed here?

RE: Trouble migrating from NCS 2.6 to 2.8

BrianW — Wed, 18 Dec 2024 09:06:08 GMT

1st error: sysbuild.conf goes int he build target sub directory.

This generates many kconfig errors:

- the DFU building part is now complex... remove for later

- the option noted int he migration guide SB_CONFIG_PM_MCUBOOT_PAD requires a hex value - but no explanation of what this option is for that I can find (both the nordic site and zephyr search options find no responses...). set to 0x200 as a likely value

- option SB_CONFIG_MCUBOOT_BOOTLOADER_MODE_SWAP_WITHOUT_SCRATCH=y as noted in the migration guide is rejected as unknown

- and the option SB_CONFIG_NETCORE_HCI_IPC gets a warning, with a handy link that leads to a search page... that doesn't find that option..

And again, the CMake fails with a useless error that doesn't give any indication of what is causing the issue....

-- west build: making build dir C:\work\dev\if-device-nrf53\cc1-med\build pristine
-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: C:/ncs/toolchains/2d382dcd92/opt/bin/python.exe (found suitable version "3.12.4", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/ncs/v2.8.0/zephyr/.cache
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: cc1medv1_nrf5340_cpuapp

warning: The choice symbol NETCORE_HCI_IPC (defined at
C:/ncs/v2.8.0/nrf/sysbuild\Kconfig.netcore:90) was selected (set =y), but no symbol ended up as the
choice selection. See docs.zephyrproject.org/.../kconfig.html
and/or look up NETCORE_HCI_IPC in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

Parsing C:/work/dev/if-device-nrf53/cc1-med/Kconfig.sysbuild
Loaded configuration 'C:/work/dev/if-device-nrf53/cc1-med/build/_sysbuild/empty.conf'
Merged configuration 'C:/work/dev/if-device-nrf53/cc1-med/sysbuild.conf'
Configuration saved to 'C:/work/dev/if-device-nrf53/cc1-med/build/zephyr/.config'
Kconfig header saved to 'C:/work/dev/if-device-nrf53/cc1-med/build/_sysbuild/autoconf.h'
CMake Error at C:/ncs/v2.8.0/nrf/sysbuild/CMakeLists.txt:117 (list):
list GET given empty list
Call Stack (most recent call first):
cmake/modules/sysbuild_extensions.cmake:583 (nrf_PRE_CMAKE)
cmake/modules/sysbuild_extensions.cmake:583 (cmake_language)
cmake/modules/sysbuild_images.cmake:16 (sysbuild_module_call)
cmake/modules/sysbuild_default.cmake:20 (include)
C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:75 (include)
C:/ncs/v2.8.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
C:/ncs/v2.8.0/zephyr/share/sysbuild-package/cmake/SysbuildConfig.cmake:8 (include)
template/CMakeLists.txt:10 (find_package)

What is missing?