Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Sigurd Hellesvik — Thu, 19 Sep 2024 08:34:11 GMT

Seems you are not getting logs for MCUboot.
I recommend that you add an overlay with logging configuration to the MCUboot image.

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Saman Niksiar — Wed, 18 Sep 2024 22:25:55 GMT

This is the logs I get from flashing and trying the FOTA. I also get Slot image has no hash TLV error on the nrf connect app side as shown below.

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Sigurd Hellesvik — Tue, 17 Sep 2024 07:17:14 GMT

[quote user="Saman Niksiar"]but it didn't show up as it rebooted[/quote]

Do you get logs from MCUboot?
If something goes wrong in the DFU, MCUboot logs usually explain what.

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Saman Niksiar — Mon, 16 Sep 2024 20:52:42 GMT

Thanks for your response

1. I have added BLE configs to the hello_world example, (I used the same project that successfully did the FOTA in my first step as explained above (didn't change anything))

2. I changed the main.c to additionally printk a message ("hello") to notice the difference but it didn't show up as it rebooted (meaning it has went back to the previous code on the board)

Let me know if you want me to upload any of the mentioned files

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Sigurd Hellesvik — Fri, 13 Sep 2024 06:46:44 GMT

Thanks for the explanation, things are more clear to me now.

I have two comments:

First: When using test&confirm, the app assumes that the new app will have BLE so it can send a confirm command to it. This will be an issue when updating from peripheral LBS to hello world, as hello world does not have BLE.

Second: When you DFU the Peripheral LBS sample, did you change anything in the code before the DFU?
If the DFU is exactly the same as the running code, the DFU will be ignored. No need to update to the same after all.

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Saman Niksiar — Wed, 11 Sep 2024 18:31:49 GMT

To learn about DFU over the air, I started with the `peripheral_lbs` and `hello_world` examples. First, I flashed the `peripheral_lbs` example onto the board. Then, I used FOTA to update the board with the `hello_world` example, which worked as expected—the board rebooted and displayed "hello world."

Next, I added external flash support to the `peripheral_lbs` example code, incorporating child_image overlays and configurations, and flashed this updated code onto the board. When I tried to use FOTA to flash the `hello_world` example again, the board did not accept the update and reverted to the previously flashed code.

I then made changes to `main.c` in my modified `peripheral_lbs` code (with external flash support) but did not flash it directly. Instead, I built the project and attempted to send the DFU update via my phone. However, the board still did not accept the FOTA update and reverted to the existing code that I had previously flashed.

Please let me know if you need further explanation or additional details.

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Sigurd Hellesvik — Wed, 11 Sep 2024 08:47:16 GMT

Byt then why are you talking about hello world?

I am a bit inquisitive here because if I get the whole picture I can help you the best

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Saman Niksiar — Tue, 10 Sep 2024 18:19:36 GMT

I was able to do DFU with the internal flash (existing example of peripheral_lbs) but when I added the overlay for the external flash even with a new version of the same project (modified main.c) it doesn't update.

This is my terminal output

*** Booting nRF Connect SDK v2.5.1 ***
Starting Bluetooth Peripheral LBS example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fd0
I: data wra: 0, 1c
I: SoftDevice Controller build revision: 
I: c5 93 ba a9 14 4d 8d 05 |.....M..
I: 30 4e 9b 92 d7 71 1e e8 |0N...q..
I: aa 02 50 3c             |..P<    
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 197.47763 Build 2370639017
I: No ID address. App must call settings_load()
Bluetooth initialized
I: Identity: E9:8B:53:AC:D8:80 (random)
I: HCI: version 5.4 (0x0d) revision 0x1102, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x1102
Flash erased successfully
Advertising successfully started
W: Ignoring data for unknown channel ID 0x003a
I: Image index: 0, Swap type: none
I: Image index: 0, Swap type: none
I: Image index: 0, Swap type: none
I: Image index: 0, Swap type: none
I: Image index: 0, Swap type: test
*** Booting nRF Connect SDK v2.5.1 ***
Starting Bluetooth Peripheral LBS example
I: 2 Sectors of 4096 bytes
I: alloc wra: 0, fe8
I: data wra: 0, 0
I: SoftDevice Controller build revision: 
I: c5 93 ba a9 14 4d 8d 05 |.....M..
I: 30 4e 9b 92 d7 71 1e e8 |0N...q..
I: aa 02 50 3c             |..P<    
I: HW Platform: Nordic Semiconductor (0x0002)
I: HW Variant: nRF52x (0x0002)
I: Firmware: Standard Bluetooth controller (0x00) Version 197.47763 Build 2370639017
I: No ID address. App must call settings_load()
Bluetooth initialized
I: Identity: E9:8B:53:AC:D8:80 (random)
I: HCI: version 5.4 (0x0d) revision 0x1102, manufacturer 0x0059
I: LMP: version 5.4 (0x0d) subver 0x1102
Flash erased successfully
Advertising successfully started
W: Ignoring data for unknown channel ID 0x003a

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Sigurd Hellesvik — Tue, 10 Sep 2024 06:02:58 GMT

Aha, I see.

So you are able to do DFU first, but then when you upload hello_world, and use test&confirm, the image runs hello world only once and then changes back to peripheral LBS?

If so, are you able to DFU to a new version of peripheral LBS?

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Saman Niksiar — Mon, 09 Sep 2024 20:45:52 GMT

Yes my mcuboot.conf and mcuboot.overlay are exactly the same as the folder you mentioned for both my peripheral_lbs example and the hello_world which I want to flash.

This is picture of my dfu package I am trying to flash if that helps

Even though it says success once I flash with Test and Confirm, it doesn't run the main.c of the hello_world and loops back to the peripheral_lbs main.c

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Sigurd Hellesvik — Mon, 09 Sep 2024 06:59:29 GMT

Thanks for the answers!

The error you get is typical for missing external flash overlays for the MCUboot child image. Have you set those in the "child_image" folder of your project, as described in the DevAcademy course, aka a folder that looks like this one?

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Saman Niksiar — Fri, 06 Sep 2024 17:06:29 GMT

Thanks. Yes I have done with the peripheral_lbs example and the app_update.bin generated for the hello world example.

I uploaded that to my phone and used the nRF connect app to upload it and it was succesful.

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Sigurd Hellesvik — Fri, 06 Sep 2024 11:20:44 GMT

Hi,

I will continue to help with this ticket.

First, i cleaned up the ticket by moving your code snippets to Insert->Code. Please use this in the future to paste code, so we dont have to scroll for miles to see the whole ticket.

Secondly, let me take a step back: Have you ever done DFU with a sample and the DK successfully before?

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Saman Niksiar — Wed, 04 Sep 2024 22:07:16 GMT

Hi,

From the memory report I see that my flash_primary and external_flash address are the same as the picture included in this course:

https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/topic/exercise-2-dfu-over-usb-adding-external-flash/

Also on my partitions.yml file my external flash’s address comes after my internal flash.

The app_update I refer to is what is generated in build → zephyr → app_update.bin

I have attached it below for your consideration

Also, Could you please link the tutorial you refer to if its different from what I mentioned above.

Thank you

devzone.nordicsemi.com/.../5444.app_5F00_update.bin

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Simonr — Tue, 03 Sep 2024 07:35:08 GMT

What is the app_update you refer to here exactly? Are you sure the start address of the secondary (external flash slot) is set to the start of the external flash device and not on the internal flash. Please try debugging and/or comparing your application to the one in the DevAcademy as there must be something you're missing here.

Best regards,

Simon

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Saman Niksiar — Fri, 30 Aug 2024 21:27:53 GMT

Hi, I managed to access the external flash as show on the memory report

Now when I try to flash the app_update of a simple hello_world application I face the following error (Image in secondary slot is not valid) followed by rebooting to the main app on the DK

Although when using the peripheral_lbs example I successfully uploaded the same file and it allowed to flash.

I wanted to know why with the external flash the invalid app is triggered and how can I fix it?

For reference here are my config , main and partition codes.

Also, I tried using both nRF connect and nRF device manager apps to flash and tried flashing both app_update and application.zip files but faced the same error

prj.conf

CONFIG_NCS_SAMPLES_DEFAULTS=y
CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y
CONFIG_BT_DEVICE_NAME="Nordic_LBS"
# Enable the LBS service

CONFIG_BT_LBS=y

CONFIG_BT_LBS_POLL_BUTTON=y

CONFIG_DK_LIBRARY=y

CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048

# STEP 2 - Enable MCUboot and FOTA

CONFIG_BOOTLOADER_MCUBOOT=y

CONFIG_NCS_SAMPLE_MCUMGR_BT_OTA_DFU=y

CONFIG_BOOT_SIGNATURE_KEY_FILE=""

CONFIG_SECURE_BOOT_VALIDATION=n

Mcuboot.conf

# Enable logging for MCUboot
CONFIG_LOG=y

CONFIG_MCUBOOT_LOG_LEVEL_WRN=y

# STEP 6.2 - Enable QSPI drivers for external flash

CONFIG_NORDIC_QSPI_NOR=y

CONFIG_BOOT_MAX_IMG_SECTORS=256

CONFIG_MCUBOOT_INDICATION_LED=y

Main.c

#include <zephyr/types.h>

#include <zephyr/kernel.h>

#include <zephyr/bluetooth/bluetooth.h>

#include <zephyr/bluetooth/gatt.h>

#include <bluetooth/services/lbs.h>

#define DEVICE_NAME CONFIG_BT_DEVICE_NAME

#define DEVICE_NAME_LEN (sizeof(DEVICE_NAME) - 1)

static const struct bt_data ad[] = {

BT_DATA_BYTES(BT_DATA_FLAGS, BT_LE_AD_GENERAL | BT_LE_AD_NO_BREDR),

BT_DATA(BT_DATA_NAME_COMPLETE, DEVICE_NAME, DEVICE_NAME_LEN),

};

static const struct bt_data sd[] = {

BT_DATA_BYTES(BT_DATA_UUID128_ALL, BT_UUID_LBS_VAL),

};

int main(void)

{

int err;

printk("Starting Bluetooth Peripheral LBS example\\n");

err = bt_enable(NULL);

if (err) {

printk("Bluetooth init failed (err %d)\\n", err);

return 0;

}

printk("Bluetooth initialized\\n");

if (IS_ENABLED(CONFIG_SETTINGS)) {

settings_load();

}

err = bt_le_adv_start(BT_LE_ADV_CONN, ad, ARRAY_SIZE(ad), sd, ARRAY_SIZE(sd));

if (err) {

printk("Advertising failed to start (err %d)\\n", err);

return 0;

}

printk("Advertising successfully started\\n");

while (1) {

k_sleep(K_SECONDS(1));  // Keep the system alive

}

}

Partitions.yml

app:

address: 0xc200

end_address: 0xfe000

region: flash_primary

size: 0xf1e00

external_flash:

address: 0xf2000

end_address: 0x800000

region: external_flash

size: 0x70e000

mcuboot:

address: 0x0

end_address: 0xc000

placement:

before:

- mcuboot_primary

region: flash_primary

size: 0xc000

mcuboot_pad:

address: 0xc000

end_address: 0xc200

placement:

align:

start: 0x1000

before:

- mcuboot_primary_app

region: flash_primary

size: 0x200

mcuboot_primary:

address: 0xc000

end_address: 0xfe000

orig_span: &id001

- mcuboot_pad

- app

region: flash_primary

size: 0xf2000

span: *id001

mcuboot_primary_app:

address: 0xc200

end_address: 0xfe000

orig_span: &id002

- app

region: flash_primary

size: 0xf1e00

span: *id002

mcuboot_secondary:

address: 0x0

device: DT_CHOSEN(nordic_pm_ext_flash)

end_address: 0xf2000

placement:

align:

start: 0x4

region: external_flash

share_size:

- mcuboot_primary

size: 0xf2000

settings_storage:

address: 0xfe000

end_address: 0x100000

placement:

align:

start: 0x1000

before:

- end

region: flash_primary

size: 0x2000

sram_primary:

address: 0x20000000

end_address: 0x20040000

region: sram_primary

size: 0x40000

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Simonr — Fri, 30 Aug 2024 06:02:03 GMT

I'd strongly suggest you check out the DevAcademy course on bootloaders and DFU FOTA on your end.

Best regards,

Simon

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Saman Niksiar — Thu, 29 Aug 2024 17:49:43 GMT

Hi and thanks for the quick response
Here is the error I am getting indicating a "FLASH" overflow by 48264 bytes
I am using SDK v2.5.1

RE: Implementing FOTA on nRF52840 DK Using External QSPI Flash (MX25R64)

Simonr — Thu, 29 Aug 2024 13:55:10 GMT

Before ensuring that the app that needs more flash space here, I think we need to clarify a few points. First off, what exactly is overflowing? It's often when adding external flash in MCUBoot that the MCUBoot overflows because it needs QSPI drivers, but please upload a snippet of the flash overflow itself, so we can see what exactly is causing this overflow, so we can make sure it's the application and not MCUBoot getting the flash overflow.

We also have a course on the DevAcademy on adding external flash to your bootloader available here that should be useful in this case. Please check it out: https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/

And finally, which SDK version are you using for development?

Best regards,

Simon