EVM6678L Emulation

Bernd,

Please try CCS 5.0.3.  5.0.3 is a generally available production release that fully supports the 66x devices.  5.1 is still in a beta state.  This is the revision that the 66x EVMs have been validated on.

http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5

Regards,
Dan

<Originally Posted By Bernd in other thread >

Hello Dan,

Thanks for your fast reply. Now I've installed CCS Version 5.0.3 which was delivered on CD with the Evaluation Board. But Target connection doesn't work either, the error is:

IcePick_D: Error connecting to the target: Cannot access register at 0x00000000  (Error -2131) @ 0 (0x0)

I don't know if there might be trouble with the Hardware Setup (I've followed the instructions on the webpage), I just give some details:

-Ethernet & JTAG via MiniUSB are connected (Shunts are set for USB)

-Serial (RS232) is not connected

-SW3-6 are set as described, but the Infopage from the HUA says that Big Endian is enabled (I think with SW3 set as described Little Endian should be enabled?)

-UserSwitch2 is Off so that a static IP is used

Best Regards,

Bernd

Bernd,

I split this off into another thread. 

Have you checked the following that was mentioned in the old thread.

Be sure the following files are included with your CCS.  They all should be.  Specifically, the highlighted ones are important for icepick.

• <CCS_INSTALL_DIR>\ccsv5\ccs_base_5.0.2.00022\common]targetdb\devices\c6678.xml
• <CCS_INSTALL_DIR>\ccsv5\ccs_base_5.0.2.00022\common]targetdb\routers\icepick_d.xml
• <CCS_INSTALL_DIR>\ccsv5\ccs_base_5.0.2.00022\common]targetdb\routers\cs_dap.xml
• <CCS_INSTALL_DIR>\ccsv5\ccs_base_5.0.2.00022\common]targetdb\cpus\c66xx.xml
• <CCS_INSTALL_DIR>\ccsv5\ccs_base_5.0.2.00022\common]targetdb\drivers\tixds100icepick_d.xml
• <CCS_INSTALL_DIR>\ccsv5\ccs_base_5.0.2.00022\common]targetdb\drivers\tixds510icepick_d.dvr

Check in your device manager to ensure that the XDS100 has been configured properly.  Specifically, I'm looking to be sure these were properly identified as XDS100 Channel A and B under the USB Serial Bus Controllers. It should look something like what I have in the image below.  There should be two XDS100 entries.

The installer should have put the drivers for the board in your Windows/System32 directory.  Can you check that directory and see if you have any of the following?

• ftd2xx.dll
• ftbusui.dll
• ftcserco.dll
• FTLang.dll

Can you try setting your board in No Boot Mode (see board documentation for DIP settings), power cycle the board, adn then try to connect again?

FYI, endian settings and IP address settings should have no effect on connecting to the target.  The most likely scenario is a missing driver or configuration file, or possibly a wrongly programmed XDS100.

Regards,

Dan

Hello,

I get the same error code as Bernd. I'm also using CCS 5.1. The XDS100 is found in the device manager and the driver files are present.

I'm able to connect to the board using an external XDS100V1 and a 60 to 14 pin adapter.

Best Regards,

Ralf

Hello Dan,

to which thread you have split of this task?

Like mentioned above, I already checked all this stuff, but to be sure I checked again. So all files are there (only the file tixds510icepick_d.dvr is located under \emulation\drivers instead of common like Joseph already found out, maybe here we have a problem?), drivers are correct displayed under system configuration and all files are given under windows/system32.

I also tried the setup with no boot. Just have to search a little bit because 'no boot' is not described in Technical Reference, but found this configuration and tried it, but the error message was the same again:

"No Boot" mode is:

SW6 [position 4, 3, 2, 1] = On, On, On, On = 4b0000

SW5 [position 4, 3, 2, 1] = Off, On, On, On = 4b1000

SW4 [position 4, 3, 2, 1] = On, On, On, On = 4b0000

SW3 [position 4, 3, 2, 1] = On, On, On, Application specific Endianess = 4b000x (where x = off for little endian and on for big endian)

Best Regards,

Bernd

Bernd,

I believe that your .dvr is in the correct location.  My CCS 5.0.3 has it in the emulation\drivers directory also.  This must've changed after 5.0.2. 

I don't have a good answer at this point.  We've seen isolated cases where a specific PC was not able to connect to the XDS100, but we've never been able to reproduce it.  It seems like these cases are getting less and less isolated, though. 

The last thing you might try is getting the latest emulation updates through the CCS Update Manager.

Help->Install new Software

Put in the link below, and be sure the "Group Items by Category is unchecked"

http://software-dl.ti.com/dsps/dsps_public_sw/sdo_ccstudio/CCSv5/Updates/Emulation/full

Regards,

Dan

Hello,

I've just updated the Emulation-SW in CCS, but only the error message have changed:

IcePick_D: Error connecting to the target:  (Error -151) @ 0 (0x0)

I'll just try it on another PC tomorrow if there's no other solution and give feedback if it works or not.

Best Regards,

