• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 2036 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

The CCS5.4 terminal plug-in doesn't display any output from a Stellaris Virtual Serial Port unless the baud rate is dropped to 9600

Chester Gillon
Guru 92251 points

I am running CCS 5.4.0.00091 on Windows XP 32-bit SP3.

Using a Stellaris launchpad EK-LM4F120XL to run programs which output to UART 0, which is connected to the Stellaris Virtual Serial Port (in this case COM17).

Starting with the default settings of 115200 baud, 8 data bits, 1 stop bit, no parity and no flow control hyper terminal would capture output but the CCS Terminal plug-in showed no output. The same problem occured with baud rates of 57600, 38400 and 19200. The baud rate was changed in the application running on the lauchpad and the com port settings.

When the baud rate was finally dropped to 9600 the CCS Terminal plug-in started capturing output.

Given that hyper terminal captured output at all the baud rates tried, but the CCS Terminal plug-in only worked at 9600 baud, suggests a problem in CCS rather than the Stellaris launch pad.

  • 0
    Guru 92251 points

    Changed the serial port set up so that Stellaris target UART1 -> TTL to RS232C converter -> PC COM2. Where PC COM2 is a physical serial port. i.e. bypassed the Stellaris Virtual Serial Port in the Stellaris launchpad.

    With this changed serial port set up the CCS Terminal plug-in worked with all baud rates of 9600, 19200, 38400, 57600 and 115200.

    Therefore, the problem appears to the combination of the Stellaris Virtual Serial Port and CCS terminal plug-in not working if baud rate is (higher than) 9600 baud.

  • 0 in reply to Chester Gillon
    TI__Genius 15580 points

    Hi Chester, 

    I also tried to get Stellaris Launchpad to work with CCS Terminal View and had similar issues at higher baud rates. Terminal view uses an open source jar/library http://rxtx.qbang.org/wiki/index.php/Main_Page. for serial data communication. We have been developing a different feature that uses RxTx libraries bypassing terminal view and we had same issues, thus we can at least eliminate the GUI aspects of Terminal View.  Unfortunately, I don't have a resolution. I scanned RxTx bug list but I did not find a bug that matches this issue. 

    Martin

  • 0 in reply to MartinS
    TI__Guru*** 130875 points

    Hi Chester,

    that I am aware of ... the launchpad (for an unkown reason so far) does not work with the terminal plug in in v4 or v5.  Putty and external terminals will work and I use putty with the launchpad myself.

    That I am aware of from the stellaris team, this issue still has an unkown root cause unfortunately.

    I hope putty or hyperterm could be an option for you and all the best.

    Best Regards,
    Lisa

  • 0 in reply to Lisa TI
    Guru 92251 points

    Lisa TI said:
    I hope putty or hyperterm could be an option for you and all the best.

    Sometimes even hyperterm causes no output from the Stellaris Launchpad to be captured. When that happens reseting the PC and/or the Launchpad makes the problem go away.

    Is the source code for the Stellaris Launchpad and PC ends of the "Stellaris Virtual Serial Port" publically available so that I could try and debug the problem?

  • 0 in reply to Chester Gillon
    TI__Guru*** 130875 points

    Hi Chester,

    this is a question for the stellaris and/or emulation team(s).   My recommendation is to post this question in the stellaris forum.

    Best Regards,

    Lisa