• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 81 subscribers
  • Views 3741 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Erase information problem, when BSL procedure...Please Help me...

Kyung Seok Yoon
Prodigy 100 points
Other Parts Discussed in Thread: MSP430F449, MSP430F2330, MSP430F2132

Hi, everyone...

I want to download program to MSP430F2330 by BSL. So, I make BSL code for MSP430F449, then I tested, and confirm worked well.

But one problem is occured.

When I sent incorrect password to MSP430F2330, then all of Main and information flash of MSP430F2330 are erased. but I have to use calibration data in inframation memory.

So, I found the method of protecting information memory in the "MSP430 Memory Programming User's Guide : SLAU265D"

In page of 19, I can see the "Note" as below.

BSL versions V2.01 and higher support automatic clearing of the LOCKA bit protecting
information flash memory. When the BSL is entered from a reset condition, LOCKA is
cleared by the BSL to mass erase the flash, including information memory. When the BSL is
entered in-application, user software should take care that LOCKA is written as 1 prior to
initiating the BSL. Otherwise, information flash will not be erased during a BSL mass erase.

But, I don't understand how can I set the LOCKA bit in MSP430F2330 by BSL....

Please...Let me know how can I set the LOCKA bit...

Thank you.

  • 0
    TI__Guru 65377 points

    In order that you can get full access to the device you need to provide the BSL password. Since you can only access the LOCKA bit once you have full access to the device (iow, you already unlocked it), you can’t use this method to “pre-toggle” the LOCKA bit to prevent the erasure of your INFOA memory containing the calibration constants. However if you do have the password, you should be able to toggle the LOCKA bit after unlocking the BSL, and then issue a mass-erase command without INFOA getting affected, or use the segment erase feature. It may seem to be a serious restriction; however it has been designed like this to allow maximum protection of customers’ IP. Otherwise, anybody could just come in and read out INFOA (including any custom data that might be stored there).

     

    Note that there also is a feature that prevents the BSL from doing the automatic mass-erase when a wrong password is supplied, at the cost of a lower level of security (see description of the BSLSKEY memory location in the device datasheet). This would allow you multiple tries to get access the device. However you would still need the right password to get in and do any re-programming.

     

    Thanks and Regards,
    Andreas

  • 0 in reply to Andreas Dannenberg
    Intellectual 345 points

    I am trying to find an example code (in C) to set the BSLSKEY to 0x0000, and assume I need to define a segment of 2 bytes at 0xFFDE to hold this value.

    Can anyone stear me to an example which will work in CCS?

    thanks, Dan

  • 0 in reply to Daniel Staver
    Intellectual 345 points

    Found an answer, to how to easily set the BSLSKEY to a value, in C, without having to mess with adding a linker command,
    since section .int15 is already defined:

    Direct method:

    _Pragma("DATA_SECTION(bslskey,\".int15\")")
    const unsigned int bslskey = 0x0000;  // set location 0xFFDE to 0x0000 to prevent bulk erase if bad bsl password used.

    Indirect method using macros if you can use for multiple places (with minor changes to allow different target section):

    #define EMIT_PRAGMA(x) _Pragma(#x)
    #define BSLSKEY(var) EMIT_PRAGMA(DATA_SECTION(var,".int15"))
    BSLSKEY(bslskey)
    const unsigned int bslskey = 0x0000;  // set location 0xFFDE to 0x0000 to prevent bulk erase if bad bsl password used.

  • 0 in reply to Andreas Dannenberg
    Expert 1530 points

    Andreas Dannenberg said:
     
    Note that there also is a feature that prevents the BSL from doing the automatic mass-erase when a wrong password is supplied, at the cost of a lower level of security (see description of the BSLSKEY memory location in the device datasheet). This would allow you multiple tries to get access the device. However you would still need the right password to get in and do any re-programming.
     

    Is this available on Rom-Based BSL parts?

    Can someone help point me to this feature? I am unable to find it on the device datasheet of the part I am using.

     

    Thanks

  • 0 in reply to Jamie Maxwell
    TI__Genius 10830 points

    Jmax604 said:

    Can someone help point me to this feature? I am unable to find it on the device datasheet of the part I am using.

    What part are you using?  The BSLSKEY is the flash data word located beneath the interrupt vector table addresses (e.g., for the MSP430F2132, address 0xFFDE).

  • 0 in reply to Jason Work
    Expert 1530 points

    I misunderstood the description in the datasheet.

    I get it now. If the BSLSKEY is set to 0x0000, the erase feature is disabled, not the password protect feature......

    Thanks for hitting me over the head with it :)

     

**Attention** This is a public forum