• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 127 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.

TM4C129ENCPDT: XDS110 erase error

Cristopher Pedano
Prodigy 102 points
Part Number: TM4C129ENCPDT
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hi,

I'm a SPEA firmware engineer and I'm trying to erase a board with the uC TM4C129ENCPDT on our customer board.

The board has been programmed with the customer programming file.

I'm using the XDS110 debugger with UNIFLASH software tool.

The UNIFLASH give me the error "DAP not accessible".

Is it possible the customer programming file lock the JTAG interface?

Is there some way to always unlock the TM4C129ENCPDT with the UNIFLASH?

Thank you,

Cristopher

  • 0
    TI__Guru**** 184346 points

    Hi,

      Please refer to  this app note  https://www.ti.com/lit/pdf/spma075 for how to debug JTAG issues and section 5.3 on how to unlock the device. You can use dbgjtag.exe to unlock Tiva device. See below. 

    “dbgjtag.exe –f @xds110 –Y unlock,mode=tiva”

  • 0 in reply to Charles Tsai
    Prodigy 102 points

    Hi,

    Unfortunately it didin't work.

    I have the same issue when i try to reconnect to the device after the power on cycle.

    Cmd execution:

    /resized-image/__size/320x240/__key/communityserver-discussions-components-files/908/cmc_5F00_execution.png

    UNIFLASH Error:

  • 0 in reply to Cristopher Pedano
    TI__Guru**** 184346 points

    Hi,

      Can you try the unlock command on a LaunchPad? This is to make sure the dbgjtag.exe is running fine. 

     How many custom boards do you have? Can you also try the unlock command on other boards you have? If all of them are having  the same problem when you try to connect then I think you have a hardware problem.

    Has the custom board have any firmware in it before the problem occurs? If there is already firmware in the device, do you remember what was in it? The device cannot be connected If the prior code puts the device is some type of low power mode (e.g. deep sleep or hibernate) where the clock is turned off to the device without a mechanism to wake up the device. Without clock, the device is unable to synchronize with the debug probe.

     I want to also give you a heads up. I'm currently OOO and my response will be very much delayed. 

  • 0 in reply to Charles Tsai
    Prodigy 102 points

    Hi,

    thank you for the feedback!

    I'll route your question to the customer and give you a feedback as soon I receive it!

    No problem about answers delayed!

    Regards,