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.

MSP430 Flasher v1.3.1 Bug

Other Parts Discussed in Thread: MSP430FG4618

In MSP430 Flasher v1.3.1, when reading memory and saving as Intel HEX, there is a bug in the way Extended Segment Address (0x02) records are created. For this record type, the data must be saved as big endian, but it is saved as little endian. This creates a problem because it appears that the write function interprets the data for this record type correctly, as big endian, so a read followed by a write of a segment that generates an Extended Segment Address record will result in a failed write. The write succeeds if I change the record data to big endian. I tested this with the MAIN segment of an MSP430FG4618.

**Attention** This is a public forum