Reset with hard fault after bluetooth advertising

RE: Reset with hard fault after bluetooth advertising

Simonr — Thu, 15 Feb 2024 12:00:07 GMT

Glad to hear that you were able to resolve this issue! Let me know if you have any further questions.

Best regards,

Simon

RE: Reset with hard fault after bluetooth advertising

simoiamma — Mon, 12 Feb 2024 08:35:22 GMT

Hi Simonr,

I've noticed that the ramp up time changes once in a while: tipically is about 350us but sometimes goes up to 700us.

However, it was a problem of ramp up time of the external crystal oscillator. Starting it before the BLE subsystem solved the problem.

Thanks

Simone

RE: Reset with hard fault after bluetooth advertising

Simonr — Mon, 29 Jan 2024 12:06:50 GMT

This assert should be raised if the HF crystal is not running when it should be, and could indicate that the crystal oscillator ramp-up is too slow or that there's an issue with the HF crystal.

If it occurs just in some boards, what are the load capacitors set as on these boards. Another common issue is that the HF crystal is soldered on 90 degrees off, so that the GND pads are on the crystal pads and vice versa.

You can also try to measure the crystal's startup time. You can use the use the code snippet below for this (must be run before bt_enable()).

	NRF_TIMER1->BITMODE = TIMER_BITMODE_BITMODE_32Bit << TIMER_BITMODE_BITMODE_Pos;
	NRF_TIMER1->TASKS_CLEAR = 1;
	NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;
	NRF_TIMER1->TASKS_START = 1;
	NRF_CLOCK->TASKS_HFCLKSTART = 1;
	while(NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);
	NRF_TIMER1->TASKS_CAPTURE[0] = 1;

	printk("HF Clock has started. Startup time: %d uS\n", NRF_TIMER1->CC[0]);

Also, are you using mpsl_clock_hfclk_latency_set() in your code?

Best regards,

Simon