7.2.18 Register file: 0x10 – RX Frame Information Register
RX Frame Information - included in swinging set
Register map register file 0x10 gives information on the received frame. It is updated after the reception of
a good PHR, i.e. PHR where the SECDED has not flagged a non-correctable error (see section 10.4).
Register file: 0x10 – RX Frame Information Register is in the RX double-buffered swinging-set. See section
4.3 – Double Receive Buffer for more details.
Note: During double buffered operation, a receiver overrun condition results in the corruption of this
RX_FINFO register 0x10, please refer to section 4.3.3 Operation of double bufferingfor details of the
correct be handling of this condition.
This RX_FINFO register contains a number of fields, separately identified and described below:
REG:10:00 – RX_FINFO – RX Frame Information
The individual sub-fields are described below:
Description of fields within Register file: 0x10 – RX Frame Information Register
RXFLEN
reg:10:00
bits:6–0
Receive Frame Length. This value is copied from the PHR of the received frame when a good
PHR is detected (when the RXPHD status bit is set). The frame length from the PHR is used in
the receiver to know how much data to receive and decode, and where to find the FCS (CRC) to
validate the received data. The frame length also tells the host system how much data to read
from the RX_BUFFER. This field is 7-bits wide to accommodate the standard IEEE 802.15.4
UWB frames which can be up to 127 bytes long. The DW1000 also supports a non-standard
mode of operation with data frame lengths up to 1023 octets, where the frame length
reported is extended by the RXFLE field.
Receive Frame Length Extension. The DW1000 supports a non-standard mode of operation
with data frame lengths up to 1023 bytes. This mode of operation is enabled via the
PHR_MODE selection bits of Register file: 0x04 – System Configuration. In this long frame
mode RXFLE adds three high-order bits to RXFLEN extending it to 10-bits, and allowing frame
lengths from 0 up to 1023 bytes be reported. See also section 3.4 – Extended Length Data
Frames.
This value is updated when a good PHR is detected (when the RXPHD status bit is set).