NRF_FAULT_ID_SDK_ERROR in application initialization

RE: NRF_FAULT_ID_SDK_ERROR in application initialization

Marjeris Romero — Thu, 07 Feb 2019 12:32:07 GMT

You're welcome!

RE: NRF_FAULT_ID_SDK_ERROR in application initialization

Bruno — Thu, 07 Feb 2019 10:26:20 GMT

hmmmm, i see, i didn't try that, that's a nice suggestion! I did flash my custom board using the SW pins from NINA-B1-EVK but didn't think about using it's RTT debugger output....

Thank you very much!!!

RE: NRF_FAULT_ID_SDK_ERROR in application initialization

Marjeris Romero — Thu, 07 Feb 2019 09:45:13 GMT

Hi Bruno,

I meant that you could maybe use the SWDIO and SWCLK pins from the NINA-B1-EVK debugger chip and connect them to your custom board, so this way you can use the onboard debugger in the NINA module to debug your custom board. So you could do the same thing as when using the onboard debugger on our nRF52 DK to debug custom boards, as explained in here.

BR,

Marjeris

RE: NRF_FAULT_ID_SDK_ERROR in application initialization

Bruno — Wed, 06 Feb 2019 16:10:06 GMT

Hi, Marjeris,

I already had my DEBUG flag in the sdk_config.h, removed compiler optimization according to nordic's tutorial for programming on eclipse and added the DDEBUG CFLAG to my Makefile. But, as i said, the line_num and p_file_name still shows 0x0 (zero)

I figured that i could see the RTT log on NINA-B1-EVK, but the problem is that when i flash the firmware to the evk I don't get any error, it runs perfectly, so there is nothing to see there....

I'm finishing some tests, but i'm almost sure the problem is with Tx and Rx pins unconnected during uart initialization. Now I'm testing the communication itself.

Thanks for your answer,

Bruno

RE: NRF_FAULT_ID_SDK_ERROR in application initialization

Marjeris Romero — Wed, 06 Feb 2019 15:48:16 GMT

Hi Bruno,

To debug this you should set the DEBUG flag, and remove compiler optimization. When using gcc you should change "OPT = -O3 -g3 " to "OPT = -O0 -g3 " in the Makefile. And set CFLAG to CFLAG += -DDEBUG

With this you may get more information when you debug and use breakpoints. You should try to get some information about lin_num and p_file_name.

And from the NINA EVK datasheet it seems as you can use the J-link hardware on the EVK-NINA-B1 to debug:

"The SEGGER J-Link software [5] is required to debug using the

onboard J-Link hardware on the EVK-NINA-B1."

So I think you should be able to get some RTT logs using the onboard debugger.

Best Regards,

Marjeris

RE: NRF_FAULT_ID_SDK_ERROR in application initialization

Bruno — Tue, 05 Feb 2019 18:33:08 GMT

Hey, I think i figured! Maybe the UART pins were unconnected and the code was getting stuck in the initialization! I'm still running some tests though.

RE: NRF_FAULT_ID_SDK_ERROR in application initialization

Bruno — Tue, 05 Feb 2019 10:34:35 GMT

So, basically, to summirize: i've written a code and generated it's image using SDK v15.2

I am able to burn it to my BLE module EVK, but i can't burn it to my custom board.

I've also written a code using SDK v14.0, generated it's image and I was able to burn it to both the EVK and my Custom Board.

Yesterday i tried changing my CustomBoard.h (pin definitions) to the same i used on my SDK v14.0 project, but the same error persists.

I also tried burning it with my EVK using the SW pins connected to my BLE module, but i did not succeed.

Is there some configuration that I'm missing in this SDK v15.2?

RE: NRF_FAULT_ID_SDK_ERROR in application initialization

Bruno — Mon, 04 Feb 2019 16:36:14 GMT

I was about to finish configuring all logs as you suggested, but then i realized: will i be able to see logs?

The problem is that i use the UART for communicating to another micro and i don't have a j linker debugger to check RTT responses, can i see RTT messages over Pe Micro Multilink Universal debug probe?

RE: NRF_FAULT_ID_SDK_ERROR in application initialization

Bruno — Mon, 04 Feb 2019 14:46:41 GMT

Hi, thanks for the answer,

Which log modules should i enable? (such as PDM_CONFIG_LOG_ENABLED, GPIOTE_CONFIG_LOG_ENABLED...?)

and by changing the log level, you mean change GPIOTE_CONFIG_LOG_LEVEL (for example) to level 4 (which is debug mode)?

RE: NRF_FAULT_ID_SDK_ERROR in application initialization

Marjeris Romero — Mon, 04 Feb 2019 13:41:17 GMT

Hi,

Do you have any debug log information? You can print the debug logs via UART or RTT by enabling the logging module in sdk_config.h. You should also change the log level to "debug", also in sdk_config.h.

Best Regards,

Marjeris