• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 31 subscribers
  • Views 374 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.

TM4C1230E6PM: error connecting target

micou ludovic
Expert 1235 points

Part Number: TM4C1230E6PM

Hello,

 use a TM4C1230E6PM microphone. I was able to program the microphone. After a test to find out what voltage my system is starting, I have the microcontroller that no longer works. I tried to reprogram the mic, but I can’t reprogram anymore.I use the XDS110 to programm. I have this message : Error connecting to the target: (Error -1170 @ 0x0) Unable to access the DAP. 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 9.6.0.00172)

In the CCS, I use the Target configuration. I have this core detected: .

When I read the Memory browser at 0xC0000000, I have only the ???? in the data.

Why is my microcontroller in this state and how to unlock it?

Best Regards,

L.Micou

  • 0
    TI__Guru**** 191886 points

    Hi,

    micou ludovic said:
    When I read the Memory browser at 0xC0000000, I have only the ???? in the data.

      You just said you cannot connect the device. If that is the case, the debugger cannot read out anything from the device. 

      I have a few questions and comments. 

      - Was the device working before you do the voltage test? Were you able to program and debug the device a couple of times before? Or the device stop working after you do some voltage test? 

      - If you program the device the first time and immediately you cannot connect and debug the device by the debugger then do you remember what program did you program to the device? If your program somehow disables the clocks to put the device in some type of sleep mode (e.g. deep sleep or hibernate) without a means to wake up then the device can no longer sync with the debugger as it has no clock. Or if you have repurposed the JTAG pins for GPIO functionality. In this case, the debugger can no longer access the device because there is no JTAG interface to connect to. Normally you can unlock the device if the problem is due to the software issue. You can unlock the device by following section 5.3.2 in this app note. https://www.ti.com/lit/pdf/spma075. If this is not true, then please continue with the below questions. 

      - Are you able to use your XDS110 to debug another good known device/board? This is to rule out any issue with the debug probe. 

      - If you can use XDS110 to debug another board then it means the first board either has a board issue or a MCU issue. To isolate if it is a board or MCU problem, you will need to do a ABA swap test. Swap a known good device to the problem board. If you can connect and program the device then the board is good. The problem is with the MCU. However, do you recall if you might accidently short something like the MCU I/O pins while you were doing the test. 

  • 0
    Expert 1235 points

    Hi,

    The device working before the test. and I can program and debug before the test. the device stopped after a only test. I can program and debug when I have already Programmed a device. 

    I don't use the deep, sleep or hibernate.The GPIO for the SWM isn't reprogrammed.

    the XDS110 is operate with the other device.

    how to do the ABA swap test?

    I don't short ccircuit when I test. I use connectors only when I have tested the device.

  • 0 in reply to micou ludovic
    TI__Guru**** 191886 points
    micou ludovic said:

    The device working before the test. and I can program and debug before the test. the device stopped after a only test. I can program and debug when I have already Programmed a device. 

    I don't use the deep, sleep or hibernate.The GPIO for the SWM isn't reprogrammed.

    the XDS110 is operate with the other device.

    Thanks for the information. 

    Can you do a unlock operation as mentioned in the app note? Can you recover the device then?

    micou ludovic said:
    how to do the ABA swap test?

    If unlock operation does not recover the problem then you need to isolate if it is a hardware issue.  

    Please read this article about ABA swap test. Your hardware engineer/technician will be able to perform such task. 

    https://forum.digikey.com/t/part-failure-vertification-a-b-a-swap-method/701

  • 0 in reply to Charles Tsai
    TI__Guru**** 191886 points

    Hi Micou,

      I have not heard back from you. I suppose the issue with error connecting to the target is resolved. I will close this thread for now. You can update this post if there is any update and the thread will automatically reopen again.