• Locked Locked
  • Replies 9 replies
  • Subscribers 83 subscribers
  • Views 3149 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.

Connecting with CCSv5 on C2000 Developer's Kit

Friedbert Maier
Prodigy 110 points

Other Parts Discussed in Thread: TMS320F28027

Hello,

I work with an c2000 PFC Developer's Kit, witch named TMDSHVPFCKIT.  There is a TMS320F28027 Mikrocontroller, with a Isolated XDS 100 USB JTAG Emulator.

My Software is CCS5.1.0.0900, with a Windows 7.

In my .ccxml-File I have put the TI Emulator XDS 100v2. Is this correct?

Now when I want to debug a example program (e.g. PFC2PhiL2 ) , then I get this error:

Error connecting to the target:
(Error -1135 @ 0x0)
The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.
(Emulation package 5.0.520.0)

now I click on retry an I will get allays this error:

Error connecting to the target:
(Error -1041 @ 0xFFFFFF87)
The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.
(Emulation package 5.0.520.0)

 

At the test connection I get this File:

8304.04.txt

Can somebody help my to find the target with the CCS?

When I work with the HVPFC2PHIL-GUI.exe then I can controll the Mikrocontroller.

Regards,

Friedbert Maier

 

 

  • Mastermind 7585 points

    Friedbert,

    I believe that all the F280xx Kits still use the XDS100V1 emulator.

     

  • in reply to Frank Bormann
    Prodigy 110 points

    Thank you, Frank. From with site can I get informations like this, because in the TI wiki I found only the C280xx and this one can unsed with bouth. XDS100v1 and XDS100v2.

     

    But I have tested it with the TI XDS100v1 USB Emulator and I get still the same error:

    Error connecting to the target:
    (Error -1135 @ 0x0)
    The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.
    (Emulation package 5.0.520.0)

    and after the retry:

    Error connecting to the target:
    (Error -1041 @ 0xFFFFFF87)
    The emulator reported an error. Confirm emulator configuration and connections, reset the emulator, and retry the operation.
    (Emulation package 5.0.520.0)

    And when I make the "Test Connection" in the .ccxml - File:

    Fullscreen 0005.100v1.txt Download 
    [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]

     

    Or is it possible, that it doesn't work with Windows 7?

     

     

     

     

     

  • in reply to Friedbert Maier
    Prodigy 110 points

    It still doesn't work.

    Can somebody send me a program with all setting, which works on the TMDSHVPFCKIT when I debug on the CCSv5.

     

    Thank you,

     

    Friedbert Maier

     

  • in reply to Friedbert Maier
    TI__Guru 57255 points

    Friedbert,

    Assuming you've gotten CCS to try to connect to a F28027 using a xds100v1 emulator you should be fine from the CCS side of things.

    From the hardware side, make sure you've re-populated the R6 and R7 near the Piccolo device.  These resistors change the configuration of the controller card between being able to run from FLASH (run the demo with the GUI) and connecting/running from CCS.  This sounds like your problem.  From pg14 of the CCS guide for HVPFC:

    1.  Connect USB connector to the Piccolo controller board for emulation. Power up the 14 V bias supply at J2. By default, resistors R6 and R7 on the Piccolo Macro of the control card are removed to enable – boot from FLASH. Re-populate these resistors to run and program RAM or program FLASH.


    Thank you,
    Brett

  • in reply to Brett Larimore
    Prodigy 110 points

    Thank you Brett,

     

    I will try it tomorrow, if this is the problem.

    Do you know how is the easiest way to connect these resistors?

     

    Regards,

    Friedbert

  • in reply to Friedbert Maier
    TI__Guru 57255 points

    Friedbert,

    They're 0 ohm resistors and I believe they're partially placed on the correct pad.  So if you have access to a solder station/tech who can do it, it should be very easy.  Because the connection should be approximately 0Ohm, I'm sure you could find another way to short the connection if you need to.


    Thank you,
    Brett

  • in reply to Brett Larimore
    Prodigy 110 points

    Thank you Brett that was it.

    Now the board works.

    Regards,

    Friedbert

  • in reply to Brett Larimore
    Prodigy 200 points

    Brett,

    They're not 0 ohm resistors! R7 is 0 ohm, but R6 is 2 kiloohm. See PiccoloA-48LQFP[R2]schem.pdf.

    Regards,

    Jozef

  • in reply to Jozef Šedo
    TI__Guru 57255 points

    Jozef,

    You are correct, my apologies.

    It appears that R7 needs to be changed from "do not populate" to a 0ohm resistor.  This allows you to either boot from flash/SCI (DNP) or connect via an emulator (0ohm).

    R6 is 2Kohm and apparently allows you to control whether you boot from flash or boot from SCI.

    Therefore only R7 needs to be populated for JTAG emulation to work properly.


    Thank you,
    Brett