NRF9160 Using customized flash partition

RE: NRF9160 Using customized flash partition

Maaike — Mon, 19 Apr 2021 13:34:34 GMT

Hi Carl,

Many thanks, this solved the problem and using the partition works now.
I made the storage_partition smaller in our custom board files (as we still need to use it) and created space for our own custom partition.

Kind regards,
Maaike

RE: NRF9160 Using customized flash partition

Carl Richard — Mon, 19 Apr 2021 10:21:01 GMT

Hi again!

This is failing as the address 0x100000 is outside the flash_primary region. To stay within the region I suggest lowering the NVS partition size using CONFIG_PM_PARTITION_SIZE_NVS_STORAGE and then changing the start address and size of your static partition accordingly.

For example by setting the NVS storage partition size to 0x0 the following pm_static.yml should work:

factory_settings_partition:
   address: 0x1f7d0
   size: 0xE0830
   #span: [example]  # Only if this partition had the span property set originally.

Best regards,
Carl Richard

RE: NRF9160 Using customized flash partition

Maaike — Wed, 14 Apr 2021 07:42:04 GMT

Hi Carl,

Thank you for your reply.

I have added the partition the the pm_static.yml file and it seems that the flash configuration now works well, as I see the partition in the partitions.yml file in the build folder.

However, I now get the following error

fs_nvs: Unable to get page info

It seems that the page of the offset does not exist.

This is my pm_static.yml file:

factory_settings_partition:
   address: 0x00100000
   size: 0x000007d0
   #span: [example]  # Only if this partition had the span property set originally.

And this is what I see in partitions.yml after building

app:
  address: 0xc000
  region: flash_primary
  size: 0xee000
bsdlib_sram:
  address: 0x20010000
  placement:
    after:
    - spm_sram
    - start
  region: sram_primary
  size: 0x10000
factory_settings_partition:
  address: 0x100000
  region: flash_primary
  size: 0x7d0
nvs_storage:
  address: 0xfa000
  placement:
    before:
    - end
  region: flash_primary
  size: 0x6000
otp:
  address: 0xff8108
  region: otp
  size: 0x2f4
spm:
  address: 0x0
  placement:
    before:
    - app
  region: flash_primary
  size: 0xc000
spm_sram:
  address: 0x20000000
  inside:
  - sram_secure
  placement:
    after:
    - start
  region: sram_primary
  size: 0x10000
sram_primary:
  address: 0x20020000
  region: sram_primary
  size: 0x20000
sram_secure:
  address: 0x20000000
  orig_span: &id001
  - spm_sram
  region: sram_primary
  size: 0x10000
  span: *id001

Here is how I initialize flash

static struct nvs_fs fs;
   
static bool set_config_hwver(const char* majorString, const char* minorString)
{   
   
    fs.offset = FLASH_AREA_OFFSET(factory_settings_partition);

    int rc = 0;
    char buf[32];
    
    struct flash_pages_info info;
    rc = flash_get_page_info_by_offs(
        device_get_binding(DT_CHOSEN_ZEPHYR_FLASH_CONTROLLER_LABEL), fs.offset, &info);
    if (rc) {
        printk("rc: %d\n", rc);
        LOG_DBG("Unable to get page info");
    }

    fs.sector_size = info.size;
    fs.sector_count = 3U;
    rc = nvs_init(&fs, DT_CHOSEN_ZEPHYR_FLASH_CONTROLLER_LABEL);
    if (rc) {
        LOG_DBG("Flash Init failed\n");
    }

I am not sure what I am missing, is the offset of my partition defined badly?

Kind regards,
Maaike

RE: NRF9160 Using customized flash partition

Carl Richard — Mon, 12 Apr 2021 14:25:33 GMT

Hi, Maaike!

As Didrik mentioned in the thread you've linked to any device tree configuration of flash partitions are ignored by the Partition Manager script. This script is used by the build system to properly allocate space for multi-image builds, and is thus used for most nRF9160 applications.

I agree that his second option in general is more suitable. The partition manager documentation should cover how to configure your own static partitions and I suggest looking into that. For examples the asset_tracker example defines a static partition configuration for the Thingy:91.

Best regards,
Carl Richard