Attachments (0)
Nordic Case Info
  • Case ID: 325534
Options

Unexpected warning message: partition_manager.cmake says I do not use pm_static.yml, even though it is there.

puz_md

Hello,

I am using a nRF5340 with mcuboot and multiple customer-specific partitions.
I did not finish creating a separate board definition yet. Currently, we are using the nRF5340-DK board definition and remove development kit specific items while adding our components. Just for reference.
Concerning the partitions, I created pm_static.yml in out project's base directory (where src/, build/ and child_image/ directories also reside). The partition handling seemed to work in our main application.

When I perform a pristine build, I receive an error message, telling me that I would not use a static partition configuration (pm_static.yml). although it is there.

...and if I double-click on the message, I see this piece of code in partition_manager.cmake:

What went wrong here? Is my pm_static.yml applied successfully?

Best regards,
Michael

Parents
  • 0

    Hello Michael,

    What went wrong here? Is my pm_static.yml applied successfully?

    Interesting. I added this warning, so I would very much like to figure out why it is wrong.

    Could you add the following in partition_manager.cmake, just before the if()?

    Regards,
    Sigurd Hellesvik

  • 0 in reply to Sigurd Hellesvik

    Hi Sigurd,

    sorry for the delay, I was very busy over the last weeks and just came back from a short holiday today.

    I also tried our your test code:

    I wonder why secure boot is enabled in the debug output, and mcuboot is not enabled even though I use ist. I do not use TFM or non-secure code.

    This is my prj.conf:

    Best regards,

    Michael

  • 0 in reply to Julia Taylor

    It is 4 months since I wrote that, so unfortunately I can no longer remember what my point was

  • +1 in reply to Sigurd Hellesvik

    Hi, let me summarize how I resolved the issue on my side:

    1. SDK v2.5.3 via multi-image build

    The only solution was to put a pm_static.yml file directly into the net core sample's directory (e.g. C:\ncs\v2.5.3\zephyr\samples\bluetooth\hci_rpmsg\pm_static.yml). This is kind of dirty because the static partitioning will be used by all projects compiled on this computer. Further, there is a risk if someone else pulls the project from the repository and forgets to update their SDK directory with the pm_static-yml, the code will link to the wrong location.

    2. SDK v2.9.0 via sysbuild

    Create the following line(s) in sysbuild.cmake in your project directory. It will use pm_static_NETCORE in your project directory as the net core's static partitioning file.

    Further, there is a bug in the SDK that must be fixed for the lines mentioned above to work as expected: Go to C:\ncs\v2.9.0\nrf\cmake\sysbuild\partition_manager.cmake, line 126, and comment out the following instruction with a hashtag:

    So there is still a bug in the SDK that would come with some risk in multi-developer teams and for filed projects, but the fix is not application-specific anymore (you can use the same fix with multiple projects that use different net core partitioning). I hope it will be included in the SDK soon. Please mind that it is not included in recend SDK v2.9.1 yet!

    Net core update problems on SDK v2.9.0 via sysbuild

    You may also want to check out my other ticket here which describes a bug in mcuboot when trying to update the net core with SDK v2.9.0 (and most likely 2.9.1).

    Good luck with your projects!
    Michael

  • 0 in reply to puz_md

    Hi,

    I have tried the solution for NCS 2.9.0, but it doesn’t seem to be working.

    • I created the sysbuild.cmake file and the pm_static_CPUNET.yml inside my project directory (at the same level as prj.conf, CMakeLists.txt, etc.).
    • I commented out line 126 in cmake/sysbuild/partition_manager.cmake.

    When doing a pristine build, I can see the status message showing the correct pm_static_CPUNET.yml file location
    -- sysbuild.cmake - hci_ipc_PM_STATIC_YML_FILE: /Users/.../pm_static_CPUNET.yml

    However, if I modify the sectors inside the pm_static_CPUNET.yml, it has no effect.
    (= the partition_manager_report is same as without the changes)

    Best regards,
    Milan

  • 0 in reply to msedlak

    Hi, do you use the hci_ipc module for the NET core? Or hci_radio? With the latter, you might have to change the target name in the sysbuild.cmake definition.

    I think this concept is still a bit instransparent... you don't set the static partitioning for the core itself (or for sysbuild), but for the main application running on the core. Which is then forwarded to the linker.

    Best regards,
    Michael

  • 0 in reply to puz_md

    Hi Michael,

    We do have IPC Radio, so changing the name in sysbuild.cmake to "ipc_radio_PM_STATIC_YML_FILE" did the trick.

    Interestingly, it doesn’t seem to include the app image region.
    When using the appcore pm_static, I get this output — and it looks legit:


    But for the netcore, the partition related to the app (ipc_radio) is missing.
    Additionally, there’s a warning message:


    Best Regards,
    Milan

