MSPL Assert Error when trying to run Beacon sample in nrf52832DK board

RE: MSPL Assert Error when trying to run Beacon sample in nrf52832DK board

Carl Richard — Wed, 01 Apr 2026 10:51:38 GMT

Hi again!

Ok. Does other BLE samples also fail? If so this may be a defective board.

What is the board version and how old is it? See the white sticker in the middle.

Best regards,
Carl Richard

RE: MSPL Assert Error when trying to run Beacon sample in nrf52832DK board

ShankarPV — Tue, 31 Mar 2026 18:14:09 GMT

Hi,

The board seems to be fine, its as per the picture you have shared. The components are soldered correctly. And I added the snippet before the bt_enable(). Also, I tried adding the CONFIG_CLOCK_CONTROL=n in the prj.cnf. As you had suggested I created a sample application that prints hello world on terminal. When I try building its throwing an error. But if I build without adding that line, its working. I'm attaching the log for reference.

devzone.nordicsemi.com/.../0211.BuildLog.txt

Thanks,

Shankar

RE: MSPL Assert Error when trying to run Beacon sample in nrf52832DK board

Carl Richard — Tue, 31 Mar 2026 08:39:02 GMT

Hello again!

Yes, this may indicate that there is an issue with the board. But first: could you explain how you were running the snippet? It must be run before bt_enable(). Also, you can try to add CONFIG_CLOCK_CONTROL=n in the configuration, so that Zephyr doesn't take hold of the clock. It's probably best to do the test in a blank sample, like hello_world.

Also, could you check if the DK is OK? Specifically the area around the X1 crystal (32 MHz):

Best regards,
Carl Richard

RE: MSPL Assert Error when trying to run Beacon sample in nrf52832DK board

ShankarPV — Mon, 30 Mar 2026 17:32:05 GMT

I tried with the code snippet. And the code seems to be stuck in the below loop

while(NRF_CLOCK->EVENTS_HFCLKSTARTED == 0)

Could it be because of any hardware issue in the board?

RE: MSPL Assert Error when trying to run Beacon sample in nrf52832DK board

Carl Richard — Mon, 30 Mar 2026 08:48:10 GMT

Hello Shankar!

Thanks for reaching out! The MPSL error you are seeing indicates a failed HFXO startup. Which specific sample are you using and have you done any alterations to it?

Please try to check if the crystal oscillator is actually able to start by using the code snippet Vidar posted here: RE: MPSL ASSERT: 112, 2134 if using multiple BLE communication.

Best regards,
Carl Richard