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

controlCARD connection problem

Roman Ermakov
Expert 1150 points
Other Parts Discussed in Thread: UNIFLASH

Hi

I have a problem  with my Concerto F28M35 controlCARD. I can't  establish connection to the CCS 5.5 under WIN 8.1.

Same board worcks fine with CCS 5.3 under WIN XP. 

Below the result of "test connection" is provided:

[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\buzz\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 'Aug 20 2013'.
The library build time was '22:56:19'.
The library package version is '5.1.232.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]

Has anyone faced this error??

thanks,

Roman

  • 0
    Guru 192875 points

    Hi,

    I hope you're using XDS100v2 in your Target Configuration. Please check your target configuration also check this link: http://e2e.ti.com/support/microcontrollers/c2000/f/171/t/321575.aspx

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Expert 1150 points

    Hi, Guatam

    Yes I am using XDS100v2 in my Target Configuration but in the WIN's device manager it is called 

    Texas Instruments Inc. XDS100 Version 1.0 A
    Texas Instruments Inc. XDS100 Version 1.0 B

    is it correct?

    As for the link you have given, the situation looks the same.

    I'll try to use Uniflash tomorrow; and also I have not touched SW1 on my controlCARD. 

    All SW1 switches are turned to the bottom side on this picture.

    I think it isn't a jumpers configuration problem because I have two identical controlCARDs and both connect to the WIN XP desktop and do not connect to the WIN 8 laptop. May be my laptop USB port can't  provide sufficient current for the controlCARD to work correctly?..

     

  • 0 in reply to Roman Ermakov
    Guru 192875 points

    using XDS100v2 in my Target Configuration but in the WIN's device manager it is called

    Texas Instruments Inc. XDS100 Version 1.0 A
    Texas Instruments Inc. XDS100 Version 1.0 B

    Thank for the info. Yes, then you do have a XDS100v1 and not v2.

    May be my laptop USB port can't  provide sufficient current for the controlCARD to work correctly?..

    I don't think that might be an issue. But do check with Uniflash and revert.

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Expert 1150 points

    Hi Gautam!

    this is my target configuration screenshot

    As you  can see the emulator is "Texas Instruments XDS100v2 USB Emulator"

    there is no possibility to select F28M35 device in case I select XDS100v1 emulator:

    but in the WIN's device manager I see "Texas Instruments Inc. XDS100 Version 1.0 A" and "Texas Instruments Inc. XDS100 Version 1.0 B"

    May be I need to reinstall something?

    Thanks,

    Roman

  • 0 in reply to Roman Ermakov
    TI__Guru 57255 points

    Hi Roman,

    Firstly, the F28M35x controlCARD has an on-card FT2232H-based xds100v2 emulator.  Therefore your target configuration is correct.  (xds100v2 + F28M35H52C1)

    I think the key thing to note here is that the card works with WinXP and CCS5.3 (it may be worth rechecking this to make sure this is still true).

    If you then move the Experimenter's Kit with the same hardware settings, cable connections and target configuration to the PC Win8 and CCS5.5.  If it fails now, this would point me toward issues with either CCS or the xds100v2 drivers on the newer Win8 PC.

    When you plug into the WinXP PC, does device manager show that Windows has assigned the controlCARD the same driver as in the Win8 PC?


    Thank you,
    Brett

  • 0 in reply to Roman Ermakov
    Guru 192875 points

    As you  can see the emulator is "Texas Instruments XDS100v2 USB Emulator"

    there is no possibility to select F28M35 device in case I select XDS100v1 emulator:

    Sorry for the misinterpretation, as Brett has mentioned it is FT2232H-based xds100v2 emulator. Do revert with what Brett has suggested.

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Expert 1150 points

    Hi Brett, Gautam,

    The problem was in the docking station. I can bypass this by connecting TP4-TP8 and TP19-TP20 because I don't need insulation in my task. Am I right?

    So, probably I will not look for the root of the problem.

    Thank you very much for your help.

    Another problem I have faced is the DIMM-100 connector. Molex 0876301001 is obsolete  and I can't find replacement for it. May be somebody knows a similar part  that I can order through farnell or elfa?

    Thanks,  regards

    Roman

  • 0 in reply to Roman Ermakov
    TI__Guru 57255 points

    Roman,

    Roman Ermakov said:

    The problem was in the docking station. I can bypass this with connecting TP4-TP8 and TP19-TP20 because I don't need insulation in my task. Am I right?

    Correct.


    Roman Ermakov said:

    Another problem I have faced is the DIMM-100 connector. Molex 0876301001 is obsolete  and I can't found replacement for it. May be somebody know similar part  which I can order throught farnell or elfa?



    For the exact reason you mention we sell a pack of 5 DIMM-100 connectors in the TI eSTORE:
    http://www.ti.com/tool/tmdsdim100con5pk


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Expert 1150 points

    Thank you very much for the quick response!

    Farnell code is 2213075 so now I can order it.

    With best wishes,

    Roman.