Data Bus Hard fault when handling secure connection bonding

RE: Data Bus Hard fault when handling secure connection bonding

Susheel Nuguru — Wed, 25 Nov 2020 08:33:05 GMT

That is hard to debug but not impossible. I would rather suggest you to increase stack modestly for every task you have and if that helps, reduce the size back to what it was before to isolate the task in question.

RE: Data Bus Hard fault when handling secure connection bonding

asaf — Wed, 25 Nov 2020 08:06:14 GMT

how can I find which task need more stack ?

RE: Data Bus Hard fault when handling secure connection bonding

Susheel Nuguru — Wed, 25 Nov 2020 07:51:10 GMT

It looks like a register pop has been done from a corrupted stack frame which in turn corrupted the PC value. Check if you have enough stack allocated for each task you have and check if you have enough heap dedicated in FreeRTOSConfig.h file to dedicate bigger chunks of stacks for tasks.

RE: Data Bus Hard fault when handling secure connection bonding

asaf — Tue, 24 Nov 2020 13:13:59 GMT

sorry my project is an company code that run on dedicated hardware.

the issue doesn't occurs on optimization level "Debug".

the fault I get while pushing button ( then no issue when call the same function the button call by software).

another fault I get is:

<error> hardfault: HARD FAULT at 0x00000004
<error> hardfault: R0: 0x20006594 R1: 0x200064E8 R2: 0x2000D444 R3: 0x2000D444
<error> hardfault: R12: 0x20008278 LR: 0x00000004 PSR: 0x6000000E
<error> hardfault: Cause: The processor has attempted to execute an instruction that makes illegal use of the EPS

RE: Data Bus Hard fault when handling secure connection bonding

Susheel Nuguru — Tue, 24 Nov 2020 13:08:48 GMT

Hmm, This thread slipped my radar, I see that there is no solution discussed here. Could you please upload your project for me to quickly do a test on my desk?

RE: Data Bus Hard fault when handling secure connection bonding

asaf — Tue, 24 Nov 2020 13:03:48 GMT

hi , I'm facing the same issue.

<error> hardfault: HARD FAULT at 0x0003210E
<error> hardfault: R0: 0xD26970F8 R1: 0x000003FF R2: 0x2000D444 R3: 0x2000D444
<error> hardfault: R12: 0x20008278 LR: 0x00032101 PSR: 0x6100000E
<error> hardfault: Cause: Data bus error (PC value stacked for the exception return points to the instruction that caused the fault).
<error> hardfault: Bus Fault Address: 0xD26970F8

addr2line gives me port.c : 104.

I have applied the suggested changes in the SDK

using sdk 16 with nrf52833

Thank you

RE: Data Bus Hard fault when handling secure connection bonding

Andreas48752 — Tue, 01 Oct 2019 10:13:28 GMT

Hello!

I think I may have the same problem here when using freeRTOS and calling nrf_ble_lesc_request_handler() in a task. But how to fix this? What was your solution? Thanks!

RE: Data Bus Hard fault when handling secure connection bonding

thin_ice — Mon, 15 Apr 2019 16:32:34 GMT

Did you mean the instruction address that I provided earlier ? Please see my previous responses

RE: Data Bus Hard fault when handling secure connection bonding

Susheel Nuguru — Mon, 15 Apr 2019 08:04:48 GMT

Sorry for very late reply. Most likely you figured this out by yourself.

the idea is to keep the logic into similar context. I do not still like the hardfault being triggered, can you get the instruction address of the memory that caused the hardfault?

if you have already solved this, can you please update this thread so that others could get help from your experience.

RE: Data Bus Hard fault when handling secure connection bonding

thin_ice — Wed, 27 Mar 2019 22:12:31 GMT

so I confirmed that cause was I put nrf_ble_lesc_request_handler() in a freeRTOS task. This is because in the barebone example I saw they put it in the main loop so I had a task and stick it in. How do I explain the hard fault and how can I fix ?

RE: Data Bus Hard fault when handling secure connection bonding

thin_ice — Wed, 27 Mar 2019 15:53:12 GMT

so I found out that in sdk_config.h if I have #define PM_HANDLER_SEC_DELAY_MS 400 then immediately after connection is initiated I get a hard fault, but if I change it to #define PM_HANDLER_SEC_DELAY_MS 0 then I don't. This is already with the sdh_freertos.c patch you mentioned so I don't think the patch did anything.

Now with the interrupt priority mod, I still have the same problem. In my application, I stripped everything hardware out, what remains is just BLE stack and a couple of tasks. One of the task has nrf_ble_lesc_request_handler(), one is the "Logger" task.

RE: Data Bus Hard fault when handling secure connection bonding

Susheel Nuguru — Wed, 27 Mar 2019 06:29:22 GMT

great, try out the patch and see if you have any application specific interrupts where you are not using our driver and forgot to configure the interrupt priority of that interrupt.

Also try the below fix by changing the define

__NRF_NVIC_SD_IRQS_1 0

__NRF_NVIC_SD_IRQS_1 ((uint32_t)(1U << (MWU_IRQn - 32)))

in the nrf_nvic.h header.

RE: Data Bus Hard fault when handling secure connection bonding

thin_ice — Tue, 26 Mar 2019 15:44:31 GMT

Hello, I am using SDK 15.2 and the address points to this line (xPortPendSVHandler) as you requested.

nRF5_SDK_15.2.0_9412b96/external/freertos/portable/GCC/nrf52/port.c:104

I am going to try the patch and let you know if it helps

RE: Data Bus Hard fault when handling secure connection bonding

Susheel Nuguru — Tue, 26 Mar 2019 08:02:08 GMT

Hi,

Which SDK are you using?

There are two parts of investigation

1) Try to find out if you have applied this patch to softdevice_task as it might cause some deadlocks and wrong states in the statemachine of peer manager

2) The Hardfault address 0x2C8FC is inside the application code. The below line should be able to reveal the instruction that is causing the hardfault. We can take a closer look after understanding what that is.

addr2line -e <src.elf> 0x0002C8FC