error_code = 0xDEADBEEF

[smart]

Hello! I'm using the evaluation kit and i have two questions: firstly, I'm trying to make up a program that allows the communication between two modules, on one side a glucose meter and on the other side a Smartphone application (re-using ble_app_uart). It worked good until three days ago the Bluetooth started to disconnect when the nRF should send the data. I followed the problem and I found this: error_code: DEADBEEF Line_num: 0x00000343 s_file_name: 0x73,0x72,0x63,0x5C,0x6C,0x6C,0x5F,0x6F,0x2E,0x73,0x30,0x2E,0x63 and I can't figure out what is the source of this error ! and don't know how to correct this. Can tell me what the source of this problem is and how to make the program work?

Secondly: there is any documentation that explain how to interface the stack with the application? Thank You.

[cocoa]

Have you enabled debug flag in compiler (-DDEBUG -g3) ?

-c

[smart]

I don't think this is the problem ! but this is my compiler control string : -c --cpu Cortex-M0 -D__EVAL --li -g -O0 --apcs=interwork --split_sections -I........\Include -I........\Include\app_common -I........\Include\s110 -I........\Include\ble\ble_services -I........\Include\ble -I........\Include\sd_common --c99 -I C:\Keil_v5\ARM\RV31\INC -I C:\Keil_v5\ARM\PACK\ARM\CMSIS\3.20.4\CMSIS\Include -DNRF51 -DBOARD_PCA10001 -DNRF51 -DDEBUG_NRF_USER -DBLE_STACK_SUPPORT_REQD -o "._build*.o" --omf_browse "._build*.crf" --depend "._build*.d"

[cocoa]

Debug flag was my hope in more verbose gdb messages about error_code when debugging using gcc. I'm not using keil compiler and I do not know much about debugging with it, I'm on OS X. -c

[cocoa]

Maybe solved, error coming from : src\ll_o.s0.c line number 835.

[John]

That assert is coming out of the Soft Device Stack. Typically when I see this, the application code has asserted, and then the Soft Device attempts to handle an event and asserts again. The easiest way to debug this is to set a breakpoint in your assert handler and catch the first assert.