• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 83 subscribers
  • Views 2289 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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 connecting to the target: (Error -1135 @ 0x0)

evs
Genius 5910 points
Other Parts Discussed in Thread: TMS320F28069M

I bricked my TMS320F28069M again. and I'm in a (hopeless) attempt  to solve this because this is getting expensive and not really robust.

 It came from a working situation. In other words: yesterday it did worked. and for as I know I didn't got a error message.

When I want to program the controller with CCS. I got in an endless loop, with the following error message:

C28xx: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.83.0)
C28xx: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.83.0)
C28xx: Error connecting to the target: (Error -1135 @ 0x0) The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation. (Emulation package 6.0.83.0)
wtc

I verified that the JTAG programmer is working with the  new target configuration file option.

I checked the following:

 I  updated the power supply to a 0.5A switching one.In the datasheet is specified that it needs 120mA to program the memory. So that more would more then enough.

The oscillator is running at 20Mhz.

The internal power supply is stable at 1.9V

 At  XRSn very  13ms I got a 50us negative pulse, This is odd. XRSn is only connected with a 2.2k resistor to VCC. So the processor is stuck in a reset loop.

So how do I prevent this from happening again. If it is pretty easy to brick the device. This can get very expansive if I have to replace customers products.

How do I solve this? Al I found so far. was just the basic stuff like power-cycle the device.

 

Hope someone can help.

 

  • 0
    TI__Guru**** 169894 points
    Hi,

    The error and some related discussions are mentioned in section 5.16 of the page below:
    processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

    We here at the CCS forum are not the most experienced in either bullet-proofing the flash programming procedure or the HW during programming. In this case, for more educated suggestions I will move this post to the C2000 forum.

    Regards,
    Rafael
  • 0 in reply to desouza
    TI__Guru 57255 points

    Hi,

    Is this happening on a custom board or a TI kit?  If it is a custom board, have you taken a look at the controlCARD schematics to see if there are any major differences - especially with respect to XRSn and JTAG.  If possible, could you send across a few snapshots of the MCU portion of your board - especially the emulator section?
    (since you keep seeing this pop up, perhaps there is a design marginality)

    Another recommendation is to make sure that CCS is up-to-date, if it isn't.

    When you are unable to connect, can you change the boot-mode to SCI-boot-mode?  Then see if you can connect.


    Thank you,
    Brett

  • 0 in reply to Brett Larimore
    Genius 5910 points

    Hi,

    It is a custom board and I used the controlcard design as reference. Because I didn't find a hardware design guide document. I know how to make a decent  PCB I made some before.  The main difference with the controlcard are: I used a 4 layer print and I split the controller and  JTAG interface, But I''m way below the maximal 15cm jtag cable distance. 

     Replacing the controller solve the problem. I really think it is a real short coming that it is possible to brick the controller when there is a problem with flashing the device. But please tell me the requirements for robust flash programming!!!!! 

    I think that there is a power surge  in the controller when flash is programmed that dips the power supply why the controller is bricked. But I can't  find any information for that in the datasheet So I tried to catch it with the scope. I already upgraded my power supply to a bigger one.   Also I added a isolated power supply to my Tjag programmer (150mA). If I only use this power supply to program the controller. The controller gets bricked. So I think I need more than 120mA to program the device then the datasheet specifies  (p 38, see also note 2).

    It only happens when I flash my real big program that use most of the peripherals and also the CLA. I didn't have the problem with small programs (jet).

    And yes, I used decent components,  real short power traces and a robust ground and power plane.

     Thanks

     

  • 0 in reply to evs
    Guru 192875 points
    Hi EVS,

    Your power supply is the issue! You need min. of 300mA Power supply to be designed for F28069M. I always prefer for a 1A supply to as to fulfil my other digital circuitry needs.
    Specially when you flash, the datasheet mentions 120mA as the required current but in actual scenario you need far more than that. Yes, if the current limit is less than that required for your flash erase ; it will be locked forever and hence the device will get bricked!

    Regards,
    Gautam
  • 0 in reply to Gautam Iyer
    Genius 5910 points

    Gautam, Thanks for sharing your experience.
    I spend way to much time on such issues. And the shortage of good technical information makes me very frustrated.

  • 0 in reply to evs
    Guru 192875 points

    evs said:
    Gautam, Thanks for sharing your experience.

    No Problem!

    evs said:
    I spend way to much time on such issues. And the shortage of good technical information makes me very frustrated.

    Simply post your question on this forum if you're unable to find the relevant data in the available documents.

    Regards,

    Gautam