nrf5340 - FLASH overflow issue

RE: nrf5340 - FLASH overflow issue

Gabriele — Thu, 24 Oct 2024 14:34:39 GMT

No problem, thank you Andreas

RE: nrf5340 - FLASH overflow issue

AHaug — Thu, 24 Oct 2024 14:03:44 GMT

Hi,

Apologies for the lack of response.

I see that you're getting help with this issue in your latest reply. I will have a look at the discussion and discuss it with the engineer handling that request.

Kind regards,
Andreas

RE: nrf5340 - FLASH overflow issue

Gabriele — Fri, 18 Oct 2024 15:15:45 GMT

Hi Andreas,

Following your advices I was able to move the mcuboot_secondary into external_flash.
This required to fix pm_partition.yml and child_image/mcuboot.overlay.

Here the mparts output:

  external_flash (0x900000 - 9216kB): 
+------------------------------------------------+
| 0x0: mcuboot_secondary (0xe0000 - 896kB)       |
| 0x0: test (0x2000 - 8kB)                       |
| 0x2000: data (0xfe000 - 1016kB)                |
| 0xe0000: mcuboot_secondary_1 (0x40000 - 256kB) |
| 0x120000: external_flash (0x6e0000 - 7040kB)   |
| 0x900000: littlefs_storage (0x0 - 0B)          |
+------------------------------------------------+

  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: app (0xabe00 - 687kB)                   |
| 0xbc000: netcore_dfu (0x40000 - 256kB)           |
| 0xfc000: settings_storage (0x2000 - 8kB)         |
| 0xfe000: cosmed_pad (0x1000 - 4kB)               |
| 0xff000: cosmed_env (0x1000 - 4kB)               |
+--------------------------------------------------+

  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_ipc (0x37800 - 222kB)       |
+--------------------------------------------+

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

A new problem arises when I enable the secure boot option.
If I set the prj.conf option CONFIG_SECURE_BOOT=y, the build gets done, but the J-Link flashing process won't work.
The board remains completely silent.

Here's the mparts output:

  external_flash (0x900000 - 9216kB): 
+------------------------------------------------+
| 0x0: mcuboot_secondary (0xe0000 - 896kB)       |
| 0x0: test (0x2000 - 8kB)                       |
| 0x2000: data (0xfe000 - 1016kB)                |
| 0xe0000: mcuboot_secondary_1 (0x40000 - 256kB) |
| 0x120000: external_flash (0x6e0000 - 7040kB)   |
| 0x900000: littlefs_storage (0x0 - 0B)          |
+------------------------------------------------+

  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: b0_container (0x8000 - 32kB)----------+
| 0x10200: b0 (0x8000 - 32kB)                      |
+---0x18200: app_image (0x51f00 - 327kB)-----------+
+---0x18200: s0 (0x51f00 - 327kB)------------------+
+---0x18200: s0_image (0x51f00 - 327kB)------------+
| 0x18200: app (0x51f00 - 327kB)                   |
+---0x6a100: s1 (0x51f00 - 327kB)------------------+
| 0x6a100: s1_image (0x51f00 - 327kB)              |
+--------------------------------------------------+
| 0xbc000: netcore_dfu (0x40000 - 256kB)           |
| 0xfc000: settings_storage (0x2000 - 8kB)         |
| 0xfe000: cosmed_pad (0x1000 - 4kB)               |
| 0xff000: cosmed_env (0x1000 - 4kB)               |
+--------------------------------------------------+

  otp (0x2fc - 764B): 
+------------------------------------+
| 0xff8100: provision (0x280 - 640B) |
| 0xff8380: otp (0x7c - 124B)        |
+------------------------------------+

  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_ipc (0x37800 - 222kB)       |
+--------------------------------------------+

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

Can you help please ?

RE: nrf5340 - FLASH overflow issue

AHaug — Tue, 10 Sep 2024 12:54:57 GMT

Thank you,

It looks like both your application slots (mcuboot_primary_app and mcuboot_secondary) are located in the internal flash, i.e:

