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.

C6726 + BH510L result Error -1060

Other Parts Discussed in Thread: TPS62420

I have the board with C6726 processor. It worked properly. But programmer destroyed power supply. I repaired power supply. But debuger don't works. I get this error

Error connecting to the target:
(Error -1060 @ 0x0)
Device is not responding to the request. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 5.0.471.0)

I start test of connection and get such log

[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 board config pathname(s)]------------------------------------

C:\Users\685F~1\AppData\Local\.TI\213602635\
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 'bhemujscl.dll'.
The library build date was 'May 30 2012'.
The library build time was '22:52:27'.
The library package version is '5.0.747.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 '10' (0x0000000a).
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 of an unknown type.
The link from controller to target is direct (without cable).
The controller has a logic ONE on its EMU[0] input pin.
The controller has a logic ONE on its EMU[1] input pin.
The controller will use rising-edge 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]----------

Test Size Coord MHz Flag Result Description
~~~~ ~~~~ ~~~~~~~ ~~~~~~~~ ~~~~ ~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~
1 none - 01 00 500.0kHz - similar isit internal clock
2 none - 01 09 570.3kHz - similar isit internal clock
3 512 - 01 00 500.0kHz O good value measure path length
4 128 - 01 00 500.0kHz O good value auto step initial
5 128 - 01 0D 601.6kHz O good value auto step delta
6 128 - 01 1C 718.8kHz O good value auto step delta
7 128 - 01 2E 859.4kHz O good value auto step delta
8 128 + 00 02 1.031MHz O good value auto step delta
9 128 + 00 0F 1.234MHz O good value auto step delta
10 128 + 00 1F 1.484MHz O good value auto step delta
11 128 + 00 32 1.781MHz O good value auto step delta
12 128 + 01 04 2.125MHz O good value auto step delta
13 128 + 01 11 2.531MHz O good value auto step delta
14 128 + 01 21 3.031MHz O good value auto step delta
15 128 + 01 34 3.625MHz O good value auto step delta
16 128 + 02 05 4.313MHz O good value auto step delta
17 128 + 02 13 5.188MHz O good value auto step delta
18 128 + 02 23 6.188MHz O good value auto step delta
19 128 + 02 37 7.438MHz O good value auto step delta
20 128 + 03 07 8.875MHz O good value auto step delta
21 128 + 03 15 10.63MHz O good value auto step delta
22 128 + 03 1E 11.75MHz {O} good value auto step delta
23 512 + 02 3E 7.875MHz O good value auto power initial
24 512 + 03 0E 9.750MHz O good value auto power delta
25 512 + 03 16 10.75MHz O good value auto power delta
26 512 + 03 1A 11.25MHz O good value auto power delta
27 512 + 03 1C 11.50MHz O good value auto power delta
28 512 + 03 1D 11.63MHz O good value auto power delta
29 512 + 03 1D 11.63MHz O good value auto power delta
30 512 + 03 13 10.38MHz {O} good value auto margin initial

The first internal/external clock test resuts are:
The expect frequency was 500000Hz.
The actual frequency was 500000Hz.
The delta frequency was 0Hz.

The second internal/external clock test resuts are:
The expect frequency was 570312Hz.
The actual frequency was 568500Hz.
The delta frequency was 1812Hz.

In the scan-path tests:
The test length was 16384 bits.
The JTAG IR length was 54 bits.
The JTAG DR length was 2 bits.

The IR/DR scan-path tests used 30 frequencies.
The IR/DR scan-path tests used 500.0kHz as the initial frequency.
The IR/DR scan-path tests used 11.75MHz as the highest frequency.
The IR/DR scan-path tests used 10.38MHz as the final frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

The frequency of the JTAG TCLKR input is measured as 10.00MHz.

The frequency of the JTAG TCLKR input and TCLKO output signals are similar.
The target system likely uses the TCLKO output from the emulator PLL.

-----[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 54 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]

