Sample smp_svr on NRF52840 dongle: .text does not fit in FLASH

RE: Sample smp_svr on NRF52840 dongle: .text does not fit in FLASH

Edvin — Fri, 24 Jan 2025 14:17:15 GMT

[quote user="Spector"]* For cmake add DMCUBOOT_OVERLAY_CONFIG="mcuboot.conf"[/quote]

I don't know where you got this from. What file are you trying to point to?

To build the sample for nRF52840dongle, use the sampe found in zephyr\samples\subsys\mgmt\mcumgr\smp_svr (the one you are already using), and I usually just copy that folder to any location, and then I add it as an existing application in VS Code (from the new location). After that, add a build configuration where you take the overlay-bt.conf file as an extra KConfig fragment, and build.

I see that if I build this for the nRF52840 dongle, it fails because it overflows the Flash. The dongle, unlike the nRF52840 DK doesn't have external flash.

It doesn't overflow by much, though. You could try to strip out the nRF5 bootloader from the dongle (using an overlay file). So that will give you one more page (4kb) from the beginning, and about 32+128kb more flash at the top of the ram:

Perhaps it is easier to start with the nRF52840DK board and strip out the external flash. But if you remove the original bootloader from the dongle, then please note that you need to add something to your own bootloader setting the correct regulator settings. Please read about this in this blog post:

nRF52840 Dongle Programming Tutorial

Particularly the section: "Adapting firmware to set REGOUT0 properly"

Best regards,

Edvin

RE: Sample smp_svr on NRF52840 dongle: .text does not fit in FLASH

Spector — Tue, 21 Jan 2025 12:21:35 GMT

Is it impossible to build with v2.9.0?

This is a capture of steps taken to try and implement the smp_svr demo.

1. Open terminal, make project work directory
❯ cd ~/work
❯ mkdir nrf_connect
❯ cd nrf_connect
❯ code .

2. Within vscode nrf_connect extension tab.
* Create a new application.
* Copy a sample
* Select nRF Connect SDK v2.9.0
* Select zephyr/samples/subsys/mgmt/mcumgr/smp_svr
* Name it ~/work/nrf_connect/discord_demo/

3. Setup vscode workspace so that it's in ~/work/nrf_connect/discord_demo/

4. Within the nrf_connect applications add a build configuration.
* Set toolchain and sdk (2.9.0)
* Set board target nrf52840dongle/nrf52840
* For Extra Kconfig fragments add overlay-cdc.conf (imported with when project was created with sample)
* For Base Devicetree overlay add usb.overlay (imported with when project was created with sample)
* For cmake add DMCUBOOT_OVERLAY_CONFIG="mcuboot.conf"

Fail because of flash...when i inspect the west build command i see

west build --build-dir /home/wtr/work/nrf_connect/discord_demo/build /home/wtr/work/nrf_connect/discord_demo --pristine --board nrf52840dongle/nrf52840 -- -DNCS_TOOLCHAIN_VERSION=NONE -DEXTRA_CONF_FILE=overlay-cdc.conf -DDTC_OVERLAY_FILE=usb.overlay -DBOARD_ROOT=/home/wtr/work/nrf_connect/discord_demo

For some reason this doens't have the mcuboot overlay. which as the config_pm .... size_mcuboot=0x10000

RE: Sample smp_svr on NRF52840 dongle: .text does not fit in FLASH

Edvin — Mon, 20 Jan 2025 14:35:30 GMT

[quote user="Spector"]The question is which I can't find a dfu tutorial in the intermediate course for 2.9.0, only 2.6.1.
[/quote]

Yes, I am aware. We are still waiting on some building blocks that aren't done before we can update the devacademy course, unfortunately. Unless you specifically need any new features, I suggest you stick on the NCS version 2.6.X for now. Mostly nRF54 and nRF7002 features are added to the SDK versions after that.

Best regards,

Edvin

RE: Sample smp_svr on NRF52840 dongle: .text does not fit in FLASH

Spector — Mon, 20 Jan 2025 09:24:00 GMT

I can start working from only one toolchain.

The question is which I can't find a dfu tutorial in the intermediate course for 2.9.0, only 2.6.1.

However running smp_svr sample on v2.6.1 I get

Running v2.9.0 I get

RE: Sample smp_svr on NRF52840 dongle: .text does not fit in FLASH

Edvin — Mon, 20 Jan 2025 08:32:16 GMT

Ok, I see that you already have your own ticket on the issue, then.

I believe it would be easier (at least fewer pitfalls) to use the VS Code extension directly to download the toolchain and nRF Connect SDK. Alternatively the nRF Connect for Desktop -> Toolchain Manager. That way you will make sure that the SDK and Toolchains are matching. Then, when building the smp_svr sample, it should automatically build the mcuboot bootloader, and link it with your application.

