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

[Achim Kraus]

With almost 4 decades of software development, trying to catch a sporadic error as this one (once in a couple of weeks) in a "black box approach" (without the sources to see potential causes and be able to focus tests on that) is a waste of time. In my opinion, this make only sense with sources and the possibility to focus on some weakness or obscurities. With that someone may have a chance to catch it. So, it's up to Nordic and your software development to go for it. Or not.

Therefore my question, if It's generally possible to downgrade from 1.3.4 to 1.3.3. ?

(Just to mention: therefore I gave up reporting such very rare or long term issues. With the Nordic policy of "user provided logs" that doesn't make sense and is very ineffective.)