Modem FW 1.3.4 Error 0x10

[mrks115]

Hey,

we're currently testing our devices with Modem FW 1.3.4 / nRF Connect SDK 2.2.0 and have observed the following error:

00:01:37.478 <inf> app_event_manager: e:modem_module_event REQ_DISCONNECT (timeout = 30, lte_lc = offline)
00:01:38.236 <err> nrf_modem: Modem error: 0x10, PC: 0x7ce68
00:01:38.236 <err> lte_lc: Failed to set functional mode. Please check XSYSTEMMODE.
00:01:38.239 <inf> nrf_modem: Modem has faulted, re-initializing

• LTE-M
• Connection was successful before, no other issues
• Data was transferred
• GPS was used in-between
• No PSM/eDRX
• State before error: RRC connected

Does this information help you in any way?
If not, what details will help you further?

Kind regards
Markus

[Didrik Rokhaug]

Hi mrks115 and Achim Kraus,

Unfortunately, we are not able to find the cause of the "Modem error: 0x10, PC: 0x7ce68"-error without a modem trace.

Are either of you able to capture a modem trace where that error occurs?

Best regards,

Didrik

[mrks115]

Regarding this error I also won't investigate further. Seems to be not reproducible.

I'm happy to help where I can, but I also want to emphasize what Achim Kraus  is saying. As a developer, if I see a bug on my desk by chance, I'm glad to provide a modem trace. On field test devices or when colleagues report such an error to me, I unfortunately don't always have the opportunity to reproduce it and I see Nordic as being more obliged here.

[David Bassil]

hey Dejans,

I already did. this is the my  Case ID : 343162

could you please check it

[dejans]

Hi,

David Bassil said:

I already did. this is the my  Case ID : 343162

Thank you for letting me know.

David Bassil said:

could you please check it

One of our engineers will look into this issue soon.
Please do not forget to upload modem trace.

Best regards,
Dejan

[David Bassil]

we do not have a modem trace right now. we will try to get it

[dejans]

Hi,

David Bassil said:

we do not have a modem trace right now. we will try to get it

Hopefully, you will be able to capture it. When you have it, please upload it to your other ticket and continue discussion there.

Best regards,
Dejan

[David Bassil]

Please check the error we are getting also before you get from us the traces. There are devices that are stopping that are customer site with this error. this comes from Nordic site. its not an application error

[Achim Kraus]

From the experience in the past years, I guess there is just not enough information, that Nordic will be able to check something. As I wrote two years ago, the users will in many cases not be able to provide traces for issues, which occurs only rarely.

I also answered on your new ticket. I recommend that you try to use a newer mfw and NCS versions, though that may have fixed your issue in the meantime (even if the 1.3.5/2.5.0 used by you is already newer than the one of this ticket).

In my case mfw 1.3.6/7 and NCS 2.6.0-4 runs pretty stable, I haven't seen the "modem crashed" with them.

(NCS 2.9.1 runs so far also well on my side, but that's too short to say too much.)