[quote user="Spector"]eventually find the -DNCS_TOOLCHAIN_VERSION flag allows it work when set to NONE or 2.6.1..[/quote]

This reminds me of a bug we had at some point. For debugging purposes, is it possible to delete all NCS versions after the one that you are using? I don't recall exactly what version it was, but it may have been around there, where it took the latest toolchain version, even though specifying another one.

BR,
Edvin

RE: Sample smp_svr on NRF52840 dongle: .text does not fit in FLASH

Spector — Sat, 18 Jan 2025 07:56:44 GMT

Step 1 pray to Odin that environment sdk and toolchain is somehow setup correctly. A nightmare after moving to 2.9.0 and rolling back.

Step 2 ensure environment is correctly setup so we can run command outlay in nrf52840dongle_nrf52840

I created a symbolic link for the mcuboot and the zephyr repo, that feed into the build output.
mcuboot -> /home/wtr/ncs/v2.6.1/bootloader/mcuboot/
zephyr -> /home/wtr/ncs/v2.6.1/zephyr/

Step 3 run first command from option 2
west build -b nrf52840dongle_nrf52840 -d build/mcuboot mcuboot/boot/zephyr

Suffer because the toolchains aren't actually working as one would be misled to think with step 1. Notice 2be090971e and b77d8c1312.

Step 4 Spend the better part of your life searching for a fix ...eventually find the -DNCS_TOOLCHAIN_VERSION flag allows it work when set to NONE or 2.6.1...it seems my environment in terminal was not the only thing needed.
Get mcuboot to build .. added .zip with log and build dirdevzone.nordicsemi.com/.../mcuboot_5F00_build_5F00_evidence.zip

Step 5 - FINALLY BACK TO WHERE this message started!

smp_svr builds and I'm unable to replicate the error stated here

It's frustrating i don't know why it works or fails sometimes. I'm too busy fighting toolchain and build process that I'm not even looking at the config_xx yy and zz kernam services/sw modules.

RE: Sample smp_svr on NRF52840 dongle: .text does not fit in FLASH

Edvin — Fri, 17 Jan 2025 09:26:52 GMT

save the build log to a txt file, and put everything in a .zip folder, and upload it here (drag and drop).

RE: Sample smp_svr on NRF52840 dongle: .text does not fit in FLASH

Spector — Fri, 17 Jan 2025 08:31:43 GMT

Whats the best way for submitting output logs? Or even the entire build directory for build/mcuboot and build/smp_svr.

RE: Sample smp_svr on NRF52840 dongle: .text does not fit in FLASH

Edvin — Thu, 16 Jan 2025 20:10:39 GMT

Hello,

Unfortunately, not all samples work with all boards. Perhaps you can share your build log, and we can look into it.

It is not recommended to change the board files directly. You can use a an overlay file, called nrf52840dongle_nrf52840.overlay, and place it in a folder called boards in your application's root folder (look at how it is done in most of the samples in NCS). There you can add things that change the default board files.

Best regards,

Edvin

RE: Sample smp_svr on NRF52840 dongle: .text does not fit in FLASH

Spector — Tue, 14 Jan 2025 15:03:48 GMT

I too have the problem with >west build -b nrf52840dongle_nrf52840 -d build/smp_svr zephyr/samples/subsys/mgmt/mcumgr/smp_svr

What i don't understand is that this https://docs.nordicsemi.com/bundle/ncs-2.6.1/page/zephyr/boards/arm/nrf52840dongle_nrf52840/doc/index.html

Is on the website as an example. It relys on files stored in the ncs2.6.1 git repo.

Yet the command fails. Why aren't the .conf files up to date? Am i suppose to manually go in and change the board config files?

RE: Sample smp_svr on NRF52840 dongle: .text does not fit in FLASH

Edvin — Wed, 08 May 2024 13:29:27 GMT

Hello Elias,

Since the dongle has a bootloader and MBR from the nRF5 SDK, it means that the flash addresses from 0x00000000 -> 0x00001000, and a chunk at the end (don't remember the address by heart, but this is the old bootloader, and it is located at the "top" of the flash) is already occupied, and you can't remove them.

Since the mcuboot bootloader from NCS is usually placed on 0x00000000, this will collide with the nRF5 MBR. Therefore, the board files say that you need to stay away from 0x00000000 -> 0x10000000, and it will. The problem however, is that it then tries to fit the bootloader into 0x00001000 -> 0x0000c000, which is a bit too small. Add this to your smp_svr\child_image\mcuboot.conf:

CONFIG_PM_PARTITION_SIZE_MCUBOOT=0x10000

This will increase the size of the MCUBOOT parition, so that it can still fit the bootloader even though it doesn't touch the MBR from the nRF5 SDK.

Best regards,

Edvin