AT86RF212 Atmel Corporation, AT86RF212 Datasheet - Page 51

• Manufacturer Part Number: AT86RF212
• Manufacturer: Atmel Corporation

Specifications of AT86RF212

• Max. Operating Frequency: 0 MHz
• Crypto Engine: AES
• Operating Voltage (vcc): 1.8 to 3.6
• Frequency Band: 700/800/900MHz
• Max Data Rate (mb/s): 1
• Antenna Diversity: No
• External Pa Control: Yes
• Power Output (dbm): 10
• Receiver Sensitivity (dbm): -110
• Receive Current Consumption (ma): 9.0
• Transmit Current Consumption (ma): 18 at 5dBm
• Link Budget (dbm): 120

5.2.3.3 Configuration of Non IEEE Compliant Scenarios
8168C-MCU Wireless-02/10
Table 5-11. Configuration of Promiscuous Mode
To signal the availability of frame data, an IRQ_3 (TRX_END) is issued, even if the FCS
is invalid. Thus, it is necessary to read register bit RX_CRC_VALID (register 0x06,
PHY_RSSI) after IRQ_3 (TRX_END) in order to verify the reception of a frame with a
valid FCS. Alternatively, bit 7 of byte RX_STATUS can be evaluated, refer to section
4.3.2.
If a device, operating in promiscuous mode, received a frame with a valid FCS that
furthermore passed the third level of filtering (according to IEEE 802.15.4-2006, section
7.5.6.2), an acknowledgement (ACK) frame would be transmitted. But, according to the
definition of the promiscuous mode, a received frame shall not be acknowledged, even
if requested. Thus, register bit AACK_DIS_ACK (register 0x2E, CSMA_SEED_1) must
be set to 1 to disable ACK generation.
In all receive modes, interrupt IRQ_5 (AMI) is issued if the received frame matches the
node’s address according to the filter rules described in section 6.2.
Promiscuous mode could also be implemented using state RX_ON (Basic Operating
Mode), refer to section 5.1. However, the RX_AACK transaction additionally enables
extended functionality like automatic acknowledgement and non-destructive frame
filtering.
Reserved Frame Types
In RX_AACK mode, frames with reserved frame types (refer to section 6.1.2.2, Table 6-
2) can also be handled. This might be required when implementing proprietary, non-
standard compliant protocols. The reception of reserved frame types is an extension of
the AT86RF212 Frame Filter, see section 6.2. Received frames are either handled like
data frames, or may be allowed to completely bypass the Frame Filter. The flow chart in
Figure 5-9 shows the corresponding state machine.
In addition to Table 5-9 or Table 5-10, the following Table 5-12 shows RX_AACK
configuration registers required to setup a node to receive reserved frame types.
Table 5-12. RX_AACK Configuration to Receive Reserved Frame Types
0x20,0x21
0x22,0x23
Register
Address
Register
Address
0x2B
0x2E
0x24
0x17
0x17
0x17
…
Register
Register
Bit
Bit
1
4
4
5
Name
SHORT_ADDR_0/1
PAN_ADDR_0/1
IEEE_ADDR_0
…
IEEE_ADDR_7
AACK_PROM_MODE
AACK_DIS_ACK
Name
AACK_UPLD_RES_FT
AACK_FLTR_RES_FT
Description
Each address shall be set to 0x00
1: Enable promiscuous mode
1: Disable acknowledgment generation
Description
1: Enable reserved frame type reception
Filter reserved frame types like data frame
type
0: Disable
1: Enable
AT86RF212
51