• State Resolved
  • Locked Locked
  • Replies 15 replies
  • Subscribers 81 subscribers
  • Views 2158 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.

XDS100 v1 cannot connect to DSP28335, probably the isolation circuits failed.

Jiayang Ruan
Prodigy 220 points
Other Parts Discussed in Thread: ISO7220C

Hello:

On my development kit provided by TI, the DSP28335 and JTAG connector of the emulator are connected through 4 ISO7220C circuits, maybe for safety 

reasons. But now the emulator cannont connect to DSP, CCS v5 reporting the error when testing the JTAG:

[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:\DOCUME~1\ADMINI~1\LOCALS~1\APPLIC~1\.TI\
1212777678\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 'Apr 2 2012'.
The library build time was '21:41:04'.
The library package version is '5.0.681.0'.
The library component version is '35.34.39.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]

Anyway, I've tested some signal waveforms of ISO7220C, as shown in my attachment.

The waveforms of DSP-side pins of ISO7220C are the same as that of Capacitance C17 in the schematics, obviously they don't follow the input signals.

I guess it's the problem of these 4 isolation circuits, is that right ?

I don't understand how could this happen that all of them failed, because I've taken the kit really cautionsly?

6567.scope.rar

  • 0
    TI__Guru 57255 points

    Jiayang,

    What development kit are you using?


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 220 points

    Hi, it's tmdshvmtrpfckit.

  • 0 in reply to Brett Larimore
    Prodigy 220 points

    BTW, when I'm using an external emulator ,ccs still reports the error.

    The external emulator can only be connected with DSP through the 4 isolation circuits as well.

  • 0 in reply to Brett Larimore
    Prodigy 220 points

    The DSP seems to be working good, and when I replaced the 28335 with another 28035 DSP, error still existed.

  • 0 in reply to Brett Larimore
    Prodigy 220 points

    1. Today I've tested waveforms of another development board, the DSP is also 28335.

        CCS can connect to this target when testing  JTAG.

    2. I tested pins TDI,TRSTn, TCK,TMS and TDO of this board. It seemed that TDI, TRSTn and TCK are the same as those of

        my  tmdshvmtrpfckit,but TMS and TDO are different. For TMS and TDO, there are signals when testing JTAG, but there are no   

       signals on the two pins of  tmdshvmtrpfckit.

    3. Can it be failures of the DSP on   tmdshvmtrpfckit? I replaced it with a 28035 DSP, the problem still exists.

  • 0 in reply to Jiayang Ruan
    TI__Guru 57255 points

    Jiayang,

    Sounds like you're doing a good job of narrowing down the problem.

    Since this TMDSHVMTRPFCKIT's board design is known to be good, this leads me to believe either:
    1) the problem is that some components are damaged
    2) that jumper settings are incorrect.
    3) CCS (I think you've eliminated this possibility).
    4) The FTDI device isn't working properly

    Let's try to rule out (2):
    I'll assume that the cCARD is powered (there should be an LED ON when powered) and the USB cable for emulation is plugged in.  The next step is to make sure that jumper [Main]-J9 is populated and that [M3]-J5 is not populated.  (note that if you use an external emulator I'd populate [M3]-J5 though)  A more thorough explanation of the jumper settings should be in HW Setup Instructions section of the HowToRunGuide.

    To try and eliminate (4), you can reprogram the FTDI chip:
    http://e2e.ti.com/support/microcontrollers/tms320c2000_32-bit_real-time_mcus/f/171/t/21086.aspx

    Has the emulator ever worked?


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 220 points

     

    Hello Brett:

    1. I've used the kit for a long time, so the jumper should be right.  When the external emulater is used, I always populate [M3-] J5, but thanks for reminding me.

    2. CCS can connect to another 28335, as I mentioned above, so possilby CCS is set correctly.

    3.I've reprogrammed the FTDI chip of both external emulater and onboard emulator, unluckily it didn't work.

    4. Now I have strong feeling that at least one of the ISO7220c circuits failed, but I can't make sure which one. But how can it be  damaged? These circuits are

       high-quality ones, as far as I know.

     What should I do now, Brett?

  • 0 in reply to Jiayang Ruan
    TI__Guru 57255 points

    Jiayang,

    Where are you probing TMS on the HVMTRPFCKIT (when you are comparing it with the working board): at the schematic net 'TMS-ISO' or 'TMS'?  How about TDO, 'TDO-ISO' or 'TDO'?

    If you're probing 'TMS', can you try probing 'TMS-ISO'?  If you're probing 'TDO-ISO' can you try probing 'TDO'?


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 220 points

    Brett:

    Both sides were tested, and they looked the same, there are no triggering captured by  the oscilloscope.

    But maybe that doesn't mean the ISO7220c are still good, because there are no variations in the waveforms?

    Anyway I dont know how CCS tested the JTAG connection integrity, is it possible that the ISO7220c transmitting TDO failed,

    so that CCS cannot get the signals sent back by DSP, then next TMS is not changed by CCS?

    Am I expressing it clearly ? :)

    Jiayang

  • 0 in reply to Brett Larimore
    Prodigy 220 points

    Hi Brett:

      1.   I checked the waveforms again today, both external emulator and on-board emulator.

       2. Waveshapes look the same, in my view.

       3. When I check the TDO_ISO pin, there are two very tiny pulses, but they don't look like normal digital signals,

           cuz the low-level of the signal is not close to 0 V but to some level between 0V and 3.3V. 

     

    Jiayang

  • 0 in reply to Jiayang Ruan
    TI__Guru 57255 points

    Brett,

    From what you've said, I would suspect the ISO chips [M3]-U6 and [M3]-U8.  If you've been working with higher voltages than 400V, I might also replace C17 while I'm there.

    It could also potentially be [M3]-U1, but I don't believe so.


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Prodigy 220 points

    OK, I'll tried that,hope it works.

    Thanks for your patience!

  • 0 in reply to Brett Larimore
    Prodigy 220 points

    Hello Brett:

    1.  The connection sitll cannot be built.

    2. I've replaced [M3]-U5,[M3]-U6,[M3]-U8 and C17 with new ones, but JTAG test still failed.

    3. Maybe the DSP is destroyed, but the LED on the DSP is blinking, which means program is being run.

        Anyway, when I replaced the 28335 with a 28035( provided with the kit) , error still exsits, it's very small probability that both DSPs are destroyed, isn't it?  

    4. I think the vital clue is that only TDO and TMS signal are missing,what is the possible reason, please?

    Jiayang

  • 0 in reply to Brett Larimore
    Prodigy 220 points

    Brett:

    The problem is solved.

    I've taken the chip FT2232D off t the board, and then the external emulator can connect to DSP.

    I think the FT2232D is destroyed and though J5 is populated, its pins still affect the external emulator, so that 

    the external emulator cannot connect to DSP,neither.

    Jiayang