UART Application Problem

RE: UART Application Problem

Ole Morten — Tue, 24 Sep 2013 18:59:16 GMT

Please make sure that your app_error_handler does not do a reset, and try to halt the chip there to see if an error of some kind occurs.

By default, the error handler does a reset, so if some kind of error occurs, the device will reset directly, and abruptly ending any UART communication.

RE: UART Application Problem

ACS — Sat, 21 Sep 2013 08:02:39 GMT

Thanks for the tip about Eclipse debugging. I use Eclipse for almost every kind of development I do.

However, I also use the typical tracing through serial port to see the execution point and still it gets stuck at the connection level. I saw that I can send messages from the terminal (uart connection) to the iphone but if I do nothing for more than 3 seconds, the nRF blocks.

And if I send a message from the iphone to the nRF, it blocks also inmediately (no possibility even to trace anything).

Have anyone had a similar problem with this application?

Regards, M.

RE: UART Application Problem

Ole Morten — Fri, 20 Sep 2013 11:18:06 GMT

Have you had a look at this question?

It seems that what actually happens is that Eclipse makes GDB jump directly to the application's reset handler, instead of starting at the reset handler.

Another way to solve it seems to be to set the program counter manually on reset, as shown in the attached screenshot. The exact address you should set it to will be dependent on the softdevice version used, but you can read it out at address 0x04 in the flash of the chip. With softdevice 5.2.0 it should be 0x114BD, 5.2.1 0x114CD and 6.0.0-alpha1 0x11D35.