nRF9151 modem faults on v2.0.2

[klaasg]

Hi,

We have deployed some devices now, and we see quite some modem faults popping up.

Could you try to give all info on what you know about these faults we have from the past month?

  modem_firmware  fault_code  program_counter  count
  --------------  ----------  ---------------  -----
  2.0.2           0x10        0x10f056         86
  2.0.2           0x10        0xf6f56          33
  2.0.2           0x4         0x7af58          9
  2.0.2           0x4         0x92716          9
  2.0.2           0x32        0x0              7
  2.0.2           0x10        0x1a7754         4
  2.0.2           0x10        0x1a582c         4
  2.0.2           0x10        0x4a5a6          2
  2.0.2           0x10        0x7fbe6          2
  2.0.2           0x32        0x10f056         1
  2.0.2           0x10        0x735b8          1
  2.0.2           0x4         0x173010a        1
  2.0.2           0x10        0x10f2f8         1
  2.0.2           0x10        0x7813a          1

Thank you.

[Simon D-M]

Hi,

For the first modem crash (0x10, pc:0x10f056), I was able to find another bug report. It has been patched around the end of last year. Please try to update your modem firmware to the latest one.

For the other faults, I didn't find anything, can you maybe share a bit more information. For example what nRF Connect SDK you are using, the context in which these modem faults happen.

Also, one of the best thing you could do would be to capture the modem trace of the few last minutes when the modem crashes. Are you able to get modem traces from the failing devices?

Last thing I want to ask is if you have a reason to stay on the mfw 2.0.2 and not use the latest one (mfw 2.0.4) ?

Best regards,

Simon D-M

[klaasg]

Good to hear that one or more will be fixed when we move to mfw 2.0.4. We did not have the FOTA set up completely from the bgeinning but will now begin to move all devices to mfw 2.0.4.

We are currently on nRF SDK 3.0.2.

In deployments we currently don't capture modem traces. We might add it in the future, but it would be challenging to retrieve the traces over-the-air.

Thank you,

Klaas

[Simon D-M]

Hi Klaas,

Just letting you know that I've asked internally about the other modem faults to see if someone can find anything about them. I'll keep you updated on that.

Best regards,

Simon D-M

[Simon D-M]

Hi Klaas,

Sorry for the wait, it took a bit more time that anticipated.

Actually, it seems that some of your issues are likely to still be present in mfw v2.0.4...

However, there should be less occurences. The modem team has already fixed a lot of things, but the fault you are seeing have quite a lot of possible source (especially the first one). We fixed the sources we were able to confirm but there probably are more that we don't know yet. 

So, if you can, it would be extremly helpful if you can collect some modem traces when the crashes happen, so that we can see what caused them and fix them.

I don't know if you already use Memfault, but I know that it can collect and send the traces and is quite easy to implement. So, if you struggle getting the traces, please reach out and we can help you get them. 

Also, I've got told this for the first fault :

2.0.2           0x10        0x10f056         86

"If you are reading the ICCID using AT+CRSM, there is a known issue (rare though) that could cause the reset. If this is your case, please use AT%XICCID instead. This command doesn't have that issue."

Best regards,

Simon D-M