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.

MSP430F5359: Does the F5xxx BSL (Bootloader) have the "Enhanced Security Feature" of the MSP430F2618?

Part Number: MSP430F5359
Other Parts Discussed in Thread: MSP430F2618

Background: We currently use the MSP430F2618 and are transitioning to the MSP430F5359.

In SLAU319AB (July 2010–Revised October 2019), the MSP430™ Flash Devices Bootloader (BSL) User's Guide, the 2xx family is described as having an "Enhanced Security Feature" whereby if you set Flash memory address 0xFFDE to 0xAA55, the BSL will hang upon entry, making it impossible to use the BS to access the chip. Here's the text from the User's Guide:

In our MSP430F2618 implementation, we currently take advantage of this feature to secure our code against inspection or modification via the TI Bootloader (BSL). But in the MSP430F5359, this feature doesn't seem to exist.

Is that the case; the feature doesn't exist?

Instead, to assure that it is impossible to enter the TI BSL (Bootloader), should we erase the Bootloader area (0x01000–0x017FF) of the Flash?

Atlant

  • Without knowing BSL password (vector table) mass erase will be triggered. F5xx BSL is stored in 2KByte flash memory, so it can be modified. It can also be erased (I checked this, and SBW with erased BSL is working fine), but in the case of JTAG fuse lock (fuse value is stored at the end of BSL flash segments) and erased BSL, device is bricked.

  • zrno:

    Thanks for your reply!

    So I take it that "No, the '2618 enhance security feature (and mass-erase control) isn't supported".

    > but in the case of JTAG fuse lock (fuse value is stored at the end of BSL flash segments) and erased BSL, device is bricked.

    Yes, we understand that. ;-)

    Thanks again!

    Atlant

**Attention** This is a public forum