Configure SPM peripherals without modifying SPM files

RE: Configure SPM peripherals without modifying SPM files

Simon — Mon, 27 Jan 2020 09:56:12 GMT

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

RE: Configure SPM peripherals without modifying SPM files

StefanHri — Sun, 26 Jan 2020 15:22:21 GMT

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.

RE: Configure SPM peripherals without modifying SPM files

Simon — Wed, 03 Jul 2019 12:07:20 GMT

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

RE: Configure SPM peripherals without modifying SPM files

Simon — Wed, 03 Jul 2019 09:27:19 GMT

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

Best regards,

Simon

RE: Configure SPM peripherals without modifying SPM files

Smitesh Mali — Wed, 03 Jul 2019 09:18:50 GMT

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.

RE: Configure SPM peripherals without modifying SPM files

Simon — Wed, 03 Jul 2019 09:11:34 GMT

A solution might be to put it in the CMakeLists.txt file inside <..>\ncs\nrf\samples\nrf9160\http_application_update.

However, you are free to place the application folder wherever you want, e.g. in C:\ncs_projects\http_application_update. All you have to do is to set ZEPHYR_BASE appropriately, and cmake will find all the repositories (nrf, zephyr, nrfxlib etc..).

In the NCS tutorial, under 2.1.4 Manage your project with west -- How to preserve your application, I will soon explain where and how to develop your application.

Best regards,

Simon

RE: Configure SPM peripherals without modifying SPM files

Smitesh Mali — Wed, 03 Jul 2019 08:53:10 GMT

Hi Simon,

Above option you suggested would bring change inside "nrf" folder.

So this option is not feasible.

Regards,

Smitesh Mali

RE: Configure SPM peripherals without modifying SPM files

Simon — Tue, 02 Jul 2019 14:29:30 GMT

I think this should be possible, take a look at ..\ncs\nrf\samples\CMakeLists.txt and the following lines:

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

You can see that the SPM path is added through the line add_subdirectory(..).

In order to use another path, e.g. ncs/your_folder, try this:

add_subdirectory(../your_folder/spm ${CMAKE_BINARY_DIR}/spm)

If this doesn't work, please tell me and I will look into it.

Best regards,

Simon

RE: Configure SPM peripherals without modifying SPM files

Smitesh Mali — Fri, 28 Jun 2019 10:46:51 GMT

Hi simon,

any update on this issue ?

I want to ask whether we can change path of "SPM" project included in the "http_update_ota"

project.

If we can then i can move SPM outside "nrf" folder and use it.

Regards,

Smitesh Mali

RE: Configure SPM peripherals without modifying SPM files

Simon — Sat, 15 Jun 2019 19:50:44 GMT

In order to set a peripheral to a Non-Secure state, you have to access the SPU register PERIPHID[n].PERM, and I don't think this is possible to do from Non-Secure firmware. E.g. the user application (I couldn't find any documentation confirming this, but it doesn't make sense that Non-Secure firmware can modify the Security state of peripherals).

If my understanding is right, you have to configure security state of the peripheral from a separate Secure firmware image. Thus you have to do it from the SPM application.

I understand your concern about modifying Nordic libraries, as it doesn't seem like a clean way of doing things.

However, I will be gone for the next two weeks, but I will ask somebody else to take over the case, which can ask one of the developers of the SPM library how to go about this.

Best regards,

Simon

RE: Configure SPM peripherals without modifying SPM files

Smitesh Mali — Fri, 14 Jun 2019 04:27:27 GMT

Hi Simon,

I think there is some disconnect between what i want and what you understood from my question.

I know that by modifying kconfig and spm.c or by modifying proj.conf file we can configure peripheral.

But all these files are inside "nrf" submodule.

We don't want to modify any of these files inside "nrf" submodule and want to use it as it is provided by you through github.

If we want to make change to application then we generally copy that application folder outside

"nrf" folder and then we use it so that there is no change inside "nrf" folder.

As you mentioned in your earlier thread "UARTE2" and "SPIM3" are both included as "Non-secure" in

spm.c file. So i don't need to configure them.

Only peripheral i need to configure is "WDT".

So is there a way to configure "WDT" as non-secure without modifying "kconfig" or "spm.c" or "proj.conf"

files inside "nrf" submodule ?

Regards,

Smitesh Mali

RE: Configure SPM peripherals without modifying SPM files

Simon — Thu, 13 Jun 2019 23:04:18 GMT

Take a look at the nRF Connect SDK Tutorial, at the bottom of section 2.2.4. There I am showing how to include peripherals to the SPM library.

Best regards,

Simon

RE: Configure SPM peripherals without modifying SPM files

Smitesh Mali — Wed, 12 Jun 2019 09:32:19 GMT

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

RE: Configure SPM peripherals without modifying SPM files

Simon — Wed, 12 Jun 2019 09:18:46 GMT

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