[ncs 1.9.0] Hard fault occurred if phone sent packet to NRF5340.

[Jeffery]

Hi Nordic team

I tried ncs 1.9.0 peripheral_uart sample (\TOOLCHAIN\v1.9.0\nrf\samples\bluetooth\peripheral_uart) at PCA10095 v1.0.0 DK. 

1. Application core: Board is nrf5340dk_nrf5340_cpuapp_ns. Flash peripheral_uart sample.

2. Network core:     Board is nrf5340dk_nrf5340_cpunet. Flash RPMsg sample.

3. NRF Connect for mobile app at Samsung s52 smart phone.

=> Advertising was ok. Phone can connect DK. Phone can send packet to DK normally.

=> But, as I tried DK sent packet to phone. RTT low showed "hard fault" and DK rebooted.

Fullscreen ncs190_ng.txt Download

00> [00:00:00.413,818] <inf> fs_nvs: 2 Sectors of 4096 bytes
00> [00:00:00.413,818] <inf> fs_nvs: alloc wra: 0, fe8
00> [00:00:00.413,818] <inf> fs_nvs: data wra: 0, 0
00> [00:00:00.441,741] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.441,772] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:21.276,428] <inf> peripheral_uart: Connected 6D:3B:6B:9B:9B:B6 (random)
00> [00:00:29.328,491] <err> os: ***** HARD FAULT *****
00> [00:00:29.328,521] <err> os:   Fault escalation (see below)
00> [00:00:29.328,521] <err> os: ***** BUS FAULT *****
00> [00:00:29.328,521] <err> os:   Precise data bus error
00> [00:00:29.328,521] <err> os:   BFAR Address: 0x36004a
00> [00:00:29.328,552] <err> os: r0/a1:  0x0036004a  r1/a2:  0x2000cd14  r2/a3:  0x00000002[0m
00> [00:00:29.328,552] <err> os: r3/a4:  0x00000020 r12/ip:  0x00000000 r14/lr:  0x000226c5
00> [00:00:29.328,552] <err> os:  xpsr:  0x21000000
00> [00:00:29.328,552] <err> os: Faulting instruction address (r15/pc): 0x000251b4
00> [00:00:29.328,552] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
00> [00:00:29.328,552] <err> os: Current thread: 0x200087f0 (unknown)
00> [00:00:29.619,140] <err> fatal_error: Resetting system
00> [00:00:00.308,563] <inf> fs_nvs: 2 Sectors of 4096 bytes
00> [00:00:00.308,563] <inf> fs_nvs: alloc wra: 0, fd0
00> [00:00:00.308,563] <inf> fs_nvs: data wra: 0, 1c
00> [00:00:00.336,853] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.336,853] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:57.290,954] <inf> peripheral_uart: Connected 6D:3B:6B:9B:9B:B6 (random)

Then, I went back to ncs 1.8.0 peripheral_uart and RPMsg samples at same DK. Everything was same except firmware.

I found DK can sent packet to phone without problem as ncs 1.9.0.

Cloud you double check this issue? I didn't modify Kconfig/prj.conf or source code.

Thanks.

Fullscreen ncs180_ok.txt Download

00> [00:00:00.011,474] <inf> fs_nvs: 2 Sectors of 4096 bytes
00> [00:00:00.011,474] <inf> fs_nvs: alloc wra: 0, fe8
00> [00:00:00.011,474] <inf> fs_nvs: data wra: 0, 0
00> [00:00:00.036,499] <inf> bt_hci_core: No ID address. App must call settings_load()
00> [00:00:00.036,499] <inf> peripheral_uart: Bluetooth initialized
00> [00:00:01.724,914] <inf> peripheral_uart: Connected 6D:3B:6B:9B:9B:B6 (random)

[Jeffery]

Hi

Same. It got same issue at nRF Toolbox/UART.

This issue was when the board sent uart data to phone. Data can be received at the app but it disconnected immediately after that.

Then, you can see "Hard Fault" information  in log.

As to "write a command" to the board, it is ok without problem.

Please help me double check it. Thanks.

[Øivind]

Ok, the "UART" in nRF Toolbox seemed to work without issues for me yesterday, but now I got a hard fault after sending data successfully both ways multiple times.

Thank you for letting us know, I'll investigate and make an internal report.

I'll update you when I know more.

[Jeffery]

Hi

Thanks.If any update, please let me know.

Thanks.

Jeffery