4 Synchronization Sequence
5 Commands
5.1 Unprotected Commands
5.2 Password Protected Commands
6 Programming Flow
Synchronization Sequence
Before sending any command to the BSL, a synchronization character (SYNC) with its value of 80h has to
be sent to the BSL. This character is necessary to calculate all the essential internal parameters, which
maintain UART and flash memory program/erase timings. It provides the BSL system time reference.
Once this is received, an acknowledge DATA_ACK = 90h is sent back by the BSL to confirm successful
reception.
This sequence must be done before every command that is sent to the BSL.
Note: The synchronization character is not part of the Data Frame described later.
Two categories of commands are available: commands that require a password and commands that do
not require a password. The password protection safeguards every command that potentially allows direct
or indirect data access.
• Receive password
• Mass erase (erase entire flash memory, main as well as information memory)
• Transmit BSL version (V1.60 or higher or in loadable BL_150S_14x.txt)
• Change baud rate (V1.60 or V1.61 or in loadable BL_150S_14x.txt)
• Receive data block to program flash memory, RAM, or peripherals
• Transmit data block
• Erase segment
• Erase check (V1.60 or higher or in loadable BL_150S_14x.txt)
• Set Memory Offset (V2.12)
• Load program counter and start user program
• Change baud rate (moved to a protected command starting with BSL version 2.01)
The write access (RX data block command) to the flash memory/RAM or peripheral modules area is
executed online. That means a data byte/word is processed immediately after receipt and the write cycle
is finished before a following byte/word has completely arrived. Therefore, the entire write time is
determined by the baud rate, and no buffering mechanism is necessary.
Data sections located below the flash memory area address are assumed to be loaded into the RAM or
peripheral module area and, thus, no specific flash control bits are affected.
Note: When losing control over the UART protocol, either by line faults or by violating the data
frame conventions, the only way to recover is to rerun the BSL entry sequence to initiate
another BSL session.
Features of the MSP430 Bootstrap Loader4 SLAA089D – December 1999 – Revised August 2006
Submit Documentation Feedback
To Next Page
Loading...
Need help?
General
