Printing Runtime Errors Through the Serial Port/ TY51822r3 ERROR with BLE API

30 Apr 2018

Hello,

I am bumping into a mysterious error on a TY51822r3 board (nRF51822 based) that is setting LED1 and making the device to stop running in the middle of printing one of the flag strings that I set on my code. I am using the BLE API for an Eddystone service.

(This error only occurs when using the mbed OS posterior to 5.2.1. Before this version the device would stop running after about 10 minutes, as described in this other post - https://os.mbed.com/forum/bugs-suggestions/topic/28352/?page=1#comment-53790)

I guess that it must be memory related but I am not being able to track it to the cause.

I am hoping that there is a way to inspect the runtime error. Is there any way of printing the error through the serial port? How can I access the runtime error log? I tried changing the baud rate, as I read somewhere that this might do the trick, but with no result.

Thank you in advance!