This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Console window text is corrupted during debug session

On a C28335-based project, we run our production board test from within the Code Composer debug session, and we use printf statements to the Console window to indicate pass, fail, or to describe details of a test result. 

On only one board (so far), the Console window text is corrupted. The rest of the test runs without failure, and the board appears functional at a higher level. This corruption almost looks like someone is holding the shift-key down (exclamation points become 1's and capitalization is often switched).

The fact that this only happens on one board suggests a hardware problem, but I would think that the debugger is somehow attaching itself to the stdio, so the entire path should be digital, so this makes no sense. 

Is there any documentation that describes the mechanism between calling printf or puts and how it attaches to the Console window? Any other ideas would be appreciated. 

Thanks,

Jim

  • Jim,

    A good page that talks about Console I/O is:
    processors.wiki.ti.com/.../Tips_for_using_printf

    The Console I/O functions are very complex and, despite properly connected to the debugger via a purely digital path, they still require a fair amount of processing on the device side (including setting a breakpoint). In this case, the status and integrity of the device will certainly influence the output. I have seen this myself in the past with corrupt messages caused by buffer overruns.

    At last, a tip to decrease the Console I/O impact on the target is mentioned in section 4.1.

    Hope this helps,
    Rafael