This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

troubleshooting of produced prototype: nrf9160

Hello,

I have developed 10pcs of one prototype with the nrf9160 SiP. 

I have some questions regarding some errors im having.

Regarding the SIM 1V8 driver VCC, for UICC interface, I am observing a fluctuation on this channel/voltage, from 0V -> 0.4 VDC, with approximately 1hz frequency.

What can cause this to happend, what is the normal behaviour of this channel when it is short-circuited with ground or something else/similar ?

My second question is regarding the attached image, im observing this on a few of my prototypes, im not able to upload any modem firmware to the SiP, any idea why?


Regards,

David

Parents
  • Could you give me some more information about how your application fails?

    Are you not able to program it, or does it fail at run-time?

    What error messages do you get?

     

    David said:

    I've read up on the SPM, and for everything to work, I have to first upload the SPM firmware without "ns", then I have to upload my application firmware, as "ns".

    Also, I have to set in proj.conf, CONFIG_SPM=n for this to be available as .elf, for me to build. If not, this wont work.

     While it is true that you had to flash the two applications separately before, that is no longer necessary. If you build for the non-secure version of a board (with "ns" at the end of the board name), it should configure the application correctly, build the Secure Partition Manager and merge the hex files into a single merged.hex.

    What happens if you remove the CONFIG_SPM and CONFIG_TRUSTED_NONSECURE lines from your prj.conf, and add

    include($ENV{ZEPHYR_BASE}/../nrf/cmake/boilerplate.cmake)

    right above the other include macro in your CMakeLists.txt file?

Reply
  • Could you give me some more information about how your application fails?

    Are you not able to program it, or does it fail at run-time?

    What error messages do you get?

     

    David said:

    I've read up on the SPM, and for everything to work, I have to first upload the SPM firmware without "ns", then I have to upload my application firmware, as "ns".

    Also, I have to set in proj.conf, CONFIG_SPM=n for this to be available as .elf, for me to build. If not, this wont work.

     While it is true that you had to flash the two applications separately before, that is no longer necessary. If you build for the non-secure version of a board (with "ns" at the end of the board name), it should configure the application correctly, build the Secure Partition Manager and merge the hex files into a single merged.hex.

    What happens if you remove the CONFIG_SPM and CONFIG_TRUSTED_NONSECURE lines from your prj.conf, and add

    include($ENV{ZEPHYR_BASE}/../nrf/cmake/boilerplate.cmake)

    right above the other include macro in your CMakeLists.txt file?

Children
No Data
Related