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.

EK-TM4C123GXL: EK-TM4C123GXL: Communicating TM4C123GXL via the USB Debugger and USB Device port, what are the differences between these two and does it affect performance?

Part Number: EK-TM4C123GXL

Hi,

I am curious to know the difference between running a serial communication to the tm4c123gxl. I am currently doing a project on ROS that rosserial into the tm4c123gxl. However, i have discovered that there are two methods of doing it. One is via ICDI through the USB Debug and one is via USB CDC through the USB Device. My question is i will like to know are there any differences in running a serial communication protocol via these two methods in terms of performance and usage? My understanding of running via USB debug is that the ICDI on the tm4c123gxl board will convert into UART signal to communicate with the computer. But i am not very sure how does the USB CDC works in terms of that it's still communicating via UART but just on a different communication protocol? 

Pardon me for any lack of understanding in this area.

Regards

 

  • Hi,

      For the ICDI debug port, only the UART0 is connected (hardwired) to the ICDI debug probe for enumeration as a virtual COM port. The virtual COM port enumerated on the ICDI debug port is mainly for debug purpose. You cannot connect UART0 to any sensor you have and neither are other UARTx connected to the ICDI and therefore cannot appear to your host computer as COM port communication. With the USB device port you don't have the restriction. You will write your application to do  whatever you want, unlike the ICDI which has preloaded firmware that is only designed to accept UART0 as the COM port.