FOTA fails from NCS 1.3.2 to NCS 2.5.1

RE: FOTA fails from NCS 1.3.2 to NCS 2.5.1

Hakon — Fri, 05 Apr 2024 12:44:14 GMT

[quote user="Umer Mahmood"]I can see that its address is not a multiple of SPU requirement of 0x4000[/quote]

The requirement for nrf9160 is 0x8000. You can try this pm_static.yml instead;

EMPTY_0:
  address: 0xc000
  end_address: 0x10000
  placement:
    before:
    - mcuboot_pad
  region: flash_primary
  size: 0x4000
app:
  address: 0x18000
  end_address: 0x80000
  region: flash_primary
  size: 0x68000
mcuboot:
  address: 0x0
  end_address: 0xc000
  placement:
    before:
    - mcuboot_primary
  region: flash_primary
  size: 0xc000
mcuboot_pad:
  address: 0x10000
  end_address: 0x10200
  placement:
    align:
      start: 0x8000
    before:
    - mcuboot_primary_app
  region: flash_primary
  size: 0x200
mcuboot_primary:
  address: 0x10000
  end_address: 0x88000
  orig_span: &id001
  - mcuboot_pad
  - spm
  - app
  region: flash_primary
  sharers: 0x1
  size: 0x78000
  span: *id001
mcuboot_primary_app:
  address: 0x10200
  end_address: 0x88000
  orig_span: &id002
  - app
  - spm
  region: flash_primary
  size: 0x77e00
  span: *id002
mcuboot_secondary:
  address: 0x88000
  end_address: 0x100000
  placement:
    after:
    - mcuboot_primary
    align:
      start: 0x1000
  region: flash_primary
  share_size:
  - mcuboot_primary
  size: 0x78000
mcuboot_sram:
  address: 0x20000000
  end_address: 0x20008000
  orig_span: &id003
  - tfm_sram
  region: sram_primary
  size: 0x8000
  span: *id003
nonsecure_storage:
  address: 0x80000
  end_address: 0x82000
  orig_span: &id004
  - settings_storage
  region: flash_primary
  size: 0x2000
  span: *id004
nrf_modem_lib_ctrl:
  address: 0x20008000
  end_address: 0x200084e8
  inside:
  - sram_nonsecure
  placement:
    after:
    - tfm_sram
    - start
  region: sram_primary
  size: 0x4e8
nrf_modem_lib_rx:
  address: 0x2000a568
  end_address: 0x2000c568
  inside:
  - sram_nonsecure
  placement:
    after:
    - nrf_modem_lib_tx
  region: sram_primary
  size: 0x2000
nrf_modem_lib_sram:
  address: 0x20008000
  end_address: 0x2000c568
  orig_span: &id005
  - nrf_modem_lib_ctrl
  - nrf_modem_lib_tx
  - nrf_modem_lib_rx
  region: sram_primary
  size: 0x4568
  span: *id005
nrf_modem_lib_tx:
  address: 0x200084e8
  end_address: 0x2000a568
  inside:
  - sram_nonsecure
  placement:
    after:
    - nrf_modem_lib_ctrl
  region: sram_primary
  size: 0x2080
otp:
  address: 0xff8108
  end_address: 0xff83fc
  region: otp
  size: 0x2f4
settings_storage:
  address: 0x80000
  end_address: 0x82000
  inside:
  - nonsecure_storage
  placement:
    align:
      start: 0x8000
    before:
    - end
  region: flash_primary
  size: 0x2000
sram_nonsecure:
  address: 0x20008000
  end_address: 0x20040000
  orig_span: &id006
  - sram_primary
  - nrf_modem_lib_ctrl
  - nrf_modem_lib_tx
  - nrf_modem_lib_rx
  region: sram_primary
  size: 0x38000
  span: *id006
sram_primary:
  address: 0x2000c568
  end_address: 0x20040000
  region: sram_primary
  size: 0x33a98
sram_secure:
  address: 0x20000000
  end_address: 0x20008000
  orig_span: &id007
  - tfm_sram
  region: sram_primary
  size: 0x8000
  span: *id007
tfm:
  address: 0x10200
  end_address: 0x18000
  placement:
    before:
    - app
  region: flash_primary
  size: 0x7e00
tfm_nonsecure:
  address: 0x18000
  end_address: 0x80000
  orig_span: &id008
  - app
  region: flash_primary
  size: 0x68000
  span: *id008
tfm_secure:
  address: 0x10200
  end_address: 0x18000
  orig_span: &id009
  - tfm
  region: flash_primary
  size: 0x7e00
  span: *id009
