CCS/TM4C1294NCPDT: How to see output of UARTprintf() in UARTstudio() on ccs console??

Respected sir,

i have already tried the method mentioned by you.  it is not working. I think it is problem of driver installation. i have uploaded the snap of device manager. In that it is not showing other devices. So i can not update the serial drivers. please tell me what should i do??

regards,

digvijay

Hello Digvijay,

I see the Stellaris Virtual Serial Port installed on COM4 from the snapshot you provided above. This is the port you would select instead of COM45 which I used in my example. No other driver is needed at this point.

Perhaps I misunderstand your question. Which of the following steps have you been able to accomplish?

1. Are you able to import and compile the example project in: "C:\ti\TivaWare_C_Series-2.1.4.178\examples\boards\ek-tm4c1294xl\hello"?

2. Are you able to connect and upload the program Debug\hello.out from your project?

If you are able to describe what you are doing, and what errors you encounter, then I will be better able to assist you.

respected sir,
i am able to import and rebuild project hello without any errors. Also i am able to program the controller successfully. i have done all the settings as u mentioned in your first reply. com port is 4. but i am not able to receive message transmitted by controller into ccs terminal. So i m not able to understand what is problem.

respected sir,

              i am able to upload hello.bin not hello.out. hello.out is not visible in LM flash programmer. i m getting just blinking cursor on terminal as shown in snap.

Loading hello.bin with LM flash loader will work, but if you are using CCS, that is the hard way to do it. If you build the project in CCS, you can use CCS to program the device as well.

Connect to the target by right clicking on the target configuration and selecting "Launch Selected Configuration". In my case I used the target configuration that was imported with the "Hello" project.

Then right click on the "Stellaris In-Circuit Debug Interface ..." and select "Connect Target"

Now from the menu select "Run" -> "Load" -> "Load Program". Select "Browse Project" and then expand the folder for "Hello" and the sub folder "Debug". Select "hello.out" and OK then OK again. This will program the code into the device and stop the device execution at the beginning of the main routine. Make sure Terminal is configured for 115200 baud and 8 data bits.

Now run the code by clicking the green arrow at the top of the window (under "Project" in the menu bar). You should see "Hello, world!" printed once on the screen.

This program only prints one time. To print again, you can reset the part either from CCS or with the reset button on the launchpad. I suspect the reason that you did not see the message when you programmed hello.bin with LM flash programmer. is that the program had run and completed after being programmed by LM Flash Programmer before you could connect with CCS. Pressing the reset button on the launchpad may have caused the message to appear in the Terminal window.

respected sir,

it is still not working. It is showing only blinking cursor like before. I still think it is problem of driver. As shown in snap there should be other devices in device manager. But according to previous snap of device manager, other devices is not there. So i think it is problem of driver. Please conform whether i am write or wrong. And if there is solution please suggest.

regards,

digvijay

I don't think it is the drivers. If you can connect to the EK-TM4C1294XL board, it is not the Stellaris ICDI drivers. If it is a driver problem, then the issue would be in the Stellaris Virtual Serial Port driver, but in the image you captured it looks like it is working.

Please check that the jumpers circled in blue in the image below are in the horizontal, UART position. This is the default position. If someone changed them to the vertical, CAN position, you would not see demo work properly.

SIR,

 they are in horizontal position only.

Windows Stellaris virtual COM driver baud rate is over ruled by application UART0 baud rate setting. Device manager Stellaris baud rate setting is for the most part meaningless.

CCS terminal baud rate 115,200BPS must match the "hello" application UART0 setting 115,200BPS. Very odd to find "hello" example application had configured UART0 for 9600BPS but not out of the question.

Respected sir,

You may be write. After reading this reply i did some analysis. I found out that it is working fine at baud rates 9600, 600 and 2400. It is giving garbage value for 4800. And it is not working at all for remaining standard baud rates. I wonder what is the problem. 

HI DJ,

The application may bottle neck data at certain UART0 baud rates. You can change UART0 rate in the applications configuration string to match your CCS terminal speed. Again you don't have to change Device manager COM speed though it is shown 9600 BPS. Since there is no hand shake between the UART FIFO and the application it can easily be flooded if the baud rate is set to high. The FIFO can also be jammed if the rate is set to low depending on the delay time between packets sent to the FIFO. Application buffer size being increased helps the FIFO at higher data rates process the payload, not so much at slower rates less the buffer is huge, 32KB or so.