Configure SPM peripherals without modifying SPM files

[Smitesh Mali]

Hi,

I am using "http_upgrade_ota" project. 

I have added UARTE2 , SPIM3 and WDT peripherals in the application. 

To use this peripherals i had to make change in "spm.c" file as below 

spm_config_peripheral(
NRFX_PERIPHERAL_ID_GET(NRF_UARTE2), 0);

spm_config_peripheral(
NRFX_PERIPHERAL_ID_GET(NRF_SPIM3_S), 0);

spm_config_peripheral(
NRFX_PERIPHERAL_ID_GET(NRF_WDT_S), 0);

There is also one more option (Use macro inside proj.conf )to do this but not for WDT peripheral ( I didn't find macro for WDT )

CONFIG_SPM_NRF_UARTE2_NS=y
CONFIG_SPM_NRF_SPIM3_NS=y

But for both options used above , i need to make change in SPM project which is in the "nrf" folder.

I don't want to make change to "nrf" folder as it is submodule and downloaded from github. 

So is there any other way through which we can configure UARTE 2, SPIM3 and WDT without modifying files inside "nrf" folder ?

Regards,

Smitesh Mali

[Simon]

UPDATE 2/24/2020: Check out this ticket for instructions on how to do this 

---

If you look at the latest commit of the nrf repo, you can see that the the subsys/spm library includes both the UARTE2 and SPIM3, so I don't see any problems of you modifying the library. I am not sure if the WDT will be inlcuded, but I can look into it if you would like so.

Best regards,

Simon

[Smitesh Mali]

Simon,

If i don't write below in spm.c file inside "spm_jump()" function then 

spm doesn't jump to the application 

spm_config_peripheral(
NRFX_PERIPHERAL_ID_GET(NRF_UARTE2), 0);

spm_config_peripheral(
NRFX_PERIPHERAL_ID_GET(NRF_SPIM3_S), 0);

spm_config_peripheral(
NRFX_PERIPHERAL_ID_GET(NRF_WDT_S), 0);

I either need to write above 3 functions in "spm_jump()" function or i need to add macro as i mentioned in above thread 

in the proj.conf.

otherwise "spm" won't jump to application. 

So basically i don't want to make these changes to "nrf" submodule files.

So is it possible ?

Regards,

Smitesh Mali

[Smitesh Mali]

Hi Simon,

But then it will collide with the "CMakeLists.txt"  of "\ncs\nrf\samples\CMakeLists.txt" path.

Both will have below statement

if (CONFIG_SPM)
zephyr_add_executable(spm require_build)
if (${require_build})
add_subdirectory(nrf9160/spm ${CMAKE_BINARY_DIR}/spm)
endif ()
endif()

In application "CMakeLists.txt" file "add_subdirectory(ncs/myfolder/spm ${CMAKE_BINARY_DIR}/spm)" 

path will be different. but it will give error.

[Simon]

Ok. I will ask of the developers of the SPM library of how to go about this.

Best regards,

Simon

[Simon]

I explained your problem to one of the developers, and he said that the intended way of configuring non-secure peripherals was to do it through nrf/subsys/spm/spm.c. If the peripherals was not included you had to either: Modify the SPM library yourself or wait for somebody to add it.

However, somebody could be you, he said the following about modifying the library:

"they can open a pull request to nrf themselves if they like"

"if they have a patch they can just submit it"

Link to the nrf repo: https://github.com/NordicPlayground/fw-nrfconnect-nrf

Best regards,

Simon

[StefanHri]

Dear Simon Ferres and Smitesh Mali did you solve this problem?

For my evaluations I want to have several separate projects with different peripherals places in the secure wold. Therefore, it is not practical to modify nrf/subsys/spm/spm.c.

In the bast case I need a boilerplate which I can place outside the ncs folder.

[Simon]

If you want to enable/disable configurations of another module without modifying it directly, you should use the approach explained here: https://devzone.nordicsemi.com/f/nordic-q-a/56459/watchdog-with-bootloader-on-nrf9160. This allows you to have several projects with different secure/nonsecure peripherals.

Best regards,

Simon