MPSL ASSERT: 112, 1617 on single board, suspect hardware

NCS 2.7.0, NRF52840, SYSBUILD with MCUBOOT

We have 1 specific board which is failing with a hardfault and assert MPSL ASSERT: 112, 1617   it occurs whenever we activate bluetooth.  Other boards of the same PCB do not have this problem.  This board previously did not have a problem but recently started.

!) Any idea what might be the root cause for the assertion?

2) If this would be caused by a hardware issue, is it possible for us to create a specific manufacturing test software to catch the issue?

Parents Reply
  • I created a test, but it is not showing a failure.

        //request HFCLK to be running
        int ret = clock_control_on(clock0, CLOCK_CONTROL_NRF_SUBSYS_HF);
        if (ret) {
            LOG_ERR("HF clock enable failed %d",ret);
        }
        nrf_clock_hfclk_t hfclk_src;
    	clkstat = clock_control_get_status(clock0, CLOCK_CONTROL_NRF_SUBSYS_HF);
    	running = nrf_clock_is_running(NRF_CLOCK, NRF_CLOCK_DOMAIN_HFCLK, &hfclk_src);
        if ((CLOCK_CONTROL_STATUS_ON != clkstat) || !running)
        {
            LOG_ERR("HF clock not running");
        }
        else if (NRF_CLOCK_HFCLK_HIGH_ACCURACY != hfclk_src)
        {
            LOG_ERR("HF clock wrong source %d",hfclk_src);
        } 
        else {
            ret =   clock_control_off(clock0, CLOCK_CONTROL_NRF_SUBSYS_HF);
            if (ret) {
                LOG_ERR("HF clock disable failed %d",ret);
            }
            else
            {
                LOG_INF("HF clock is working");
            }
        }

Children
No Data
Related