nRF9160 returns +CME ERROR 0 with #XGPS AT command

Hello,

I have a custom prototype board using the nRF9160 that will gather GPS position information as a feature.  The (previous)first PCB (of the exact same board) that I began development with was working and I was able to start GNSS using the #XGPS AT command and then get a GPS fix (from the #XGPS: notifications).  In getting the second board up and running, the nRF9160 is (now) replying with +CME ERROR 0 when I send the #XGPS (AT#XGPS=1,1) command.  The GNSS in the nRF9160 has been enabled using the AT%XSYSTEMMODE command.  Can someone tell me why the nRF9160 would send this error message when the GNSS has been enabled?

nRF SDK v2.0.0 (for SLM)

nRF9160 Modem firmware v1.3.2, using the SLM application communicating via UART to a host microprocessor (using AT commands)

Thank you very much.

Parents Reply Children
  • I cannot provide any RTT logging as we are not currently using Visual Code Studio for our primary code development.  We are using the TI CC1352 as an external processor to the nRF9160, and the host processor is communicating with the nRF9160 using AT commands over a UART.  I however have available the Tera Term terminal output that we use for logging/debugging.  Please see the Tera Term terminal text output below:

    Note:
    AT CMD[x]: is the current AT command being sent to the nRF9160 by the CC1352 host processor (by UART interface).. TX PASS indicates the command was sent successfully.
    AT CMD[x] RX: is the subsequent response received from the nRF9160...

    AT CMD[0]: AT TX PASS

    AT CMD[0] RX:

    OK

    AT CMD[1]: AT+CFUN=4 TX PASS

    AT CMD[1] RX:

    OK

    %XSIM: 1

    AT CMD[2]: AT+CFUN? TX PASS

    AT CMD[2] RX:

    +CFUN: 4

    OK

    AT CMD[3]: AT%XSYSTEMMODE=1,0,1,0 TX PASS

    AT CMD[3] RX:

    OK

    AT CMD[4]: AT%XSYSTEMMODE? TX PASS

    AT CMD[4] RX:

    %XSYSTEMMODE: 1,0,1,0

    OK

    AT CMD[5]: AT+CFUN=0 TX PASS

    AT CMD[5] RX:

    OK

    %XSIM: 0

    AT CMD[6]: AT+CFUN=31 TX PASS

    AT CMD[6] RX:

    OK

    AT CMD[7]: AT+CFUN? TX PASS

    AT CMD[7] RX:

    +CFUN: 31

    OK

    AT CMD[8]: AT%XSYSTEMMODE? TX PASS

    AT CMD[8] RX:

    %XSYSTEMMODE: 1,0,1,0

    OK

    AT CMD[9]: AT%XCOEX0? TX PASS

    AT CMD[9] RX:

    %XCOEX0: 1,1,1565,1586

    OK

    AT CMD[10]: AT+CGMI TX PASS

    AT CMD[10] RX:

    Nordic Semiconductor ASA

    OK

    AT CMD[11]: AT+CGMM TX PASS

    AT CMD[11] RX:

    nRF9160-SICA

    OK

    AT CMD[12]: AT+CGMR TX PASS

    AT CMD[12] RX:

    mfw_nrf9160_1.3.2

    OK

    AT CMD[13]: AT#XSLMVER TX PASS

    AT CMD[13] RX:

    #XSLMVER: "2.0.0"

    OK

    AT CMD[14]: AT+CGSN=1 TX PASS

    AT CMD[14] RX:

    +CGSN: "351358812450465"

    OK

    AT CMD[15]: AT%XICCID TX PASS

    AT CMD[15] RX:

    %XICCID: 89148000005567824099

    OK

    AT CMD[16]: AT+CIMI TX PASS

    AT CMD[16] RX:

    311270004399370

    OK

    AT CMD[17]: AT+CMEE? TX PASS

    AT CMD[17] RX:

    +CMEE: 0

    OK

    AT CMD[18]: AT+CMEE=1 TX PASS

    AT CMD[18] RX:

    OK

    AT CMD[19]: AT+CMEE? TX PASS

    AT CMD[19] RX:

    +CMEE: 1

    OK

    AT CMD[20]: AT#XGPS? TX PASS

    AT CMD[20] RX:

    +CME ERROR: 0

  • In getting the second board up and running, the nRF9160 is (now) replying with +CME ERROR 0 when I send the #XGPS (AT#XGPS=1,1) command.

    Have you changed any application configurations between the two? Does the same application work on the first board? Do you have access to an nRF9160 DK? 

Related