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

Extra byte read from BSL interface on startup (MSP430F5438A)

Pak Woon
Prodigy 105 points
Other Parts Discussed in Thread: MSP430F5438A

Hello Forum,

I am looking for confirmation of what I've found during BSL programming of a MSP430F5438A device. We are using mspdebug to field upgrade our devices with the standard connection command (mspdebug -d /dev/ttyUSB1 flash-bsl) to connect to the micro. According to the source code, on connection, the application performs a 'mass erase' followed by an 'unlock'. Using mspdebug from sourceforge and a MSP430F5438A, we have noticed that the first response from the device is 00 00 80 02 00 3B .... This causes mspdebug to fail since it does not expect an extra 00. The rest of the response message is correct. As a work around, we added an additional read at device open from the 'serial' port to remove the first 00 byte.

Note, this only happens for the first command. The 'unlock' returns the proper sequence.

Has anyone else observed this behavior?

Regards,

Pak

  • 0
    Guru 25210 points

    I'm not an expert on mspdebug tool, but in general flushing a serial port on open would seem like a good idea before initiating any part of a communications protocol.

    Just my 2-cents.

**Attention** This is a public forum