Attachments (3) Download All
Nordic Case Info
  • Case ID: 231957
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

TZ_NONSECURE_FUNC_PTR_CREATE SPM error with v1.0.0 for nRF9160

MJD093

Hello,

I have seen today that the new releases of the v1.0.0 SDK and v1.0.0 modem firmware were release for the nRF9160 DK. I have been able to update the modem firmware but I'm coming across an error with the SDK.

Every time I try to build I get an error from the SPM code about about TZ_NONSECURE_FUNC_PTR_CREATE. This error occurs no matter what the code I try to build, be that my own custom application, SPM itself or any of the example programs.

I had orginally updated my ncs folder with my custom additions but this occurred after I updated. I then renamed that ncs_backup and did a fresh install in a new ncs folder of the repos using the instructions in 'Getting Started' and the same issue occurs.

Parents
  • 0

    I have managed to build 1.0.0 by updating the branch and west and pip3 with latest requirements on Ubuntu. While this is not particularly helpful for your issue, it does mean it is buildable.  Attaching a built asset tracker firmware if you wish to test things with it if that helps. I face the following issue with it: https://devzone.nordicsemi.com/f/nordic-q-a/49328/nrf91-sdk-v1-0-0-at-command-baud-problem  build_nrf9160_pca10090ns-v1_0_0-merged.hex

  • 0 in reply to slomusti

    Yes I did this as well, fresh install of the repos, west update, git checkout and pip3 the 3 required python module scripts as in the 'Getting Started Assistant' but it still didn't work :/

    Do you happen to have at_client's merged.hex? The asset_tracker won't work on my DK as I have no NB-IoT network in my current location (and the NB-IoT network I do have can't use the Dynamic Amazon IP address the asset_tracker needs for nRF Cloud Sweat smile) but the at_client would allow me to test the modem firmware update in the mean time.

    EDIT:

    Oh dear, I get an immediate hardware fault with that hex file, and that's during the boot up information, not the main application. :/

Reply
  • 0 in reply to slomusti

    Yes I did this as well, fresh install of the repos, west update, git checkout and pip3 the 3 required python module scripts as in the 'Getting Started Assistant' but it still didn't work :/

    Do you happen to have at_client's merged.hex? The asset_tracker won't work on my DK as I have no NB-IoT network in my current location (and the NB-IoT network I do have can't use the Dynamic Amazon IP address the asset_tracker needs for nRF Cloud Sweat smile) but the at_client would allow me to test the modem firmware update in the mean time.

    EDIT:

    Oh dear, I get an immediate hardware fault with that hex file, and that's during the boot up information, not the main application. :/

Children
Terms of service