• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 473 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 to connect 6678 kit

Nivaldo T. Schiefler Jr.
Intellectual 640 points

I´m trying to connect the TMDSEVM6678LE   example given in the BIOS mcsdk user's guide for Windows. And i´ve this msg 

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)

Any ideas for this problem???

thank´s Nivaldo

  • 0
    TI__Guru* 84110 points

    Nivaldo,

    Which version of CCS are you using?

    Which emulator did you setup your Target Configuration for?

    Where did you plug in your USB cable to the board? Should be on the mezzanine board not the main lower board.

    In CCS, open your Target COnfiguration and click the Test Connection box. What does it report?

    Regards,
    RandyP

  • 0 in reply to RandyP
    Intellectual 640 points

    Hi Randy,

    my ccs  version is   5.1.0.09000 

    The target config is  XDS100v1  USB Emulator_0  (in my kit i´ve the XDS560v2 pluged too)

    the usb cable i pluged in USB mini for XDS100

    the report for connection is:

    [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 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 27 2011'.
    The library build time was '17:12:35'.
    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 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]

    what do you think?   I dont´t figured out where is wrong step to configure.

    Regards

    Nivaldo

  • 0 in reply to Nivaldo T. Schiefler Jr.
    TI__Guru* 84110 points

    Nivaldo,

    You need to update your CCS using Help->Check for updates, to make sure you have the latest emulation drivers and to use the latest version of CCS. Then you need to follow the instructions in the online BIOS MCSDK 2.0 Getting Started Guide, specifically using the correct emulator, XDS560v2.

    Also, please make sure your USB cable is plugged into the correct USB plug on the board, the one on the mezzanine card. The Quick Start Guide that came with the board should be able to guide you.

    Try the Test Connection button again with the correct setup, then let us know the status, please. If it works, then please mark the Verify Answer button, but not until your question has been answered.

    Regards,
    RandyP

  • 0 in reply to RandyP
    Intellectual 640 points

    Hi Randy

    I did all new instalation and i was trying tocompile my fisrt prog. I have thid msg


    This project was created using a version of compiler that is not currently installed: 7.3.1 [C6000]. Another version of the compiler will be used during build: 7.4.2. Please install the compiler of the required version, or migrate the project to one of the available compiler versions by adjusting project properties. led_play properties TI Problem Marker

    where in the properties i must to change the configuration ?  

    my ccs is 

    Version: 5.3.0.00090

    Thanks

    Nivaldo

  • 0 in reply to Nivaldo T. Schiefler Jr.
    TI__Guru* 84110 points

    Nivaldo,

    Learning to use the tools is not the easiest thing to do. There is a lot to learn, and it is difficult to teach every point over the forum, and it is inefficient for you to have to wait so long for your answers.

    That is why we have uploaded our training workshops to the TI Wiki Pages for you. There are also a variety of online video trainings that you can search for at TI.com or on the TI Wiki Pages.

    For now, I recommend you go to the TI Wiki Pages and search for "c6000 training" (no quotes) to find the Category of C6000 Training support including a list of available classes on the Wiki.

    Look at the student guide of the C6000 workshop with BIOS, and there is a chapter on the Basics of CCS. One page (2-6) shows a screen shot where the compiler version is selected. There may be minor changes in versions of CCS, but this will help you find this answer and also many of the questions that will come up next.

    Regards,
    RandyP