Debugging without disconnect

[mobi]

Hi,

I understand the the Android Counter part will disconnect from the my NRDF board if for debugging purposes I stop at break point in the code. (I'm using Keil uVision). because of no ack after the connection interval time I guess.

Is there a way it doesn't disconnect while I stop to debug some code in Keil.

Thanks

[Bill Siever]

This isn't quite what you asked for, but I've squashed many of my bugs with log messages (printing variable values and messages that help me see both the order of events and what code is being executed) rather than breakpoints.

If you are using Segger's J-Link, you can use Segger's Real-Time Terminal (RTT) for logging over the J-Link cable. Thanks to forum member jeremysf and post devzone.nordicsemi.com/.../ for sharing info. about RTT.

Segger's RTT package is available at: www.segger.com/jlink-real-time-terminal.html

I've put together a blog entry with some directions and even a package that makes it a bit easier to start using RTT. (The package is just an alpha version that suited my needs when I put it together. It could use an overhaul). If you're interested take a look at: http://siever.info/blog/?p=1

[Hung Bui]

Hi Mobi,

It's not possible to get back to a connection after you stop for a break point when debugging. The timing will not be correct after you resume, and most likely you will have a connection timeout from the peer device (which is not halted). As mentioned by Bill, it's better to use log message rather than breakpoint.