Potential Modem Failure

RE: Potential Modem Failure

Håkon Alseth — Thu, 18 Jul 2019 10:08:40 GMT

Hi,

[quote user="webfeet"]I'd be grateful if you would explain the EXACT steps that you would perform if an erase all was completed with NRF Connect Programmer and how to load the modem firmware after that has been done.[/quote]

You cannot erase the modem. You can only upgrade it. What you can erase is the application space, which is performed by issuing "nrfjprog -e".

[quote user="webfeet"]A new piece of information that is more than a little bit disturbing, is if I downgrade and use an nrf9160_DK 0.8.2 with the same application and the latest version of the modem.software.[/quote]

This points to something wrong with the DK itself, but I need more information in order to evaluate. Were you able to get a trace log?

Kind regards,

Håkon

RE: Potential Modem Failure

John — Thu, 18 Jul 2019 07:44:30 GMT

A new piece of information that is more than a little bit disturbing, is if I downgrade and use an nrf9160_DK 0.8.2 with the same application and the latest version of the modem.software.

The problem that we were experiencing with the carrier goes away.

I'd be grateful if you would explain the EXACT steps that you would perform if an erase all was completed with NRF Connect Programmer and how to load the modem firmware after that has been done.

RE: Potential Modem Failure

John — Tue, 16 Jul 2019 20:21:29 GMT

Replied to myself 🙂

RE: Potential Modem Failure

John — Tue, 16 Jul 2019 20:13:14 GMT

Replied to myself 🙂

RE: Potential Modem Failure

John — Tue, 16 Jul 2019 20:11:38 GMT

Hakon, you touched on something interesting regarding current draw.

In all cases when we fail to reconnect, the current draw is fixed at 33 mA

May I ask if the two lines of code.

bsd_shutdown();

and

sys_reboot(SYS_REBOOT_COLD);

Ultimately react with the modem in a similar manner, whilst trying to achieve a graceful shutdown, which demonstrably seems to not be occurring?

RE: Potential Modem Failure

John — Tue, 16 Jul 2019 07:58:29 GMT

Yes I do have low signal strength where the test has been running.

I'll rerun the trace now that you have shown me what to do.

Kind regards

John

RE: Potential Modem Failure

Håkon Alseth — Tue, 16 Jul 2019 07:42:56 GMT

Hi,

Sorry for the late reply. I can confirm that there is an open issue internally on bsd_shutdown() where the current consumption is left high after it is done, which is being looked into. However; given your symptoms, it seems that this is a new issue.

You mention that this is mostly visible on a single carrier. Is there anything out-of-the-ordinary, like low signal strength or similar?

PS: Your trace file is empty (just filled with zeros). Did you remember to give the AT command "AT%XMODEMTRACE=1,2" after booting?

If you have erased the nRF52 firmware on the DK, you might need to reprogram it to get the UART pins outputted to the segger IC. You can find a .zip file here: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/how-to-get-modem-trace-using-trace-collector-in-nrf-connect

Kind regards,

Håkon

RE: Potential Modem Failure

John — Sun, 14 Jul 2019 20:54:17 GMT

Here's a new nRF Connect log and modem trace for it.devzone.nordicsemi.com/.../trace_2D00_2019_2D00_07_2D00_14T15_2D00_51_2D00_38.384Z.bin devzone.nordicsemi.com/.../2019_2D00_07_2D00_14T15_5F00_03_5F00_09.338Z_2D00_log.txt