• State Verified Answer
  • Replies 1 reply
  • Subscribers 86 subscribers
  • Views 58 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 360017
Options

softSIM library conflicts

rtphilipson

I've built the softsim external profile from Onomondo and it works.  But when I try to incorporate it into the app I'm currently developing, it renders the code unable to boot.

I did a lot restructuring of my code in order to accommodate they code as I got a RAM overflow the first time I tried to incorporate.  If I incorporate softsim-overlay.conf, my unit can no longer boot, but If I leave it out, it does and runs normally.

Are there any known conflicts with the Onomondo library that might cause anything like this.  I'm using NRF_CLOUD to get A-GNSS data and the AWS IoT Client library to communicate with AWS IoT Core.

I'll include my prj.conf here in case that might provide any other information.  Let me know if other files, like the pm_static might also be helfpul.6518.prj.conf

Parents
  • 0

    I don't know why there would be a conflict, but by getting rid of the NRF Provisioning shell commands

    CONFIG_NRF_PROVISIONING_SHELL=n
    Now it works.  I think I can figure out a workaround to the provisioning commands, but why that would create a conflict is beyond me. Unless the system was just so under-resourced with the softSIM addition, peeling back just a little made it work.
Reply
  • 0

    I don't know why there would be a conflict, but by getting rid of the NRF Provisioning shell commands

    CONFIG_NRF_PROVISIONING_SHELL=n
    Now it works.  I think I can figure out a workaround to the provisioning commands, but why that would create a conflict is beyond me. Unless the system was just so under-resourced with the softSIM addition, peeling back just a little made it work.
Children
No Data
Related
Terms of service