What I can to do?

  • Constantine,

    The Test Connection portion looks like all the connection is working okay, so the problem is more on the logical connection part, getting CCS to interact with the emulation logic inside the DSP.

    You will want to do all the things that are highlighted in yellow. Shut down CCS, remove power from your board, unplug JTAG from the board, remove power from the JTAG controller (if not embedded on the board), re-apply power to the JTAG controller, re-plug JTAG to the board, re-apply power to the board, start CCS, and try to Launch the Target Configuration and then Connect to the DSP.

    Please let us know how this helps, or not.

    Regards,
    RandyP

  • I tried to change frequency settings for emulator, tried to repower, reset or other operations on the board and BH510L. The situation remains the same.

    This error (-1060) appears after some times after start debugger. Oscilloscope shows many informations on TDI, TDO and TCK pins.

  • Constantine,

    The sequence I gave you is not a list of things to try one or the other, but my recommendation of the sequence of all of these to try to recover from this problem. Please try following all of these, in order, and see if the situation remains the same:

    1. shut down CCS
    2. remove power from your board
    3. unplug JTAG from the board
    4. remove power from the JTAG controller (if not embedded on the board)
    5. re-apply power to the JTAG controller
    6. re-plug JTAG to the board
    7. re-apply power to the board
    8. start CCS
    9. Launch the Target Configuration
    10. Connect to the DSP

    Constantine Musatoff said:
    This error (-1060) appears after some times after start debugger.

    Does this also mean that some times the error does not appear and the emulation works as expected?

    Regards,
    RandyP

  • I executed all steps as above and error remains. 

    I tried to restart and reset JTAG and board in any consequence and error remains.

    When board and JTAG workes normaly, debugger cursor appeared after 1-2 seconds after start. 

    Now CCS freezes on about 10 seconds, after what error appears on screen. All this time JTAG and DSP makes communication in both directions

  • In addition. I deinstall CCS 5.2 and install actual version of CCS 5.3. The error remains.

    I made reconfiguration project with F28069 from X100 to BH510L. This project I can  debug by 510L without any errors. I attached 510L into board with 6726 and the error appear.

    Is any log files of comunication of BH510L with borad or CCS with BH510L ? 

  • Constantine,

    Do you have another board to try? Since you had a power supply problem on the board, it is always possible that the DSP was damaged or other components on the board were damaged at that time.

    When the lock-up occurs, without doing anything such as power cycling or reset, can you try the Test Connection and find that it works? Or does it fail in that case?

    Do any of the resets help? In CCS there are several resets, for emulator and device or system. Sometimes these will help.

    You may need to debug on the board, looking at the JTAG signals to see if they match the levels expected in the datasheet and Hardware Designers Resource Guide.

    The easiest would be to try another board, if you have one.

    Did the emulation work without these problems before the problem with the power supply? Is it possible the power supply is not completely repaired? Have you inspected all power connections to make sure they are good at the beginning and when the problem occurs?

    Regards,
    RandyP

  • I have two boards, but one here and second in far town at programmer.

    About possibility of SDP damage. Yes, it is may be. Is method to understand that DSP is damaged or I did not finish repairment of board?

    If I start test connection, result is OK - green strings in the firest post. 

    I check TRST signal by oscilloscope while try to debug. There are one or several resets in the beginning of the process.

    All JTAG signals have normal levels: 0 - about 0 volts and 1 about 3.3 volts.

    Power supply made on TPS62420 and output voltages are 1.205 and 3.306 volts. There are no ripples on supply voltages.

    Second board, that is in other town, works normally. First board worked normally before damage. Buy and replace DSP chip is hard process and I try to understand - is it single decision or I did not finish repairment.

  • Constantine,

    It is not possible for me to make that judgement for you. Only you can know all the tradeoffs between the different possible problems on your board and how the power supply failed and what might have happened on the board during that failure.

    If one board works with the emulator setup and another board does not, then at least you know the emulator setup is correct.

    You can continue looking for other problems, but this will require a difficult engineering effort on your part to monitor everything and try to correlate everything to the point in time when the DSP fails.

    I think we have established that your emulation setup works.

    Regards,
    RandyP

  • Thank you, RandyP!

    I think that it is require to change DSP chip on the board.