How to analyse bus fault, hardware exception crashes in zephyr on nrf52840

[Umamaheswara Rao Lankoti]

We have custom board based on nrf52840 and using  an application based Zephyr RTOS platform.

Sometimes, it is observed bus fault and hardware exception logs are observed and system is crashed.

SEGGER J-Link V6.44g - Real time terminal output
J-Link OB-SAM3U128-V2-NordicSemi compiled Jan 7 2019 14:07:15 V1.0, SN=683340489
Process: JLinkExe

rtt:~$ i2c probe 0
i2c probe 0
---Probing on 'I2C_0'---

***** BUS FAULT *****
Instruction bus error
***** Hardware exception *****
Current thread ID = 0x20000b58
Faulting instruction address = 0x30f808f0
Fatal fault in thread 0x20000b58! Aborting.

How to find where the crash occurred ?

If I use addr2line sometimes, I am getting ??:0 as response.

/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-addr2line -e hw_tests/build/zephyr/zephyr.hex 0x30f808f0
??:0

What are the best approaches available to resolve these kind of crashes ?

[bjorn-spockeli]

Hi Umamaheswara

Nordic contributes device support to the Zephyr open source project and can recommend it as a solution, though we do not offer technical support for Zephyr RTOS on nRF52 in DevZone today.

Hence, my suggestion would be to reach out to the Zephyr community through one of these channels:

• Mailing Lists: [email protected] is usually the right list to ask for help. Search archives and sign up here.
• Slack: Zephyr's workspace is https://zephyrproject.slack.com; you can register with this Slack invite.
• GitHub: Use GitHub issues for bugs and feature requests.

Best regards

Bjørn