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.

EK-TM4C1294XL: UART echo example code not working with UART 7

Part Number: EK-TM4C1294XL

Dear All,

In UART echo example when I changed the UART 0 to UART 7. The code is debugging but there is no output.

Please help me in resolving the issue.uart_echo_u7.zip

Regards,

Gunit

  • What do you mean there is no output? Please use the scope to capture the TX/RX signals. The UART7 is not connected to the ICDI debug probe if you meant to have a virtual COM port from your PC to UART7.
  • Greetings Charles,

    Such, 'UART Failure to Connect' occurs SO Often - does this not suggest that, 'More effective detailing' of the Care/Handling of  'Other than the Standard - pre-connected, Eval/LPad board UART' - would trump (endless/repeated) UART connection detailing - presented here?

    You of course bear, 'No blame' - yet this (and the hundreds of other (near identical) Forum 'UART Solutions') shortly, 'rotate off 'Page 1' into forum oblivion' - rarely (if ever) to be seen again.

    Properly presented & publicized  - 'UART Selection detailing UP FRONT' - appears (far) superior to the existing (after the fact) 'rescue efforts' - needlessly burdening vendor staff... (and permitted to drag on & on...)

  • Hi cb1,
    The place that makes the most sense about which UARTx is connected to the ICDI for communicating to the PC's virtual COM port is the EVM/LaunchPad User's Guide. This is in fact already done in the user's guide. Below are the various notes about this.

    In the default configuration, UART0 is used for the ICDI virtual UART and CAN is not present on the BoosterPack headers.
    In this configuration, the ROM serial bootloader can be used over the ICDI virtual UART. When the jumpers are configured for CAN on the
    BoosterPack, then UART2 must be used for the ICDI virtual UART.

    JP4 and JP5 are used to configure CAN signals to the BoosterPack 2 interface. In the default horizontal
    configuration, CAN is not present on the BoosterPack. UART2 goes to the BoosterPack and UART 0 goes
    to the ICDI virtual serial port to provide ROM serial bootloader capability. In the vertical CAN-enabled
    configuration, UART2 goes to the ICDI virtual serial port and CAN signals are available on the
    BoosterPack. The ROM serial bootloader is not available to the ICDI virtual serial port while the jumpers
    are in the CAN position.

    2.3.3 Virtual COM Port
    When plugged into a USB host, the ICDI enumerates as both a debugger and a virtual COM port. JP4 and
    JP5 control the selection of which UART from the TM4C1294NCPDTI is connected to the virtual COM
    port. In the default configuration, UART0 maps to the virtual COM port of the ICDI. In the CAN jumper
    configuration, UART2 maps to the virtual COM port of the ICDI.

    As we are creating the FAQ section in the forum, it can be another place for clarification.
  • Hi Charles,

    Indeed - such UART data has, 'been in such place for awhile' - has it not?     And still - witness our hapless 'UART denied poster' - such presentation appears to have 'failed' - again.

    The fact that (some and/or certain) precautionary notes 'do appear' - does not speak (at all) to their effectiveness!       (this poster is here - despite such notes...) 

    Surely you & vendor others MUST have noted the, 'On-going - UART-Migration Over-Challenge' - which the move from the 'plain Vanilla (default)' UART to (any) other - (continues) to present...