MSP430F6733: challenging The MSPBoot application report (slaa600a)

Part Number:MSP430F6733

Hello

We consider a bootloader implementation based on the MSPBoot slaa600a application report, in one of our MSP430F6733 based products.

One of our senior engineers was challenging the boot force mechanism (option 2)

It says in the report:

“

2.2.1.1 Force Bootloader Mode

Even with a valid application, bootloader mode can be forced by these options:

• Option 1: " .....  "

• Option 2: An application calls execution of bootloader mode. The variables StatCtrl and PassWd are reserved and shared between application and bootloader. To force bootloader mode, the application sets these variables to:

PassWd = 0xC0DE

StatCtrl.BIT0 = 1

“

But the shared variables (PassWd and StatCtrl) are written to RAM have a random value after reset, so:

1. Does those words retain their values after reset (how a ram retain its value after reset)?

2. When powering the device the shared variables  have a random value, so it is possible that

PassWd = 0xC0DE

StatCtrl.BIT0 = 1

And than we have an unexpected bootloader behavior.

How it is prevented?

Does anyone has experienced such problems?

Thanks