Received ASH Ack
Sent ASH Ack
Timer expired waiting for ack
Received frame with bad ackNum
Received frame with illegal control byte
Received frame with CRC error
Received frame with illegal length for its type
Frame in progress cancelled
Received frame with comm error
ASH protocol connected
ASH protocol disconnected
Unexpected ncp reset
Invalid ncp processor type
Timed out waiting for RSTACK
Invalid ncp reset method
Exceeded max ACK timeouts
Incompatible ASH version
XON/XOFF not supported by host driver
Operation not yet complete.
Received ASH Nak
Sent ASH Nak
Fatal error detected by NCP.
Received frame out of sequence
Received ASH RST
Sent ASH RST
ASH RX
ASH protocol started
ASH Status
Received frame longer than maximum
Received frame shorter than minimum
ASH TX
Failed to connect to CPC daemon or failed to open CPC endpoint
Tried to send DATA frame too long.
Tried to send DATA frame too short.
The command has been filtered out by NCP.
The length of the command exceeded the maximum EZSP frame length.
Configuration values can no longer be modified.
The NCP received a command containing an unsupported frame ID.
The configuration id was not recognized.
The value was out of bounds.
The NCP failed to respond to a command.
Insufficient memory was available.
The overflow flag in the frame control field was set, indicating one or more callbacks occurred since the previous response and there was not enough memory available to report them to the Host.
The UART receive queue was full causing a callback response to be dropped.
EZSP Security Key is already set
EZSP Security Key is not set
EZSP Security Parameters are already set
EZSP Security Parameters are invalid
EZSP Security Parameters are not set
EZSP Security Type is invalid
Serial port initialization failed
The truncated flag in the frame control field was set, indicating there was not enough memory available to complete the response or that the response would have exceeded the maximum EZSP frame length.
Received frame is unsecure, when security is established
Received frame with unsupported control byte
The NCP received a command before the EZSP version had been set.
The direction flag in the frame control field was incorrect.
Fatal error detected by host.
No reset or error
No receive data available.
No space for rec'd DATA frame.
No space for tx'ed DATA frame.
Not in Connected state.
The Response frame of the current transaction indicates the previous transaction was aborted (nSSEL deasserted too soon).
The Host attempted to send an oversized Command (the length byte is too large) and the AVR's spi-protocol.c blocked the transmission.
The NCP attempted to send an oversized Response (the length byte is too large) and the AVR's spi-protocol.c blocked the reception.
Fatal error.
The NCP has not asserted nHOST_INT within the time limit defined by WAKE_HANDSHAKE_TIMEOUT.
The Response frame of the current transaction indicates the frame terminator is missing from the Command frame.
The Response frame of the current transaction indicates the NCP has reset.
The Response frame from the NCP is missing the frame terminator.
The NCP is reporting that the Command frame of the current transaction is oversized (the length byte is too large).
The Host attempted to verify the SPI Protocol activity and version number, and the verification failed.
The NCP has not asserted nHOST_INT after an NCP reset within the time limit defined by STARTUP_TIMEOUT.
The Host has sent a command with a SPI Byte that is unsupported by the current mode the NCP is operating in.
The NCP has not provided a Response within the time limit defined by WAIT_SECTION_TIMEOUT.
The Host has sent the Command and is still waiting for the NCP to send a Response.
Success.
Status values used by EZSP.