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-F280049C: SCI-A Mapping

Part Number: LAUNCHXL-F280049C
Other Parts Discussed in Thread: C2000WARE

Hi,

Re: TMS320F28004x Microcontroller Workshop.

I am working with the Lab 11 titled sci_ex1_echoback.c.  In the text under the heading "Lab 11: C2000Ware SCI Echoback Example, Objective" it mentions that "SCI-A is mapped to the virtual COM port ... using GPIO28 and GPIO29.  I can tell that the program is running correctly due to the console output which does indeed echo the characters I type.  I was also expecting to see electrical signals on GPIO28 and GPIO29 but none are present, I was able to detect a signal on the TXD of J101 however.  My question is whether there should also have been signals on GPIO28  and GPIO29 and if so what might be inhibiting them.

Thanks,

Steve

  • Steve,

    By default, GPIO28 and GPIO29 are routed to the virtual COM port and not available on the BoosterPack connector.  To route these signals to the BoosterPack connector you would need to change switches S6 and S8.  See page 12 in the F280049C LaunchPad User's Guide:

    www.ti.com/lit/SPRUII7

    Also, see the schematic for switches S6 and S8 on page 17.

    I hope this helps. If this answers your question, please click the green "Verified Answer" button. Thanks.

    -Ken

  • Steve,

    I haven’t heard back from you, so I am assuming that my last reply resolved your issue. If this isn’t the case, please reject this resolution or reply to this thread. If this thread locks, please make a new thread describing the current status of your issue.  Thank you.

    -Ken

  • Ken,

    Thanks.  I don't know why but the buttons to mark this as resolved didn't appear until I originally posted this reply, this is an edited version in which I have changed the content.  I ended up using the checkbox below the edit window to mark it as resolved, I suspect there is some incompatibility with the Safari browser.

    Steve