mcuboot_primary:
  address: 0x10000
  end_address: 0x64000
  orig_span: &id001
  - app
  - mcuboot_pad
  region: flash_primary
  sharers: 0x1
  size: 0x54000
  span: *id001
mcuboot_primary_app:
  address: 0x10200
  end_address: 0x64000
  orig_span: &id002
  - app
  region: flash_primary
  size: 0x53e00
  span: *id002
mcuboot_secondary:
  address: 0x64000
  end_address: 0xb8000
  placement:
    after:
    - mcuboot_primary
    align:
      start: 0x4000
    align_next: 0x4000
  region: flash_primary
  share_size:
  - mcuboot_primary
  size: 0x54000

I assume that you would like to have the secondary slot on the external flash? If so, could you have a look at 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/ to see if you're able to spot a configuration that you're missing?

Kind regards,
Andreas

RE: nrf5340 - FLASH overflow issue

Gabriele — Tue, 10 Sep 2024 12:14:17 GMT

here you are Andreas

EMPTY_0:
  address: 0xb8000
  end_address: 0xbc000
  placement:
    after:
    - mcuboot_secondary
  region: flash_primary
  size: 0x4000
app:
  address: 0x10200
  end_address: 0x64000
  region: flash_primary
  size: 0x53e00
cosmed_env:
  address: 0xff000
  end_address: 0x100000
  placement:
    after:
    - settings_storage
  region: flash_primary
  size: 0x1000
cosmed_pad:
  address: 0xfe000
  end_address: 0xff000
  placement:
    after:
    - settings_storage
  region: flash_primary
  size: 0x1000
data:
  address: 0x0
  end_address: 0x100000
  region: external_flash
  size: 0x100000
external_flash:
  address: 0x100000
  end_address: 0x100000
  region: external_flash
  size: 0x0
mcuboot:
  address: 0x0
  end_address: 0x10000
  placement:
    before:
    - mcuboot_primary
  region: flash_primary
  size: 0x10000
mcuboot_pad:
  address: 0x10000
  end_address: 0x10200
  placement:
    before:
    - mcuboot_primary_app
  region: flash_primary
  size: 0x200
mcuboot_primary:
  address: 0x10000
  end_address: 0x64000
  orig_span: &id001
  - app
  - mcuboot_pad
  region: flash_primary
  sharers: 0x1
  size: 0x54000
  span: *id001
mcuboot_primary_app:
  address: 0x10200
  end_address: 0x64000
  orig_span: &id002
  - app
  region: flash_primary
  size: 0x53e00
  span: *id002
mcuboot_secondary:
  address: 0x64000
  end_address: 0xb8000
  placement:
    after:
    - mcuboot_primary
    align:
      start: 0x4000
    align_next: 0x4000
  region: flash_primary
  share_size:
  - mcuboot_primary
  size: 0x54000
netcore_dfu:
  address: 0xbc000
  end_address: 0xfc000
  placement:
    before:
    - settings_storage
  region: flash_primary
  size: 0x40000
otp:
  address: 0xff8100
  end_address: 0xff83fc
  region: otp
  size: 0x2fc
pcd_sram:
  address: 0x20000000
  end_address: 0x20002000
  placement:
    after:
    - start
  region: sram_primary
  size: 0x2000
rpmsg_nrf53_sram:
  address: 0x20070000
  end_address: 0x20080000
  placement:
    before:
    - end
  region: sram_primary
  size: 0x10000
settings_storage:
  address: 0xfc000
  end_address: 0xfe000
  region: flash_primary
  size: 0x2000
sram_primary:
  address: 0x20002000
  end_address: 0x20070000
  region: sram_primary
  size: 0x6e000

RE: nrf5340 - FLASH overflow issue

AHaug — Tue, 10 Sep 2024 11:38:51 GMT

Hi,

Could you also share your partition map?

You can either upload the generated map in build/partitions.yml, enter "ninja partition_manager_report" in command line or use the built in "memory report" action in VS Code.

Kind regards,
Andreas