Reply
  • 0 in reply to puz_md

    Hi Michael,

    We do have IPC Radio, so changing the name in sysbuild.cmake to "ipc_radio_PM_STATIC_YML_FILE" did the trick.

    Interestingly, it doesn’t seem to include the app image region.
    When using the appcore pm_static, I get this output — and it looks legit:


    But for the netcore, the partition related to the app (ipc_radio) is missing.
    Additionally, there’s a warning message:


    Best Regards,
    Milan

Children
  • 0 in reply to msedlak

    Hi Milan,

    if I remember correctly, the first screenshot is normal output and I have something similar, too - it just tells you that the partitions are statically defined and the system doesn't try to place them arbitrarily.

    I checked and I have the second screenshot's warning message, too... probably the build system overwrites some arbitrarily generated partitioning file with the configured static partitioning file. At least you can check in the build directory which partition offsets/sizes were actually used in the build.

    Best regards,
    Michael

  • 0 in reply to puz_md

    Hi,

    Yes, the first screenshot is correct — the point is that the second screenshot (cpunet) is missing any information about the app_image.

    I would expect to see something like:

    “Partition ‘app_image’ is not included.”

    Currently, if I modify the app memory region in pm_static_CPUNET.yml, the change has no effect.
    However, if I modify the b0n memory region, the change is reflected (e.g., memory overflow errors, etc.).

    Thank you.
    Best Regards,
    Milan

  • 0 in reply to msedlak

    Hi, if I remember correctly, the app region is used as a placeholder to place the main application or so... maybe this could be the reason? Please check in the Nordic Academy courses about partitions. Unfortunately, I can't help you with this, as I'm still struggling with some aspects of the build system myself.

    I would suggest to automatically create a net core partitioning file and use it as basis for your pm_static_NETCORE.yml. In this file, there should be a partition for ipc_radio or so which you could move (togther with the app partition... it is a bit confusing with overlapping partition names).

    Best regards,
    Michael

  • 0 in reply to puz_md

    Hi Michael,

    Yes, the pm_static_CPUNET file is taken over from the dynamic build, and has correct definitions.

    The point is, since the netcore contains both B0n and the app, the solution you provided works only for the B0n partition on the netcore, but not for the app partition.

    That’s why the second screenshot shows only:
    Partition 'b0n' is not included in the dynamic resolving since it is statically defined.
    Partition 'b0n_container' is not included in the dynamic resolving since it is statically defined.
    Partition 'provision' is not included in the dynamic resolving since it is statically defined.

    But it’s missing:
    Partition 'app_image' is not included in the dynamic resolving since it is statically defined.

    (which is visible in the first screenshot, as the pm_static for the APPCore works correctly).

    => the app region from pm_static_CPUNET.yml is not taken into account — only the b0n region is.

    Sure, no problem.

    Thank you.
    BR.
    Milan

  • 0 in reply to msedlak

    Hi Milan,

    I don't know what your 'app_image' partition is as I don't have it in my setup. Though I can say that neither for the net core nor for the app core, I have this 'not included' message for the main image (which would be hci_ipc on the net core in my case). In my case, moving the 'hci_ipc' partition to reserve some extra space to b0n for possible future updates worked without any problems.

    One more hint I can give you: Check if there are flash pages not covered by any partition in your net core pm_static. I remember reading somewhere that the 'app' partition was just a placeholder for the remaining free space which is eventually used for the main application. If you want to add some reserved unused space to your pm_static, create a dummy partition for it. And in my setup, 'app' and 'hci_ipc' are overlapping partitions with exactly the same offset and size (where 'app' has this strange span syntax included).

    Best regards,
    Michael

Terms of service