nrf51822 + gdb + printf

RE: nrf51822 + gdb + printf

L.B. — Mon, 11 Mar 2019 09:46:09 GMT

YESSS! I've included -DDEBUG as you said and then the printf would go into the function app_error_save_and_stop( ) and hang. I followed the comments in it -

// If printing is disrupted, remove the irq calls, or set the loop variable to 0 in the debugger.

and changed (at compile time, not with the debugger)

volatile bool loop = true; ------> to ------> volatile bool loop = false;

in that same function and yay - it works now!

Thanks for the help!

Really appreciate it!

RE: nrf51822 + gdb + printf

Hakon — Fri, 08 Mar 2019 13:02:51 GMT

Try to set the DEBUG preprocessor symbol and run the code again.

RE: nrf51822 + gdb + printf

L.B. — Fri, 08 Mar 2019 08:58:42 GMT

Unfortunately it still resets but this time stops at the line when I was previously on. I can't even explain this behahiour :-D

RE: nrf51822 + gdb + printf

Hakon — Thu, 07 Mar 2019 15:32:17 GMT

Hey, try removing all the breakpoints and see if it still resets.

RE: nrf51822 + gdb + printf

L.B. — Wed, 06 Mar 2019 17:56:42 GMT

Our team has found that commenting out the ble_advertising_start() function will make the printf operate correctly, so we assume that this is due to the softdevice that interrupts the current main context. And we have no debugging info for it.

But we are not 100% sure if this is the cause...