EmberZNet serial protocol
SN260
Table 30. EmberStatus (continued)
Structure
EMBER_SIM_EEPROM_ERASE_PAGE_GREEN
EMBER_SIM_EEPROM_ERASE_PAGE_RED
EMBER_SIM_EEPROM_FULL
EMBER_SIM_EEPROM_FLASH_WRITE_
FAILED
EMBER_SIM_EEPROM_INIT_1_FAILED
EMBER_SIM_EEPROM_INIT_2_FAILED
EMBER_SIM_EEPROM_INIT_3_FAILED
EMBER_ERR_TOKEN_UNKNOWN
EMBER_ERR_TOKEN_EXISTS
EMBER_ERR_TOKEN_INVALID_SIZE
EMBER_ERR_TOKEN_READ_ONLY
EMBER_ERR_BOOTLOADER_TRAP_
TABLE_BAD
Field
0x43
0x44
0x45
0x46
0x47
0x48
0x49
0x4B
0x4C
0x4D
0x4E
0x58
Description
Simulated EEPROM is telling the application that there is
at least one flash page to be erased. GREEN status
means the current page has not filled above the
ERASE_CRITICAL_THRESHOLD. The application should
call the function halSimEepromErasePage() when it
can to erase a page.
Simulated EEPROM is telling the application that there is
at least one flash page to be erased. RED status means
the current page has filled above the
ERASE_CRITICAL_THRESHOLD. Due to the shrinking
availability of write space, there is a danger of data loss.
The application must call the function
halSimEepromErasePage() as soon as possible to
erase a page.
Simulated EEPROM has run out of room to write any
new data and the data trying to be set has been lost.
This error code is the result of ignoring the
SIM_EEPROM_ERASE_PAGE_RED error code. The
application must call the function
halSimEepromErasePage() to make room for any
further calls to set a token.
A fatal error has occurred while trying to write data to the
Flash and the write verification has failed. The data in
the flash cannot be trusted after this error, and it is
possible this error is the result of exceeding the life
cycles of the flash.
Attempt 1 to initialize the simulated EEPROM has failed.
This failure means the information already stored in
Flash (or a lack thereof), is fatally incompatible with the
token information compiled into the code image being
run.
Attempt 2 to initialize the simulated EEPROM has failed.
This failure means Attempt 1 failed, and the token
system failed to properly reload default tokens and reset
the simulated EEPROM.
Attempt 3 to initialize the simulated EEPROM has failed.
This failure means one or both of the tokens
TOKEN_MFG_NVDATA_VERSION or
TOKEN_STACK_NVDATA_VERSION were incorrect and
the token system failed to properly reload default tokens
and reset the simulated EEPROM.
An unknown flash token was specified.
Could not create new flash token because it already
exists.
An incorrect size was specified when retrieving token
data.
Couldn't write token because it is marked read-only.
Bootloader received an invalid message (failed attempt
to go into bootloader).
46/88