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

The modem restarts after sending the command AT+CFUN=1

Hi, 

When running the at_client example, I send the AT+CFUN=1 command via the LTE link monitor. After a few seconds, the nrf9160 reboots.

I want to say that before my program worked and connected to the server. However, now I cannot even work through at_client. Commands like AT+CGMR work

If I pull out the sim card, the nrf9160 will not restart. What could be the problem?

P.S. I tried to get modem trace but tace collecor is not accepting anything. Are there any other ways to debug this problem?

Modem firmware version - mfw_nrf9160_1.1.0
I use nRF Connect SDK v1.3.0

  • I apologize for the long answer, for some reason I stopped receiving notifications.

    I have done what you asked.

    After starting the command was sent:

    AT+CFUN? 
    +CFUN: 0 
    OK


    Then I pressed reset and sent the following command:

    AT+CFUN=1 
    OK

    Waited for the device to restart and stopped the tracer

    here is trace.bin:

    trace-2020-08-19T12-39-39.333Z.bin

    Here's the log if needed:

    2020-08-19T12:39:24.871Z INFO Application data folder: C:\Users\y.morgunov\AppData\Roaming\nrfconnect\pc-nrfconnect-tracecollector
    2020-08-19T12:39:24.972Z DEBUG App pc-nrfconnect-tracecollector v1.0.3 official
    2020-08-19T12:39:24.972Z DEBUG App path: C:\Users\y.morgunov\.nrfconnect-apps\node_modules\pc-nrfconnect-tracecollector
    2020-08-19T12:39:24.972Z DEBUG nRFConnect 3.4.2 is supported by the app (^3.0.0)
    2020-08-19T12:39:24.972Z DEBUG nRFConnect path: C:\Users\y.morgunov\AppData\Local\Programs\nrfconnect\resources\app.asar
    2020-08-19T12:39:24.972Z DEBUG HomeDir: C:\Users\y.morgunov
    2020-08-19T12:39:24.972Z DEBUG TmpDir: C:\Users\YDBE4~1.MOR\AppData\Local\Temp
    2020-08-19T12:39:24.978Z VERBOSE Could not fetch serial number for serial port at COM1
    2020-08-19T12:39:24.979Z VERBOSE Could not fetch serial number for serial port at COM20
    2020-08-19T12:39:30.195Z INFO Device opened
    2020-08-19T12:39:39.335Z INFO Tracefile created: C:\Users\y.morgunov\AppData\Roaming\nrfconnect\pc-nrfconnect-tracecollector\trace-2020-08-19T12-39-39.333Z.bin
    2020-08-19T12:40:16.773Z INFO Tracefile closed
    

  • Hi Yury,
    I was hoping you could share the full serial output of the responses when running the at_client.

    Please try to redo the modem trace, it was invalid. (only 1Kb)

  • Hi Martin,

    I'm sorry, but I don't quite understand what you mean. I sent a trace when the modem crashes, is that not enough?

  • Hi Yury,
    The modem trace you sent (.bin file) was empty. 
    Please make sure you have followed the guide correctly: https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/how-to-get-modem-trace-using-trace-collector-in-nrf-connect

    Also what I mean by serial output, is the actual logging from the application. (This can be seen from the LTE Link Monitor or just a serial output terminal)


  • I remember exactly that Tace size was not equal to 0, maybe I accidentally sent the wrong file ...
    Here's another one. Trace size = 334 B

    trace-2020-08-25T10-18-52.520Z.bin

Related