slau358q.pdf - 第63页
63 SLAU358Q – September 2011 – Revised October 2019 Submit Documentation Feedback Copyright © 2011–2019, Texas Instruments Incorporated Firmware Chapter 3 SLAU358Q – September 2011 – Revised October 2019 Firmware 3.1 Com…
Benchmarks
www.ti.com
62
SLAU358Q–September 2011–Revised October 2019
Submit Documentation Feedback
Copyright © 2011–2019, Texas Instruments Incorporated
Operation
2.7.4 Benchmarks for MSP432P401R
(1)
Programming speed without startup procedures (access to target device).
Table 2-8. Benchmark Results – MSP432P401R, 256kB Code, Mode: From Image
(1)
Erase, Blank Check,
Program, and Verify
(s)
Verify
(s)
Programming Speed
(kB/s)
JTAG Fast 5.3 0.3 55.6
JTAG Med 13.0 0.8 21.5
JTAG Slow 27.0 1.2 10.5
SWD Fast 6.6 0.7 45.0
SWD Med 15.0 0.9 19.0
SWD Slow 32.0 1.5 9.0
(1)
Programming speed without startup procedures (access to target device).
Table 2-9. Benchmark Results – MSP432P401R, 256kB Code, Mode: Interactive, Communication by
USB
(1)
Erase, Blank Check,
Program, and Verify
(s)
Verify
(s)
Programming Speed
(kB/s)
JTAG Fast 8.0 0.3 36.0
JTAG Med 15.5 0.5 18.0
JTAG Slow 29.0 0.8 9.5
SWD Fast 8.9 0.3 31.0
SWD Med 17.7 0.5 16.0
SWD Slow 34.0 0.9 8.0
63
SLAU358Q–September 2011–Revised October 2019
Submit Documentation Feedback
Copyright © 2011–2019, Texas Instruments Incorporated
Firmware
Chapter 3
SLAU358Q– September 2011 –Revised October 2019
Firmware
3.1 Commands
The MSP-GANG can be controlled by firmware commands received through USB or its RS-232 serial
port. The following firmware commands are supported:
== Commands supported by the BOOT loader ======
• "Hello"
• Boot Commands Disable
• Boot Commands Enable
• Transmit Diagnostics
• Select Baud Rate
• Erase Firmware
• Load Firmware
• Exit Firmware update
• Get Label
• Get Progress Status
== Commands supported by API firmware ======
• Main process
• Interactive process
• Erase Image
• Read Info memory from MSP-GANG
• Write Info memory to MSP-GANG
• Verify Access Key
• Load Image Block
• Verify Image Checksum
• Read Image Header
• Boot update
• Read from Gang Data buffer
• Write to Gang Data buffer
• Disable API Interrupts
• Select Image
• Display Message on the LCD display
• Set temporary configuration
• Get selected status
• Self-test
Firmware Interface Protocol
www.ti.com
64
SLAU358Q–September 2011–Revised October 2019
Submit Documentation Feedback
Copyright © 2011–2019, Texas Instruments Incorporated
Firmware
3.2 Firmware Interface Protocol
The MSP Gang Programmer supports a UART communication protocol at baud rates from 9.6 to 115.2
kbaud in half duplex mode. The default baud rate at startup is 9.6 kbaud. This allows for communication
between the MSP Gang Programmer and devices that have a lower communication speed than the
maximum 115.2 kbaud. It is recommended that after startup the communication speed be increased to the
common maximum for both devices to enable faster communication. If the control device has a USB
interface with a virtual COM port, then it is recommended to use USB for communication between the
control device and the MSP Gang Programmer, because USB is several times faster than RS-232.
Communication requires one start bit, eight data bits, even parity bit, and one stop bit. A software
handshake is performed by a (not) acknowledge character.
3.3 Synchronization Sequence
To synchronize with the MSP-GANG Programmer the host serial handler transmits a SYNC (CR)
character (0x0D) to the MSP-GANG Programmer. The MSP-GANG Programmer acknowledges successful
reception of the SYNC character by responding with a DATA ACK character (0x90). If the SYNC is not
received correctly, no data is sent back. This sequence is required to establish the communication
channel and to react immediately to line faults. The synchronization character is not part of the data frame
described in Section 3.4.1. When communication is established, the synchronization character is not
required any more, but it can be send at any time for checking the "alive" status if required.
The synchronization character is not part of the data frame described in Section 3.4.1.
3.4 Command Messages
The MSP-GANG has a few type of messages with mandatory responses for each received command.
• Short TX messages with one byte only
"Hello"
Tx -> 0x0d (CR)
Rx -> 0x90 (ACK)
Get Progress Status
Tx -> 0xA5
Rx -> 0x80 0x00 <...data...> (without Check Sum)
• Standard TX messages with data frame
Tx -> 0xA5
Rx -> 0x80 0x00 <...data...> (without Check Sum)
3.4.1 Frame Structure
The data frame format follows the TI MSP serial standard protocol (SSP) rules, extended with a preceding
synchronization sequence (SS), as described in Section 3.3. The MSP Gang Programmer is considered
the receiver in Table 3-1, which details the data frame for firmware commands. The redundancy of some
parameters results from the adaptation of the SSP or to save boot ROM space.
The data frame format of the firmware commands is shown in Table 3-1.
• The first eight bytes (HDR through LH) are mandatory (– represents dummy data).
• Data bytes D1 to Dn are optional.
• Two bytes (CKL and CKH) for checksum are mandatory
• Acknowledge done by the MSP Gang Programmer is mandatory.