Failed to build FOTA firmware (nRF 1.9.1)

RE: Failed to build FOTA firmware (nRF 1.9.1)

Simon — Thu, 07 Jul 2022 09:27:02 GMT

With this sample you will be able to update netcore and appcore (not simultaneously): https://github.com/simon-iversen/ncs_samples/tree/eb7fa36387783f8faf94b7861f144acf9f994462/update_mcuboot_app_and_netcore

The patch you see there is present in v2.0.0.

If you want to update netcore and appcore simultaneously, you can take a look at the machine learning sample, as mentioned in this reply: https://devzone.nordicsemi.com/support-private/support/290081#permalink=764996

Best regards,

Simon

RE: Failed to build FOTA firmware (nRF 1.9.1)

wangrj — Thu, 07 Jul 2022 01:32:59 GMT

thanks ,

so how did you upgrade these two core

could you give some advice

RE: Failed to build FOTA firmware (nRF 1.9.1)

Simon — Wed, 06 Jul 2022 12:32:25 GMT

No, the sample I uploaded in RE: Failed to build FOTA firmware (nRF 1.9.1) will only update the application core.

RE: Failed to build FOTA firmware (nRF 1.9.1)

wangrj — Wed, 06 Jul 2022 09:07:01 GMT

hi Simon

it 5381.peripheral_uart_ble_dfu_53.zip can upgrade netcore?

RE: Failed to build FOTA firmware (nRF 1.9.1)

Simon — Tue, 21 Jun 2022 23:11:35 GMT

Could you enable log in the application (CONFIG_LOG=y) and mcuboot (set CONFIG_MCUBOOT_LOG_LEVEL_DBG=y in the mcuboot prj.conf file) to see if you get any information what is happening on the nRF5340 and if that may be the cause of the failure.

RE: Failed to build FOTA firmware (nRF 1.9.1)

d.p — Tue, 21 Jun 2022 21:35:08 GMT

Hi Simon,

Thank you again for the reply. I finally managed to get past the assert error and successfully build our application with external flash enabled and multi-image DFU support (by following the machine learning example you pointed me to). The problem was: 1) before looking at the machine learning example, I wasn't using an mcuboot configuration file and after that 2) the build system wasn't picking up the `app.overlay` file, which was needed to create the flash simulator for the multi-image DFU.

So I am at a stage where our app builds successfully and the partitions look like this:

+------------------------------------------------+
| 0x0: mcuboot_secondary (0xe0000 - 896kB)       |
| 0xe0000: mcuboot_secondary_1 (0x40000 - 256kB) |
| 0x120000: external_flash (0x6e0000 - 7040kB)   |
+------------------------------------------------+

  flash_primary (0x100000 - 1024kB):
+--------------------------------------------------+
| 0x0: mcuboot (0x10000 - 64kB)                    |
+---0x10000: mcuboot_primary (0xe0000 - 896kB)-----+
| 0x10000: mcuboot_pad (0x200 - 512B)              |
+---0x10200: mcuboot_primary_app (0xdfe00 - 895kB)-+
| 0x10200: spm (0xc000 - 48kB)                     |
| 0x1c200: app (0xd3e00 - 847kB)                   |
+--------------------------------------------------+
| 0xf0000: settings_storage (0x10000 - 64kB)       |
+--------------------------------------------------+

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

  ram_flash (0x40000 - 256kB):
+------------------------------------------+
| 0x0: mcuboot_primary_1 (0x40000 - 256kB) |
| 0x40000: ram_flash (0x0 - 0B)            |
+------------------------------------------+

  sram_primary (0x80000 - 512kB):
+------------------------------------------------+
| 0x20000000: pcd_sram (0x2000 - 8kB)            |
+---0x20002000: sram_secure (0x8000 - 32kB)------+
| 0x20002000: spm_sram (0x8000 - 32kB)           |
+---0x2000a000: sram_nonsecure (0x76000 - 472kB)-+
| 0x2000a000: sram_primary (0x66000 - 408kB)     |
| 0x20070000: rpmsg_nrf53_sram (0x10000 - 64kB)  |
+------------------------------------------------+

However, now I am facing another problem: Once I try to do a DFU through the Device Manager mobile app, I see the following error after the binary file transfer completes:

State: Invalid value (3)

This occurs no matter whether I try to update the app image, the network processor image or both at the same time. Any idea what it means?

RE: Failed to build FOTA firmware (nRF 1.9.1)

Simon — Mon, 13 Jun 2022 12:58:02 GMT

[quote user="d.p"]Thanks for the prompt reply Simon. I've managed to update the application of the main processor, but I cannot update both the application processor and the network processor at the same time, using `CONFIG_UPDATEABLE_IMAGE_NUMBER=2`. I am getting the `BUILD_ASSERT(IMG_MGMT_UPDATABLE_IMAGE_NUMBER == 1` error when I try that. Is the only option to update one processor at a time? This is not ideal. [/quote]

Could you take a look at the machine learning sample and copy the approach there. It supports multi-image update. If this approach doesn't help you, please let me know, and I will take a deeper look at it (I don't have too much experience with multi image DFU currently). Take a look at this page as well: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.1/nrf/ug_nrf5340.html#simultaneous-multi-image-dfu

[quote user=""]We don't have an external flash chip on our custom board, will there be enough space in the internal flash storage? [/quote]

I just talked to a developer internally, and got informed that multi img DFU (update netcore and appcore) is not supported without external flash at the moment. My apologies for that.

