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.

TMS320F28377S: TMS320F28377S

Part Number: TMS320F28377S
Other Parts Discussed in Thread: C2000WARE

Hi

I tried Example_2837xSSci_Echoback.c. I configured putty like this

 correct COM13 port
Bits per second = 9600
Date Bits = 8
 Parity = None
 Stop Bits = 1
 Hardware Control = None

I open the session but it does not show any messages. In some posts I saw some jumpers should be changed on other boards. Do I need to reconfigure LAUNCHXL F28377S? 

thanks vadim

  • Hi Vadim,

    The configuration that you've done for Putty terminal is perfect. Since you're using the LaunchPad, can you confirm whether you're using the external DB9 connector for communication with the PC? The JTAG connection doesn't support the USB communication for LaunchPad. You would need a DB9 connector for successful echoback operation.

    Thanks,

    Aditya

  • Hi Aditya,

    Thanks for your support! I use USB.

    I do not have DB9 connector on my machine, only USB.

    Is there any other way to communicate with launchpad via USB on the launchpad?

    My goal is to be able to communicate from MATLAB to launchpad. MATLAB has serial port object.

    There is FT2232H USB Hi-Speed to Dual Channel Serial UART/FIFO/JTAG/SPI/I2C chip on the board. Can I use it to translate from USB to SCI.

    Is there a way to write and read to launchpad from MATLAB via USB?

    Just to confirm for SCI:

    1. I need to use external DB9 with two wires for SCITXDB GPIO10 connector pin and SCIRXDB GPIO11 connector pin
    2. I need USB to DB9 adapter
    3. I need to wire DB9 RXD(pin3) to SCITXDB  and TXD (pin2) to SCIRXDB and GND (pin5) to Launchpad GND
    4. The rest of DB9 pins are not connected.
    5.  I will have two serial ports seen in device manager:  JTAG and SCI when two cables are connected?

    Thanks, vadim

  • Hi Vadim,

    Sorry first of all. The example that you referred to has to be modified a little to make sure that it is compatible with the LaunchPad. It would work fine after those changes.

    The GPIO configurations done in the example are for the ControlCard. You need to update them for the LaunchPad.

       GPIO_SetupPinMux(28, GPIO_MUX_CPU1, 1);
       GPIO_SetupPinOptions(28, GPIO_INPUT, GPIO_PUSHPULL);
       GPIO_SetupPinMux(29, GPIO_MUX_CPU1, 1);
       GPIO_SetupPinOptions(29, GPIO_OUTPUT, GPIO_ASYNC);
    

    You need to replace the above lines of code with the one I pasted below:

       GPIO_SetupPinMux(43, GPIO_MUX_CPU1, 15);
       GPIO_SetupPinOptions(43, GPIO_INPUT, GPIO_PUSHPULL);
       GPIO_SetupPinMux(42, GPIO_MUX_CPU1, 15);
       GPIO_SetupPinOptions(42, GPIO_OUTPUT, GPIO_ASYNC);

    Additionally, you would need to go to the Properties -> C2000 Compiler -> Advanced Options -> Predefined Symbols and under Pre-define NAME section along with CPU1 you need to define "_LAUNCHXL_F28379D" to enable all the configurations for the LaunchPad.

    This should solve your issue.

    Incase you plan to use external DB9 connector, the connection that you've mention would work perfectly fine. Additionally, you can use the example from the C2000Ware_XX_XX/driverlib/f2837xs/examples/sci section using which you would not have to make the above mentioned changes except adding a predefined symbol for the LaunchPad.

    Thanks,

    Aditya

  • Hi Aditya,

    I am using 28f377S and not 28279D. Could you please look at the schematics

    https://www.ti.com/lit/ug/sprui25d/sprui25d.pdf?ts=1628533676838&ref_url=https%253A%252F%252Fwww.google.com%252F

    and confirm the configuration for GPIOs. It looks like GPIO84 and GPIO85  are SCITXDA and SCIRXDA for this board and connected to FTDI chip. Could you please verify on your board if it works?

    thanks vadim

  • Hi Vadim,

    Sorry for that. You can try this code pasted below:

       GPIO_SetupPinMux(85, GPIO_MUX_CPU1, 5);
       GPIO_SetupPinOptions(85, GPIO_INPUT, GPIO_PUSHPULL);
       GPIO_SetupPinMux(84, GPIO_MUX_CPU1, 5);
       GPIO_SetupPinOptions(84, GPIO_OUTPUT, GPIO_ASYNC);

    I do not have the board with me currently but I have tested on 79D variant so it should work on your end as well. You just need to add the predefined symbol _LAUNCHXL_F28377S.

    Let me know if this helps.

    Regards,

    Aditya

  • Thank you Aditya! It helped. I did not paid attention to the mux index.

  • Never mind. Glad you resolved this.

    Aditya

  • Hi Aditya, one thing though i found. It works from RAM, but if I load it to flash, it tries to send unsuccessfully. After some blinking no text at the cursor. 

    thanks vadim

  • Vadim,

    When you select the build configuration FLASH, the predefined symbol that you added for RAM config does not get transferred here. You will need to add the symbol "_LAUNCHXL_F28377S" again for flash config incase you haven't. This ensures the proper clock configuration for the device and would solve your problem.

    Thanks,

    Aditya

  • Thank you again!

    vadim