MPSL Assert Error and Arch_Except Reason 3 error when using BLE

[mchamberlain1980]

Hello, I have a custom board that was designed for me, but based off of the Acconeer XM126.  It is very similar with a few minor differences.  The person who designed it has bailed and is no longer reachable.  I am a mechanical engineer with limited coding and electrical knowledge.  I have had to stumble my way through.  There were multiple errors with the board that I have had to fix so far including the wrong HF crystal.  He originally had a 24mhz crystal and I had it replaced with a 32 and proper load capacitance.  The other issue is that he added a push button for BLE pairing.  It appears he meant to send 1.8v to pin y23 when the button is pushed.  It is incorrect and is sending 1.8v to y23 all the time.  I don't know if that could be an issue or not.  I'm not sure where the call out would be for what to do with that pin when it was getting the voltage.  I have searched his source and header files.  The board works with the radar sensor when I flash it with normal distance detecting programs.  However, when I load my program or any example program that uses BLE it gives me the errors I have attached.  MPSL Assert 112, 2185 and Arch except reason 3.  Also, zephyr fatal error 3: Kernel oops on cpu 0, fault during interrupt handling.  This is the last piece of the puzzle for me.  Does anyone have any idea what this might be?  Please remember I am limited in my knowledge.  I have already spent thousands to get here, so I am trying to solve this on my own.  Thanks.

[mchamberlain1980]

Thanks.  I am curious at what the error codes mean.  I am still a little confused about why my program works with the original xm126 board, but not this board if it is a SW or config issue. 

I did notice that I can't flash my program to the xm126 using the 52840dk, only using mcuboot.  I get an error.  However, I can flash it both ways on my board.  I thought that I read if it is setup for mcuboot then it could have some memory issues if flashed by jlink?

My program does use the acconeer sdk.  Does the sdk or config settings matter in terms of the board though?  The xm126 uses the 52840 and the same sensor, of course.  The only major thing that was changed was the bluetooth antenna.  Just a different manufacturer.  

Thanks,

Mike

[JONATHAN LL]

Its clock related,

The MPSL assertion suggests that the 32M crystal did not ramp up, which could indicate a soldering or placement issue with the crystal. Please try to check if the crystal oscillator is able to start by using the code snippet I posted here:  RE: MPSL ASSERT: 112, 2134 if using multiple BLE communication 

So how is it working with another application? If you get one of our BLE apps to run on your device then you have some issues in SW, like manipulating the HFCLK from the application in some way.


Regards,
Jonathan

[mchamberlain1980]

Ok, that makes sense.  I'll try that code for checking ramp up time on the clock.  I haven't tried the other application yet.  I will try that tomorrow.  Is there any chance the load capacitance/crystal capacitors are causing it?  I know they are barely off, but just want to make sure.  

Also, how do I know what capacitors to use on the BLE circuit for matching?

Mike

[mchamberlain1980]

Also, I tried the peripheral_uart example and in my terminal I just get : *** Booting nRF Connect SDK 2.5.0 *** Starting Nordic UART service example.  It just keeps repeating that.  I tried adding in the snippet of code for the clock ramp up time from the thread you posted and I just got errors and couldn't build it.  Not sure what I did wrong there.  I just tried to add it to the uart example.  Would I get the error with the uart or would it just reboot over and over?  Any suggestions with testing the clock?  Sorry, I may be missing something. 

Mike

[JONATHAN LL]

Can you add this before "Bluetooth Initialized". 

NRF_CLOCK->EVENTS_HFCLKSTARTED = 0;

    NRF_CLOCK->TASKS_HFCLKSTART=1;

    while (NRF_CLOCK->EVENTS_HFCLKSTARTED == 0)

    {

        // Do nothing

    }

    LOG_INF("HFCLK started successfully. Stat: 0x%08x", NRF_CLOCK->HFCLKSTAT);

mchamberlain1980 said:

Sorry, I may be missing something. 

no problem, will try to solve this. 

Regards,
Jonathan