• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 54 subscribers
  • Views 7728 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.

error connecting BLACKHAWK TMDSEVM6678LE XDS560v2 emulator to CCS via USB

Elana Granston
Prodigy 110 points
Other Parts Discussed in Thread: TMS320C6670

 

 

I'm trying to connect the TMDSEVM6678le XDS560v2 emulator (on windows 7) to ccsv5.3.   The emulator is physically connected thru a USB port.  After creating a target configuration, I selected "test connection". 

I get the error following error message:

 

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\ELANAG~1\AppData\Local\.TI\693494126\     0\0\BrdDat\testBoard.dat

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

This utility has selected a 560/2xx-class product. This utility will load the program 'bh560v2u.out'. E_RPCENV_IO_ERROR(-6) No connection: emulator was not found Download failed for file C:\ti\ccsv5\ccs_base\common\uscif\xds560v2.out

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 or utilities.

The value is '-250' (0xffffff06). The title is 'SC_ERR_ECOM_EMUNAME'.

The explanation is: An attempt to access the named emulator via USCIF ECOM has failed.

[End]

Not usprisingly, if I try to "launch configuration", that fails too. 

 

The emulator shows up in the device manager (Windows 7).  When I hit full reset, I get the expected output in the hyperterminal (per the  "TMS320C66x Evaluation Module Quick Start Guide").  The emulator does not show up in the Blackhawk config utility, not even when I hit search.  On the board itself, the red and yellow lights are on, the green light blinks and then turns off.  If I understood another forum post correctly, this means it is NOT in safe mode.  I tried various usb ports on my computer - no difference. 

I installed everything as directed in the  "TMS320C66x Evaluation Module Quick Start Guide" and then the "BOIS-MCDSK Getting Started Guide" using software from the disk except that I am using ccs5.3 instead of the version of ccs5.0.3 that came on the disk.  I should have the proper license for 5.3  I also tried installing a clean copy of 5.4 (selecting license for emulators and simulators).  Neither could not find the emulator.  However,

The switches are in the positions indicated in the Quick Start Guide, step 2.

When I try running with a target configuration that specifies xds100v1 instead of Blackhawk xds560v2, I get a different error message but still an unsuccessful connection:

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\ELANAG~1\AppData\Local\.TI\693494126\     0\0\BrdDat\testBoard.dat

