Internal byte counter in packet handler counts from
Length field transmitted and received
Rx and Tx PKTLEN value set to mod
Infinite packet length enabled
Packet Filtering in Receive Mode
filtering: address filtering, maximum
length filtering and CRC filtering.
value than zero enables the packet address
The packet handler engine will compare
the destination address byte in the packet with
the programmed node address in the
register and the 0x00 broadcast address when
0xFF broadcast addresses when
address matches a valid address, the packet is
received and written into the RX FIFO. If the
address match fails, the packet is discarded
ve mode restarted (regardless of the
If the received address matches a valid
address when using infinite
address filtering is enabled, 0xFF
will be written into the RX FIFO follow
address byte and then the payload data.
In variable packet length mode,
If the received length byte has a larger
value than this, the packet is discarded and
receive mode restarted (regardless of the
The filtering of a packet when CRC
auto flush function will flush the
FIFO if the CRC check fails. After auto flushing
the RX FIFO, the next state depends on the
for the CRC auto flush function to work
When using the auto flush function, the
maximum packet length is 63 bytes in variable
packet length mode and 64 bytes in fixed
length mode. Note that the maximum
allowed packet length is reduced by two bytes
enabled, to make room in the RX FIFO for the
two status bytes appended at the end of the
when the CRC check fails, the previously
received packet must be read out of the FIFO
before receiving the current packet. The MCU
must not read from the current packet until the
CRC has been checked as OK.
rent CRC implementations.
2 options. The CRC check is different for the 2
To Next Page
Loading...
Need help?
General
