CCS 4.1 and XDS100v2 connection errors

Hi,

die you have a solution. I have the same problem.

My JTAG Hardware Konfiguration is as in the EDSP borad F2812. and I use the XDS100 from Olimex.

Can any on help me to connect to the traget ?

Tahnks

If I try to connect to the Target I receive this Error:

Error connecting to the target:
Error 0x00001200/-1135
Error during: OCS, Target,
Unrecoverable emulation error

I use  Code Composer Studio Version: 4.1.1.00014

Hi, could provide the information requested here: http://tiexpressdsp.com/index.php/Troubleshooting_CCS#Information_for_Support Thanks.

4. Output from the tests specified in Debugging JTAG Connectivity Problems:

Path Length JTAG test:

C:\>"C:\Program Files\Texas Instruments\ccsv4\common\uscif\dbgjtag.exe" -f "C:\P

rogram Files\Texas Instruments\ccsv4\DebugServer\bin\win32\BrdDat\ccBoard0.dat"

-rv -S pathlength

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

This utility has selected an XDS510 class product.

This utility will load the adapter 'jioserdesusb.dll'.

This utility will operate on port address '0'.

The controller does not use a programmable FPGA.

The emulator adapter is named 'jioserdesusb.dll'.

The emulator adapter is titled '(null)'.

The emulator adapter is version '(null)'.

The emulator adapter is using 'Normal-Mode'.

The controller has a version number of '4' (0x0004).

The controller has an insertion length of '0' (0x0000).

The cable+pod has a version number of '0' (0x0000).

The cable+pod has a capability number of '0' (0x0000).

The local memory has a base address of '0' (0x000000).

The local memory has a word capacity of '1048576' (0x100000).

This utility will now attempt to reset the controller.

This utility has successfully reset the controller.

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

The bridge library used to access the controller

and adapter does not read their log-files.

