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

Question

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. 
 [{ "resource": "/c:/ncs/v2.5.2/nrf/cmake/partition_manager.cmake",
 "owner": "nrf-connect",
 "severity": 4,
 "message": "CMake Warning at C:/ncs/v2.5.2/nrf/cmake/partition_manager.cmake:79 (message):",
 "source": "cmake",
 "startLineNumber": 79,
 "startColumn": 1,
 "endLineNumber": 79,
 "endColumn": 2147483647
}] 
 ...and if I double-click on the message, I see this piece of code in partition_manager.cmake: 
 if (NOT static_configuration AND
 (CONFIG_BOOTLOADER_MCUBOOT OR CONFIG_SECURE_BOOT))
 message(WARNING "
 ---------------------------------------------------------------------
 --- WARNING: Using a bootloader without pm_static.yml. ---
 --- There are cases where a deployed product can consist of ---
 --- multiple images, and only a subset of these images can be ---
 --- upgraded through a firmware update mechanism. In such cases, ---
 --- the upgradable images must have partitions that are static ---
 --- and are matching the partition map used by the bootloader ---
 --- programmed onto the device. ---
 ---------------------------------------------------------------------
 
"
 )
endif()
 
 What went wrong here? Is my pm_static.yml applied successfully? 
 Best regards, Michael

puz_md · Accepted Answer

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:
cs\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. 
 set(hci_ipc_PM_STATIC_YML_FILE ${APPLICATION_CONFIG_DIR}/pm_static_CPUNET.yml CACHE INTERNAL "" FORCE)
message(STATUS "sysbuild.cmake - hci_ipc_PM_STATIC_YML_FILE: ${hci_ipc_PM_STATIC_YML_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:
cs\v2.9.0
rf\cmake\sysbuild\partition_manager.cmake , line 126, and comment out the following instruction with a hashtag: 
 #set(static_configuration) 
 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

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

Top Replies