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

TM4C1292NCPDT: Unable to perform Unlock Sequence Using Uniflash and XDS Debug Probes

Kiranjit Kaur
Intellectual 395 points
Part Number: TM4C1292NCPDT
Other Parts Discussed in Thread: UNIFLASH

Hello,

I am facing issue to perform unlock sequence on my custom PCB board.

Please refer below image for errors.

Please share your comments on it.

Thanks,

Kiran

  • 0
    Intellectual 395 points

    Hi,

    It seems that debug probe connection was not proper. Now, I'm able to perform the unlock operation. 

    But still, I'm unable to restore my MAC address to the factory settings. My MAC address is currently 00-00-00-00-00-00 but I want to bring it change it from this value or restore it to factory mode value, i.e., FF-FF-FF-FF-FF-FF. I'm referring to spma075.pdf for performing the unlock steps using command prompt, i.e., www.ti.com/.../spma075

    Could you please suggest why is it not getting restored to factory mode value, is there anything in the schematic that we need to check for this issue? It is our prototype board.

    Best Regards,

    Kiran

  • 0
    TI__Guru**** 190826 points

    Hi Kiran,

      Your image show you are using Uniflash v3.4. This is a fairly old version. Can you try a newer version? Normally, I use the dbgjtag.exe from CCS. For example, if you have CCS12 installed, you can find in C:\ti\ccs1200\ccs\ccs_base\common\uscif\dbgjtag.exe. 

     One note of caution, dbjtag.exe will not guarantee to unlock in all circumstances. If there is a hardware issue then it will not work. It also depends on what state the processor was in for the program it was running. I have seen circumstances where dbjtag.exe cannot work for reasons such that the processor was continuously in a reset event or others. Refer to your device specific datasheet and look for the below subsection that talks about unlocking the device. Basically, dbgjtag.exe is following the sequence described in the datasheet. 

  • 0 in reply to Charles Tsai
    Intellectual 395 points

    Hi Charles,

    Thanks for your response.

    As per datasheet:

    How can i send below mentioned point using programming? Please advise!!

    Thanks,

    Kiran

  • 0 in reply to Kiranjit Kaur
    TI__Guru**** 190826 points

    Hi Kiran,

      That is how dbgjtag.exe will produce when you invoke it. dbgjtag.exe will instruct your debug probe (.e.g. XDS200 or LM flash programmer) to create these sequence on TCK and TMS signals. There is no need for you to create this on your own unless you must to. For example, if you don't have a debug probe like XDS200/XDS100/ICDI and if you need to unlock the device, you will create the described signal waveforms on your own. You could possibly use two GPIO pins on a 2nd device and connect these two GPIO pins to the TCK  and TMS inputs of the target device (the device that needs to be unlocked) in a bit-bang method. 

      What was in the flash prior to you not able to unlock the device? I remember in another post I supported you, you were eventually able to unlock the device with MAC changing to all F's. 

  • 0 in reply to Charles Tsai
    Intellectual 395 points

    Hi Charles,

    Yes I was able to unlock in one custom board but unable to perform the unlock procedure on another custom board. 

    That is why I asked could it be a hardware problem?

    Charles Tsai said:
    What was in the flash prior to you not able to unlock the device?

    The MAC address before performing the unlock procedure was 00-00-00-00-00-00

    Best Regards,

    Kiran

  • 0 in reply to Kiranjit Kaur
    Intellectual 395 points

    Tried the unlock in newer version of CCS, i.e., ccs1210. Following was the result.

  • 0 in reply to Kiranjit Kaur
    TI__Guru**** 190826 points

    In your screenshot you have the command wrong. It is not @xds=200. It should be @xds200

  • 0 in reply to Charles Tsai
    Intellectual 395 points

    Corrected the command and this didn't unlock successfully too. MAC address is still 00-00-00-00-00-00.

  • 0 in reply to Kiranjit Kaur
    TI__Guru**** 190826 points

    Why don't you first try on another custom board that you said was working before? Need to rule out any toolchain issue. If it works for the other custom board but not your current custom board then there is something wrong your your current custom board. You can compare the TCK and TMS waveforms between each other. Having said, I don't think you can do much even if you find the waveform differences between them. If unlock operation doesn't unlock the device then I don't really see a method to erase the MAC address. The only way to erase MAC is via unlock.