Hardfault Error after calling sd_ble_gap_adv_start

RE: Hardfault Error after calling sd_ble_gap_adv_start

RK — Wed, 10 Feb 2016 13:09:49 GMT

oh if you're trying to debug with the softdevice running that's not going to work, that's another often-discussed topic. Once you break into anything with the softdevice running, you can't restart, the softdevice will assert as you're ruined its strict timing rules.

RE: Hardfault Error after calling sd_ble_gap_adv_start

JensWoermann — Wed, 10 Feb 2016 13:06:13 GMT

Ok. If gote some new findings. The system runs correctly when I don't use the Seeger debug module (and let it run in free mode). It seems it may be a debugger problem.

RE: Hardfault Error after calling sd_ble_gap_adv_start

RK — Wed, 10 Feb 2016 12:52:14 GMT

ok if you really are in the hardfault handler then you can try to piece things together and work out where you came from and what was going on to cause the hardfault. It's painful but not impossible and with a bit of luck you'll find you were in a piece of your own code.

RE: Hardfault Error after calling sd_ble_gap_adv_start

JensWoermann — Wed, 10 Feb 2016 08:52:17 GMT

Hello,

Me again. I try it with PCA10028 Demoboard, Softdevice S110_nrf5_8_0.0 (Id:0x0064) and the ble_app_cts_c example. And it dosn't work either. The result is the same. After one cycle the system runs to Hard fault.

RE: Hardfault Error after calling sd_ble_gap_adv_start

JensWoermann — Wed, 10 Feb 2016 08:29:57 GMT

No. The only time we are calling a softdive function outside the scheduler calling from main are in the moment in on_conn_params_evt

err_code = sd_ble_gap_disconnect(m_conn_handle, BLE_HCI_CONN_INTERVAL_UNACCEPTABLE);

Regards

Jens Wörmann

RE: Hardfault Error after calling sd_ble_gap_adv_start

RK — Wed, 10 Feb 2016 08:21:27 GMT

are you calling any softdevice functions (ie anything starting sd_) from inside your interrupt handler?

RE: Hardfault Error after calling sd_ble_gap_adv_start

JensWoermann — Wed, 10 Feb 2016 07:18:36 GMT

Hello,

I only use two interrupt by my side. Its for one timer to realise the time scheduler (1ms) and the security timer (like discriebed in ble_cts_c exapmple for the sequrity request timeout). The only perepheries I using are these 2 timers and some digital IO's. (excluded the ble stack events and error handlers)

There is no further code except the timer init and the time scheduler, the IO initialistion and the ble stack. (mostly taken from ble_cts_c)

I do not getting any error code when calling the function. At this point the system chrash down / run to hard fault handler and give not back any error code. (because it dons't reach the return potin). I check the error codes during all other ble stack initalisations (ble stack init, gab init, etc.) - that looks fine. (returns always NRF_SUCCSES or 0x00000000)

I'm going to check today the interrupt priorties. There is no point in my mind where i disable the IRQ functionalties knowingly. I'm going to check this, too.

Regards

Jens

RE: Hardfault Error after calling sd_ble_gap_adv_start

run_ar — Wed, 10 Feb 2016 05:52:52 GMT

Do you get any error code when calling sd_ble_gap_adv_start? What interrupts priorities are you useing? Do you have any critical sessions in your code where you could be disabling interrupts?