Troubleshooting Initialization Failures in Icarus IoT Dev Board (nRF9160): Error Code -8 During GPS and IoT Module Setup

I'm working on a tracking project using the Icarus IoT Dev Board (nRF9160), which employs both NB-IoT and GPS functionalities. During the project, I encountered an issue where, after successfully initializing either the GPS or the IoT module, attempting to initialize the other module fails. The error message returned is:

`<err> lte_lc: Could not send AT command, error: -8`.

I am using toolchain version 1.5.1.

I am seeking to understand the potential reasons behind this error. Specifically, why might the initialization of one module interfere with the initialization of the other, resulting in the inability to send AT commands? What are the possible underlying causes for this error code, and how can they be resolved to ensure successful initialization of both the GPS and IoT modules on the nRF9160 board?

  • hi
    Apologies for the inconvenience. Could you please review my source code? I believe it's now accessible on my drive. in addition i upgraded my system to NCS v2.6.1 + MFW v1.3.6.

  • Hi Nagib,

    Thanks! Now I see your source codes, but I have problem to build your project to my NCS v2.6.1 toolchain.

    Are you sure you have updated your codes to NCS v2.6.1, or you have updated the wrong project? Because following warnings reminds that you are use some undefined symbols which might be deprecated from old NCS versions.

    c:/NCS/myApps/demoTIM/prj.conf:21: warning: attempt to assign the value 'y' to the undefined symbol AT_CMD

    c:/NCS/myApps/demoTIM/prj.conf:22: warning: attempt to assign the value 'y' to the undefined symbol AT_NOTIF

    c:/NCS/myApps/demoTIM/prj.conf:72: warning: attempt to assign the value 'n' to the undefined symbol LTE_AUTO_INIT_AND_CONNECT

    c:/NCS/myApps/demoTIM/prj.conf:78: warning: attempt to assign the value 'y' to the undefined symbol BOARD_SELECT_SIM_EXTERNAL

    Best regards,

    Charlie

Related