Hangs on sd_softdevice_enable

[studzinski]

It happens on a new board. It is possible that an HW problem occurs (Xtall), but how to debug it?
How to know if Xtall correctly runs? The same code runs correctly on another board...
It is also possible, that the SD (112  v. 5.1) is not correctly loaded, but how to check it with Keil?

In my case, I suspect a wrong Xtall frequency (16MHz instead of  32), but why does it hang the application?

It is strange enough, only the radio part of application does not run (hangs up). The not "ble" functions work well.

How to manage this kind of errors?

Thank you in advance for any help

[Hakon]

How to know if Xtall correctly runs?

 You can try this

// Start HFCLK from crystal oscillator.
NRF_CLOCK->TASKS_HFCLKSTART = 1;
while (NRF_CLOCK->EVENTS_HFCLKSTARTED == 0);

When the HFCLK starts, it generates an event, so if the application never exits the while, it means that the HFCLK hasn't started.

[studzinski]

So, if I well understand, I have to wait some time (1 second?) for event, and not initialize BLE if no such event occurs.

Have not I?

Cordially

Andre

[Hakon]

I don't know how long it takes for the HF clock to start, but that's how you know it's running. Have you confirmed that the HF clock doesn't start?

[studzinski]

My question is only for the error management. In my case it was the wrong X-tal frequency. All works well after the crystal replacement to a good one... But we need to check it during standard manufacturing test. Could you confirm that one second is enough?

[Hakon]

It says in the product spec  that the HFXO has a typical startup time of 0.36 ms. I'm sure it will vary to some degree. You decide whether you think one second is enough based on that.

[studzinski]

Thank you for your comment.
I understand now that it is enough.
But it was a QUESTION to YOU.
I thought that YOU could "decide" better then I.
Sorry for my stupidity...

Cordially yours

Andre