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

[Torje]

Hello Markus,

I suspect Nordic employees might request you to do a modem trace, unless they already know what the issue could be.
Providing this will perhaps make the case easier to assist with.
Is this on a custom board?

Kind regards.
Torje

[Didrik Rokhaug]

Hi,

I'll check with the modem team if they know what the error means.

However, as Torje says, a modem trace will probably be very helpful.

Best regards,

Didrik

[mrks115]

The error unfortunately only occurred occasionally during testing (without tracing).

We'll try to reproduce this error with modem trace. But this might need some time to set this up.

[Didrik Rokhaug]

Unfortunately, there isn't much we can do without a modem trace, but they did offer some thoughts:

This comes from the library (based on some trigger from modem), but "Failed to set functional mode. Please check XSYSTEMMODE" kind of hints that in system mode there would be some systems active that are not supported by the HW version. Or, that there is a band lock active and none of the locked bands are supported by the currently activated system mode. These are just initial guesses without a modem log. Should be easy to resolve if a modem log is received.

[mrks115]

Hey,

now I can provide you a Modem Trace, but I'm not sure whether this is related to my original post.

Conditions changed:

• NB-IoT
• Connect to Cellular
• Connect to our LwM2M Server
• Stay connected forever
• After about 4 minutes modem error occurs
  • It is reproducible in most cases

trace-2023-02-27T10-24-52.749Z.bin

[00:00:14.773,803] <inf> lwm2m: EVT_CONNECTED
[00:00:25.052,734] <wrn> modem: RRC idle
[00:04:23.321,899] <err> Modem error: 0x10, PC: 0x9af46

Please let me know if you need more details.