
22
8111C–MCU Wireless–09/09
AT86RF231
Figure 6-10. Example SPI Sequence - Frame Buffer Write of a Frame with 4 byte PSDU
Access violations during a Frame Buffer read or write access are indicated by interrupt IRQ_6
Notes
The Frame Buffer is shared between RX and TX; therefore, the frame data are overwritten by
new incoming frames. If the TX frame data are to be retransmitted, it must be ensured that no
frame was received in the meanwhile.
To avoid overwriting during receive Dynamic Frame Buffer Protection can be enabled, refer to
It is not possible to retransmit received frames without a Frame Buffer read and write access
cycle.
For exceptions, e.g. receiving acknowledgement frames in Extended Operating Mode
6.2.3
SRAM Access Mode
The SRAM access mode allows accessing dedicated bytes within the Frame Buffer. This may
reduce the SPI traffic.
The SRAM access mode is useful, for instance, if a transmit frame is already stored in the Frame
Buffer and dedicated bytes (e.g. sequence number, address field) need to be replaced before
retransmitting the frame. Furthermore, it can be used to access only the LQI value after frame
reception. A detailed description of the user accessible frame content can be found in
SectionEach SRAM access starts with /SEL = L. The first transferred byte on MOSI shall be the com-
mand byte and must indicate an SRAM access mode according to the definition in
Table 6-2 onpage 19. The following byte indicates the start address of the write or read access. The address
space is 0x00 to 0x7F for radio transceiver receive or transmit operations.
On SRAM read access, one or more bytes of read data are transferred on MISO starting with the
Figure 6-11. Packet Structure - SRAM Read Access
COMMAND
PHR
PSDU 1
PSDU 2
PSDU 3
PSDU 4
PHY_STATUS
XX
SCLK
MOSI
MISO
/SEL
0
reserved[4:0]
0
MOSI
PHY_STATUS
MISO
byte 1 (command byte)
0
ADDRESS[6:0]
XX
byte 2 (address)
XX
DATA[7:0]
byte 3 (data byte)
XX
DATA[7:0]
byte n-1 (data byte)
XX
DATA[7:0]
byte n (data byte)
0