• State Not Answered
  • Replies 3 replies
  • Subscribers 65 subscribers
  • Views 174 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 328111
Options

Custom board, Modem crash, error 0x11. Modem FW 1.3.6

tsotnek

Hello,

My application runs perfectly for like 14-15 hours and then when trying to connect to go into RRC connected mode to transmit the modem crashes with following error. I enabled modem fault handling in Kconfig, so it should reset the modem during the fault, but that also gives me an error.

[15:01:46.602,844] <inf> System: RRC mode: Connected
[15:01:47.988,006] <err> nrf_modem: Modem has crashed, reason 0x11, PC: 0x688de
[15:01:47.988,067] <inf> nrf_modem: Modem has crashed, re-initializing
[15:01:47.988,098] <err> lte_lc: Failed to set functional mode. Please check XSYSTEMMODE.


P.S. The program counter value seems to be always same: 0x688de

  • 0

    Hello,

    can you do a modem trace, and try to get what happens right before the crash?

  • 0 in reply to Hakon

    Hello,

    Unfortunately, I cannot provide a modem trace, as the unit is being field tested and it is also very random. So it might take 26 hours for the modem to crash. 

    I can however explain what the application does. So I trigger single fix GNSS but only when RRC is in Idle mode (controlled by semaphore) and I trigger MQTT task (so switching to RRC connected mode) only when GNSS is in sleep mode (controlled by semaphore). Also, I am using UART1 in interrupt mode to receive some data from a sensor. 

    As I said, the system works for different amounts of time before encountering the modem crash, which happens randomly, but only in RRC-connected mode.

    I hope that this information might be helpful.

  • 0 in reply to tsotnek
    tsotnek said:
    I can however explain what the application does.

    It's hard to know what is going on inside the modem without a modem trace. Can you reproduce this issue locally using a DK or something connected with UART or RTT? What you are describing seems like it should not cause any error at all, so to further debug the problem, you should find some way to reproduce the issue and get a modem trace. You can also try to enable as much logging in the application as possible, both MQTT logging and GPS logging.

Related