-----[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 succeeded.

The JTAG IR instruction path-length is 0 bits.

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

The JTAG DR bypass path-length is 0 bits.

C:\>

Broken path JTAG test:

C:\>"C:\Program Files\Texas Instruments\ccsv4\common\uscif\dbgjtag.exe" -f "C:\P

rogram Files\Texas Instruments\ccsv4\DebugServer\bin\win32\BrdDat\ccBoard0.dat"

-rv -S brokenpath

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

This utility has selected an XDS510 class product.

This utility will load the adapter 'jioserdesusb.dll'.

This utility will operate on port address '0'.

The controller does not use a programmable FPGA.

The emulator adapter is named 'jioserdesusb.dll'.

The emulator adapter is titled '(null)'.

The emulator adapter is version '(null)'.

The emulator adapter is using 'Normal-Mode'.

The controller has a version number of '4' (0x0004).

The controller has an insertion length of '0' (0x0000).

The cable+pod has a version number of '0' (0x0000).

The cable+pod has a capability number of '0' (0x0000).

The local memory has a base address of '0' (0x000000).

The local memory has a word capacity of '1048576' (0x100000).

This utility will now attempt to reset the controller.

This utility has successfully reset the controller.

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

The bridge library used to access the controller

and adapter does not read their log-files.

-----[Perform the Broken Path scan-test on the JTAG IR]----------------------

This test will use blocks of 512 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

All of the values were scanned correctly.

The JTAG IR Broken Path scan-test has succeeded.

-----[Perform the Broken Path scan-test on the JTAG DR]----------------------

This test will use blocks of 512 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

All of the values were scanned correctly.

The JTAG DR Broken Path scan-test has succeeded.

C:\>

Integrity JTAG test:

C:\>"C:\Program Files\Texas Instruments\ccsv4\common\uscif\dbgjtag.exe" -f "C:\P

rogram Files\Texas Instruments\ccsv4\DebugServer\bin\win32\BrdDat\ccBoard0.dat"

-rv -S integrity

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

This utility has selected an XDS510 class product.

This utility will load the adapter 'jioserdesusb.dll'.

This utility will operate on port address '0'.

The controller does not use a programmable FPGA.

The emulator adapter is named 'jioserdesusb.dll'.

The emulator adapter is titled '(null)'.

The emulator adapter is version '(null)'.

The emulator adapter is using 'Normal-Mode'.

The controller has a version number of '4' (0x0004).

The controller has an insertion length of '0' (0x0000).

The cable+pod has a version number of '0' (0x0000).

The cable+pod has a capability number of '0' (0x0000).

The local memory has a base address of '0' (0x000000).

The local memory has a word capacity of '1048576' (0x100000).

This utility will now attempt to reset the controller.

This utility has successfully reset the controller.

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

The bridge library used to access the controller

and adapter does not read their log-files.

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

This test will use blocks of 512 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 512 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.

C:\>

My complete message was cut while posted, so here it is in segments:

(2nd error message after clicking "Retry")

   2. CCS Version: Version: 4.0.2.01003

   3. CCS Installation directory:

 c:\Program Files\Texas Instruments

   4. Setup Configuration .CCXML file for configuration being used (found in the "<user name>\user\CCSTargetConfigurations" directory):

“Td-2.ccxml” file:

<?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 XDS100 USB Emulator_0">

        <instance XML_version="1.2" desc="Texas Instruments XDS100 USB Emulator_0" href="connections\TIXDS100usb_Connection.xml" id="Texas Instruments XDS100 USB Emulator_0" xml="TIXDS100usb_Connection.xml" xmlpath="connections"/>

        <connection XML_version="1.2" id="Texas Instruments XDS100 USB Emulator_0">

            <instance XML_version="1.2" href="drivers\tixds100c28x.xml" id="drivers" xml="tixds100c28x.xml" xmlpath="drivers"/>

            <property Type="choicelist" Value="0" id="The JTAG TCLK Frequency (MHz)"/>

            <property Type="choicelist" Value="0" id="The JTAG nTRST Boot-Mode"/>

            <property Type="choicelist" Value="0" id="The Power-On-Reset Boot-Mode"/>

            <platform XML_version="1.2" id="platform_0">

                <instance XML_version="1.2" desc="TMS320C2810_0" href="Devices\c2810.xml" id="TMS320C2810_0" xml="c2810.xml" xmlpath="Devices"/>

            <device HW_revision="1" XML_version="1.2" description="" id="TMS320C2810_0" partnum="TMS320C2810" simulation="no">

                    <cpu HW_revision="1.0" XML_version="1.2" description="CPU" deviceSim="false" id="C2800" isa="TMS320C28xx">

                        <property Type="choicelist" Value="0" id="bypass"/>

                    </cpu>

                </device>

            </platform>

        </connection>

    </configuration>

</configurations>

   5. Setup Configuration ccBoard0.dat file (found in \ccsv4\DebugServer\bin\win32\BrdDat)(Please make sure it is saved after failure.) (optional):

“ccBoard0.dat”

# config version=3.5

$ sepk

  pod_drvr=jioserdesusb.dll

  pod_port=0

$ /

$ product

  title="Texas Instruments XDS100 USB"

  alias=TI_XDS100_USB

  name=FTDI_FT2232

$ /

$ ftdi_ft2232

  usb_vid=0x0403

  usb_pid=0xa6d0

  gpio_l0="TRSTn,Active_Low"

  gpio_l1="EMU_Pin_Enable,Active_Low"

  gpio_l2="EMU_Pin_0,Active_Low"

  gpio_l3="EMU_Pin_1,Active_Low"

  gpio_h0="SRSTn,Active_High"

  gpio_h1="SRSTn_In,Active_Low"

  gpio_h2="Power_Loss_Detect,Active_Low"

  gpio_h3="Power_Loss_Reset,Active_High"

$ /

$ uscif

  tdoedge=FALL

  jtagboot_mode=disable

  jtagboot_value=hiz

  powerboot_mode=disable

  powerboot_value=hiz

  tclk_program=SPECIFIC

  tclk_frequency=1.0

$ /

@ c28xx family=tms320c28xx

# /

   6. Any GEL files used for each CPU (optional, mandatory if customized by user):

Unmodified standard “C2810.gel”

   7. Chip Part Number and revision:

            TMS320F2810PBKA CG-73A5RXW G4

   8. Target Board Manufacturer:

Custom PCB made by us.

 Note that JTAG on this board is fully functional with CCS3.1 + XDS510, so hardware should be OK.

   9. Target board part #:

  10. Target board revision #:

  11. Target connector used (ex: 14 pin TI JTAG): 14pin TI JTAG

  12. If customer board, please provide schematic, chips in the scan chain for the JTAG scan chain (up to and including resistors, FETS, etc. that are in the scan chain):

  13. Picture of target board (optional): NA

  14. Host Operating System: Win XP Pro

  15. Host Operating System Version: 2002

  16. Host Operating System Service pack: SP2

  17. Host Operating System bits (32-bit or 64-bit): 32-bit

  18. Emulator Board Manufacturer: Blackhawk

  19. Emulator model # (ex: XDS560): XDS100v2

  20. Emulator connector used (ex: 14 pin TI JTAG): 14 pin TI JTAG

  21. Emulator adapter used (ex: TI 14 pin emulator to 20 pin ARM target, 14 to 14 pin isolation adapter, etc.):     6” ribbon cable between Target Board and XDS100v2  

3. CCS Diagnostic Logs:

and for me her is the Information needed:

I am trying to connect to an TMS320F2812 with an XDS100v2 emulator. After starting CCS v4.1.1, I click "debug" and I get:

1.  
   1. Screenshot of error message
      After clicking connect Target

 

After clicking “Retry”

1.  
   1. CCS Version: Version: 4.1.1.00014
   2. CCS Installation directory:       C:\Programme\Texas Instruments
   3. Setup Configuration .CCXML file for configuration being used (found in the "<user name>\user\CCSTargetConfigurations" directory):

1.  
   1. Setup Configuration ccBoard0.dat file (found in \ccsv4\DebugServer\bin\win32\BrdDat)(Please make sure it is saved after failure.) (optional):

1.  
   1. Any GEL files used for each CPU (optional, mandatory if customized by user):
      Standard:         f2812.gel
   2. Chip Part Number and revision: TMS320F2812GFQ CG-6BA26VW G4
   3. Target Board Manufacturer: NA
   4. Target board part #: NA
   5. Target board revision #: NA
   6. Target connector used (ex: 14 pin TI JTAG):

1.  
   1. If customer board, please provide schematic, chips in the scan chain for the JTAG scan chain (up to and including resistors, FETS, etc. that are in the scan chain):

1.  
   1. Picture of target board (optional):
   2. Host Operating System:           WINDOWS XP
   3. Host Operating System Version:  2002
   4. Host Operating System Service pack: SP3
   5. Host Operating System bits (32-bit or 64-bit)             32-bit
   6. Emulator Board Manufacturer:            Olimex
   7. Emulator model # (ex: XDS560):        XDS100
   8. Emulator connector used (ex: 14 pin TI JTAG):           14 pin JTAG
2. CCS Diagnostic Logs (as described Troubleshooting_CCS#CCS_Diagnostic_Logs):

C28xx: GEL: Warning loading file 'C:\Programme\Texas Instruments\ccsv4\emulation\gel\f2812.gel', line 103: the function 'GEL_OpenWindow' is not supported.

C28xx: GEL: Warning loading file 'C:\Programme\Texas Instruments\ccsv4\emulation\gel\f2812.gel', line 112: the function 'GEL_CloseWindow' is not supported.

C28xx: Error connecting to the target: Error 0x00001200/-1135 Error during: OCS, Target,  Unrecoverable emulation error

C28xx: Error connecting to the target: Error 0x00001200/-1041 Error during: OCS, Target,  Device driver: Problem with the Emulation Controller. It is recommended to RESET EMULATOR.  This will disconnect each  target from the emulator.  The targets should then be power cycled or hard reset followed by an emureset and reconnect to each target. 

From the configuration information, it looks that you have a XDS100v1 emulator and have selected the XDS100v2 in CCS. We tried that configuration and updated the wiki article here: http://tiexpressdsp.com/index.php/XDS100#Q:_What_happens_when_I_plug_a_XDS100v1_into_a_card_but_select_an_XDS100v2_in_CCS.3F 

For this problem, we would like to also see the logs from: http://tiexpressdsp.com/index.php/Debugging_JTAG_Connectivity_Problems 

Also, do you have an Olimex XDS100v1 emulatior or Olimex XDS100v2 emulator? If you have a Olimex XDS100v1, then you need to select an XDS100v1 in the CCS emulator configuration.

Anadi, after looking through this, we think the problem is that an XDS100v1 has been selected in CCS emulator configuration when you actually have an XDS100v2. We updated the wiki here:

http://tiexpressdsp.com/index.php/XDS100#Q:_What_happens_when_I_plug_a_XDS100v2_in_to_my_card_but_select_XDS100v1_or_XDS100_as_the_emulator.3F

Thanks Steve,

How do I select the Blackhawk XDS100v2? The only option I see in the "New Target Configuration" is for "Texas Instruments XDS100 USB Emulator", which is what I have used?

The Update Manager lists one "Blackhawk CCSv4 Emulation (4.0.1.1)" update available, but gives this error message: "Blackhawk CCSv4 Emulation (4.0.1.1) requires feature "com.ti.ccstudio.product (4.0.2.00013)", or equivalent. " (I have  Version: 4.0.2.01003) and does not update.

Thank you stev for the Help,

I have Olimex XDS100v2 emulator (with 20 pin JTAG and adapter kabel to the 14 pin JTAG) SO if  I read the WIKI it is a V2 Emulator.

But I have tested it by selecting XDS100V1 in the configuration but still same eroors.

I did the dbgtests. tghe 1. one (Jtag not plugged) than i plugg  the Jtag in PC and did the others tests (is it right so?)

C:\Dokumente und Einstellungen\rachid\Desktop>"C:\Programme\Texas Instruments\ccsv4\common\uscif\dbgjtag.exe" -f "C:\Programme\Texas Instruments\ccsv4\DebugServ
er\bin\win32\BrdDat\ccBoard0.dat" -rv

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

This utility has selected an XDS510 class product.
This utility will load the adapter 'jioserdesusb.dll'.
This utility will operate on port address '0'.

An error occurred while soft opening the controller.

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

This error is generated by TI's USCIF driver.

The value is '-151' (0xffffff69).
The title is 'SC_ERR_POD_OPEN'.

The explanation is:
This utility failed to open the adapter for a custom emulator.
The adapter returned an error.

C:\Dokumente und Einstellungen\rachid\Desktop>"C:\Programme\Texas Instruments\ccsv4\common\uscif\dbgjtag.exe" -f "C:\Programme\Texas Instruments\ccsv4\DebugServ
er\bin\win32\BrdDat\ccBoard0.dat" -rv -S pathlength

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

This utility has selected an XDS510 class product.
This utility will load the adapter 'jioserdesusb.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.
The emulator adapter is named 'jioserdesusb.dll'.
The emulator adapter is titled '(null)'.
The emulator adapter is version '(null)'.
The emulator adapter is using 'Normal-Mode'.
The controller has a version number of '4' (0x0004).
The controller has an insertion length of '0' (0x0000).
The cable+pod has a version number of '0' (0x0000).
The cable+pod has a capability number of '0' (0x0000).
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '1048576' (0x100000).
This utility will now attempt to reset the controller.
This utility has successfully reset the controller.

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

The bridge library used to access the controller
and adapter does not read their log-files.

-----[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.

C:\Dokumente und Einstellungen\rachid\Desktop>"C:\Programme\Texas Instruments\ccsv4\common\uscif\dbgjtag.exe" -f "C:\Programme\Texas Instruments\ccsv4\DebugServ
er\bin\win32\BrdDat\ccBoard0.dat" -rv -S brokenpath

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

This utility has selected an XDS510 class product.
This utility will load the adapter 'jioserdesusb.dll'.
This utility will operate on port address '0'.
The controller does not use a programmable FPGA.
The emulator adapter is named 'jioserdesusb.dll'.
The emulator adapter is titled '(null)'.
The emulator adapter is version '(null)'.
The emulator adapter is using 'Normal-Mode'.
The controller has a version number of '4' (0x0004).
The controller has an insertion length of '0' (0x0000).
The cable+pod has a version number of '0' (0x0000).
The cable+pod has a capability number of '0' (0x0000).
The local memory has a base address of '0' (0x000000).
The local memory has a word capacity of '1048576' (0x100000).
This utility will now attempt to reset the controller.
This utility has successfully reset the controller.

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

The bridge library used to access the controller
and adapter does not read their log-files.

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

This error is generated by TI's USCIF driver.

The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.

I have CCS v4.1 and it has XDS100v2 support. There is a drop down item there that shows "Texas Instruments XDS100v2 USB Emulator" in that version and newer. You should be able to download the latest CCS here: http://www.tiexpressdsp.com/index.php/Xds100#Installation_for_Code_Composer_Studio_v4.1 

All the tests should be done with the emulator plugged into the target and PC. If the later tests were done with the emulator plugged in, the problem is with the target card connection to the JTAG header. SC_ERR_PATH_BROKEN means that the JTAG scan chain is broken from the connector to the target device. You may want to check the electrical connections.

Is the Olimex unit you are using this one: http://www.olimex.com/dev/tms320-jtag-usb.html ? If yes, this is an XDS100v1.

Dear Steve,

I downloaded CCS4 4.1.1 and this did the trick: I can now connect to the XDS100v2 and debug. Thanks for your support...

Ok I will repete he tests as you mentioned.

yes te Emu I use is this one http://www.olimex.com/dev/tms320-jtag-usb.html 

I will giv you my test result if I finish testing

Hi Steve,

I did new test with the EMU as XDS100_V1 and hav some Errors.

the dbgjtag test is attached as pdf file

The best source for C2000 is the C2000 Getting Started Guide for CCSv4.

Thanks

ki

I use it

Thank you

Even after selecting XDS100 V2, i am facing same props:

Error 0x00001200/-1135 Error during: OCS, Target, Unrecoverable emulation error