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.

MSP432E401Y: REGARDING PASSWORD SET AND WRITE PROTECTION TO EEPROM

Part Number: MSP432E401Y

Hi all ,

We are using MSP432E401Y microcontroller in our project . And for Password set and Write protection for EEPROM ,we are refering "MSP432E4 DriverLib API Guide: Eeprom_api (ti.com)" this document .

Needed clarification's are:

1. Once the password is set and the type of protection is set  using the API , will it be permanent even if the MC restarts.

2. I am also doing the Mass Erase using the API (after the EEPROM initialization) and I am getting the return status as 0(means erase successfull) , but even after doing this , if I do   

EEPROMBlockProtectGet()           

the return status is 0 means 

#define  EEPROM_PROT_RW_LRO_URW   0x00000000

SO then how to resolve this?

Regards,

HARSHA

 

  • 1. Once the password is set and the type of protection is set  using the API , will it be permanent even if the MC restarts.

    Yes, it will be permanent. 

    7.2.4.1.3 Locking and Passwords
    The EEPROM can be locked at both the module level and the block level. The lock is controlled by a
    password that is stored in the EEPROM Password (EEPASSn) registers and can be any 32-bit to 96-bit
    value other than all 1s. Block 0 is the master block, the password for block 0 protects the control registers
    as well as all other blocks. Each block can be further protected with a password for that block.
    If a password is registered for block 0, then the whole module is locked at reset. As a result, the
    EEBLOCK register cannot be changed from 0 until block 0 is unlocked.

    2. I am also doing the Mass Erase using the API (after the EEPROM initialization) and I am getting the return status as 0(means erase successfull)

    If you do a mass-erase of EEprom the EEprom is restored to its factory setting which is no protection. 

    but even after doing this , if I do   

    EEPROMBlockProtectGet()           

    the return status is 0 means

    7.2.4.1.4 Protection and Access Control
    The PROT protection field in the EEPROM Protection (EEPROT) register provides discrete control of read
    and write access for each block which allows various protection models per block. The protection
    configurations allowed are as follows:
    • PROT = 0x0
    – Without password: Readable and writable at any time. This mode is the default when there is no
    password.
    – With password: Readable, but only writable when unlocked by the password. This mode is the
    default when there is a password.

  • Thank you Charles , got the clarification . It would be better if there will be example under this , so that everyone could understand easily.