Part Number: DK-TM4C129X
I have a project for which I started development with the DK-TM4C129X and made use of UART0. This UART is supposed to be accessible through the virtual COM port that is set up when the DK-TM4C129X ICDI port is connected to the PC.
I have long since moved development to a custom board, which makes heavy use of UART0, and everything works fine. For various reasons, I wanted to make use of the DK-TM4C129X again, using some of the UART code being used for the custom board.
When the DK-TM4C129X ICDI port is connected, the virtual COM port is properly set up in Windows. However, when I open the Stellaris COM port using a terminal emulator like Putty and enter some characters, the entered characters appear to be echoed back to the terminal emulator by the debugger circuitry on the DK-TM4C129X without being forwarded to the TMC4 MCU.
I have the necessary jumpers installed on the DK-TM4C129X to connect UART0 to the debugger circuitry, and, in the application running on the TM4C, the UART is not set up to automatically echo back the characters.
I'm using IAR to develop, and can properly download and debug an application via the onboard debug circuitry, so the debug circuitry appears to work fine for this. If I put a breakpoint in the interrupt function for UART0 in my application running on the TM4C MCU, the breakpoint is not triggered when a character is sent.
I thought this virtual COM port to UART functionality was working when I started working with the DK-TM4C129X, but now it is not.
Any one else have this problem, and any recommendations for getting the virtual COM port to forward the characters to the TM4C UART instead of echoing them back to the terminal emulator?
Thanks in advance.
