DFU with static pm_static.yml

RE: DFU with static pm_static.yml

Sigurd Hellesvik — Fri, 30 Jun 2023 11:11:25 GMT

See https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/tree/main/bootloader_samples/smp/mcuboot_smp_uart_feat_external_flash for how to configure external flash.

Regards,
Sigurd Hellesvik

RE: DFU with static pm_static.yml

IvanR — Fri, 30 Jun 2023 09:29:01 GMT

just noticed this warning:

I: Starting bootloader
W: Failed reading sectors; BOOT_MAX_IMG_SECTORS=256 - too small?
W: Cannot upgrade: not a compatible amount of sectors
I: Bootloader chainload address offset: 0x10000

RE: DFU with static pm_static.yml

IvanR — Fri, 30 Jun 2023 08:28:28 GMT

Thank you, excellent support.

Got it to work. Well, managed to compile without error, not tested the DFU but keeping my hope up!

RE: DFU with static pm_static.yml

Sigurd Hellesvik — Fri, 30 Jun 2023 07:58:28 GMT

[quote user="IvanR"]

I cant find in Kconfig PM_PARTITION_SIZE_MCUBOOT.

If I explicitly add it to my Kconfig file it does not effect the size.

[/quote]

You must configure this for the mcuboot child image.

See https://github.com/hellesvik-nordic/samples_for_nrf_connect_sdk/blob/17d4eb86e0e18032f80712ab1e0be64132852fc2/bootloader_samples/smp/mcuboot_smp_uart_feat_external_flash/child_image/mcuboot.conf#L5 for an example on how to do this

Regards,
Sigurd Hellesvik

RE: DFU with static pm_static.yml

IvanR — Fri, 30 Jun 2023 07:37:58 GMT

Thanks, found west and partition printout.

  external_flash (0x8f4000 - 9168kB):
+------------------------------------------------+
| 0x0: mcuboot_secondary (0xf4000 - 976kB)       |
| 0xf4000: littlefs_storage (0x800000 - 8192kB)  |
| 0x8f4000: external_flash (-0xf4000 - -999424B) |
+------------------------------------------------+

  flash_primary (0x100000 - 1024kB):
+-------------------------------------------------+
| 0x0: mcuboot (0xc000 - 48kB)                    |
+---0xc000: mcuboot_primary (0xf4000 - 976kB)-----+
| 0xc000: mcuboot_pad (0x200 - 512B)              |
+---0xc200: mcuboot_primary_app (0xf3e00 - 975kB)-+
| 0xc200: app (0xf3e00 - 975kB)                   |
+-------------------------------------------------+

  otp (0x2fc - 764B):
+------------------------------+
| 0xff8100: otp (0x2fc - 764B) |
+------------------------------+

  sram_primary (0x80000 - 512kB):
+-----------------------------------------------+
| 0x20000000: pcd_sram (0x2000 - 8kB)           |
| 0x20002000: sram_primary (0x6e000 - 440kB)    |
| 0x20070000: rpmsg_nrf53_sram (0x10000 - 64kB) |
+-----------------------------------------------+

 CPUNET flash_primary (0x40000 - 256kB):
+--------------------------------------------+
+---0x1000000: b0n_container (0x8800 - 34kB)-+
| 0x1000000: b0n (0x8580 - 33kB)             |
| 0x1008580: provision (0x280 - 640B)        |
+---0x1008800: app (0x37800 - 222kB)---------+
| 0x1008800: hci_rpmsg (0x37800 - 222kB)     |
+--------------------------------------------+

 CPUNET sram_primary (0x10000 - 64kB):
+-------------------------------------------+
| 0x21000000: sram_primary (0x10000 - 64kB) |
+-------------------------------------------+

I cant find in Kconfig PM_PARTITION_SIZE_MCUBOOT.

If I explicitly add it to my Kconfig file it does not effect the size.

RE: DFU with static pm_static.yml

Sigurd Hellesvik — Fri, 30 Jun 2023 06:59:04 GMT

[quote user="IvanR"]west: unknown command "build"; do you need to run this inside a workspace?[/quote]

[quote user="IvanR"]And I tried to search for documentation on CONFIG_PM_PARTITION_SIZE_MCUBOOT but there is none?[/quote]

Since MCUboot is technically an application and not part of the build system, the Kconfig search does not list this. It is weird.
However, you can see it defined here: https://github.com/nrfconnect/sdk-nrf/blob/0af5b7870b495d26c2c89337fd3c2b3178b57185/modules/mcuboot/boot/zephyr/Kconfig#L21

Configure this not for the application but for the MCUboot child image.

Regards,
Sigurd Hellesvik

RE: DFU with static pm_static.yml

IvanR — Fri, 30 Jun 2023 05:16:42 GMT

> west build -t partition_manager_report
usage: west [-h] [-z ZEPHYR_BASE] [-v] [-V] <command> ...
west: unknown command "build"; do you need to run this inside a workspace?

And I tried to search for documentation on CONFIG_PM_PARTITION_SIZE_MCUBOOT but there is none?

