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

TM4C129XNCZAD: Uniflash user register write error

Peter Borenstein
Mastermind 8695 points
Part Number: TM4C129XNCZAD
Other Parts Discussed in Thread: UNIFLASH, EK-TM4C1294XL

In UniFlash, the fields for user register 0 and 1 both program user register 1. The MAC address field can program the whole thing, which would be a nice workaround if the mac address was easy to re-program. The only method I know to erase the mac address is using dbgjtag:

/ti/ccsv7/ccs_base/common/uscif/dbgjtag.exe -f @xds100v2 -Y unlock,mode=tiva

  • 0
    TI__Guru*** 135355 points
    Hello Peter,

    I seem to be finding even worse behavior than you describe as in my attempts to re-create the issue on the EK-TM4C1294XL LaunchPad using version 4.2.0 of Uniflash. I am not even able to write the correct values to Register 1. Did you observe the same?

    In any event, I'll have to reach out to the Uniflash team to see what is going on there.

    In the meantime, I tested LM Flash Programmer and that worked fine for me, so see if that will work for you in the interim.
  • 0 in reply to Ralph Jacobi
    Mastermind 8695 points

    Thanks for passing the word along.

    I think this is a memory type that can only write 1s to 0s which works for me. In user reg 1, I can go from 0xff to 0x55 but not then back to 0xff.

  • 0 in reply to Peter Borenstein
    TI__Guru*** 135355 points

    Hi Peter,

    We've confirmed the issue is on the Uniflash side, so it will be looked into and get fixed for a future release. Not sure when that will be yet (too early to tell) though. In the meantime, the LM Flash Programmer is still good old reliable if needed in a pinch. Thanks for reporting this, we probably wouldn't have noticed for a while if you hadn't...

  • 0 in reply to Ralph Jacobi
    TI__Guru**** 171004 points
    Hi,

    The bug number CCBT-2207 was filed. In about 1 hour you can check its status in the link SDOWP in my signature below.

    I apologize for the inconvenience,
    Rafael