slau358q.pdf - 第21页

www.ti.com Programming MSP Flash Devices Using the MSP Gang Programmer 21 SLAU358Q – September 2011 – Revised October 2019 Submit Documentation Feedback Copyright © 2011–2019, Texas Instruments Incorporated Operation NOT…

Programming MSP Flash Devices Using the MSP Gang Programmer

www.ti.com

SLAU358Q–September 2011–Revised October 2019

Submit Documentation Feedback

Operation

NOTE: This window displays the code addresses on the left side, data in hex format in the center column, and the

same data in ASCII format in the right column.

Figure 2-5. Flash Memory Data

2.1.2 Programming From Image

A programming configuration like the one created in Section 2.1.1 can be stored in the form of an image.

The advantage of an image is that it contains both the configuration options necessary for programming

as well as the code files that are flashed to target devices. Moreover, only images can be saved to internal

MSP Gang Programmer memory and used in Standalone mode, in which the programmer can operate

without being connected to a PC. Using the From Image mode allows the user to test images with full GUI

support before committing them to production.

When an image has been created, it can be used to greatly simplify programming by using the procedure

described in Section 2.1.9. Figure 2-6 shows the main dialog GUI where the From Image option is

selected for programming (top left corner). Here the user can load an image from MSP Gang Programmer

internal memory. An image can be created in Interactive Mode and saved to the programmer. One of 96

different images can be selected from internal memory, or one image from each external SD-Card can be

used.

www.ti.com

Programming MSP Flash Devices Using the MSP Gang Programmer

SLAU358Q–September 2011–Revised October 2019

Submit Documentation Feedback

Operation

NOTE: MSP Gang Programmer internal memory and SD-Card are mutually exclusive.

To avoid confusion during programming, connecting an SD-Card to the MSP Gang

Programmer disables its internal memory used for other images. Therefore, when an SD-

Card is connected to the programmer only the image on the SD-Card is usable or

accessible. If the SD-Card is empty, or contains a corrupted image, then it must be

disconnected before MSP Gang Programmer internal memory can be used.

NOTE: This figure shows the From Image Mode (see the Mode section near the top left corner). The user can

load an image from MSP Gang Programmer internal memory. Saved images contain all configuration

necessary for programming and all code files. An image can be created using the Interactive Mode and

saved to the programmer. One of 96 different images can be selected from internal memory, or one image

from each external SD-Card can be used.

Figure 2-6. Main MSP Gang Programmer Dialog GUI, From Image Mode

Programming MSP Flash Devices Using the MSP Gang Programmer

www.ti.com

SLAU358Q–September 2011–Revised October 2019

Submit Documentation Feedback

Operation

Figure 2-6 highlights several parts of the GUI. The drop-down menu in the Object in Image memory group

(top right) is used to select which image is used for programming, because up to 96 different images might

be available. In the same group, the Config. from Image option is enabled, meaning that all configurations

options, such as which devices are enabled or power options are being taken from the image.

Sometimes it is useful to use the basic files from an image, such as the MCU type and code files, but also

make a few minor modifications to test a different configuration. Figure 2-7 shows the additional

configuration options available when the Config. from Image button is disabled. These are high-lighted in

red and include which devices are enabled for programming, target V

and current, interface,

communication, and security. However, these changes cannot be committed to the image. If the user

wishes to change the current image's configuration or code files then the image needs to be recreated

using the original project file and procedure described in Section 2.1.9.