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.

LAUNCHXL-F28379D: SCI Echoback Program not executing in F28379D

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: TMS320F28379D, C2000WARE

Hi,

I tried the SCI Echoback Program from the device support library(C2000Ware Latest) as my first code on Ti TMS320f28379D. I was able to built and debug the code onto the board with out any error.But when i connect the same to Hyper terminal or Putty the Port shows nothing. It is BLANK. When I type something and press Enter the "D8" Led Blinks (Shows some Response). I am not getting proper SCI Echoback output.  Tried with different SCI Ports by following some TI forums still no response. 

Please Help Me at the earliest.

Thanks.

Shiva

  • Maybe simple question, but i have to ask : Did you check baud rate ?
  • Hi Shiva,

    I'd definitely try scoping the SCI pins that you are using to see what, if any, activity is occurring on the pins. If you see activity you can also pretty easily estimate baud rate and see if it matches expectations.

    Are you using the virtual COM port or a physical RS-232 transceiver?
  • Yes.
    I have checked the Baud rate.
  • Hi Devin,
    I am using Virtual COM port.
    The TI board is receiving data from the System but not sending back any to the PC.
    Only the D8 LED blinks and Echoback LED doesn't.
  • Hi Shiva,

    Do you get garbage or nothing on the PC serial console when you start running the MCU code while the PC is listening and the MCU transmits the initial "Hello World!" and then "You will enter a character, and the DSP will echo it back!"?

    If you get nothing, next step would be to double check the GPIO muxing for your board. If that looks good in SW, use a scope to observe the SCI pins and see what activity is occurring when that initial message is sent. If you see activity, then check that the baud looks good. If the baud looks good, then make sure that the virtual COM port is recognized by the PC. If that looks good, make sure your serial console is listening on the correct port.

    If you get garbage, you want to check the SCI baud settings, MCU system clock, LSPCLK, and baud configurations in the serial console.