Configure and Debug Clock Control

RE: Configure and Debug Clock Control

Vidar Berg — Wed, 11 Jun 2025 12:07:58 GMT

Hello Jackie,

Thanks for the update. This confirms that the crystal oscillator is able to start up. If you need to request the HFXO clock in your actual application, I recommend using the onoff API as shown here:https://github.com/nrfconnect/sdk-nrf/blob/fc00e381aa120b6348d1f7afac5884e9e831d8f3/samples/peripheral/radio_test/src/main.c#L21. This will increment the request count for the crystal oscillator ensuring that the HFXO cannot be released by other SDK modules.

Note that keeping the HFXO active will make the idle current go from ~2-3 uA to ~200 uA.

Best regards,

idar

RE: Configure and Debug Clock Control

notkuroneko — Wed, 11 Jun 2025 03:14:58 GMT

Hello Vidar!

Sorry for the late reply, we were testing the crystal rampup code on both the old and new revision of the board.

So far the clock initiates just fine with the snippet you provided. I replaced that snippet into the clock startup method in our firmware and it seems to be working just fine!

Once again, thank you for your support!

RE: Configure and Debug Clock Control

notkuroneko — Fri, 06 Jun 2025 13:40:06 GMT

Thank you Vidar for your support!

We have a few prototypes for our hardware at the moment, i will try to run that on the boards that are not functioning.

I'll assume that the code for starting the clock manually should work and I'll debug it alongside your snippet.

Once again, thank you! I'll update once we get this running.

Best regards,

Jackie

RE: Configure and Debug Clock Control

Vidar Berg — Fri, 06 Jun 2025 12:41:03 GMT

Hello Jackie,

The CPU and other peripheral's requiring the HF clock runs by default from the internal RC oscillator (HFINT) and the clock_control_on() is to request the more accurate crystal oscillator (HFXO), but it seems like it is failing to ramp up as it's returns with -EAGAIN (-11). Could you please try to run the snippet I posted here and see if the program is able to exit the while loop RE: MPSL ASSERT: 112, 2134 if using multiple BLE communication ?

Best regards,

Vidar