[quote user=""]I read here there may not be enough: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_thingy53.html#external-flash But we do have an SD card which we could use.[/quote]

I have not tested this, but I think that it should be possible put the secondary slot in the SD card. See https://devzone.nordicsemi.com/f/nordic-q-a/85987/mcuboot-secondary-slot-in-external-spi-flash

Best regards,

Simon

RE: Failed to build FOTA firmware (nRF 1.9.1)

d.p — Fri, 10 Jun 2022 13:11:44 GMT

Thanks for the prompt reply Simon. I've managed to update the application of the main processor, but I cannot update both the application processor and the network processor at the same time, using `CONFIG_UPDATEABLE_IMAGE_NUMBER=2`. I am getting the `BUILD_ASSERT(IMG_MGMT_UPDATABLE_IMAGE_NUMBER == 1` error when I try that. Is the only option to update one processor at a time? This is not ideal.

P.S.: I am not sure I can update the title.

RE: Failed to build FOTA firmware (nRF 1.9.1)

Simon — Tue, 07 Jun 2022 12:37:53 GMT

I was able to update the nRF5340 DK using the peripheral_uart sample and following the steps in DFU over Bluetooth. Here is the sample I used,

devzone.nordicsemi.com/.../5381.peripheral_5F00_uart_5F00_ble_5F00_dfu_5F00_53.zip

Here is the diff of the changes I applied to peripheral_uart:

diff --git a/samples/bluetooth/peripheral_uart/prj.conf b/samples/bluetooth/peripheral_uart/prj.conf
index e5262de64..e055dfb1e 100644
--- a/samples/bluetooth/peripheral_uart/prj.conf
+++ b/samples/bluetooth/peripheral_uart/prj.conf
@@ -48,3 +48,24 @@ CONFIG_LOG_BACKEND_RTT=y
 CONFIG_LOG_BACKEND_UART=n
 
 CONFIG_ASSERT=y
+
+# 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
+
+# Some command handlers require a large stack.
+CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=4096
\ No newline at end of file
diff --git a/samples/bluetooth/peripheral_uart/src/main.c b/samples/bluetooth/peripheral_uart/src/main.c
index 8a1ca1e50..c1445c13e 100644
--- a/samples/bluetooth/peripheral_uart/src/main.c
+++ b/samples/bluetooth/peripheral_uart/src/main.c
@@ -32,6 +32,10 @@
 
 #include <logging/log.h>
 
+#include <mgmt/mcumgr/smp_bt.h>
+#include "os_mgmt/os_mgmt.h"
+#include "img_mgmt/img_mgmt.h"
+
 #define LOG_MODULE_NAME peripheral_uart
 LOG_MODULE_REGISTER(LOG_MODULE_NAME);
 
@@ -76,7 +80,9 @@ static const struct bt_data ad[] = {
 };
 
 static const struct bt_data sd[] = {
-	BT_DATA_BYTES(BT_DATA_UUID128_ALL, BT_UUID_NUS_VAL),
+	BT_DATA_BYTES(BT_DATA_UUID128_ALL,
+		      0x84, 0xaa, 0x60, 0x74, 0x52, 0x8a, 0x8b, 0x86,
+		      0xd3, 0x4c, 0xb7, 0x1d, 0x1d, 0xdc, 0x53, 0x8d),
 };
 
 #if CONFIG_BT_NUS_UART_ASYNC_ADAPTER
@@ -571,6 +577,10 @@ void main(void)
 	if (IS_ENABLED(CONFIG_BT_NUS_SECURITY_ENABLED)) {
 		bt_conn_auth_cb_register(&conn_auth_callbacks);
 	}
+	printk("build time: " __DATE__ " " __TIME__ "\n");
+	os_mgmt_register_group();
+	img_mgmt_register_group();
+	smp_bt_register();
 
 	err = bt_enable(NULL);
 	if (err) {

Here is the output I got

*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0xc000
I: Jumping to the first image slot
*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
Starting Nordic UART service example
build time: Jun  7 2022 14:22:19
*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=good, swap_type=0x2, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: test
I: Bootloader chainload address offset: 0xc000
I: Jumping to the first image slot
*** Booting Zephyr OS build v2.7.99-ncs1-1  ***
Starting Nordic UART service example
build time: Jun  7 2022 14:24:45

[quote user=""]

1. How to make the project build for multi-image FOTA, BLE updates? Do I need to include the following in the MCUboot configuration?

Fullscreen

CONFIG_BOOT_UPGRADE_ONLY - The simultaneous update of multiple images does not support network core image reversion, so you need to disable application image reversion.

CONFIG_PCD_APP - Enable commands exchange with the network core.

CONFIG_UPDATEABLE_IMAGE_NUMBER - Enable support for multiple update partitions by setting this option to 2.

[/quote]

No, if you just want to update the application, you don't need to add these

[quote user=""]2. I haven't found any nRF samples that demonstrate how to do an FOTA update via BLE, using the nRF5340-DK. Can you please point me to any?[/quote]

Check my attached sample above

[quote user=""]3. The peripheral_uart example uses external flash for the FOTA update. We don't have an external flash chip on our custom board, will there be enough space in the internal flash storage? I read here there may not be enough: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_thingy53.html#external-flash But we do have an SD card which we could use.[/quote]

I was able to perform a DFU using the peripheral_uart and the nRF5340 without using external flash (confirmed it by running ninja partition_manager_report from the build folder). However, if your application is large, you might need to use external flash.

Also, could you change your title and include 'nRF5340', so other people can find it more easily

Best regards,

Simon