• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 79 subscribers
  • Views 1105 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.

MSP Flasher erasing InfoA Constants

Vikas Chola
Expert 5260 points

Other Parts Discussed in Thread: MSP430G2955, MSP430-FLASHER

Hello ,

One of my customers has used MSP Flasher + MSP-FET430UIF with MSP430G2995 in production. They have used below command for programming MSP430G2995:

MSP430Flasher.exe -n MSP430G2x55 -m SBW2 -w MSP430g2955.txt -v -z [VCC] > Status_write_1.txt

As per me, They should also provide option of -e(ERASE_ALL or ERASE_MAIN) but they missed it in their command. What they observed that it has erased MSP430G2995 INFO-A segment i.e. DCO and calibration constants. As per slau654a, erase default option is ERASE_ALL which erase only unlocked information segment with main memory so INFO-A shouldn't be erased as INFO-A is locked in this device.. As per me, If they are not providing option of -e then it should either work as default erase option or it shouldn't erase anything but it is erasing whole memory. Please advise on this.

Regards,

Vikas Chola

  • 0
    TI__Guru**** 223077 points

    Hello Vikas,

    What version of the MSP430-FLASHER is the customer using? It is possible that the ERASE_ALL command unlocks the INFOA segment so that it can be erased along with the main memory, however one would assume that this shouldn't happen unless the trigger -u is used. This is either a software bug or misinformation in the tool documentation, either way I am pulling in the MSP430-FLASHER owner to comment on the problem.

    Edit: The MSP430-FLASHER owner is ooo until Monday, August 29th.  I would recommend that the customer make sure to use the ERASE_MAIN trigger to avoid deleting information memory at the moment.

    Regards,
    Ryan

  • 0
    TI__Guru**** 223077 points
    Vikas,

    What is the status of this customer's problem? Response from the tool owner:

    "-e ERASE_ALL should definitely not erase INFOA unless –u is used as well. I tried to reproduce the issue with the latest MSP Flasher version, a UIF and an MSP430G2955 (assuming this is what the customer is actually using) – INFOA was not erased. I also tried to overwrite the INFOA section with the –w option without using –u and got a verification error as expected, the INFOA data was still there.

    Can we rule out that INFOA was erased before? Could the customer do a sanity check by writing something into INFOA before running the Flasher command? Also, can we be sure that the customer didn’t mix up the order of the INFO memory segments? For the G2955, INFOA is located at the end of the INFO block (0x10c0 – 0x1100)."

    Regards.
    Ryan
  • 0 in reply to Ryan Brown1
    TI__Expert 5260 points
    Hello Ryan,
    Thanks for information. I will check with customer on the same and if required will respond to you offline on mail with cutomer information.

    Regards,
    Vikas Chola

**Attention** This is a public forum