• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 78 subscribers
  • Views 61 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.

MSP430F249: Segment B Flash Memory Erasure Using MSP430-FLASHER on MSP430F249

Conor
Guru 10210 points
Part Number: MSP430F249
Other Parts Discussed in Thread: MSP430-FLASHER,

Tool/software:

Dear Support Team,

I am writing to seek your guidance regarding an issue with the MSP430-FLASHER tool when programming the MSP430F249 microcontroller. Below are the details of the situation:

Overview:
When programming the MSP430F249 using the MSP430-FLASHER tool with a HEX file created in Code Composer Studio (CCS), the data in Segment B of the flash memory (address range 0x1080–0x10BF) is unexpectedly erased, resulting in all data being set to 0xFF. Segment B contains preloaded data that should not be modified during programming. However, this erasure behavior does not occur when writing the same program directly using CCS.

Details:

  • Programming Tool: MSP430-FLASHER.
  • Programming Method: JTAG interface.
  • HEX File: Created using CCS and expected to write only to the ROM region.
  • Behavior Observed:
    • When using MSP430-FLASHER, Segment B's contents are erased (set to 0xFF).
    • When programming via CCS, Segment B's contents remain intact.

Questions:

  1. Does the MSP430-FLASHER tool perform a Mass Erase operation by default before writing the HEX file, which could include Segment B?
  2. Are there any specific settings or configurations within MSP430-FLASHER that can be used to prevent Segment B from being erased?
  3. Could this behavior be related to write protection settings or other memory-specific configurations for Segment B?
  4. What steps can be taken to ensure the preloaded data in Segment B is preserved during programming with MSP430-FLASHER?

Additional Information:

  • Segment B is being used to store critical preloaded data, so maintaining its integrity during programming is essential.
  • The HEX file being programmed does not include any addresses corresponding to Segment B.

We would appreciate your insights into the potential cause of this issue and any recommendations to resolve it. Please let us know if additional information or logs are required for further investigation.

Thanks,

Conor

  • +1
    TI__Guru 66521 points

    Hi Conor,

    According to the MSPFlasher user guide, there is one command to erase only MAIN (erase_main) and one command to erase MAIN + INFO (erase_all) excluding INFOA if protected.   Is there a reason you cannot locate the data you want preserved into INFOA instead?

**Attention** This is a public forum