MPSL ASSERT: 1, 1310

RE: MPSL ASSERT: 1, 1310

Kenneth — Mon, 25 Aug 2025 13:14:26 GMT

No, it's telling the software how far ahead of the BLE event that it should startup the HFCLK.

Kenneth

RE: MPSL ASSERT: 1, 1310

HauJohn — Mon, 25 Aug 2025 02:49:35 GMT

I just want to clearly understand what the parameter CONFIG_MPSL_HFCLK_LATENCY means. Is it the ramp-up time during packet transmission and reception as shown in this diagram?

If that’s the case, then increasing this parameter could reduce the transmission speed, right?

RE: MPSL ASSERT: 1, 1310

Kenneth — Fri, 22 Aug 2025 16:59:35 GMT

Hi,

This is directly related to the settling time of the HFXO, in nRF Connect SDK v2.9.x it simply was configured to short.

Kenneth

RE: MPSL ASSERT: 1, 1310

HauJohn — Fri, 22 Aug 2025 06:13:22 GMT

As I understand, the most accurate method is to use a spectrum analyzer through a radio test to precisely determine the required capacitor value for stable radio clock operation. Increasing MPSL_HFCLK_LATENCY is only a workaround, correct?

Could you explain in detail what aspects are affected by increasing MPSL_HFCLK_LATENCY? For example, does it impact data transmission speed, power consumption during data transfer, etc.

RE: MPSL ASSERT: 1, 1310

Kenneth — Thu, 21 Aug 2025 18:37:43 GMT

[quote user="HauJohn"]MPSL_HFCLK_LATENCY [/quote]

Use this one yes.

[quote user="HauJohn"]HFXO internal capacitor configuration[/quote]

You should only configure this parameter during radio_test to ensure the carrier is as close as possible to the configured frequency when you are outputting a continuous carrier. For instance if you setup a carrier on channel 2, then use a spectrum analyzer and check which setting that get you closest to frequency 2402MHz. This parameter can also indirectly affect the startup time, but with wrong setting you can be off frequency (e.g. out of spec). The carrier should for a BLE device be maximum +-96kHz off center frequency (+-40ppm at 2.4GHz).

Kenneth

RE: MPSL ASSERT: 1, 1310

HauJohn — Thu, 21 Aug 2025 09:17:53 GMT

Hi, your method works. I also tried another approach by configuring the internal capacitor for the HFXO. With values from 4000 to 10750, the issue no longer occurs. However, specifically with the value 10500, the device encounters the same error immediately during advertising.

From what I read, increasing MPSL_HFCLK_LATENCY impacts power consumption.

Could you clarify the relationship between MPSL_HFCLK_LATENCY and the HFXO internal capacitor configuration as described above? Which approach would be the most appropriate to resolve the issue?.

RE: MPSL ASSERT: 1, 1310

Kenneth — Wed, 20 Aug 2025 10:38:57 GMT

Hello,

Try to change CONFIG_MPSL_HFCLK_LATENCY=1500

Kenneth