slau358q.pdf - 第35页

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

Programming MSP Flash Devices Using the MSP Gang Programmer

www.ti.com

SLAU358Q–September 2011–Revised October 2019

Submit Documentation Feedback

Operation

2.1.5.1 Writing and Reading BSL Flash Sectors in the MSP430F5xx and MSP430F6xx MCUs

The MSP430F5xx and MSP430F6xx microcontrollers have BSL firmware saved in flash memory sectors.

By default, access to these sectors (Read or Write) is blocked, however it is possible to modify the BSL

firmware if required, which allows the user to upload newer or custom defined BSL firmware. These BSL

sectors are located in memory starting at 0x1000 to 0x17FF. The MSP Gang Programmer software

handles modification of these BSL flash sectors using the same method as all other memory sectors.

However, to avoid unintentional erasing of BSL sectors, the most commonly used memory option, All

Memory , blocks access to these BSL sectors. Access to BSL sectors is unlocked only when the Used by

Code File or User defined option is selected and desired selected BSL sectors are enabled, as shown in

Figure 2-12. Contents of BSL sectors can be read even when the All Memory option is selected.

NOTE: The user can select which segments of memory are written to or read from. The selected configuration

shows how the user can configure the programmer to overwrite segments of memory used by the Bootloader

(BSL).

Figure 2-12. Memory Options, BSL Sectors Selected

www.ti.com

Programming MSP Flash Devices Using the MSP Gang Programmer

SLAU358Q–September 2011–Revised October 2019

Submit Documentation Feedback

Operation

2.1.6 Secure Device Setup and Memory Protection

The MSP430 family has an option to block access to the MCU through the JTAG and SBW interface. To

select the Secure Device option, press the Secure Device Option button on the GUI or select the option

from the pulldown menu under Setup→Secure Device. Figure 2-13 shows the Secure Device Options

window. When the Secure Device option is selected, the device is secured at the end of the GO

programming procedure if all programming steps pass successfully. Otherwise, the device is not secured.

For MSP430 devices, the Secure Device process is not reversible.

NOTE: Irreversible unless password option used. Can be done automatically after programming (at end of GO

operation)

Figure 2-13. MSP430 Secure Device Options

In some MCUs, typically the FRAM family, a lower JTAG and SBW protection level is available. The JTAG

and SBW can be protected by password that is saved in the MCU flash at the addresses 0xFF80 through

0xFFFF. If the password in the code file at this address is the same as the password saved inside the

flash, then access to JTAG and SBW is unlocked, and flash can be reprogrammed. This is useful for

updating firmware after initial programming.

However, if the device is secured using the Secure Device procedure, then unlocking by using this

password is no longer possible. The Secure Device mechanism provides a higher level of protection.

The MSP432 family implements a different approach to memory protection. The MSP432 can provide

protection for selected memory regions or to block communication. All protection options are described in

the MSP432 technical reference manual and are implemented by programming the flash mailbox (see the

MSP432P4xx Family Technical Reference Manual (SLAU356) for details). The MSP-GANG can program

the flash mailbox according to user settings or directly from a code file. When the Secure Device Option

button is selected for the MSP432 family, the Secure Device Options screen is displayed (see Figure 2-

14).

Programming MSP Flash Devices Using the MSP Gang Programmer

www.ti.com

SLAU358Q–September 2011–Revised October 2019

Submit Documentation Feedback

Operation

NOTE: The flash mailbox can be programmed to provide memory protection of some memory, or communication

can be blocked. Can be done automatically after programming (at end of GO operation)

Figure 2-14. MSP432 Secure Device Options