RE: DFU with static pm_static.yml

Sigurd Hellesvik — Thu, 29 Jun 2023 13:04:27 GMT

From your log, it looks like your mcuboot partition is too small.

Can you do "west build -t partition_manager_report" to list your partitions?

Do you see the same issues if you dedicate less space to littlefs?

Try to increase MCUboot size with CONFIG_PM_PARTITION_SIZE_MCUBOOT

Regards,
Sigurd Hellesvik

RE: DFU with static pm_static.yml

IvanR — Thu, 29 Jun 2023 12:41:36 GMT

Im using nRF Connect SDK 2.3.0

/delete-node/ &storage_partition;

/ {
	chosen {
		nordic,pm-ext-flash = &mx25r64;
	};

	fstab {
		compatible = "zephyr,fstab";
		lfs1: lfs1 {
			compatible = "zephyr,fstab,littlefs";
			mount-point = "/lfs1";
			partition = <&lfs1_part>;
			automount;
			read-size = <16>;
			prog-size = <16>;
			cache-size = <64>;
			lookahead-size = <32>;
			block-cycles = <512>;
		};
	};
};

&mx25r64 {
	partitions {
		compatible = "fixed-partitions";
		#address-cells = <1>;
		#size-cells = <1>;

		lfs1_part: partition@0 {
			label = "storage";
			reg = <0x00000000 0x00800000>;
		};
	};
};

c:/ncs/toolchains/v2.3.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.exe: zephyr\zephyr_pre0.elf section `rodata' will not fit in region `FLASH'
c:/ncs/toolchains/v2.3.0/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.exe: region `FLASH' overflowed by 5962 bytes
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
[284/300] Generating ../../zephyr/net_core_app_update.bin
sign the payload
[285/300] Generating ../../zephyr/net_core_app_signed.hex
sign the payload
[286/300] Generating ../../zephyr/net_core_app_test_update.hex
sign the payload
[287/300] Generating ../../zephyr/net_core_app_moved_test_update.hex
FAILED: modules/mcuboot/mcuboot_subimage-prefix/src/mcuboot_subimage-stamp/mcuboot_subimage-build mcuboot/zephyr/zephyr.hex mcuboot/zephyr/zephyr.elf
cmd.exe /C "cd /D C:\Users\iv\Desktop\Projects\Programing\nRF\st_ble_sensor\build\mcuboot && C:\ncs\toolchains\v2.3.0\opt\bin\cmake.exe --build . --"
[289/300] Linking C executable zephyr\zephyr.elf
Memory region Used Size Region Size %age Used
FLASH: 248116 B 998912 B 24.84%
RAM: 59980 B 440 KB 13.31%
IDT_LIST: 0 GB 2 KB 0.00%
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'c:\ncs\toolchains\v2.3.0\opt\bin\cmake.EXE' --build 'c:\Users\iv\Desktop\Projects\Programing\nRF\st_ble_sensor\build'

RE: DFU with static pm_static.yml

Sigurd Hellesvik — Thu, 29 Jun 2023 12:31:24 GMT

Which version of the nRF Connect SDK do you use?

Do you have any warnings in your log? (evt upload the full log in a code box)

Have you enabled external flash for the Partition Manager?

Regards,
Sigurd Hellesvik

RE: DFU with static pm_static.yml

IvanR — Thu, 29 Jun 2023 12:23:17 GMT

Im using nRF Connect SDK 2.3.0

Ive removed pm_static.yml and enabled

CONFIG_PM_PARTITION_REGION_LITTLEFS_EXTERNAL=y

CONFIG_PM_PARTITION_SIZE_LITTLEFS=0x8000

and it compiles ok, but as soon as I enable

#Enable mcumgr.
CONFIG_MCUMGR=y

# Enable most core commands.
CONFIG_MCUMGR_CMD_IMG_MGMT=y
CONFIG_MCUMGR_CMD_OS_MGMT=y

# Ensure an MCUboot-compatible binary is generated.
CONFIG_BOOTLOADER_MCUBOOT=y
# Allow for large Bluetooth data packets.
CONFIG_BT_L2CAP_TX_MTU=252
CONFIG_BT_BUF_ACL_RX_SIZE=256

# Enable the Bluetooth (unauthenticated) and shell mcumgr transports.
CONFIG_MCUMGR_SMP_BT=y
CONFIG_MCUMGR_SMP_BT_AUTHEN=n

I get > ld.exe: region `FLASH' overflowed by 5962 bytes

RE: DFU with static pm_static.yml

Sigurd Hellesvik — Thu, 29 Jun 2023 10:53:24 GMT

Which version of the nRF Connect SDK do you use?

Try to use CONFIG_PM_PARTITION_SIZE_LITTLEFS and CONFIG_PM_PARTITION_REGION_LITTLEFS_EXTERNAL instead of pm_static.
Then if you want to make a static configuration after that, you can use build/parititions.yml to learn from.

Regards,
Sigurd Hellesvik