1.2.21 Trigger EEPROM Secure Write

Description

The SPI command “Trigger EEPROM Secure Write” starts a write process from some SRAM data to EEPROM. The command checks for the following pattern:

0xAA 0xCC 0xF0

If this pattern is sent correctly, the variable triggerEEPwr is set to 0xEE. Within the “ATA_check4extRequests_C” function, this variable is checked and, in case of matching the 0xEE, the function “ATA_eepromSecureWrite_C” is called.

The data to write to the EEPROM is stored in the tmpAryApp. The first and second bytes of this array are the EEPROM address. The third byte is the length and from the fourth byte the data buffer is starting. The total size of the tmpAryApp is 10 bytes. This means that a maximum of seven data bytes are available for the secure EEPROM write.

Command Frame

Parameters

• 0x16 – Command ID
• 0xAA – First byte of trigger pattern
• 0xCC – Second byte of trigger pattern
• 0xF0 – Third byte of trigger pattern

Return Values

• events.system – Event byte (for details see SPI command ”Get Event Bytes”)
• events.events – Event byte (for details see SPI command “Get Event Bytes”)
• 0x00 – Dummy byte (no information)
• 0x00 – Dummy byte (no information)