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.

  • Resolved

Can't download software on F28035 ControlCARD using CCSv6

Prodigy 230 points

Replies: 10

Views: 915

Hi there. I am developing an application based on F28035 with CCSv6. The first version of the software was developed using the Experimenter Kit along with the F28035 ControlCARD.

In the second stage of development, the ControlCARD must be connected on a self-developed hardware. The hardware connection (USB), is based on the same hardware present on the Experimenter Kit (FT2232 - FTDI adapter).
When I want to download the software from CCSv6, to the self-developed hardware, I get the following error message:

C28xx: 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.1.507.0)

Then I ran a connection test from CCSv6, which got the following result:

[Start: Texas Instruments XDS100v1 USB Emulator]

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)]------------------------------------

/home/martin/.ti/ti/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 'libjioserdesusb.so'.
The library build date was 'May 21 2014'.
The library build time was '13:04:29'.
The library package version is '5.1.507.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 succeeded.
The JTAG IR instruction path-length is 39 bits.

The test for the JTAG DR bypass path-length succeeded.
The JTAG DR bypass path-length is 2 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.

[End: Texas Instruments XDS100v1 USB Emulator]


In this output, no error report is observed. However, there is a difference from the same test run for Experimenter kit.

In this case (self-developed hardware), the parameter "JTAG IR instruction path-length" is 39 while for the Experimenter Kit is 38, and the parameter "JTAG DR bypass path-length" is 2, while for the Experimenter Kit is 1.
I Do not know if this can cause the error, but is the only difference I see between Experimenter Kit and self-developed hardware. Experimenter Kit works fine, self-developed hardware no.

Of course, I checked with an oscilloscope activity in 5 lines of JTAG.

Can anyone suggest any ideas?


Leonardo Martin Petrei

quod nos sumus, qui esse velimus.

  • Hi Leo,

    I hope you've programmed the EEPROM of FTDI chip with VID=0403 PID=A6D0.

    Regards,

    Gautam

     

    If a post answers your question, please click on "This resolved my issue" button

    Are You A Beginner or New to TI's C2000™ Family? Do Check This Book!

  • Hi Leonardo,

    Have you programmed the FTDI chip so that it behaves as an xds100v1?
    http://e2e.ti.com/support/microcontrollers/c2000/f/171/t/21086.aspx


    Thank you,
    Brett

  • In reply to Gautam Iyer:

    Hi Gautam. Yes, I programmed the EEPROM. Even copy the contents of the EEPROM in the Experimenter Kit, but neither worked.


    Leonardo Martin Petrei

    quod nos sumus, qui esse velimus.

  • In reply to Leonardo Martin Petrei:

    Leonardo Martin Petrei
    Hi Gautam. Yes, I programmed the EEPROM. Even copy the contents of the EEPROM in the Experimenter Kit, but neither worked.

    Did you program the EEPROM of FTDI in Experimenter's kit too??? If so, Why?

    Do you've an external XDS emulator?

    Regards,

    Gautam

     

    If a post answers your question, please click on "This resolved my issue" button

    Are You A Beginner or New to TI's C2000™ Family? Do Check This Book!

  • In reply to Gautam Iyer:

    @Gautam. No I don't write the EEPROM on the Experimenter's Kit. I make a copy of the contents from the Experimenter's Kit, and save it in a file; then I write this configuration on my hardware.

    Firstly, I write the EEPROM on my hardware with the configuration suggested by TI.

    Sorry for my english!!! :)


    Leonardo Martin Petrei

    quod nos sumus, qui esse velimus.

  • In reply to Leonardo Martin Petrei:

    Leonardo Martin Petrei
    Sorry for my english!!! :)

    Happens... No problem :)

    Leonardo Martin Petrei
    I make a copy of the contents from the Experimenter's Kit, and save it in a file; then I write this configuration on my hardware.

    Ok, you can try one thing: try using the emulator on experimenter's kit (using the JTAG connector on-board). I just want to check whether the issue is truly on emulator side or at board's end.

    Regards,

    Gautam

     

    If a post answers your question, please click on "This resolved my issue" button

    Are You A Beginner or New to TI's C2000™ Family? Do Check This Book!

  • In reply to Gautam Iyer:

    Gautam Iyer

    Ok, you can try one thing: try using the emulator on experimenter's kit (using the JTAG connector on-board). I just want to check whether the issue is truly on emulator side or at board's end.

    I connect the USB on Experimenter's Kit (without ControlCARD inserted), then, I connect the JTAG (with a ribbon wire) from J2 on Experimenter's Kit to JTAG on my board.

    The result of the connection test (from CCSv6) is the same (no errors reported), and the error when I want to download the software, is the same (error=-1135).

    Hardware problem? Configuration?


    Leonardo Martin Petrei

    quod nos sumus, qui esse velimus.

  • In reply to Leonardo Martin Petrei:

    Leonardo Martin Petrei
    Hardware problem? Configuration?

    Yup, this clearly means that your on-board emulator is all well. Now, we need to check the board part; check the connections of JTAG port with the controller. Refer one of TI's reference document/ schematic for this info.

    Regards,

    Gautam

     

    If a post answers your question, please click on "This resolved my issue" button

    Are You A Beginner or New to TI's C2000™ Family? Do Check This Book!

  • Problem found and resolved.

    In the implementation of the emulator, based on the Experimenter's kit, four optocouplers were added to interface with ControlCARD.

    The error was the specification for the optocouplers: ISO7220A (1 Mbps signaling rate) instead of ISO7220C (25 Mbps signaling rate). The solution: reducing the speed of the communication to the microcontroller (reduced to 100 kbps). The default speed is 1 Mbps.


    This worked for all boards.

    Thanks a lot for your attention!!!


    Leonardo Martin Petrei

    quod nos sumus, qui esse velimus.

  • In reply to Leonardo Martin Petrei:

    That's Great, Leo!

    Goodluck & Regards,

    Gautam

     

    If a post answers your question, please click on "This resolved my issue" button

    Are You A Beginner or New to TI's C2000™ Family? Do Check This Book!

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.