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.

Attaching an FT232 to SCI pins

Other Parts Discussed in Thread: TMS320F28335, CONTROLSUITE

Hi all,

I am currently developing with a TMS320F28335 experimenter kit and I have encountered a problem interfacing an FTDI FT232 USB-to-UART chip to the TMS320's SCI ports. I am using the example project sci_echoback. I downloaded the code to the TMS320 (booting from RAM) and used an oscope to probe the TX line of the TMS320 (GPIO 29), and verified that it is transmitting the correct pattern. I also 'scoped the output of the FTDI chip and verified that I was getting the correct UART patterns when I entered characters in a terminal.

However, when I attach the FTDI output to the RX pin of the TMS320 (GPIO28), in the scope trace the FTDI cannot pull the RX line to below about 2.7V. The edges of the square wave look crisp, but the voltage just stops at 2.7V. According to the code, the GPIO settings of GPIO28 are:

GpioCtrlRegs.GPAPUD.bit.GPIO28 = 0;    // Enable pull-up for GPIO28 (SCIRXDA)

GpioCtrlRegs.GPAPUD.bit.GPIO29 = 0;   // Enable pull-up for GPIO29 (SCITXDA)

GpioCtrlRegs.GPAQSEL2.bit.GPIO28 = 3;  // Asynch input GPIO28 (SCIRXDA)

GpioCtrlRegs.GPAMUX2.bit.GPIO28 = 1;   // Configure GPIO28 for SCIRXDA operation

GpioCtrlRegs.GPAMUX2.bit.GPIO29 = 1;   // Configure GPIO29 for SCITXDA operation

 

I tried configuring the SCIB module in the same way as SCIA and attached the FTDI to its RX line (GPIO 19), and I got the same behavior.

As another experiment, I configured GPIO pin 25 as digital input with the pullup disabled (GpioCtrlRegs.GPAPUD.bit.GPIO25 = 1, GpioCtrlRegs.GPADIR.bit.GPIO25 = 0). When I attached the FTDI output line to this pin, it DID work; that is, the FTDI was able to drive the line all the way down to 0V.

Has anyone else encountered problems attaching an FTDI to the SCI modules on the TMS320? Also, are there any ESD protection diodes or some other GPIO setting that I have neglected to consider? Thanks.

-SW

  • The newer experimenter's kit already has a FTDI FT2232 USB-to-Serial device on it.  Perhaps you are using an older experimenter's kit without this circuit.

    Regardless, the TMS320F28335 code examples found in controlSUITE have an example where the SCI interface echoes characters received from the FT2232 and sends them back to the FT2232.  This would allow you to have HyperTerminal, or other terminal program, sending characters to the target board and have them echoed back.

    The example is called sci_echoback found in <CONTROLSUITE_INSTALL_DIR>\device_support\f2833x\v132\DSP2833x_examples_ccsv4\sci_echoback

     

  • Hi Brandon,

    Thanks for the reply. I noticed there was an FTDI chip on the experimenter's kit. However, for the sake of verification I would like to use an external FTDI chip. Also, I am using the exact example you listed, with the exception that my example directory is version 131 instead of 132: <CONTROLSUITE_INSTALL_DIR>\device_support\f2833x\v131\DSP2833x_examples_ccsv4\sci_echoback.

    I will try the example using the experimenter's kit. I know the FT2232 presents 2 COM ports to the PC; can I use one COM port for XDS100 debug and the other COM port for the terminal?

    Thanks so much,

    -SW

  • Scott Wisdom said:

    I will try the example using the experimenter's kit. I know the FT2232 presents 2 COM ports to the PC; can I use one COM port for XDS100 debug and the other COM port for the terminal?

    Yes.