reset message on flash

[Timothy]

I have a nRF9160 board that is running fine with a modified asset_tracker_v2. Recently I started getting the message shown below. after some time the system does connect and everything runs fine but if I reset or reflash the message appears again. This makes the system unusable for some initial time. what am I doing wrong or missing? How do I get rid of this message and connect to LTE on startup.

[00:00:21.365,936] <wrn> modem_module: The modem has detected a reset loop. LTE network attach is now restricted for the next 30 minutes. Power-cycle the device to circumvent this restriction.

[Achim Kraus]

If "flashing" uses a reset, the modem is processing that as any other reset.

It enters the "reset loop", if "too many reset" have been detected.

Modem Reset Loop Restriction Reset

One way to prevent that is to use "AT+CFUN=0" ahead of flashing, or flash less frequently.

For more details, read %MDMEV and Modem Reset Loop Restriction

[Timothy]

Achim

thanks for the quick response. I did do the command you suggested before I flashed and the results are shown below. I still got the same message and I cannot connect to LTE. I am debugging code and I cannot "flash less often". I have been using the nRF9160 and a modified version of asset_tracker_v2 for several years. I have never seen this message before. I have made edits and flashed dozens of times a day all of the time. did something change?

This is a debugging showstopper. I cannot debug code if I have to wait 30 minutes to see if any change I made is working and then wait 30 minutes again to retry. How do I get around this problem?

> at +cfun=0
at +cfun=0
AT+cfun=0: OK

%MDMEV: SEARCH STATUS 2
%CESQ: 255,0,255,0
+CEREG: 0
[00:00:30.942,138] <inf> app_event_manager: MODEM_EVT_LTE_CELL_UPDATE
[00:00:41.270,172] <err> modem_info_params: Link data not obtained: 5 -22

[Achim Kraus]

Your issue above reported:

<wrn> modem_module: The modem has detected a reset loop.

My answer and the links can only help for the "reset loop". Do you still see that reported?

at+cfun=0

helps only, if the device is not already in the "reset loop". If you read the comments in the first link, that shows how to overcome the 30 min in development even if the device is already in that "reset loop".