CCSV4.1 and XDS100V2 Initialization problem

WhenI get a similar problems, I usually try working it from the lowest level. For me,that means checking the JTAG connection and then working on up to find the problem. I found this wiki helpful: http://www.tiexpressdsp.com/index.php/Debugging_JTAG_Connectivity_Problems (note that the v4 commands are in the middle). Using that article I usually verfiy that the XDS unit is working, the windows drivers are installed OK and the config setup in CCS is correct. If I can get scan path passing, I know it's not the hardware, os drivers, setup or emulation stuff.

The ccs dump files may also be helpful to those supporting CCS: http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/3131.aspx details where to find them.

I have already gone through the connectivity problems wiki process multiple times.  There is no dump log generated.  The only item in the error log is:

eclipse.buildId=4.1.1.00014
java.version=1.5.0_14
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86

Error
Tue Mar 09 00:02:45 EST 2010
Error: C28xx: Error initializing emulator

I have used XDSPROBE and DBGJTAG to check the scan path, all test were succcessful.  The target board jtag and processor are working fine, as verified with CCSV2.2 and XDS510PP emulator.  Also, the CCSV4.1/XDS100V2 configuration worked 3 weeks ago when V4.1 was first installed - with the same App code and configuration info.  My conclusion is there is a problem with CCSV4.1 now that wasn't there during the initial installation - possibly something else interferring with the connection between CCSV4.1 and the emulator drivers.  Removing all traces of CCSV4.1 and FTDI drivers and reinstalling from the same distribution that worked originally doesn' change the situation now.  I have also tried deleting the workspace and starting from scratch, and also tried a new workspace and the timers example code only, with the same results.

I did find some other log files, don't know if they are of any use or not, but I have attached a zip of them, in case anyone is interested in reviewing them.

There is no log in C:\Program Files\Texas Instruments\ccsv4\DebugServer\win32\components\Logs ?

The trace log file is probably not going to help here, it is useful for debugging trace software problems.

I just noticed this was in etech days forum. I am not moderator so I cannot move it to the CCS forum. I posted a link to this one instead.

No log there.  I did a search on .log, and the ones I included previously are all that were found in the CCSV folders.  If  I unplug the emulator, then run debug, the same symptom occurs - error initializing emulator pops up and when I click on cancel CCSV4.1 disappears and the attached window pops up.  (don't know if there is any useful info in it)

Resolved the CCSV crashing problem when opening debug.  Uninstalled CCSV, and went through the registry and tried to remove any references to CCSV and XDS100 manually. (I found that FTCLEAN did not actually clean out the USB enum hives - probably due to Win7 restrictions). Then reinstalled CCSV4.1 (last version known to work with the XDS100), and now I can enter debug.  Still get the error initializing emulator at start, but canceling the error window doesn't crash CCSV4, it will go into debug mode without the emulator.

HOWEVER, I still cannot communicate with the emulator, and still don't know why. No errors other than the initial 'error initializing emulator', and no idea what to look for, nor what to do next.  I have submitted an official problem request to TI AND to Spectrum Digital (sellor of emulator) - NO REPLIES FROM EITHER CO.!!!  My once high opinion of both co's is in a rapid downward slide now.

I was using XDS100v2 with 28x today, and encountered a similar problem. However, in my case, the EEPROM was not programmed properly. You may want to check if it is programmed correctly: http://tiexpressdsp.com/index.php/XDS100#Q:_How_can_I_check_if_the_VID.2FPID_for_the_EEPROM_are_programmed_correctly.3F But the error in that case is -150, so it looks a little different.

Can you post the XML from your setup? This is found in the target connections-->source tab. That can show us the relative paths that the CCS is searching for in the dirivers.

Just to recap, were you able to run dbgjtag with the current target configuration set as the default and doing a connectivity test? That would also tell us if the CCS configuration files are generated OK.

DBGJTAG integrity and brokenpath tests both pass each time, using the current board config.  When I try "DBGJTAG -A scanpath", I get the following error report:

"The configure file indicates just one JTAG device should be in the system.

This test indicates zero JTAG devices are actually in the system.

This test cannot analyse the scan-path when the

configure file and the scan-path do not match."

I have tried various lines from the config file as the device name, but no different results

The board data file is as below:

# config version=3.5
$ sepk
  pod_drvr=jioserdesusb.dll
  pod_port=0
  pod_serial=SDSMA6OP
$ /
$ product
  title="Texas Instruments XDS100v2 USB"
  alias=TI_XDS100v2_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="Adaptive_Clock,Active_High"
  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"
  gpio_h4="EMU_Pin_1,Active_Low"
  gpio_h5="Cable_Disconnect,Active_High"
  gpio_h6="Loopback,Active_High"
$ /
$ uscif
  tdoedge=FALL
  jtagboot_mode=disable
  jtagboot_value=hiz
  powerboot_mode=disable
  powerboot_value=hiz
  tclk_program=SPECIFIC
  tclk_frequency=1.0
  loopback_mode=disable
  loopback_value=disable
$ /
@ c28xx family=tms320c28xx
# /

Here is the target configuration XML source, as well.  Don't see what relationship this has to anything DBGJTAG is doing.

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

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

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

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

<property Type="choicelist" Value="1" id="Emulator Selection">

<choice Name="Select by serial number" value="0">

<property Type="stringfield" Value="SDSMA6OP" id="-- Enter the serial number"/>

</choice>

</property>

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

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

</platform>

</connection>

</configuration>

</configurations>

Thanks. We tried to duplicate the error you have and were unable.

We built a special 28x driver to help us debug this problem.

Could you respond to my friend request so we can setup a conference call directly? Thanks.

Hi Steve,

I am getting the same problem/errors  with XDS100V2 while connecting to TMS320DM6467 on my custom board

Did you manage to solve the problem with WGauss?

Regards,

Sid

Ok, thanks. To answer your other question, we were not able to solve WGauss problem. We actually created a special driver to help find the problem, but were not able to get it to WGauss to use it and find the problem.