Trouble building with mcuboot.

[dlewis]

Hi All,

I am getting build errors for a project. Project specifics below:
- nRF52832 (custom board)
- NCS v2.6.0
- Custom board files and other configuration files attached. pm_static.yaml included as text because file type not supported for upload.
1348.centurion_anywhere_button.zip00355.prj.conf3566.mcuboot.conf

### pm_static.yaml ###
partitions:
  mcuboot:
    address: 0x00000000
    size: 0x000C0000  # 48 KB
    region: flash_primary

  image-0:
    address: 0x000C0000
    size: 0x00032000  # 200 KB
    region: flash_primary

  image-1:
    address: 0x003E0000
    size: 0x00032000  # 200 KB
    region: flash_primary

  image-scratch:
    address: 0x00700000
    size: 0x0000A000  # 40 KB
    region: flash_primary

  storage:
    address: 0x007A0000
    size: 0x00006000  # 24 KB
    region: flash_primary

regions:
  flash_primary:
    device: flash0
    size: 0x00080000  # 512 KB

Attached below is the build error(s) I am receiving. Any insight on what the issue may be would be greatly appreciated!

[Sigurd Hellesvik]

dlewis said:

oving the partitions.yml to be the pm_static.yml.

Right, this is one of the use-cases.

In my mind there are two use-cases for pm_static.yml:

1. Freezing partitioning for DFU. This is required for release.
   1. Not needed for developing.
   2. Done by copying partitions.yml
2. Adding a custom partition
   1. Only define the custom partition, and the partition manager will try to dynamically partition around this

dlewis said:

Now when building it would get past the previous issues but it would give a warning about not having a pm_static.yml file.

I added this warning, and it is to remind users of the Static partition requirement for DFU.

This being said, there should be no change in an app which does not use pm_static.yml, and an app that uses the same pm_static.yml as build/partitions.yml. This just freezes the partition, so that you can never change partitioning again.

In other words, unless you are developing for release now, I do not think pm_static.yml is the solution to your issue.

[dlewis]

Thanks for the information. The issue seems to be resolved now. I reinstalled vs code and the sdk/toolchain and the issue seemed to have gone away.