Bernd

Hello,

I've tried it on another PC, but I get exactly the same error message as on the other one:

IcePick_D: Error connecting to the target: Cannot access register at 0x00000000  (Error -2131) @ 0 (0x0)

So I don't think it's problem with the PC, I think there's something wrong with the configuration. Do you have any further ideas I can check, e.g. the target configuration or something on the EVM?

Best Regards,

Bernd

Bernd,

Can you attach your .ccxml file.  I will have a look at it.

Regards,

Dan

Hello Dan,

here is the configuration file as txt:

<?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_d.xml" id="drivers" xml="tixds100icepick_d.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds100c66xx.xml" id="drivers" xml="tixds100c66xx.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds100cs_dap.xml" id="drivers" xml="tixds100cs_dap.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMS320C6678_0" href="devices/C6678.xml" id="TMS320C6678_0" xml="C6678.xml" xmlpath="devices"/>
            </platform>
        </connection>
    </configuration>
</configurations>

Best Regards,

Bernd

Bernd,

Everything there looks ok. Have you tried seeing if you can get the output from the Out Of Box Demo to display on a terminal through the USB connection?  I'm trying to figure out now if this is a CCS or a USB problem. 

In device manager, on XDS100 channel B, go to properties->Advanced, and check the Load VCP box. Now, look under the Ports list,  there should be a USB serial port assigned to the COM port.  If you select the properties of the USB port, the Manufacturer should be FTDI.  You can use the assigned COM port with a terminal program to display output from the out of box demo.  The instructions for this should be in the Quick Start guide.  If we can get data this way, then I would suspect the USB connection is OK.

Regards,

Dan

Hello Dan,

I've already checked the output from the HUA, it's visible via a HyperTerminal Session (see picture below). In the device manager, no tab with 'Load VCP box' are present. I've also made a picture. But with the output being visible I think the USB-connection is okay.

Best Regards,

Bernd

I agree, this looks good.

I've asked for one of the XDS100 experts to have a look at this.  I'm out of things to try.  Your setup looks good.  It seems like all the right files are there. 

Regards,

Dan

Bernd,

Can you try this and send me the results?

From the command line, use the following command.  dbgjtag is located in <CCS_INSTALL_DIR>\ccs_base_5.0.3.00028\common\uscif

dbgjtag -f <board config file> -rv -Spathlength -Sgivendata,repeat=10

 The board config file is found at:

C:\Documents and Settings\<user account>\Local Settings\Application Data\.TI\<CCS instance #>\0\BrdDat\ccBoard0.dat

<user account> is your account name

<CCS instance #> is a random appearing ID for each instance CCS installed on the system

Regards,

Dan

Hello Dan,

the output of this command can be seen below. To check the cable, I've just tested to run the board with another USB-To-MiniUSB-cable. With other cables, the HUA was not able to be started (nor the web page could be called neither the output via HyperTerminal appears). But the error message from dbgjtag was the same as with the original cable.

Best Regards,

Bernd

D:\CCS5.0.3\ccsv5\ccs_base_5.0.3.00023\common\uscif>dbgjtag -f C:\Users\z001yuvf\AppData\Local\.TI\15
20015880\0\BrdDat\ccBoard0.dat -rv -Spathlength -Sgivendata,repeat=10

