Hi guys,

I am implementing a system for debugging an LPC82x device. I am also running FreeRTOS v8.0.1, and debugging through the JLinkGDBServer.

Previously, I used Segger RTT with no hassle using an nRF51822-based device. I brought the RTT source into the new project and can, periodically, see messages. All of the configurations are left as their default. However,

1. The messages come very sporadically and incompletely while the device is not stopped.
2. Once the device is stopped, either by halting debug or pausing, it causes the message buffer to be flushed

I can't see anything in the API or the configurations that would indicate that I would need to flush the buffer, and it's my understanding that the JLink device scans the memory to locate the control block and handle it from there. It looks like something is preventing the debugger from actually scanning the memory continuously. Are there any settings that would help to prevent this?

Thanks,
-Alex

Hi Niklas,

Thanks for the fast response.

I am using

* The LPCXPresso-824Max development board
* JLink Plus (SN609301623) using 5.12g software, firmware Aug 3
* The latest LPCOpen software

The reproduction steps were basically just to

* Use LPCXpresso to open the FreeRTOS blinky project (I duplicated it, but that shouldn't matter)
* Bring the SEGGER_RTT.h, .c, _conf, and _printf files
* Use SEGGER_RTT_WriteString(0, "In task2\n") in task2. Include the RTT header. I changed the rate to 1Hz
* Set up GDB debugging for the project via your instructions

Nothing else changed. I can compile and debug the project just fine, and changes to the code work as well. But I have tried both RTT Viewer, RTT Client, and a telnet connection (putty) to 19021 and I see similar behavior for RTT output in all methods. It works perfectly once I stop the target, where it should output on a regular basis without having to do that (from my experience with the nRF51 chip).

[Edit] I also thought that maybe operating from within a task was causing issues, so I put some additional writeString calls in main. Those were also not flushed unless I stopped the hardware.

Thanks,
-Alex

Hi,

It's been a while, I just wanted to check in. Are there any recommended steps to troubleshoot the issue?

Thanks,
-Alex