The generic "no error" message.

The generic "fatal error" message.

An invalid value was passed as an argument to a function.

The manufacturing and stack token format in non-volatile memory is different than what the stack expects (returned at initialization).

The API call is not allowed given the current state of the stack.

The manufacturing token format in non-volatile memory is different than what the stack expects (returned at initialization).

The stack token format in non-volatile memory is different than what the stack expects (returned at initialization).

There are no more buffers.

Specified an invalid baud rate.

Specified an invalid serial port.

Tried to send too much data.

There was not enough space to store a received character and the character was dropped.

Detected a UART framing error.

Detected a UART parity error.

There is no received data to process.

The receive interrupt was not handled in time, and a character was dropped.

No pending data exists for device doing a data poll.

The frequency hopping client failed the frequency hopping synchronization procedure, it timed out trying to reach the frequency hopping server.

The frequency hopping client failed the frequency hopping synchronization procedure, the server is currently using a different seed.

MAC security operation failed.

Transmission failed: the destination node does not appear in the neighbor or child tables.

Transmission failed: the local node does not support security or a secured transmission has been requested to a child that does not support security.

The MAC transmit queue is full.

MAC ACK header received.

The MAC can't complete this task because it is scanning.

The requested operation cannot be completed because the MAC is currently busy performing some high priority task.

We expected to receive an ACK following the transmission, but the MAC level ACK was never received.

Indirect data message timed out before polled.

Transmission failed: the indirect message was purged because the destination child has been removed or updated.

The Simulated EEPROM is telling the application that there is at least one flash page to be erased. The 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.

The Simulated EEPROM is telling the application that there is at least one flash page to be erased. The 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.

The 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.

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.

The Simulated EEPROM is repairing itself.

While there's nothing for an app to do when the SimEE is going to repair itself (SimEE has to be fully functional for the rest of the system to work), alert the application to the fact that repairing is occurring. There are debugging scenarios where an app might want to know that repairing is happening; such as monitoring frequency.

Note

Common situations will trigger an expected repair, such as using an erased chip or changing token definitions.

A fatal error has occurred while trying to write data to the Flash. The target memory attempting to be programmed is already programmed. The flash write routines were asked to flip a bit from a 0 to 1, which is physically impossible and the write was therefore inhibited. The data in the flash cannot be trusted after this error.

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.

A fatal error has occurred while trying to write data to the flash, possibly due to write protection or an invalid address. 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.

A fatal error has occurred while trying to erase flash, possibly due to write protection. 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.

The bootloader received an invalid message (failed attempt to go into bootloader).

Bootloader received an invalid message (failed attempt to go into bootloader).

The bootloader cannot complete the bootload operation because either an image was not found or the image exceeded memory bounds.

The message to be transmitted is too big to fit into a single over-the-air packet.

Conversion is complete.

Conversion cannot be done because a request is being processed.

Conversion is deferred until the current request has been processed.

No results are pending.

Sleeping (for a duration) has been abnormally interrupted and exited prematurely.

The transmit hardware buffer underflowed.

The transmit hardware did not finish transmitting a packet.

An unsupported channel setting was specified.

An unsupported power setting was specified.

The requested operation cannot be completed because the radio is currently busy, either transmitting a packet or performing calibration.

The transmit attempt failed because all CCA attempts indicated that the channel was busy.

The expected ACK was received after the last transmission.

The stack software has completed initialization and is ready to send and receive packets over the air.

The network is not operating.

The node failed to initiate the scanning process during the joining process.

An attempt to join a network failed.

An attempt to join a network was rejected.

The node timed out waiting for a response during the joining process.

An attempt to join or rejoin the network failed because no valid beacons could be heard by the joining node.

The security data provided was not valid, or an integrity check failed.

The node has not joined a network.

An index was passed into the function that was larger than the valid range.

There are no empty entries left in the table.

The requested function cannot be executed because the library that contains the necessary functionality is not present.

The stack accepted the command and is currently processing the request. The results will be returned via an appropriate handler.

NVM3 is telling the application that the initialization was aborted as no valid NVM3 page was found.

NVM3 is telling the application that the initialization was aborted as the NVM3 instance was already opened with other parameters.

NVM3 is telling the application that the initialization was aborted as the NVM3 instance is not aligned properly in memory.

NVM3 is telling the application that the initialization was aborted as the size of the NVM3 instance is too small.

NVM3 is telling the application that the initialization was aborted as the NVM3 page size is not supported.

NVM3 is telling the application that there was an error initializing some of the tokens.

NVM3 is telling the application there has been an error when attempting to upgrade SimEE tokens.

NVM3 is telling the application that there has been an unknown error.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.

This error is reserved for customer application use. This will never be returned from any portion of the network stack or HAL.