Unable to flash new firmware with DFU because of 'invalid address'

RE: Unable to flash new firmware with DFU because of 'invalid address'

Vidar Berg — Tue, 25 Jun 2024 07:22:42 GMT

Hello,

Have you already integrated the flash in your application, and is it working? The SDK is currently only supporting QSPI/SPI NOR FLASH, not NAND. There is a PR upstream which aims to add support for NAND, but it has not been merged yet: https://github.com/zephyrproject-rtos/zephyr/pull/50690.

Instructions on how to place the mcuboot secondary slot in an external flash partition can be found in the documentation here:

https://docs.nordicsemi.com/bundle/ncs-2.6.1/page/nrf/config_and_build/bootloaders/bootloader_external_flash.html

But this has only been tested with NOR flash.

RE: Unable to flash new firmware with DFU because of 'invalid address'

BENBF — Mon, 24 Jun 2024 15:55:49 GMT

Hello,

Thank you for your time and the information. After checking the size of our firmware, we realized we were indeed trying to put an application that was too large onto the card. As you recommended, we will try using an external flash for our DFU. Our flash is a NAND Flash (ref: W25N02KVZEIR). Can we use it for the DFU?

Thank you very much for your time and have a great day.

RE: Unable to flash new firmware with DFU because of 'invalid address'

Vidar Berg — Mon, 24 Jun 2024 11:27:55 GMT

I missed this earlier when looking at your memory report, but I see now that you've changed redefined CONFIG_FLASH_SIZE value in your prj.conf. This symbol defines the amount of the flash available to the appcore, which is 1024kB, and should not be changed. Given the size of your application, you will need to include an external SPI flash on your board to support DFU.

RE: Unable to flash new firmware with DFU because of 'invalid address'

BENBF — Mon, 24 Jun 2024 09:52:04 GMT

No worries ! Our SDK version is the v2.6.1.

RE: Unable to flash new firmware with DFU because of 'invalid address'

Vidar Berg — Mon, 24 Jun 2024 09:21:38 GMT

Sorry, I forgot to ask which SDK version you were on. I want to make sure we're debugging the same version.

RE: Unable to flash new firmware with DFU because of 'invalid address'

BENBF — Fri, 21 Jun 2024 14:16:26 GMT

Of course! Here is a minimal version of our project you can run on an nRF7002-DK Nordic devboard. Please don't hesitate to reach out if you need more information. Thank you very much, and have a great day.

devzone.nordicsemi.com/.../bugHunt-_2800_1_2900_.zip

RE: Unable to flash new firmware with DFU because of 'invalid address'

Vidar Berg — Fri, 21 Jun 2024 13:59:10 GMT

The memory layout appears to be correct. Would you be able to share a minimal version of your project here or in a private ticket so I could try to debug this on a development board?

RE: Unable to flash new firmware with DFU because of 'invalid address'

BENBF — Thu, 20 Jun 2024 12:25:12 GMT

Also, if it can help, i noticed that if i try flashing with the app the same app as the one curently on the card, the app will tell me it has been successful and the board will show me this error:

00> [00:03:34.919,891] <err> flash_nrf: invalid address: 0x001bbff0:16
00> [00:03:34.919,891] <inf> mcuboot_util: Secondary image of image pair (0.) is unreachable. Treat it as empty
00> [00:03:34.919,891] <inf> mcuboot_util: Image index: 0, Swap type: none

it s still an error, but a shorter one.

RE: Unable to flash new firmware with DFU because of 'invalid address'

BENBF — Thu, 20 Jun 2024 12:22:18 GMT

Thank you for the quick response, here is the report:

  flash_primary (0x1c0000 - 1792kB): 
+--------------------------------------------------+
| 0x0: mcuboot (0x32000 - 200kB)                   |
| 0x32000: EMPTY_0 (0x2000 - 8kB)                  |
+---0x34000: mcuboot_primary (0xc4000 - 784kB)-----+
| 0x34000: mcuboot_pad (0x200 - 512B)              |
+---0x34200: mcuboot_primary_app (0xc3e00 - 783kB)-+
| 0x34200: app (0xc3e00 - 783kB)                   |
+--------------------------------------------------+
| 0xf8000: mcuboot_secondary (0xc4000 - 784kB)     |
| 0x1bc000: EMPTY_1 (0x4000 - 16kB)                |
+--------------------------------------------------+

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

  sram_primary (0x80000 - 512kB): 
+-----------------------------------------------+
| 0x20000000: sram_primary (0x70000 - 448kB)    |
| 0x20070000: rpmsg_nrf53_sram (0x10000 - 64kB) |
+-----------------------------------------------+

 CPUNET flash_primary (0x40000 - 256kB): 
+--------------------------------------+
+---0x1000000: app (0x40000 - 256kB)---+
| 0x1000000: hci_ipc (0x40000 - 256kB) |
+--------------------------------------+

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

I hope it helps

RE: Unable to flash new firmware with DFU because of 'invalid address'

Vidar Berg — Thu, 20 Jun 2024 12:18:32 GMT

Hello,

The write address shown in the debug log is well above the valid address range for the internal flash. Could you create a memory report of the flash layout and post it here? You can do this using the memory report button in vs code, or with the following command from the terminal

$ west build -t partition_manager_report

Thanks,

Vidar