This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

RTT - Slow Erase/Program Cycle

I just started using the RTT - It's proven to be a VERY helpful debugging tool. As soon as I started using it I located several minor bugs. I exited debug mode, fixed the bugs. After compiling, when I clicked Keils debug option, which erases and reprograms my part, the RTT-Viewer log went nuts, and the erase/program cycle takes a lot longer to complete.

My solution, is to close the viewer, reprogram, and re-open the viewer. Closing the viewer and reopening it is faster than letting it run while programming, but is a pain. Under the Terminals menu I disabled the "View Log". The erase and programming cycle is still very slow. Not to mention, viewer often locks up, after programming and I have to restart it.

Is there a way to disable the RTT Viewer while programming, so every time I modify my code I don't have to close and reopen it?

Here's a screen shot of the log: image description

Parents
  • Hi, c cook RTT viewer need a Jlink process to get the log data. When you select the USB connect mode, RTT viewer will create a new process to do this. The problem is when you start download or debug the chip, another new process will be created too. And they are all trying to connect the only one JLink device, it will be very slowly.

    image description

    If you used to view the terminal when debug the chip, you should select the Existing Session mode.

Reply
  • Hi, c cook RTT viewer need a Jlink process to get the log data. When you select the USB connect mode, RTT viewer will create a new process to do this. The problem is when you start download or debug the chip, another new process will be created too. And they are all trying to connect the only one JLink device, it will be very slowly.

    image description

    If you used to view the terminal when debug the chip, you should select the Existing Session mode.

Children
No Data
Related