• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 84 subscribers
  • Views 1944 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.

F28377D ControlCard connection problem

Ralf Juchem
Prodigy 40 points

I am quite new to using CCS and interfacing to a target board. So please excuse in case my question is somewhat stupid.

I have a ControlCard plugged  into a dock (TMDXDOCK28377D) and I connected that system using all of the three USB cables provided to my computer.

To get started I now wanted to perform the basic target setup in CCS. As far as I understand, I have to select the Connection ("Texas Instruments XDS100v2 USB Debug Probe") and the device TMS320F377D. Then I saved the configuration.

Testing the connection results in the following output:

[Start: Texas Instruments XDS100v2 USB Debug Probe_0]

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\juchem\AppData\Local\TEXASI~1\CCS\
    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 'jioserdesusb.dll'.
The library build date was 'Sep  4 2015'.
The library build time was '21:59:23'.
The library package version is '6.0.14.5'.
The library component version is '35.35.0.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 64 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 64 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 64 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: Texas Instruments XDS100v2 USB Debug Probe_0]

As far as I understand, I got a bunch of error messages. What am I doing wrong?

Thank you very much,

  Ralf

  • 0
    TI__Guru 61235 points

    Hello Ralf,

    The USB jack along the long edge of the ControlCard is the actual USB peripheral on the F28377D.  You don't need this cable at this time.  The USB jack along the short edge of the ControlCard is the XDS100v2 connection.  You need this cable connected to your PC.  You also need the USB jack on the docking station for power connected (unless you are using an external 5V supply in the barrel jack, which I don't think you're doing).

    Now not to insult you, but make sure you have the switch next to the power jack on the docking station set to the "USB-ON" position.  Maybe this is the problem.  If the switch is in the "Ext" position (which is for the barrel jack power), you will think the power is on because the LEDs on the ControlCard will still come on due to the USB connection for the XDS100, but the power is not on to the F28377D (the ControlCard has two power planes with isolation between them).  'Test connection' if this switch is wrong will give the results you showed in your post.  After confirming the switch position, run your test connection again.

    Regards,

    David

  • 0 in reply to David M. Alter
    Prodigy 40 points
    I have the exact same results. However, I do not have the docking station - the only connection is the USB cable from the F2837x controlCARD R1.1 to the PC USB port. The switch positions are: A:SW1 1 is UP (ON) and 2 is down; SW1: 1 is UP (OFF) and 2 is down. Only the A:D2 LED is ON. The PC Device Manager shows TI XDS100 Channel A and TI XDS100 Channel B and both are reported as working properly.
  • 0 in reply to Peter Clarke
    TI__Guru 61235 points
    The ControlCard is not intended to be used without a docking station. If you just connect the XDS100 USB cable to the ControlCard, the emulation chip will be powered, but the F28377D will not be. As I mentioned, there are two power planes on the card with isolation between them. The XDS100 chip is on one side, and the F28377D is on the other side of the isolation barrier.

    So in your case, the F28377D is not being powered, and you get a failed 'Test Connection' result which is to be expected.

    - David
  • 0 in reply to David M. Alter
    Prodigy 40 points
    Thanks David - it now works.
  • 0 in reply to Peter Clarke
    Prodigy 40 points
    Hi David, hi Peter,
    thanks a lot for your replies. In my case, the main problem was introduced by wrong switch settings of A:SW1. Now I set them according to Peter's description and everything seems to be fine now!

    Thank you very much!
  • 0 in reply to David M. Alter
    Expert 2220 points

    I have the 28377D R1.1 board and the docking station.

    I was having similar issues and did as per you stated here with the Switch in the USB on position on the docking board, and the USB JTAG connector.

    Everything worked once power was applied to the main processor as you say, and development has proceeded.

    I am now trying to use the USB connector on the long side for development, so I now have all 3 usb connections.  I need to understand the power planes a bit better, because when I only connect the two USBs (JTAG USB / short edge & USB USB / long edge ) then I am able to communicate with the board and load programs to it, without power supplied by the docking station board... ie: power can be in OFF position on docking station.

    This implies to me the long edge USB must have some connection to the power plane, and so the question amounts to what is the proper configuration.

    Should I:

    ALWAYS apply power through the USB on the docking station with the switch in the on position if I don't use the barrel connector, even if I'm doing development with the USB USB / long edge?

    Is the 2nd USB on the long edge designed to supply power to the board in adequate amounts instead of the docking station board?

    Is there any possible issues if power is coming from both the USB USB / long edge or the USB on the docking station with switch in on position?

    If I'm following the schematic properly, it appears the 5V power from the USB USB /long edge or the HSEC 5V power is just tied together (implying can use either power sources) feeding U14 which then generates the 3.3 and 1.2V for the processor.  WIll there be any conflict if both are connected?

    I also see the HSEC has a 5V supply going to various pins that feed to the processor, so this implies to me that:

    We MUST connect the 5V power through either the JTAG or barrel connector on the docking station board.

    This must imply that the additional 5V supplied by the USB/USB on the long edge will not conflict with that supplied by the docking station, but just provides additional power if needed I suppose.

    Could you verify this?

  • 0 in reply to David M. Alter
    Expert 2220 points

    I have the 28377D R1.1 board and the docking station.

    I was having similar issues and did as per you stated here with the Switch in the USB on position on the docking board, and the USB JTAG connector.

    Everything worked once power was applied to the main processor as you say, and development has proceeded.

    I am now trying to use the USB connector on the long side for development, so I now have all 3 usb connections.  I need to understand the power planes a bit better, because when I only connect the two USBs (JTAG USB / short edge & USB USB / long edge ) then I am able to communicate with the board and load programs to it, without power supplied by the docking station board... ie: power can be in OFF position on docking station.

    This implies to me the long edge USB must have some connection to the power plane, and so the question amounts to what is the proper configuration.

    Should I:

    ALWAYS apply power through the USB on the docking station with the switch in the on position if I don't use the barrel connector, even if I'm doing development with the USB USB / long edge?

    Is the 2nd USB on the long edge designed to supply power to the board in adequate amounts instead of the docking station board?

    Is there any possible issues if power is coming from both the USB USB / long edge or the USB on the docking station with switch in on position?

    If I'm following the schematic properly, it appears the 5V power from the USB USB /long edge or the HSEC 5V power is just tied together (implying can use either power sources) feeding U14 which then generates the 3.3 and 1.2V for the processor.  WIll there be any conflict if both are connected?

    I also see the HSEC has a 5V supply going to various pins that feed to the processor, so this implies to me that:

    We MUST connect the 5V power through either the JTAG or barrel connector on the docking station board.

    This must imply that the additional 5V supplied by the USB/USB on the long edge will not conflict with that supplied by the docking station, but just provides additional power if needed I suppose.

    Could you verify this?

  • 0 in reply to Rob Barton
    TI__Guru 57255 points

    Hi Rob,

    The schematic tells most of the story.  As you've seen in the schematic, HSCE_5V0 (5V from the baseboard) and USB_5V0 (5V from J8 - the long-edge USB) are quasi-connected together.

    Powering the emulator via A:J1 and the MCU (and etc) via J8 is a feasible option.  It is worth noting that the power from J8 will not power the baseboard - because of D1.  J8 will provide enough power for the MCU and its circuitry.

    Powering the controlCARD assembly with three source (at A:J1, J8 and via the Docking Station) is also viable.  The only thing to watch out for in this configuration is that the baseboard power should not be at a higher voltage than the voltage sourced by the supply at J8.  For example, if HSEC_5V0 is 5.5V and USB_5V0 is 5.0V then D1 will turn on.  This would cause the assembly to source current into your PC, which may cause you issues.  This 'problem' is likely only an issue if you use the barrel connector on the Docking Station to provide power.

    Hopefully this helps!


    Thank you,
    Brett