-----[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 'Jan  3 2011'.
The library build time was '22:22:34'.
The library package version is '5.0.281.0'.
The library component version is '35.34.29.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 now 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).

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

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

The JTAG IR instruction path-length was not recorded.

-----[Perform the Given Data scan-test on the JTAG IR]-----------------------

This test will use blocks of 512 32-bit words.
This test will be applied 10 times.
It uses all of the 10 different test-cases.

Do a test using 0x5533CCAA.
Scan tests: 1, skipped: 0, failed: 0

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver.

The value is '-183' (0xffffff49).
The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.

The explanation is:
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.

Bernd,

I'm concerned about the fact that HUA is affected by the type of USB cable.  It should boot and work even without a USB connection.  I think this is a secondary problem, though. 

With a standard emulator, you would typically get the CTL_CBL_BREAK_FAR message when the emulation header is not connected to the connector.  Far typically means FAR from the PC.  I don't know if this could be a connection problem on your board.  I'm waiting for advice. 

Regards,

Dan

Hello Dan,

you're right: starting the board without the USB-connection, HUA is booting and I can connect via the webpage. With another USB cable, this hasn't worked. But I don't think we have to focuss on this problem.

Best Regards,

Bernd

Bernd,

Can you look at your CCS configuration file and confiem that you have selected XDS100v1 and not XDS100v2.  For this EVM, it should be a V1.  I am told that selecting v2 when it should be v1 will give the Cable Break Far message.

I had thought you had mentioned XDS100v1 earlier in the thread, but that was in reference to an external XDS100.

Regards,

Dan

Hello Dan,

you're right, with the test output below the V2 were set. Configure the emulator with V1, the result is as seen below.

Best Regards,

Bernd

D:\CCS5.0.3\ccsv5\ccs_base_5.0.3.00023\common\uscif>dbgjtag -f C:\Users\z001yuvf\AppData\Local\.TI\15
20015880\0\BrdDat\ccBoard0.dat -rv -Spathlength -Sgivendata,repeat=10

-----[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 'Jan  3 2011'.
The library build time was '22:22:34'.
The library package version is '5.0.281.0'.
The library component version is '35.34.29.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 now 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).

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

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

The test for the JTAG IR instruction path-length failed.
The JTAG IR instruction scan-path is stuck-at-ones.

The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-ones.

-----[Perform the Given Data scan-test on the JTAG IR]-----------------------

This test will use blocks of 512 32-bit words.
This test will be applied 10 times.
It uses all of the 10 different test-cases.

Do a test using 0x5533CCAA.
Test 1 Word 0: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 1: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 2: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 3: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 4: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 5: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 6: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 7: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 10, skipped: 0, failed: 10
Some of the values were corrupted - 100.0 percent.

The JTAG IR Given Data scan-test has failed.

-----[Perform the Given Data scan-test on the JTAG DR]-----------------------

This test will use blocks of 512 32-bit words.
This test will be applied 10 times.
It uses all of the 10 different test-cases.

Do a test using 0x5533CCAA.
Test 1 Word 0: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 1: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 2: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 3: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 4: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 5: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 6: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 7: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 10, skipped: 0, failed: 10
Some of the values were corrupted - 100.0 percent.

The JTAG DR Given Data scan-test has failed.

Hi Bernd,

I see you have CCS installed in D: drive. Could you please try installing CCS in drive C: and see if that works.

Thanks and regards,

one and zero

Hello Dan,

with CCS installed on drive C: the same error occurs, see below.

Best Regards,

Bernd

C:\Program Files (x86)\Texas Instruments\ccsv5\ccs_base_5.0.3.00023\common\uscif>dbgjtag -f C:\Users\
z001yuvf\AppData\Local\.TI\3719693756\0\BrdDat\ccBoard0.dat -rv -Spathlength -Sgivendata,repeat=10

-----[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 'Jan  3 2011'.
The library build time was '22:22:34'.
The library package version is '5.0.281.0'.
The library component version is '35.34.29.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 now 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).

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

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

The test for the JTAG IR instruction path-length failed.
The JTAG IR instruction scan-path is stuck-at-ones.

The test for the JTAG DR bypass path-length failed.
The JTAG DR bypass scan-path is stuck-at-ones.

-----[Perform the Given Data scan-test on the JTAG IR]-----------------------

This test will use blocks of 512 32-bit words.
This test will be applied 10 times.
It uses all of the 10 different test-cases.

Do a test using 0x5533CCAA.
Test 1 Word 0: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 1: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 2: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 3: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 4: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 5: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 6: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 7: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 10, skipped: 0, failed: 10
Some of the values were corrupted - 100.0 percent.

The JTAG IR Given Data scan-test has failed.

-----[Perform the Given Data scan-test on the JTAG DR]-----------------------

This test will use blocks of 512 32-bit words.
This test will be applied 10 times.
It uses all of the 10 different test-cases.

Do a test using 0x5533CCAA.
Test 1 Word 0: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 1: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 2: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 3: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 4: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 5: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 6: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
Test 1 Word 7: scanned out 0x5533CCAA and scanned in 0xFFFFFFFF.
The details of the first 8 errors have been provided.
The utility will now report only the count of failed tests.
Scan tests: 10, skipped: 0, failed: 10
Some of the values were corrupted - 100.0 percent.

The JTAG DR Given Data scan-test has failed.

C:\Program Files (x86)\Texas Instruments\ccsv5\ccs_base_5.0.3.00023\common\uscif>

hello, Bernd

I have the same problem as described as above， only with a little difference，setup is as followed：

-TMDXEVM6670L-Board is used

-Installed CCS Version 5.0.3.00028

-configure .ccxml with the basic set as : connection—>Taxas Instrument XDS100v1 USB Emulator, Board or device —> TMS320C6670 and the Target Configuration set as : add  C:\Program Files\Texas Instruments\ccsv5\ccs_base_5.0.3.00028\emulation\boards\evmc6670l\gel\evmc6670l.gel file onto C66**_0

While connection to the core, the following error  same as yours occurs:

IcePick_D: Error connecting to the target: Cannot access register at 0x00000000  (Error -2131) @ 0 (0x0)

have you settled the problem? if so, can you please help me with it?

Best Regards,

Tina 

Hello Tina,

solution was the external 60 pin header, in my case external BlackHawk-Emulator (mentioned above). If this is still connected, the internal JTAG is not accessed. So I have to connect to the target via the BlackHawk or remove the BlackHawk-Emulator from the board.

Best Regards,

Bernd

hi  Dan,
i have the same problem 
i use TMS320C6670 and make the the steps to make a connection using XDS100 v1,
i configured target configuration to support  XDS100 v1 and Device number ,
and checked all the previous steps in this post ,
but i faced the same error
any help please ...
Thanks in advanced.
Muhammed