otSysInit freeze

[AshLabs]

Hello

I have an application running which boots up fine.

I've written a bootloader which boots up first, and then jumps into the application including softdevice.

So the application works without the bootloader. If i jump into the application from the bootloader, the application freezes at the thread_init function.

I suspect it to be the otSysInit function.

 

The bootloader device uses the app_timer instance, which initializes the RTC.

Because i think it's something related with the clocks that messes up the thread initialization process, but i'm not sure.

Any thoughts ?

Kind regards

[Edvin]

Hello,

You are using the nRF5 SDK for Thread and Zigbee, and not NCS, right?

Can you tell me how you programmed the device, and what you programmed on it? Did you remember to erase it before programming it?

And what did you program on the chip? bootloader? Softdevice? Bootloader settings?

What does the DK look like after you programmed it? Any LEDs turned on? Or is it a custom board?

Does the log say anything?

Have you tried debugging the application? What IDE are you using? Segger Embedded Studio? If so, look for the option Tools->Attach Debugger, as this doesn't program the device, but only starts a debugger session. If you program the device through the IDE, then the bootloader settings will be wrong. And how did you generate the bootloader settings (if you did)?

Best regards,

Edvin

[AshLabs]

Edvin

Thanks for the quick response!

Im programming it using GCC. So no SES. Using an ST-Link to flash my program to the board. It's a custom board.
I have serial output, so i have debug messages.
I've narrowed it down to the otInstanceInitSingle routine.

I've managed to find a thread that talks about this specific issue. Seems it's related to memory regions which kicks the MPU.
Trying to move some memory around, but no luck thus far. Hope i find it soon

https://devzone.nordicsemi.com/f/nordic-q-a/40790/thread-initialization-error-on-pca10059-using-multi-protocol-support-for-ble-and-thread-works-with-no-problem-in-pca10056/161336#161336

[AshLabs]

Ok it is solved. It is to do with the OT storage location.

The MPU does trigger everything. Since when moving the OT storage location from 0xFC0000 to 0xE00000 it gets resolved.

https://devzone.nordicsemi.com/f/nordic-q-a/60550/dfu-on-uart-for-pca10056