• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 97 subscribers
  • Views 276 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.

TMS320C6678: Assistance required: UART Communication Issues on TMDSEVM6678LE

Krishn_JI
Expert 2145 points
Part Number: TMS320C6678
Other Parts Discussed in Thread: MAX232

Tool/software:

Hi TI Support Team,

We are currently working on interfacing UART communication with the TMDSEVM6678LE (EVM) and have encountered some challenges.

We seek your guidance regarding the following concerns:

Issue 1. UART Data Mismatch / Corruption Issue

We are experiencing data mismatch or corruption when transmitting and receiving data over UART (RX-TX and TX-RX). We are using TI’s official library located at:
C:\ti\pdk_c667x_2_0_16\packages\ti\platform\evmc6678l\platform_lib\include\evmc66x_i2c_uart.h

Could you please advise on potential causes for this issue and suggest any necessary configurations or modifications to ensure reliable data transmission?

Request for Clarification;

Could you confirm which of these calculations is correct for configuring the UART baud rate on TMDSEVM6678LE? If any of our assumptions or parameters are incorrect, we would appreciate your guidance on how to rectify them.

We look forward to your expert advice and appreciate your prompt support in resolving these issues.

Warmest Regards,
Krishn Singh Chauhan

  • 0
    TI__Mastermind 48283 points

    Krishn,

    Issue1: Have your hardware or board design expert verified the h/w schematics for UART interface? 

    Issue 2: Have you looked into the TI SDK? Also, which T SDK are you looking at?

    Thanks.

  • 0 in reply to Praveen Rao
    Expert 2145 points

    Hi Praveen R.,

    Greetings of the day!

    Thank you for your prompt response.

    Issue 1: Hardware Verification of UART Interface

    Yes, we have thoroughly verified the hardware schematics for the UART interface. We are using two pins from the TMDSEVM6678LE for UART communication, as detailed below:

    Pin Signal Description
    71 DSP_UARTTXD UART Serial Data Out (+3.3V)
    73 DSP_UARTRXD UART Serial Data In (+3.3V)

    These pins are interfaced with the MAX232 (Dual EIA-232 Driver and Receiver) to establish UART communication (TX → RX and RX → TX). However, we are encountering the issues previously mentioned in this thread.

    Issue 2: SDK and TI Library Used

    Yes, we are using pdk_c667x_2_0_16 for the UART communication interface, as referenced earlier.

    The TI official library is located at:
    C:\ti\pdk_c667x_2_0_16\packages\ti\platform\evmc6678l\platform_lib\include\evmc66x_i2c_uart.h

    We hope this information provides clarity and assists in further analysis. Please guide us in resolving these issues, as we are looking forward to your valuable insights and support.

    Looking forward to your response.

    Warmest regards,
    Krishn Singh Chauhan

  • 0 in reply to Krishn_JI
    TI__Mastermind 48283 points

    On Issue 1 - Compared to the TI EVM, which the SDK is based on, what changes have been made to your platform concerning hardware changes and pin usages? We suggest looking into the code and checking if all the code updates are taken care of based on your design. It is hard for us to guess what the issue is.

    On Issue 2: What are you expecting from us? The SDK source code is entirely public. Can you debug at your end? Note that we can suggest 3Ps who can help with the development and service for custom development on your platform.

    Thanks.

  • 0 in reply to Praveen Rao
    Expert 2145 points

    Hi Praveen R.,

    Sorry for the late reply, Thank you for your prompt response.

    Kindly close this thread.

    Warmest regards,

    Krishn Singh Chauhan

  • 0 in reply to Krishn_JI
    TI__Mastermind 48283 points

    Thanks, will close the thread.