Modem stops responding after CFUN? and modem trace lib crashes

Custom nRF9160 hardware. UART0 over RX/TX-TTL. Updated to MFW 1.3.6. nRF SDK 2.5.2.

Two issues:

1)

Normal at_client w/ PDN enabled to set APN. LTE Link Monitor, and AT&CFUN=1, then AT&CFUN? gives me all the usual info about serial number, firmware, etc., with the last line being the selected bands, and then the app stops responding to AT commands. Breaking in the debugger says the app is running, idling.

2)

In order to get more info on what's wrong: enable modem lib trace (CONFIG_NRF_MODEM_LIB_TRACE=y). Start app, then crash.

Temporary breakpoint 1, main () at /.../252-cellular-at-client/src/main.c:30
30 printk("The AT host sample started\n");
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
0x00000758 in ?? ()
(gdb)

Nothing in the map files matches the address.

Tried various options, including -S tfm-enable-share-uart to force it to uart0, to no avail.

What more can I do?

-----

ADDENDUM.

For no reason, whatsoever, the modem suddenly started working and I have absolutely no idea why. I did nothing different.

Is it that the modem hangs - or seems to hang - when it's registering the SIM on the network? It's impossible to tell, and I really do think it should respond to AT commands during that time.

Moreover, _please_ don't remove LTE Link Monitor. Cellular Monitor requires working modem trace to get signal quality, and all the other useful information I can see directly in the LTE Link Monitor side panel. 
But since I can't get modem lib trace, or at the very least requires two UARTs, it's useless to me, and from what I can tell in the numerous support tickets on modem lib trace and nRF91, I'm not the only one having problems.

Parents
  • Hi Mikael,

    For no reason, whatsoever, the modem suddenly started working and I have absolutely no idea why. I did nothing different.

    Is it that the modem hangs - or seems to hang - when it's registering the SIM on the network? It's impossible to tell, and I really do think it should respond to AT commands during that time.

    My colleague is setting up a test to try to reproduce the hanging issue. Depending on the results we could have an explanation on why the modem (appears to) hang. Thank you for your patience on this.

    That being said, a possibility could be that the power supply on your board is not sufficient to supply the modem during network registration. Have you had us do a hardware review for your board?

    Tried various options, including -S tfm-enable-share-uart to force it to uart0, to no avail.

    The tfm-enable-share-uart snippet was introduced in NCS v2.6.0. Have you added the snippet to NCS v2.5.2?

    Best regards,

    Maria

Reply
  • Hi Mikael,

    For no reason, whatsoever, the modem suddenly started working and I have absolutely no idea why. I did nothing different.

    Is it that the modem hangs - or seems to hang - when it's registering the SIM on the network? It's impossible to tell, and I really do think it should respond to AT commands during that time.

    My colleague is setting up a test to try to reproduce the hanging issue. Depending on the results we could have an explanation on why the modem (appears to) hang. Thank you for your patience on this.

    That being said, a possibility could be that the power supply on your board is not sufficient to supply the modem during network registration. Have you had us do a hardware review for your board?

    Tried various options, including -S tfm-enable-share-uart to force it to uart0, to no avail.

    The tfm-enable-share-uart snippet was introduced in NCS v2.6.0. Have you added the snippet to NCS v2.5.2?

    Best regards,

    Maria

Children
Related