I am working on a demo project using a PyBoard v1.1 (STM32F405RG) and want to use the RTT functionality to assist with live debugging.
For this i'm using the SEGGER J-link GDB server and RTT client.
However it seems that I'm having some issues where the RTT buffer only gets read out when I hit a breakpoint somewhere in my application.
After it hits a breakpoint once, the RTT text seems to work, but lags behind one step from a printf on a serial terminal for a while.
So the RTT will output "Test: 19" whilst the serial terminal outputs "Test:20".
After a while, messages start to overlap on the RTT, even though this function is only called maybe once a second, manually via the serial terminal.
Essentially all i'm doing is this:
I have tried disabling interrupts which appears to have no effect on the results.
I have also tried changing the RTT config to it's various modes, which also had no effect.
Changing the SWD clock speed also had no impact on this.
Is there anything else I should be doing to get the RTT messages sent correctly?
For this i'm using the SEGGER J-link GDB server and RTT client.
However it seems that I'm having some issues where the RTT buffer only gets read out when I hit a breakpoint somewhere in my application.
After it hits a breakpoint once, the RTT text seems to work, but lags behind one step from a printf on a serial terminal for a while.
So the RTT will output "Test: 19" whilst the serial terminal outputs "Test:20".
After a while, messages start to overlap on the RTT, even though this function is only called maybe once a second, manually via the serial terminal.
Essentially all i'm doing is this:
I have tried disabling interrupts which appears to have no effect on the results.
I have also tried changing the RTT config to it's various modes, which also had no effect.
Changing the SWD clock speed also had no impact on this.
Is there anything else I should be doing to get the RTT messages sent correctly?