• State
  • Locked Locked
  • Replies 15 replies
  • Subscribers 82 subscribers
  • Views 5587 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.

DIY XDS100V2 error debugging

Olovskos
Intellectual 420 points
Other Parts Discussed in Thread: TMS320F28027, TMS320F28062, TMDSEMU110-U

Hello,

I didn`t want to build my XDS100V2 emulator from scratch or with the files provided so I thought I would be super smart, if I cut a launchxl f28027 behind the XDS100V2 debugger and solder my own connector.

Now when I try to debug a device with my selfmade debugger, It flashes the code to the flash and I can debug a short time but after some time the debugger reports error -1135 and I cant debug anymore...

Whats the problem?

Maybe someone can help :)

Thanks

EDIT
The connection between debugger and F28027 is about 20cm, is that the problem?

EDIT 2 

No the length of the cable is not the problem :/

  • 0
    Guru 192875 points
    Hi,

    What is that you're debugging? Is it a live motor drive application or power system? or Is it just the controlCard ?

    Regards,
    Gautam
  • 0 in reply to Gautam Iyer
    Intellectual 420 points
    It is just a TMS320F28027PTT on a pcb. Just with the minimal circuit. I tied The Boot Pins to vcc, except "trst" but since i use an emulator, the boot Pins should be "don't cares". I had 3 launchxl boards attached to the PC, Could this be a Problem? I already Set the tablet settings of ccs7 to use the emulator by serial number.
  • 0 in reply to Olovskos
    Guru 192875 points

    Olovskos said:
    I had 3 launchxl boards attached to the PC, Could this be a Problem?

    This should not be a problem. 20cm cable length worries me though. Can you try reducing?

  • 0 in reply to Gautam Iyer
    Intellectual 420 points
    See my first post the "EDIT 2" I already shortened the cable to 5cm but it makes no difference...
    The complete eror message is as follows:

    "C28xx: Error: (Error -1135 @ 0x3F0536) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.576.0)
    C28xx: Unable to determine target status after 20 attempts
    C28xx: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging"

    The wierd thing is, that as long as I am setting breakpoints and jump through the code, change some values etc everything is fine. As soon as I leave the debugger running alone for some time I get the error message above...
  • 0 in reply to Olovskos
    Guru 192875 points

    Apart from loose connections I don't think there can be any other issue for such an issue.

  • 0 in reply to Gautam Iyer
    Intellectual 420 points
    I really don't know... I checked and resoldered everything 3 times :/
    I will investigate and reply if I found out what is happening.

    Which emulator/debugger would you recommend to buy? I only want to debug C2000 DSPs (TMS320F28027, TMS320F28062 etc.)
  • 0 in reply to Olovskos
    Guru 192875 points

    Olovskos said:
    Which emulator/debugger would you recommend to buy? I only want to debug C2000 DSPs (TMS320F28027, TMS320F28062 etc.)

    XDS110 (TMDSEMU110-U) which is now recommended over XDS100v2.

  • 0 in reply to Gautam Iyer
    Intellectual 420 points

    I got the XDS100v2 Emulator running. There was a cold solder joint becuase our guys populated the boards by hand and did a poor solder job on the DSP :/ now everything is working fine with the "self-made" debugger BUT,

    we also bought 2 XDS110 Debugger and now have problems to get those running. The boards that should be debugged are the same as before. Debugging in general is working but not with the XDS110. I have connected: NTRST, TDI, TDO, TMS, TCK from the debug port and from the aux Port: TGTSUPPLYOUT and GND

    I selected "Probe supply Power" with 3.3 in the the target configs in CCSv7.

    When trying to debug the chip I get error 267 - The controller could not detect valid target supply.

    On the osciloscope I can see that TGTSUPPLYOUT is pulled to 3.3V for a short time but it stops with the error above.

    Any suggestions?

    EDIT

    Get the same error when powering the target from external supply... device has power all connections correct, triplle checked

  • 0 in reply to Olovskos
    Intellectual 420 points
    Also I can`t set the serial number of the xds110 debuggers...

    Error DFU_ERR_UNKNOWN (-4) reported while setting serial number

    What is this and how to solve?
  • 0 in reply to Olovskos
    Guru 192875 points
    Hi,

    I'm not sure about these errors. Lets wait for the TIers to jump in here.

    Regards,
    Gautam
  • 0 in reply to Gautam Iyer
    Intellectual 420 points

    I searched the web and it looks like that we are not the only ones that have this problems setting the serial number but there is no solution out there or rather none that is working for us....

  • 0 in reply to Olovskos
    TI__Guru 57255 points

    Hi Olovskos,

    Could you create a diagram showing your physical connections between the xds110 & your C2000 device?  This will likely help us remotely debug.

    If the 'self'-made xds100v2 is working, but the xds110 isn't - I suspect the hacked xds100v2 you are using may have some circuitry that really should be near the chip.

    Specifically, I'm wondering if your main board has the pullup & pulldown resistors described in the figure "Emulator Connection without Signal Buffering for the MCU" inside the datasheet:
    http://www.ti.com/lit/gpn/tms320f28027


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Intellectual 420 points

    Hello,

    sorry that I didn`t write earlier, much work to do...

    In the picture you see my schematics of the board. I have to say, that I do not have the EMU0/EMU1 pins connected to VDDIO through a 4.7-kΩ resistor.

    Is this causing the failure?

  • 0 in reply to Olovskos
    TI__Guru 57255 points

    Hi Olovskos,

    I wouldn't suspect the lack of EMU0/EMU1 pull-ups would cause what you are seeing, but it is feasible.  If you can try adding them to your setup, that should enable us to figure out whether this is the issue (and pretty quickly).

    Outside of trying to add these EMU0/1 pull-ups, I don't see anything obviously wrong with your connections. 

    I only have three other thoughts (none of which are likely all that helpful):
    1) Consider double-checking the connection between connector X8 and your emulator.
    2) If your board is custom, I might check how well X8 is soldered down.  I suspect X8 may be a relatively small SMT connector.
    3) Double-check that R49 was populated with a 2.2K ohm resistor.


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Intellectual 420 points

    So, it is working now. 

    The Problem was, that on the AUX Port is the "TGTVDD(Sense)" Pin, and this Pin has to be connected to VDD (in my case I bridged it to TGTSUPPLYOUT)

    The debug Probe was not able to detect the Target Voltage. The XDS100v2 doesn`t check this, so this was working perfectly before.

    I think this step schould be mentioned in the XDS110 Datasheet/Wiki/Manual