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.

TMS570LS SCI communication can only talk with terminal in CCS.

Other Parts Discussed in Thread: HALCOGEN

Hello All,

I've come across a very confusing issue during one of our developments. We use TMS570LS1115ZWT processor. We configured the SCI port to be used as DEBUG UART. Configuration was done using HALCOGEN.

Configuration,

baud: 57600
data width: 8
stop bits: 2
parity: none
flow control: none

This is working fine in CCS terminal window. 

But everywhere else this does not work. This is the first time such a thing happened to me. Any though on this issue?

Thank you.

  • Pradeepa,

    This doesn't make a lot of sense to me because there isn't really anything special about the Terminal program in CCS compared to another terminal program like PuTTY ..

    What exactly do you mean by "We configured the SCI port to be used as DEBUG UART. "
    Where did you configure this? That terminology doesn't ring a (specific) bell to me - so I am not sure what this means exactly.

    Best Regards,
    Anthony
  • Hello Anthony,

    Thank you for your reply. 

    I

    Anthony F. Seely said:
    What exactly do you mean by "We configured the SCI port to be used as DEBUG UART. "

    What I meant was, we configured the SCI interface to provide UART communication. And used that to make it easier for us to DEBUG the code. We would send messages through UARTPrintf function to the terminal connected to the SCI pins.

    Anthony F. Seely said:
    Where did you configure this

    All configurations were done in HALCOGEN.

    Anthony F. Seely said:
    This doesn't make a lot of sense to me because there isn't really anything special about the Terminal program in CCS compared to another terminal program like PuTTY ..

    I am also startled by the behavior. I have ordered a TMS570LS launchpad. I will test the code there to determine whether it works there. 

    Basically what happens is my usual terminal application "TeraTerm" cannot receive correct characters. It gives garbage output. But the terminal in CCS works perfectly. It does not provide any garbage character at all. I know it sounds unimaginable, but some issue is there.

    Let me know if someone has any thoughts on this.

  • Pradeepa,

    All I can recommend is:
    a) double check all of the COM port parameters, including the COM port # to see if they are matching between CCS and Teraterm.
    b) try a third program like PuTTY.

    -Anthony
  • Pradeepa,

    Just following up to see if there is still an open issue here?