XDS100V2

Hi,

vijayabharathi chelladurai said:

Is the CCS supports this combaination ? OMAPL138+XDS100V2? Or original licensed CCS version only supports XDS100V2 + OMAPL138

Sorry, but I really don't understand what is your question. XDS100v2 allows using the Free Limited License of CCSv4. Check the page: http://processors.wiki.ti.com/index.php/Licensing_-_CCSv4#Free_Licenses Hope this helps, Rafael

Sorry, Actually we bought a new hawk board,now we want to connect to the target using CCS 4 which is downloaded free edition having XDS100 license.

Iam confused whether the freely downloaded edtion supports XDS100v2?? i mean it supports only v1??

 

Then we tried using the dbgjtag utility, still we face this error

"A bad controller handle has been given to a function,
either before attempting to open the controller, or after
having opened the controller and ignored its error status.
Valid controller handles are generated when attempts
to open the controller return a clean error status. "

 

Kindly help us

 

 

Hi

From the link u provided,Iam sure that XDS100v2 is supported in CCS4 free edition,Kindly help me in the error

Regards

Vijayabharathi C

 

 

HI

Thanks for your reply. I included ur "ccBoard0.dat" and run the dbgjtag utility. I found some improvement now. But still some error comes if i run the dbgjtag utility

Sometimes i get the following success

C:\Program Files\Texas Instruments\ccsv4\common\uscif>dbgjtag.exe -f ccBoard0.da
t -rv

-----[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 'Jun 30 2010'.
The library build time was '22:08:44'.
The library package version is '5.0.104.0'.
The library component version is '35.34.24.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).

 

Many times i get below error message

 

C:\Program Files\Texas Instruments\ccsv4\common\uscif>dbgjtag.exe -f ccBoard0.da
t -rv

-----[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 'Jun 30 2010'.
The library build time was '22:08:44'.
The library package version is '5.0.104.0'.
The library component version is '35.34.24.0'.
The controller does not use a programmable FPGA.

An error occurred while hard opening the controller.

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

This error is generated by TI's USCIF driver.

The value is '-180' (0xffffff4c).
The title is 'SC_ERR_CTL_NO_TRG_POWER'.

The explanation is:
The controller has detected a target power loss.
The user must turn-on or connect the power supply for the target.

kindly advise me for further steps..

Regards

Vijayabharathi C

 

Hi

We have another OMAP 3530(SBC8100) board. I tried using dbgjtag utility in that board using XDS100v2 and the ccBoard0.dat u provided.Follwing were the error messages

 

C:\Program Files\Texas Instruments\ccsv4\common\uscif>dbgjtag -f ccBoard0.da
v

-----[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 'Jun 30 2010'.
The library build time was '22:08:44'.
The library package version is '5.0.104.0'.
The library component version is '35.34.24.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).

C:\Program Files\Texas Instruments\ccsv4\common\uscif>dbgjtag -f ccBoard0.da
v -S pathlength

-----[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 'Jun 30 2010'.
The library build time was '22:08:44'.
The library package version is '5.0.104.0'.
The library component version is '35.34.24.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.

C:\Program Files\Texas Instruments\ccsv4\common\uscif>dbgjtag -f ccBoard0.da
v -S brokenpath

-----[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 'Jun 30 2010'.
The library build time was '22:08:44'.
The library package version is '5.0.104.0'.
The library component version is '35.34.24.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).

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

C:\Program Files\Texas Instruments\ccsv4\common\uscif>dbgjtag -f ccBoard0.da
v -S integrity

-----[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 'Jun 30 2010'.
The library build time was '22:08:44'.
The library package version is '5.0.104.0'.
The library component version is '35.34.24.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).

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

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Vijayabharathi,

The fact that the <ccBoard0.dat> file I sent you works better indicates that your target configuration file (.ccxml) is not properly configured. Make sure you are properly selecting OMAPL138 and XDS100v2. For now, let's check the messages you are getting.

The first error message: 

The value is '-180' (0xffffff4c).
The title is 'SC_ERR_CTL_NO_TRG_POWER'.

The explanation is:
The controller has detected a target power loss.
The user must turn-on or connect the power supply for the target.

Indicates that the board has no power applied to it. I would check the power to the Hawkboard (I managed to make it work with both the 5V and the USB power) or the JTAG line TVRef. For details on JTAG pinout check section Emulation Header signal definitions of  the page below:

http://processors.wiki.ti.com/index.php/XDS_Target_Connection_Guide

The subsequent error messages:

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.

Indicate that the JTAG path has one of its data lines held at logic level 0 (ground) or 1 (Vcc). This may also be an issue with the board - check the voltage or maybe a shorted pull-ups or downs on the JTAG lines.

I would also try another emulator or a combination of emulator/board where everything connects fine, so you can rule out any issues. 

Hope this helps,

Rafael

Hi Rafael

Thanks for the reply.. some obsevations from my side

C:\Program Files\Texas Instruments\ccsv4\common\uscif>dbgjtag -f ccBoard0.da
v -S brokenpath

-----[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 'Jun 30 2010'.
The library build time was '22:08:44'.
The library package version is '5.0.104.0'.
The library component version is '35.34.24.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).

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

Above error appears even in another OMAP 3530 board(SBC8100) which is working correctly with u-boot,Linux kernel. I tried to connect this board with same XDS100v2 and CCS!! Is this anything related to PC side or driver problem?

Regards

Vijayabharathi C

Vijayabharathi,

Since dbgjtag is the software closest to the emulation hardware, it is either an issue with the hardware or the low-level device drivers - in other words, chances are pretty slim that CCS is influencing this. Are you running from a virtual machine like VmWare? Could you test the whole setup in another PC?

Unfortunately I don't know the SBC8100 board in details, but can you check if there are any jumpers that configure the boot mode of this board? I've seen in the past Beagleboard and OMAP3530EVM prevent emulator access after Linux started (I had power management enabled which caused disruptions), therefore to test the connection I used to halt the u-boot autoboot and connect to CCS. You could try that.

Also, since the other SBC8100 board is running properly, the emulator itself may be bad. If you have another emulator in hand that could help, but the important thing is to try to find a combination of PC/emulator/board that works, so you could use that as a baseline for subsequent tests.

Sorry for the trouble,

Rafael

 

 

 

Rafeal

 

Thanks for the inputs, let me check in another PC/board. Hope atleast some improvement comes

 

Regards

Vijayabharathi C