• State Resolved
  • Locked Locked
  • Replies 24 replies
  • Subscribers 82 subscribers
  • Views 5179 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.

(Error -1015 @ 0x0)

Filippo Cona
Intellectual 450 points
Other Parts Discussed in Thread: TMS320F28335

Hi,

I'm developing a SW for TMS320F28335 using the XDS100v2 JTAG.

Everything fine till the last time I tried to debug. Suddenly, I started getting the following error:

Error connecting to the target:
(Error -1015 @ 0x0)
Device is not responding to the request.  Device may be locked, or the emulator connection may be unreliable. Unlock the device if possible (e.g. use wait in reset mode, and power-cycle the board). If error persists, confirm configuration and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 5.1.232.0)

I also tried to test the connection and got the following message that I can't quite understand, but for sure the word "failed" appears too often...

[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:\Users\fcona\AppData\Local\.TI\693494126\
    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 'Aug 20 2013'.
The library build time was '22:56:19'.
The library package version is '5.1.232.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 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.
Test 1 Word 0: scanned out 0xFFFFFFFF and scanned in 0x035F3D89.
Scan tests: 1, skipped: 0, failed: 1
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.
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: 2
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 3
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 4
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 5
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 6
Some of the values were corrupted - 83.4 percent.

The JTAG DR Integrity scan-test has failed.

[End]

What might it be the problem?

I would have difficulties in obtaining both a second board and a second JTAG, so please consider these options only as last ratio.

Thanks in advance,

Filippo

  • 0
    Guru 192875 points
    Hi Filippo,

    This can be due to various issues. First of all I would like you to go through the troubleshooting wiki:
    processors.wiki.ti.com/.../XDS100

    Regards,
    Gautam
  • 0 in reply to Gautam Iyer
    Intellectual 450 points
    Thanks Gautam for your feedback!
    Today the debugger started on its own, just because I gave it another try...
    Not sure how long my good star will shine, thus I'll have a look to the wiki you linked and try to figure out why I had the issue, and in case I succeed I'll post what I find out.
    For now thanks and have a nice day!

    Filippo
  • 0 in reply to Filippo Cona
    Guru 192875 points
    Yes, sometimes restarting CCS or mcu does the trick too.

    Regards,
    Gautam
  • 0 in reply to Gautam Iyer
    Intellectual 450 points
    Broken again, this time with 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.1.232.0)...
  • 0 in reply to Filippo Cona
    Intellectual 450 points
    I read through the wiki, but couldn't find what the problem is.
    Any guess on what I may try to do to figure out the problem?
  • 0 in reply to Filippo Cona
    Guru 192875 points
    Supply issues can be a problem, sometimes changing USB cable works...
  • 0 in reply to Gautam Iyer
    Intellectual 450 points
    I tried that already with no success.
    Both cables do not work for debug and both work with other devices...
  • 0 in reply to Filippo Cona
    Guru 192875 points
    Monitoring the JTAG signals remain the only option now. Also, check the XRS pin status.
  • 0 in reply to Gautam Iyer
    Intellectual 450 points
    Can you please provide more detailed information on what I should monitor, what to expect and how I should interpret what I find?
    UPDATE: still once in a while I can debug but most of the times it doesn't work.

    Thank you
  • 0 in reply to Filippo Cona
    Guru 192875 points
    Do you feel this can be some connectivity issue... due to loose connections?
  • 0 in reply to Gautam Iyer
    Intellectual 450 points
    The fact that sometimes it works and it started having problems suddenyl without any significant change in SW or HW suggests that it maybe some kind of HW problem, e.g. loose connections as you say?
    However, the fact that it prefers to work after a restart (PC, CCS, board) from my point of view suggest more of a SW problem.

    I should point out that before starting having this problem I installed the driver for a USB-RS422 converter which happens to have a FTDI chip on it, just like the XDS100v2, however I already uninstalled/reinstalled the XDS driver and rebooted everything without solving the problem.

    Another point that may be related, but I'm not sure, is that the when the debugger works (even before this problem began) the program loading sometimes freezes. It doesn't happen too often but all and each time I have to kill CCS from task manager.
  • 0 in reply to Filippo Cona
    Guru 192875 points
    So would you prefer installing a fresh copy of CCS v6.1 ?
  • 0 in reply to Gautam Iyer
    Intellectual 450 points
    I took into consideration trying reinstalling CCS, but I'm not ready to do it right now because I'm quite in a hurry with the SW development. Before doing that I'd like to try with the laptop of a colleague of mine who is on vacation now.
    (On a side note, I have to use CCS v5.5 for project constraints)

    Back to the "monitoring of the JTAG signals" option, what can I do about that? Must I measure some voltages on the JTAG pins? Must it be done with JTAG connected? Board powered? While trying to debug? I really do not what should I do, so each piece of information is most welcome.

    Thank you again,

    Filippo
  • 0 in reply to Filippo Cona
    Guru 192875 points

    Filippo Cona said:
    Back to the "monitoring of the JTAG signals" option, what can I do about that? Must I measure some voltages on the JTAG pins? Must it be done with JTAG connected? Board powered? While trying to debug? I really do not what should I do, so each piece of information is most welcome.

    This doesn't make any sense now as you debugger works randomly. I went through your previous statements:

    I should point out that before starting having this problem I installed the driver for a USB-RS422 converter which happens to have a FTDI chip on it, just like the XDS100v2, however I already uninstalled/reinstalled the XDS driver and rebooted everything without solving the problem.

    Driver conflict.... I don't think so as the drivers have their own IDs for identification.

    Another point that may be related, but I'm not sure, is that the when the debugger works (even before this problem began) the program loading sometimes freezes. It doesn't happen too often but all and each time I have to kill CCS from task manager.

    This is a very serious issue...as if you disconnect the debugger while stuck in erasing the flash - you can brick your controller.

    Just to be clear, you checked on all your USB ports? They all perform in the similar way?


    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Intellectual 450 points
    Hi Gautam,
    first of all thanks again for your support!

    I tried two usb ports with similar results, actually as I said, the thing that I would like to try is even another computer... Probably in a not defined future my company may buy also another JTAG, but for now I must do with what I have...

    For the problem of the frozen program loading should I open a different thread or can I ask you here? It is something that I wanted to figure out too, but since it didn't completely stop my work and with the hope of the new JTAG to come I decided to overlook for now...
  • 0 in reply to Filippo Cona
    Guru 192875 points

    Filippo Cona said:
    For the problem of the frozen program loading should I open a different thread or can I ask you here? It is something that I wanted to figure out too, but since it didn't completely stop my work and with the hope of the new JTAG to come I decided to overlook for now...

    What I feel is, once your primary issue is resolved this will get resolved too. BTW Do you've a docking station?

    If yes, you can try using XDS100v2 embedded on it.

    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Intellectual 450 points
    No, I don't have one of those :(
  • 0 in reply to Filippo Cona
    Guru 192875 points

    Try a JTAG test connection that can be found in your .ccxml file under Target Configuration.

    www.youtube.com/watch?v=o_2iMqZ1EbU


    Regards,

    Gautam

  • 0 in reply to Gautam Iyer
    Intellectual 450 points
    I already tried the test connection, you can find the output in my first post.
    Or is it something different you're speaking of?
  • 0 in reply to Filippo Cona
    Guru 192875 points
    Filippo, yes went through it and that reports the JTAG connection to be broken (when it doesn't work).
    I'm out of ideas now :) But I would've liked to go through your hardware personally (if that was possible)
    Anyways, its all in your hands... Jtag connecting and disconnecting randomly can mean multiple things that we discussed previously.
    If you get to try it on another PC/laptop, just do it at first.

    Regards,
    Gautam
  • 0 in reply to Gautam Iyer
    Intellectual 450 points
    You've been far too kind in helping me through this.
    Fortunately, today the JTAG has decided to work (except for some frozen program loading).
    I Just hope to be able to work through the days that separate me from the new JTAG.
    In case I find out what's the issue or if I have new pieces of information I'll update the thread.

    For now thanks for the help!

    Regards,

    Filippo
  • 0 in reply to Filippo Cona
    Guru 192875 points
    Yup Filippo, keep us updated :)

    Regards,
    Gautam
  • 0 in reply to Gautam Iyer
    Intellectual 450 points
    Hi Gautam,
    I think I've found what the problem was.
    I noticed that when the JTAG worked, my power supply recorded a higher current absorption (like 10% more) wrt the times when the JTAG did not work.
    So I reviewed the whole power circuit of my board and re-soldered a few connections.
    I could do just a few tries, but since then the current absorption is stable and the JTAG works like a charm.
    It is likely then that the micro-controller was not powered properly and that can also justify, imho, the frozen program downloading (at least I hope).

    I verified your answer about "loose connections", (even if it seems that it was an issue of power rather than signal connections) since it seems to me that it was a very good guess.

    Thanks again for the great support!

    Filippo
  • 0 in reply to Filippo Cona
    Guru 192875 points
    Excellent Filippo, I'm happy you were able to find the root cause of the issue :)

    Goodluck & Regards,
    Gautam