NRF_FAULT_ID_SDK_ERROR in application initialization

[Bruno]

Hi, 

I'm attempting to flash program a Nina B112 Bluetooth Module (from Ublox), which is built uppon a NRF52832 board and i'm attaching this module to a custom board.

I'm Using SDK version 15.2.0 and softdevice s132 version 6.1.0. I was able to compile and flash program Nina B1 EVK and it worked perfectly.

I'm coding and flashing programing in Eclipse IDE on windows 10 64 bits.

The problem is when i try to flash program my custom board. The code start running (when flashing the .out file for debugging) and it stops at the app_error_fault_handler in the NRF_FAULT_ID_SDK_ERROR case. I don't know how to monitor the log output in eclipse so i added a breakpoint to see the error_info_t var and it's displays

line_num = 0, p_file_name = 0 and err_code = 12

 I've done some codes before, using the SDK version 14.0, generated the images and flash programed this custom board and it worked with no errors. Because of that i don't think it's a hardware issue. I don't know where the problem might be. This application basically uses uart, flash storage (internal flash), BLE (Nordic Uart Service and Battery Service), ADC and App Scheduler.

Could someone please help me?

Thanks in advance,

Bruno.

[Bruno]

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?

[Marjeris Romero]

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

[Bruno]

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

[Marjeris Romero]

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

[Bruno]

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!!!

[Marjeris Romero]

You're welcome!