CCS/TMS320C6457: Can't to start debugging TMDSEVM6457L module on CCS version 5 or more late

Hello,
Are you using the same ccxml file that you were using with CCSv4?

Also, CCSv5 is still quite old. I'd like for you to update to the latest version of the tools before proceed with further investigation. Can you update to the latest CCSv7 build (CCSv7.3)?

Thanks
ki

Hello,
We haven’t heard back from you, I’m assuming you were able to resolve your issue. If not, please provide post a reply with an update below (or create a new thread).

thanks,
ki

Sorry for my long delay with answer. I don't yet resolve this problem.

ArtiG!
You link in the previous post (EINFOCHIPS EVMC6457L and LE, CCS V.5 gel file doesn't work). I studied all messages from this post in detail. I opened the GEL-file (evmc6457l.gel):

Global_Default_Setup_Silent()
{
// Set DSP cache to pre defined values...
Set_DSP_Cache();

// Setup Pll1 DSP @ 1000 MHz
Set_Pll1_1000_MHz();

// Setup all Power Domains on
Set_Psc_All_On( );

// Setup DDR timing @ 660.0 MHz (External Clk * 10 and ddr ext /2)
Set_DDR2(660000000);
}

In this Function, I tried to change PLL frequency from 1000 MHz to 850 and 900 MHz, but debug launch don't started. IDE showed again same message:

Error connecting to the target:
(Error -1265 @ 0x0)
Device ID is not recognized or is not supported by driver. Confirm device and emulator configuration is correct, or update device driver.
(Emulation package 5.0.520.0)

I tried to start the test connetion, which showed this report:

[Start: Texas Instruments XDS100v1 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


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

C:\Users\David\AppData\Local\TEXASI~1\CCS\
TI_CCSv7\1\0\BrdDat\testBoard.dat

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

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Jul 21 2017'.
The library build time was '19:36:41'.
The library package version is '7.0.48.0'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
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]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 64 32-bit words.

The test for the JTAG IR instruction path-length succeeded.
The JTAG IR instruction path-length is 6 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 1 bits.

-----[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 XDS100v1 USB Debug Probe_0]

Ki-Soo Lee!
And then I installed the CCSv7 IDE, but the compiler for C6000 version 8.1 is not support C64x+ processors. I had to install the compiler of version 7.4.23 for the work with C6457 processor. After all settings i tried to start the debug launch, ang IDE showed same message:

Error connecting to the target:
(Error -1265 @ 0x0)
Device ID is not recognized or is not supported by driver. Confirm device and debug probe configuration is correct, or update device driver.
(Emulation package 7.0.48.0)

How I may to start work in CCSv7 with TMDSEVM6357L?

But TMDSEVM6457L work in CCSv4 IDE.

The fact that it works with CCSv4 means that it is likely not a HW issue. The other key things to check is to make sure you are using the same target configuration file that worked with v4 and especially also check that the same startup GEL files that were being used with v4. Note that the target config file often references gel files with a relative path so even if you are using the same target config file from v4, it may be picking up a gel file from v5.

Thanks
ki

I agree! It's not a HW problem with module.

But I tried to copy the ccxml-file from CCSv4 an to start debug.  Debug is not started. The IDE show same message. Initial script in CCSv4 (evmc6457l.gel) is the same as in CCSv7. This files in CCSv4 and in CCSv7 is binary equal. I checked this by kdiff3-program.

Listing ccxml file in CCSv4 project:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
<configuration XML_version="1.2" id="Texas Instruments XDS100v1 USB Emulator_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS100v1 USB Emulator_0" href="connections\TIXDS100usb_Connection.xml" id="Texas Instruments XDS100v1 USB Emulator_0" xml="TIXDS100usb_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS100v1 USB Emulator_0">
            <instance XML_version="1.2" href="drivers\tixds100icepick_c.xml" id="drivers" xml="tixds100icepick_c.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers\tixds100c64xp.xml" id="drivers" xml="tixds100c64xp.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMDSEVM6457L_0" href="boards\evmc6457l.xml" id="TMDSEVM6457L_0" xml="evmc6457l.xml" xmlpath="boards"/>
            </platform>
        </connection>
    </configuration>
</configurations>

Listing ccxml file in CCSv7 project:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
<configuration XML_version="1.2" id="Texas Instruments XDS100v1 USB Debug Probe_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS100v1 USB Debug Probe_0" href="connections/TIXDS100usb_Connection.xml" id="Texas Instruments XDS100v1 USB Debug Probe_0" xml="TIXDS100usb_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS100v1 USB Debug Probe_0">
            <instance XML_version="1.2" href="drivers/tixds100icepick_c.xml" id="drivers" xml="tixds100icepick_c.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds100c64xp.xml" id="drivers" xml="tixds100c64xp.xml" xmlpath="drivers"/>
            <property Type="choicelist" Value="2" id="The JTAG TCLK Frequency (MHz)"/>
            <property Type="choicelist" Value="0" id="Emulator Selection"/>
            <property Type="choicelist" Value="0" id="dataFileRequired"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMDSEVM6457L_0" href="boards/evmc6457l.xml" id="TMDSEVM6457L_0" xml="evmc6457l.xml" xmlpath="boards"/>
                <board XML_version="1.2" description="eInfochips C6457 Lite EVM Board" id="TMDSEVM6457L_0">
                    <device HW_revision="1.0" XML_version="1.2" description="C64x+ Core - This configuration contains full peripheral register specifications." id="TMS320C6457 (Full Peripheral Register set)_0" partnum="TMS320C6457" simulation="no">
                        <router HW_revision="" XML_version="1.2" description="" id="device_1" isa="ICEPICK_C">
                            <subpath desc="Subpath_2" id="Subpath_1"/>
                        </router>
                    </device>
                </board>
            </platform>
        </connection>
    </configuration>
</configurations>

Module is not work in CCSv7

I found the note on the TI wiki page: for XDS100v1 emulators, support for multiple FTDI devices is only available in CCSv4. Link:

processors.wiki.ti.com/images/tmp/f1259094397-281698652.html

Can this be the reason that don't work the debugging in CCSv7? Do I need an external emulator to work with this module (XDS560 for example)?