• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 79 subscribers
  • Views 326 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

MSP430FR2353: BSL via Uart , Gangprogrammer not taking in account set password

Colombo Carlo
Mastermind 24620 points
Part Number: MSP430FR2353


Hi everyboyd , 

I m using gangprogrammer  and BSL via Uart . everything is fine .

Now I must have password set to protect my code . I enabled  BSL with password and disabled mass erase .

now  I set a password , OK .  but in Gangprogrammer if a set a new password  I can enter  in any case the device memory  , it looks like the gang is ignoiring the password .   

as I understodd  password shoudl be in the inetrrupt vector table  ( address 0xFFE0 e 0xFFFF )  in attach you can see memory in the cases   .

it looks gang jumpsHere are gang programmer settings.doc no matter  worng password .

please where am I wrong  ?  what should I test /check ?

eragrds

Carlo

  • 0
    TI__Genius 17960 points
    Hi Carlo,
    based on your description I assume the following is happening in the background.
    When setting the BSL password, you're activating the access protection by password. This means, any access attempt to the MSP430 device via BSL communication, with a wrong password, automatically triggers the mass erase by the BSL.
    The Gangprogrammer is utilizing this functionality for loading a new password and code, by transmitting a wrong password intentionally. This erases the device including the interrupt vector table. This way the password is known again and the device can be re-flashed. Doing so, the IP is also protected, as it has been erased and thus not readable anymore. On the re-flashing of the device, of course also the new password/ interrupt vector table is being applied.

    I hope this answers your question.

    Best regards
    Peter
  • 0 in reply to Peter Spevak
    TI__Mastermind 24620 points
    Hi Peter ,
    thank you for your superfast reply .
    in my code I disabled mass erase in BSL using this
    const unsigned long bsl_lock @ 0xFF84=0xAAAAAAAA; // enable BSL with Password protection and disable mass erase on wrongPassword
    #pragma required=bsl_lock

    how coudl the mass eras by Gang Happen ? any idea/suggestion where am I wrong ?
    best regards
    Carlo
  • 0 in reply to Colombo Carlo
    TI__Mastermind 24620 points
    Hi Peter ,
    we did some extra test . it seems memory is protected with previous setting on a READ ( so if you try to read wth wrong password , no reading and no mass erase ) .
    while if you do a write it seems you can erase and have a mass erase , at least this is what we see .
    where are we wrong ?
    thakn you
    regards
    Carlo
  • 0 in reply to Colombo Carlo
    TI__Genius 17960 points
    Hi Carlo,
    if not disabling the BSL completely, it is not possible to protect the FRAM against write access. The IP is protected, as it cannot be read out, and would be erased or overwritten by the respective activities, but the overwrite can only be prevented by disabling the BSL access completely.

    Another option for the IP protection in the sense of overwrite protection would be the use of a customized BSL in FRAM, where any desired behavior and protection could be implemented.

    Best regards
    Peter

**Attention** This is a public forum