The TI E2E™ design support forums will undergo maintenance from Sept. 28 to Oct. 2. If you need design support during this time, contact your TI representative or open a new support request with our customer support center.

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.

TMDSEVM6657LS

Other Parts Discussed in Thread: CDCE62005, TMS320C6657

Hi this is James form D1 company

The TMDSEVM6657LS board ordered on September 13th is powered up, so the IC below has a severe fever, so please check if it's normal.

  • Hello,

    Is the board working correctly?  Can you connect with CCS/JTAG?

    What is the part # of the component you have highlighted?  What is the temperature of the case of the component?

    Thanks,

    Kyle

  • Hello

    The power is working but there is no equipment to measure heat, so I can't tell you the exact temperature, but even though only the power is connected, it generates so much heat that I can't touch. 
    The CCS/JTAG connection is not possible because there is a concern that hatching may worsen.
    When connecting CCS/JTAG, please let me know how to install which program.

    the part is CDCE62005 and Board marking is TP45

    Thanks

  • Kayla

    We have not heard of any issues with TP45 IC being abnormally heated up etc. 

    Can you run a few software examples with ccs to make sure that board is ok?

    https://software-dl.ti.com/processor-sdk-rtos/esd/docs/latest/rtos/index_how_to_guides.html#tmdsevm6657l-evm-hardware-setup-guide

    I will assign this thread to our software colleague if you need more guidance on running the SDK examples 

    Here is an FAQ on how to build and run the examples 

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1040872/faq-tms320c6657-how-to-generate-the-ccs-pdk-examples-for-c6657

    Regards

    Mukul 

  • Hi Kayla,

    Good day!.

    I have the same board as yours. i.e, The TMDSEVM6657LS board with me. Even that board dissipates more heat. Despite, I keep, using it for the past six months. And able to run the example-programs normally.

    In my board, the reason might be, "the heat cooling fan" is not connected. 

    -------

    customer says "The CCS/JTAG connection is not possible because there is a concern that hatching may worsen.
    When connecting CCS/JTAG, please let me know how to install which program."

    This EVM has a onboard emulator ( blue add-on board on your picture ) - XDS 2xx emulator.

    Through this, you can connect the "TMDSEVM6657LS board" to a computer with "CCS" ( Code composer studio )  installed in it.

    -----------

    These are the Steps

                 1. Pre-requisite:  Install CCS 9.3 from CCSTUDIO_9.3.0.00012 | TI.com

    1.  How to connect the CCS with C6657 EVM via the XDS emulator and how to do the target connection of C6657 EVM ?

    Open CCS →File → New → Target configuration file-->"NewTargetConfiguration.ccxml"→Finish

           open  "NewTargetConfiguration.ccxml". Click Basic--> 

           Connection : Texas Instruments XDS2xx USB Debug probe

           Board or Device : TMS320C6657

        2. click "save" 

        3. click "Test connection"

    If the connection is successful, the following messages will be displayed in CCS screen.

    =============================Test Connection Screen =============

    [Start: Texas Instruments XDS2xx USB Emulator_0]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

    [Result]


    -----[Print the board config pathname(s)]------------------------------------

    C:\Users\Admin\AppData\Local\TEXASI~1\CCS\
    ccs1040\0\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 560/2xx-class product.
    This utility will load the program 'xds2xxu.out'.
    The library build date was 'Jun 25 2021'.
    The library build time was '16:23:59'.
    The library package version is '9.4.0.00129'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '13' (0x0000000d).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    This emulator does not create a reset log-file.

    -----[Perform the Integrity scan-test on the JTAG IR]------------------------

    This test will use blocks of 64 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG IR Integrity scan-test has succeeded.

    -----[Perform the Integrity scan-test on the JTAG DR]------------------------

    This test will use blocks of 64 32-bit words.
    This test will be applied just once.

    Do a test using 0xFFFFFFFF.
    Scan tests: 1, skipped: 0, failed: 0
    Do a test using 0x00000000.
    Scan tests: 2, skipped: 0, failed: 0
    Do a test using 0xFE03E0E2.
    Scan tests: 3, skipped: 0, failed: 0
    Do a test using 0x01FC1F1D.
    Scan tests: 4, skipped: 0, failed: 0
    Do a test using 0x5533CCAA.
    Scan tests: 5, skipped: 0, failed: 0
    Do a test using 0xAACC3355.
    Scan tests: 6, skipped: 0, failed: 0
    All of the values were scanned correctly.

    The JTAG DR Integrity scan-test has succeeded.

    [End: Texas Instruments XDS2xx USB Emulator_0]

    =============================Test Connection Screen =============

    2. How to load and run the Gel file on C6657 EVM?

    1. Set the EVM to No-boot mode. evmc6657l.gel

                        No boot switch settings on C6657 EVM ( e-infoChips)

                                             SW3 :(off, on, on, on, on, on, on, on)

                                             SW5: (on, on, on, on, on, on, on, on

    2. In CCS, Open the Target configuration file ( which was created in above step ), click on "advanced" options next to "Basic"

    3.   Click on ICEPICKD and provide the path of the gel file in the initialization script. ( I have attached the gel file in step 1)

    4.    Repeat the same by clicking the core 0 and core 1.

    5.   Right click and launch the target configuration file.

    6.  In the debug window, click on core 0 and click "Connect target"; click on core 1 and click "Connect target";

      The Output of gel file will get printed in the console messages

    ===============Gel output ================

    IcePick_D: GEL Output: Setup_Memory_Map...
    IcePick_D: GEL Output: Setup_Memory_Map... Done.
    C66xx_0: GEL Output: Setup_Memory_Map...
    C66xx_0: GEL Output: Setup_Memory_Map... Done.
    C66xx_1: GEL Output: Setup_Memory_Map...
    C66xx_1: GEL Output: Setup_Memory_Map... Done.
    IcePick_D: GEL Output:
    Connecting Target...

    C66xx_0: GEL Output:
    Connecting Target...
    C66xx_0: GEL Output: DSP core #0
    C66xx_0: GEL Output: C6657L GEL file Ver is 1.00199997
    C66xx_0: GEL Output: Global Default Setup...
    C66xx_0: GEL Output: Setup Cache...
    C66xx_0: GEL Output: L1P = 32K
    C66xx_0: GEL Output: L1D = 32K
    C66xx_0: GEL Output: L2 = ALL SRAM
    C66xx_0: GEL Output: Setup Cache... Done.
    C66xx_0: GEL Output: Main PLL (PLL1) Setup ...
    C66xx_0: GEL Output: PLL in Bypass ...
    C66xx_0: GEL Output: PLL1 Setup for DSP @ 1000.0 MHz.
    C66xx_0: GEL Output: SYSCLK2 = 333.333344 MHz, SYSCLK5 = 200.0 MHz.
    C66xx_0: GEL Output: SYSCLK8 = 15.625 MHz.
    C66xx_0: GEL Output: PLL1 Setup... Done.
    C66xx_0: GEL Output: Power on all PSC modules and DSP domains...
    C66xx_0: GEL Output: Set_PSC_State... Timeout Error #03 pd=12, md=4!
    C66xx_0: GEL Output: Power on all PSC modules and DSP domains... Done.
    C66xx_0: GEL Output: DDR3 PLL (PLL2) Setup ...
    C66xx_0: GEL Output: DDR3 PLL Setup... Done.
    C66xx_0: GEL Output: DDR3 Init begin (1333 auto)
    C66xx_0: GEL Output: XMC Setup ... Done
    C66xx_0: GEL Output:
    DDR3 initialization is complete.
    C66xx_0: GEL Output: DDR3 Init done
    C66xx_0: GEL Output: DDR3 memory test... Started
    C66xx_0: GEL Output: DDR3 memory test... Passed
    C66xx_0: GEL Output: PLL and DDR3 Initialization completed(0) ...
    C66xx_0: GEL Output: configSGMIISerdes Setup... Begin
    C66xx_0: GEL Output: SGMII SERDES has been configured.
    C66xx_0: GEL Output: Enabling EDC ...
    C66xx_0: GEL Output: L1P error detection logic is enabled.
    C66xx_0: GEL Output: L2 error detection/correction logic is enabled.
    C66xx_0: GEL Output: MSMC error detection/correction logic is enabled.
    C66xx_0: GEL Output: Enabling EDC ...Done
    C66xx_0: GEL Output: Global Default Setup... Done.
    C66xx_1: GEL Output:
    Connecting Target...
    C66xx_1: GEL Output: DSP core #1
    C66xx_1: GEL Output: C6657L GEL file Ver is 1.00199997
    C66xx_1: GEL Output: Global Default Setup...
    C66xx_1: GEL Output: Setup Cache...
    C66xx_1: GEL Output: L1P = 32K
    C66xx_1: GEL Output: L1D = 32K
    C66xx_1: GEL Output: L2 = ALL SRAM
    C66xx_1: GEL Output: Setup Cache... Done.
    C66xx_1: GEL Output: Global Default Setup... Done.

    Regards

    Shankari G

  • Dear Customer,

    Do your C6657 EVM works normally despite of heat ?

    I have not heard from you for long-time. 

    Until, I hear from you, changing the status of this thread as closed.

    Once you reply, automatically the status of this thread will get opened.

    Regards

    Shankari G