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.

BSL security on the MSP430F67xx

Other Parts Discussed in Thread: MSP430F67451

I've been through the docs specific to MSP430F67451, and the family guide, The latest revised BSL programming guide, and the errata sheets, three times and I can't find any way to set the BSL to do erase flash on a bad password. Is there such a thing? I found reference to a "BSLSKEY" in some  MSP430F5xx series parts. I found the SYSBSLPE bit in the SYSBSLC register but only a bootstrap loader that set this bit on startup will help anyway, as I can't set it in my code since that won't run on a BSL startup. I also don't know if the MSP430f67xx parts are immune to the 'ACK latency on bad password means of hacking via the BSL'? 

Please help, I know this info must be somewhere, but where, and how, and why?

  • Hello Richard,

    Unless disabled by the user, the default BSL supplied by TI will have this feature on by default on F5xxx and F6xxx devices. That is to say, if the wrong password is supplied while accessing the BSL, a mass erase will be initiated and erase all code flash, but not Information Memory. This is described under the RX Password command description found in found in section 3.5.2 Command Descriptions in the application note, MSP430 Programming Via the Bootstrap Loader (BSL) .

    From what I am familiar with, the 'ACK latency on bad password means of hacking' is only really valid if multiple attempts are made on the password. In the default case, this would not work for all of code flash will be erased and the BSL password reset to all 0xFF's. If one where to turn off this feature, you can customize the BSL to add delays before responding to an "ACK" to avoid this.

    Hope this helps!

    Regards,
    JH

  • If that's correct then I have my answer, and it's a perfect one because I have to do anything!

    Yes, the validity of your first paragraph makes the question of ACK irrelevant.

    I missed the operative part in section 3.5.2 of SLAU319i because I thought it only applied to USB and not serial BSL, fooled by the previous page that was all about USB. Great help, thanks!

    Thanks