• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 54 subscribers
  • Views 1656 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Could not connect to C6678L via XDS100v2/v1

Sayan Ghosh
Intellectual 255 points


I am remotely accessing to a machine which is connected to a C6678L via XDS100 USB emulator. I am specifying the emulator as XDS100v2 in the target configurations. When I try to Run as Debug I get the following error:

 

 

IcePick_D: Error connecting to the target:

(Error -151 @ 0x0)

This utility failed to open the adapter for a custom emulator.

The adapter returned an error.

(Emulation package 5.0.520.0)

 

 

This is another error one of my colleague is getting when he tries from a different system:

 

Error connecting to the target:
(Error -183 @ 0x0)
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.
(Emulation package 5.0.520.0)

 

I am using CCS 5.1 on 32 bit Ubuntu 10.04. Please help me in solving the error.

 

Thank you

Sayan

  • 0
    TI__Guru**** 468041 points

    The Error -151 is something I've seen in the past. One thing is to check the EEPROM is programmed correctly:

    http://processors.wiki.ti.com/index.php/XDS100#Q:_How_can_I_check_if_the_VID.2FPID_for_the_EEPROM_are_programmed_correctly.3F

    Also you can try running dbgjtag to run more JTAG diagnostics. You can run it by pressing the 'Test Connection' button in the target configuration tool

  • 0 in reply to Ki
    Intellectual 255 points

    Thank you for replying. I noticed that the "test connection" button is grey-ed out for XDS100v2. And I checked the VID/PID, it seems alright.

    lsusb ---> Bus 001 Device 006: ID 0403:a6d0 Future Technology Devices International, Ltd

    The EEPROM needs to be programmed for a VID=0403 PID=A6D0. The device name string should be, “Texas Instruments Inc.XDS100 Ver 2.0”.  from here.

    Can you please give me any ideas to solve this?

  • 0 in reply to Sayan Ghosh
    Intellectual 255 points

    I noticed while doing <lsusb -v>, that emulator is listed as "Texas Instruments XDS100+RS232 V1.0" .

    Does this mean that the C6678L has XDS100v1....when I try updating the Target Configurations to that, I get the following error:

    :

      And going by my last post, shall I try to re-program the EEPROM? If yes, then please point me to a Linux utility to do so.

     

    Thanks,

  • 0 in reply to Sayan Ghosh
    TI__Guru**** 171224 points

    Hi,

    Regarding this last error box, the bug SDSCM00042610 was just filed. Please check its status in the link SDOWP below.

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 255 points

    I had to edit the answer completely because I guess I was told to read the .dat file, and I gave the command line to read the RTSC cfg file. Anyways, I feel that my test connection is passing, as shown below (I have used XDS100v1 BTW); but when I try to Debug my program I get the same connection error as shown below:

     

    This is the output of "Test Connection":

     

     

    /opt/CCS5.1.0/ccsv5/ccs_base/common/uscif/dbgjtag.exe -f /home/c7364u07/.TI/2193391159/0/0/BrdDat/testBoard.dat -rv -o -F inform,logfile=yes -S pathlength -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 'libjioserdesusb.so'. The library build date was 'Oct 27 2011'. The library build time was '18:01:52'.

    The library package version is '5.0.520.0'.

    The library component version is '35.34.38.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).


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

     

     

     

  • 0 in reply to Sayan Ghosh
    Intellectual 255 points

    The issue is solved. Since the board is set up for remote access, so there were concurrent accesses on the host machine (when the host machine had a trial version of CCS), which was the reason for this error. Thanks for all the help.

  • 0 in reply to Sayan Ghosh
    Prodigy 40 points

    Hi Sayan,

    I have somewhat similar problem. I have received the EVMC6678L with the board and both XDS100 and XDS560.

    When I try to use XDS100 (as indicated in the brochure) with my Ubuntu 12.04, it fails.

    For XDS100v1 selected it reports

    Error connecting to the target:
    (Error -2131 @ 0x0)
    Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
    (Emulation package 5.0.520.0)

    And dbgjtag reports

    #:~/ti/ccsv5$ ./ccs_base/common/uscif/dbgjtag -f /home/vzivkovic/.TI/1613324925/0/0/BrdDat/ccBoard0.dat -rv

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

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'libjioserdesusb.so'.
    The library build date was 'Oct 27 2011'.
    The library build time was '18:01:52'.
    The library package version is '5.0.520.0'.
    The library component version is '35.34.38.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).

    which is similar to your message.

    Similarly, the lsusb reports:

    Bus 002 Device 007: ID 0403:a6d0 Future Technology Devices International, Ltd

    Now, if I select XDS100v2 then the error is different but the issue stays.

    And, btw, the blackhawk jtag also doesn't manage to connect.

    So, it is something which has to do with the way CCS is set up under Linux

    I saw your report but I couldn't understand much from it - in terms how did you resolve it?

    Thank you for the answers

    Vladimir

  • 0 in reply to Vladimir Zivkovic
    Intellectual 255 points

    Hello Vladimir,

    My board was connected to a remote machine, which was accessible by multiple users. Along with me, someone else was also trying to 'load' something on the board, and hence I was getting the error. Although, I did not setup the environment of the host machine with which the board was connected to, but I remember the person who did it followed the CCS installation wiki (http://processors.wiki.ti.com/index.php/Linux_Host_Support). I would suggest that create a new thread with this question if you have not already done it.

    //Sayan

  • 0 in reply to Sayan Ghosh
    Prodigy 40 points

    Hi Sayan,

    Just to let you know, interestingly enough I managed to create a "platform configuration" using my Linux Ubuntu 12.04 x86_64 and TMDSEVM6678.

    This was the issue:

    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/130970/512656.aspx#512656

    Apparently my EVM has both JTAG's xds560v2-usb-BlackHawk-Mezzanine and xds100v1-FTDI - and the guides from http://processors.wiki.ti.com/index.php/TMDXEVM6678L_EVM_Hardware_Setup and  http://processors.wiki.ti.com/index.php/BIOS_MCSDK_2.0_Getting_Started_Guide etc are not really pointing which configuration is possible etc. Basically, the moment I physically removed xds560 from the 60-pin things start working (at least in terms of Target Configurations, Launching, Emulation, etc - still far to go, but at least I can now load "Example 1").

    Hence, the "guide" shall describe unambiguously that "for such EVM an such JTAG such and such pin-switch shall be used and  other things shall be removed or not-used"... but at least browsing the e2e helped... it took a while but it did help.

    However, I still cannot decipher why my RS232 at minicom or cutecom doesn't report anything.

    Basically, I verified that my PC ttyS0 works and it is definitely working because when I short-circuited DB9 pins 2 & 3, I could see what I was typing in minicom,

    However, when the board was connected to UART (switches set to option for "IBL NOR boot on image 0 (default) "), and when I typed via WEB diagnostics page a message for UART, the board simply didn't report anything via cable to ttyS0...

    But that's perhaps other topic than JTAG. So thanks for the efforts

    Kind regards

    Vladimir