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

MSP430I2020: Msp430Flasher - Problem with INFO segment memory during programming - MSP430i2020

Joao Carlos Chies
Prodigy 40 points
Part Number: MSP430I2020

Got into a bit of problem when using MSP430 Flasher to upgrade firmware in one of our products with the MSP430I2020 MCU.

When using the MSP430Flasher to upgrade firmware code, the INFO segment got erased and the factory calibration lost.
This only happens if we already had our own calibration data in the INFO segment. If only factory data was present on the INFO segment, it was properly preserved

Several different switches were used in the command line to attempt to prevent the issues but we were nothing worked.

Any information can be given to us about this issue?

  • 0
    Prodigy 40 points

    After intensive verification of the code and its interaction with Msp430Flasher, it was noticed that the tool executes an extra step, compared with CCS load function.

    This step resets the target one more time about 500ms after programming the unit and steady running our code. Since our code was already in its way to upgrade the system's calibrations, it would cause the read-erase-reprogram of the INFO segment to fail.

    Adding a 750ms delay on our code at power-up, which is ok for the product, will ensure we can use the Msp430Flasher to upgrade code in the future without fear of loosing the factory calibration.

    It would be nice to have a timing diagram on the Msp430Flasher documentation, showing the interaction of the tool with the reset of the processor and user code initialization.

  • 0 in reply to Joao Carlos Chies
    Guru 22765 points

    Writing your calibration data to another segment and leaving the factory calibration alone is the best plan.

    I can't imagine using so much of the information memory that I absolutely had to use the last little bit of the calibration segment.

  • 0 in reply to Joao Carlos Chies
    TI__Genius 16985 points

    Hi Joao,

    Oh, That is a good finding, I assume there should be some method to let the MSPFlasher not reset the device after firmware loading, but actually I am not familiar with it. Currently the delay operation is a good workaround.

    Thanks for feedback! Hope this thread can help other user with the usage.

    B.R.

    Sal

**Attention** This is a public forum