pm_static_nrf5340dk_nrf5340_cpunet not being picked up.

[shlomots]

I am updating my ncs from ncs2.7.0 to 2.9.2. 
I have a dfu application for which the build targer is nrf52840 and nrf5340. 
For this reason, I have pm_static files. for some reason, build system picks up on my pm_static_nrf5340dk_nrf5340_cpuapp.yml but not on the pm_static_nrf5340dk_nrf5340_cpunet.yml. 
I also tried to it from the sysbuild.cmake file as follows: 

set(hci_ipc_PM_STATIC_YML_FILE ${CMAKE_CURRENT_LIST_DIR}/pm_static_nrf5340dk_nrf5340_cpunet.yml CACHE INTERNAL "" FORCE)

but that didnt work as well. 

what is the problem? 
and also, if the "set(hci_ipc_PM_STATIC_YML_FILE ..." would have worked, doesnt that mean I should that something similer for the b0n bootloader?

Thanks in advance, 
Shlomo

[Marte Myrvold]

Hi Shlomo,

This is a bug. It was fixed in v3.0.0, so I recommend migrating to that version if possible. If this is not possible, you can try manually applying the fix: https://github.com/nrfconnect/sdk-nrf/pull/20561.

Best regards,
Marte

[shlomots]

Thanks for the quick response Marte!
what about the second question? 

shlomots said:

and also, if the "set(hci_ipc_PM_STATIC_YML_FILE ..." would have worked, doesnt that mean I should that something similer for the b0n bootloader?

[shlomots]

also, it seems to only work with the 

set(hci_ipc_PM_STATIC_YML_FILE ${CMAKE_CURRENT_LIST_DIR}/pm_static_nrf5340dk_nrf5340_cpunet.yml CACHE INTERNAL "" FORCE)

in the cmake file, still the naming convention didn't do the job, does the bug only fix the problem that it isnt picked up weh using set(hci_ipc_PM_STATIC_YML_FILE ... ? 

[Vidar Berg]

Hello,

Sorry for the delayed response. I inherited this case from Marte and have not really had the time to investigate. But if you are unsure if your PM file is applied correctly, you can check if the partitions_CPUNET.yml file in your build folder matches your static partitioning file. 

Best regards,

Vidar