-----[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 'Oct  3 2012'. The library build time was '21:58:41'. The library package version is '5.0.872.0'. The library component version is '35.34.40.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 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 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 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. Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 7: scanned out 0x00000000 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: 2, skipped: 0, failed: 1 Do a test using 0xFE03E0E2. Scan tests: 3, skipped: 0, failed: 2 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 3 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 4 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 5 Some of the values were corrupted - 83.3 percent.

The JTAG IR Integrity scan-test has failed.

-----[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. Test 2 Word 0: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 1: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 2: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 3: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 4: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 5: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 6: scanned out 0x00000000 and scanned in 0xFFFFFFFF. Test 2 Word 7: scanned out 0x00000000 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: 2, skipped: 0, failed: 1 Do a test using 0xFE03E0E2. Scan tests: 3, skipped: 0, failed: 2 Do a test using 0x01FC1F1D. Scan tests: 4, skipped: 0, failed: 3 Do a test using 0x5533CCAA. Scan tests: 5, skipped: 0, failed: 4 Do a test using 0xAACC3355. Scan tests: 6, skipped: 0, failed: 5 Some of the values were corrupted - 83.3 percent.

The JTAG DR Integrity scan-test has failed.

[End]

 

  • 0
    TI__Guru**** 171044 points

    Elana,

    I am able to connect to my C6678LE board, and I tried all the utilities you used (the Test Connection, the Bh560v2 Config Utility, the same DIP switch settings) and everything just works here. The only detail that was not clear is if you used the Blackhawk XDS560v2-USB System Trace Emulator or the Blackhawk XDS560v2-USB Mezzanine Emulator. However, I tested both configurations and at least the Test Connection button returned a successful result.

    One detail: I get the same failure as you when I try to use the XDS100v1 - thus the mezzanine card must be unplugged before trying to use this emulator.

    All that said, my impression is the mezzanine card may be either faulty or it has a bad connection to its baseboard. You can try to unplug/plug it or unplug it and test the XDS100v1 directly.

    Hope this helps,

    Rafael

     

     

     

     

  • 0 in reply to desouza
    Prodigy 110 points

    Rafael,

    Thanks for your response.  I'll test the xds100v1 connection and I'll respond with the result. 

    Which version of ccs did you use?  I have several versions installed. The relevant ones are ccs 5.3 with license and a version of 5.4 that I just downloaded.  The 5.4 version is supposed to be for emulators and simulators and was free.  I did not try the 5.0.3 that came on the disk.  Should 5.3 or 5.4 work ro do I need 5.0.3?

    In the meantime, as I mentioned in the original post,  the xds560v2 is also not showing up in the Blackhawk config utility.  I suspect that this is key to why ccs cannot connect to the board.  How do I get this resolved?  I'm trying to figure out if this is a hardware or software problem. 

    Elana

  • 0 in reply to Elana Granston
    TI__Guru**** 171044 points

    Elana,

    The CCS releases I am using are the same: 5.3 and 5.4 (5.0.3 is not recommended at all). Regarding Licensing, the Mezzanine emulator and configuration do not require a paid license, therefore you will not have trouble with your v5.4 install.

    The fact the emulator is not showing in BH's config utility is indicative of either a failed device driver instantiation or a hardware failure. Since you have switched USB ports (which usually helps with any USB enumeration issues) and the emulator is still inoperative, I suspect you have a failed mezzanine emulator board.

    Another detail: are you running inside a Virtual Machine or natively?

    Regards,

    Rafael

  • 0 in reply to desouza
    Prodigy 110 points

    Thanks for the information.  I am running natively.  I would like to try to reinstall the driver(s)  Can you point me to the right driver/reference for uninstalling/reinstalling.  I want to confirm that I am reinstalling the appropriate driver(s) and the appropriate software. 

     

    Elana

  • 0 in reply to Elana Granston
    Prodigy 110 points

    More information on my experience with the config utility...In the Blackhawk config utility, the search does not find the emulator.  It does find something on the network with the ip address of the emulator, but does not recognize it as a Blackhawk device.

     

     If I manually add the device (via ip address) and then search, the config utility now says it found one device.  However, when I select this device, all the buttons (reboot, update..., restore..., test usb interface etc.)remain greyed out and I get the following error message:

    CMD: dtc_conf get bh560v2e 192.168.1.130 E_RPCENV_IO_ERROR(-6) No connection: Error on socket connect: Connection refused (ECONNREFUSED): Check the IP address ERROR: 14 : remote procedure call failed : failed to open the DTC configuration service for url bh560v2e:-1062731390

     

    I also tried adding the device with the usb connection (USB:1).  The search "finds" the deivce, but the buttons remain greyed out when I select the device from the list.

     

     

  • 0 in reply to Elana Granston
    Prodigy 110 points

    I cannot connect with the xds100v1 option either.  I get the following error message when I try to debug a hello world testcase:

     

    Error connecting to the target: (Error -151 @ 0x0) One of the FTDI driver functions used during the connect returned bad status or an error. The cause may one or more of: invalid emulator serial number, blank emulator EEPROM, missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utility in the 'common/uscif' folder to verify the emulator can be located. (Emulation package 5.1.73.0)

     

    Unable to connect to target

     

    If I try to launch the configuration (by clicking on view and then clicking on the configuration), I get:

     

     

    [Start]

    Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

    [Result]

    -----[Print the board config pathname(s)]------------------------------------

    C:\Users\ELANAG~1\AppData\Local\.TI\1290299693\     0\0\BrdDat\testBoard.dat

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

    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 or utilities.

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

    The explanation is: One of the FTDI driver functions used during the connect returned bad status or an error. The cause may one or more of: invalid emulator serial number, blank emulator EEPROM, missing FTDI drivers, faulty USB cable. Use the xds100serial command-line utility in the 'common/uscif' folder to verify the emulator can be located.

     

    I am guessing that I need to solve the problem with the config utility first.  How do I proceed from here?

     

    Elana 

     

     

  • 0 in reply to Elana Granston
    TI__Guru**** 171044 points

    Elana,

    I just want to clarify a few things: when you say you are connecting a XDS560v2 emulator to your TMDSEVM6678LE you mean using the board on top of the main EVM board (also called Mezzanine) or an external XDS560v2 emulator? In other words, are you doing this:

    Or this:

     

    Also, regarding the BH utility: that is what I see when I run mine here when I am using the Mezzanine (disregard the LAN emulators).

     

    The Windows device drivers for the emulator are typically installed by Blackhawk and the default placement is:

    C:\Program Files (x86)\Blackhawk\Emulation\Drivers\Bh560v2\v1.0.0.7

    The base device drivers don't change much across the years, and since you see a properly initialized entry in the Control Panel I am really not sure if this is the issue...

    I did another test: I just removed the Mezzanine board and the CCS connection to the XDS100v1 emulator on the base board succeeded without problems.

    This comparison indicates there is something going bad on the board. Do you think you could try to get a different 12V power supply and retry connecting to the board? I've seen this before (sometimes the output voltage is lower, or there is too much noise and the devices do not get properly initialized).

    At last, if you can get a similar OutputLog as shown in the Bh560v2 config utility above, can you copy it to a .txt file and attach to your post? I can compare the settings with mine and ask for some help from Blackhawk.

    Regards,

    Rafael

     

  • 0 in reply to desouza
    Prodigy 110 points

    Thank you for posting the photos.  You solved the problem.  The documentation said to use usb:1.  Moving the usb cable to usb:0 (as shown in your photo) solves the problem.

  • 0 in reply to desouza
    Intellectual 505 points

    Hi Elana ,
    i have the same problem ,
    i would like to make a connection between CCS v5.3 and TMS320C6670 using Blackhawk XDS560v2-USB Mezzanine Emulator , i am put the USB on the the top board like the previous  picture buts when i go to the Device manager it says that it is required a driver like the below picture .
    Can you help me please ?
    Thank you in advanced
    Muhammad .