• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 25 subscribers
  • Views 156 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 286120
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nrf9160 access to FICR SIPINFO is not implemented in nRF connect SDK

user114480

Hello,

i would like to access the SIPINFO field from FICR https://infocenter.nordicsemi.com/topic/ps_nrf9160/ficr.html from a non-secure application using the SPM.

Unfortunately there is no support for SIPINFO in the source code:

1. The available svd file only contains INFO, but not SIPINFO: https://raw.githubusercontent.com/NordicSemiconductor/nrfx/master/mdk/nrf9160.svd

2. The FICR struct https://github.com/NordicSemiconductor/nrfx/blob/master/mdk/nrf9160.h#L722 does not contain SIPINFO and there is no FICR_SIPINFO_Type defined.

3. The spm does not allow access to SIPINFO in FICR via spm_request_read(), see https://github.com/nrfconnect/sdk-nrf/blob/main/subsys/spm/secure_services.c#L88 

Could this be added to be available in a future version of the nRF connect SDK?

Regards,

Christian Taedcke

  • +1

    Hi,

     

    My apologies for this inconvenience! Thank you for reporting this issue in the mdk ficr struct. I will report this internally.

    3. The spm does not allow access to SIPINFO in FICR via spm_request_read(), see https://github.com/nrfconnect/sdk-nrf/blob/main/subsys/spm/secure_services.c#L88 

    If the range is not per your requirement, I would recommend that you modify this specific file to ensure that you can read the specific area from non-secure region.

     

    Kind regards,

    Håkon

  • 0 in reply to user2115

    Thank you.

    user2115 said:
    If the range is not per your requirement, I would recommend that you modify this specific file to ensure that you can read the specific area from non-secure region.

    I did this, but without the struct and addresses in the mdk it is all a little bit hacky. It would be good if this would also be accessible from a non-secure via spm in the future without modifying the nrf-sdk code (like it is already possible for FICR INFO).

    For now everything works for me, i just wanted to report the issue so a fix is incorporated in future connect sdk releases.

    Regards, 

    Christian

Related
Terms of service