• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 939 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.

TMS320F28379D: GPIO28 is not connected out how to test sci_echoback_cpu01 example project?

Sunglin Chen
Expert 2335 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: LAUNCHXL-F28379D, C2000WARE

Hi Everyone,

I am testing sci_echoback_cpu01 example project with LAUNCHXL-F28379D Rev2.0, it uses GPIO28 and GPIO29 as SCI-Rx and SCI-Tx, respectively. But the GPIO28 pin is not connected out of the MCU F28379D.  I would like to know how to test this example project? Thank you.

XView.

  • 0
    Expert 2335 points
    The example project is designed for testing with F2837x ControlCARD, not for LAUCHXL-F28379D.
  • 0 in reply to Sunglin Chen
    TI__Guru 60865 points
    Hi Sunglin,

    This example uses SCI-A.

    If you look in datasheet table for GPIO pin multiplexing (www.ti.com/.../gpio-muxed-pins-sprs8809789 you can search for "SCIRXDA" and "SCITXDA" to see the possible pins for SCI-A:

    GPIO8 + GPIO9
    GPIO28 + GPIO29
    GPIO35 + GPIO36
    GPIO42 + GPIO43
    GPIO48 + GPIO49
    GPIO64 + GPIO65
    GPIO84 + GPIO85
    GPIO135 + GPIO136

    So you have plenty of options (you just need to change the GPIO muxing)

    If you look in c2000ware in .\C2000Ware_1_00_03_00\boards\LaunchPads\LAUNCHXL_F28379D\R2.0 and look at the launchpad schematic the FTDI chip is connected to GPIO42/43 which you can use if you want to use a virtual COM port over USB. Otherwise you probably need to get an external RS-232 transceiver and then connect to some other GPIOs.
  • 0 in reply to Devin Cottier
    Expert 2335 points

    Hi, 

    Thank you for your information. I try to use GPIO8 and GPIO9, but it doesn't work.  The code is as follows,

    GPIO_SetupPinMux(9, GPIO_MUX_CPU1, 6);
    GPIO_SetupPinOptions(9, GPIO_INPUT, GPIO_PUSHPULL);
    GPIO_SetupPinMux(8, GPIO_MUX_CPU1, 6);
    GPIO_SetupPinOptions(8, GPIO_OUTPUT, GPIO_ASYNC);

    Does anything I have to configure to make it work?

    XView.

  • 0 in reply to Sunglin Chen
    TI__Guru 60865 points

    Hi Sunlin,

    Does this code compile for you?

    If I look at the SCI echoback example in C2000ware in

    .\ti\c2000\C2000Ware_1_00_03_00\driverlib\f2837xd\examples\cpu1\sci

    The gpio and gpio mux configuration code looks like this:

        //
    // GPIO28 is the SCI Rx pin.
    //
    GPIO_setMasterCore(28, GPIO_CORE_CPU1);
    GPIO_setPinConfig(GPIO_28_SCIRXDA);
    GPIO_setDirectionMode(28, GPIO_DIR_MODE_IN);
    GPIO_setPadConfig(28, GPIO_PIN_TYPE_STD);
    GPIO_setQualificationMode(28, GPIO_QUAL_ASYNC);

    //
    // GPIO29 is the SCI Tx pin.
    //
    GPIO_setMasterCore(29, GPIO_CORE_CPU1);
    GPIO_setPinConfig(GPIO_29_SCITXDA);
    GPIO_setDirectionMode(29, GPIO_DIR_MODE_OUT);
    GPIO_setPadConfig(29, GPIO_PIN_TYPE_STD);
    GPIO_setQualificationMode(29, GPIO_QUAL_ASYNC);

    Which is not using the same functions you are.  Are you using the latest C2000ware examples?