tfm_sram:
  address: 0x20000000
  end_address: 0x20008000
  inside:
  - sram_secure
  placement:
    after:
    - start
  region: sram_primary
  size: 0x8000

RE: FOTA fails from NCS 1.3.2 to NCS 2.5.1

Umer Mahmood — Fri, 23 Feb 2024 14:50:30 GMT

I tried the following as per the migration guide:
- copied partition.yml from NCS 1.3.2 app's build folder to NCS 2.5.1 based apps root as pm_static.yml
- renamed all instances of spm to tfm
- added tfm non_secure and tfm_secure partitions

The pm_static.ym looks as follows:

EMPTY_0:
  address: 0xc000
  placement:
    before:
      - mcuboot_pad
  region: flash_primary
  size: 0x4000
app:
  address: 0x1c200
  region: flash_primary
  size: 0x6be00
mcuboot:
  address: 0x0
  placement:
    before:
      - mcuboot_primary
  region: flash_primary
  size: 0xc000
mcuboot_pad:
  address: 0x10000
  placement:
    align:
      start: 0x8000
    before:
      - mcuboot_primary_app
  region: flash_primary
  size: 0x200
mcuboot_primary:
  address: 0x10000
  orig_span: &id001
    - app
    - tfm
    - mcuboot_pad
  region: flash_primary
  sharers: 0x1
  size: 0x78000
  span: *id001
mcuboot_primary_app:
  address: 0x10200
  orig_span: &id002
    - app
    - tfm
  region: flash_primary
  size: 0x77e00
  span: *id002
mcuboot_secondary:
  address: 0x88000
  placement:
    after:
      - mcuboot_primary
    align:
      start: 0x1000
  region: flash_primary
  share_size:
    - mcuboot_primary
  size: 0x78000
otp:
  address: 0xff8108
  region: otp
  size: 0x2f4
tfm:
  address: 0x10200
  inside:
    - mcuboot_primary_app
  placement:
    before:
      - app
  region: flash_primary
  size: 0xc000
tfm_nonsecure:
  address: 0x1c200
  orig_span: &id008
    - app
  region: flash_primary
  size: 0x60000
  span: *id008
tfm_secure:
  address: 0x10000
  orig_span: &id009
    - mcuboot_pad
    - tfm
  region: flash_primary
  span: *id009
  size: 0x10000

But now I get alignment error for tfm_nonsecure partitions. I can see that its address is not a multiple of SPU requirement of 0x4000, but it depends on start address of the app. Now, I want to keep the start address of the app same, as the start address of the app in NCS 1.3.2 based app. How do I fix this error? or for the FOTA to work I only have to match mcuboot_primary and mcuboot_secondary address, and can change app start address.

RE: FOTA fails from NCS 1.3.2 to NCS 2.5.1

JONATHAN LL — Fri, 23 Feb 2024 09:02:52 GMT

Hi,

We have the migration guide here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/security/tfm.html#migrating-from-secure-partition-manager-to-trusted-firmware-m advise on following that to start with.

Regards,
Jonathan

RE: FOTA fails from NCS 1.3.2 to NCS 2.5.1

Umer Mahmood — Wed, 21 Feb 2024 17:56:49 GMT

I added a file pm_static.yml to the root dir of NCS 2.5.1 based application, with same app and mcuboot addresses and sizes as in the NCS 1.3.2 based application in the root dir of the project with following contents:

app:
  address: 0x1c200
  region: flash_primary
  size: 0x6be00
mcuboot:
  address: 0x0
  placement:
    before:
      - mcuboot_primary
  region: flash_primary
  size: 0xc000

but this results in build time error:

-- Found partition manager static configuration: nrf91_app_firmware_ncs_2_5/pm_static.yml
Partition 'mcuboot' is not included in the dynamic resolving since it is statically defined.
Dropping partition 'nrf_modem_lib_trace' since its size is 0.
Partition manager failed: Error when inspecting mcuboot_pad, invalid address 0x8000, expected 0xc000,
Failed to partition region flash_primary, size of region: 1048576
Partition Configuration:
app:
  size: 441856
mcuboot:
  placement:
    before:
    - mcuboot_primary
  size: 49152
mcuboot_pad:
  placement:
    align:
      start: 32768
    before:
    - mcuboot_primary_app
  size: 512
mcuboot_secondary:
  placement:
    after:
    - mcuboot_primary
    align:
      start: 32768
  size: 458752
settings_storage:
  placement:
    align:
      start: 32768
    before:
    - end
  size: 8192
tfm:
  placement:
    before:
    - app
  size: 65024

-- Configuring incomplete, errors occurred!