AMIS-53000 Datasheet, PDF (84/99 Pages) AMI SEMICONDUCTOR – Frequency Agile Transceiver

AMIS-53000 Frequency Agile Transceiver
Data Sheet
7.2.2. AMIS-53000 in Slave Mode
The AMIS-53000 cannot be the slave for streaming data. The requirements of adding header information such as preamble or SOF
requires that the AMIS-53000 be in control of the data interface transfer. The receiver has similar requirements with removing the
header information.
As the slave for the data interface, the AMIS-53000 will simply issue an interrupt to the external host indicating data is available after a
data packet has been received.
For buffered transmit operation, the AMIS-53000 will issue an interrupt indicating it is ready to load the packet. After the packet is
received by the AMIS-53000, the transmitter is enabled, any packet formatting is done and the packet is sent.
7.2.3. Manchester Operation
Figure 47: Manchester Coded Data
If the Manchester option is selected in the data rate and format register, the AMIS-53000 will internally encode and decode both
transmit and receive data respectively. The format for the signal interface remains NRZ in this mode.
7.2.4. Packet Framing
Three options bits located in the general options A register determine the method with which the transceiver will process packets: use
ID, length of packet (LOP) enable and cyclic redundancy check (CRC) enable. An additional bit in the TX config register enables the
buffered TX mode of operation.
Table 100: Register Configuration Bits
General Options A
TX Config
Bit 7 Bit 6 Bit 5 Bit 3 Bit 2
0
X
X
X
X
1
X
X
X
X
X
0
X
X
X
1
1
X
X
X
X
X
0
X
X
1
1
1
X
X
X
1
X
1
X
X
X
X
0
X
X
X
X
X
0
X
X
X
X
1
X
X
X
X
X
?
X
X
X
X
SOF
All
X
X
X
X
X
X
X
X
X
X
0x00
All other
Use
No ID
ID
No LOP
LOP/ID
No CRC
CRC/ID/LOP
Buffer/LOP
No Buffer
Chip ID
Global ID
No SOF
SOF
Comments
The ID must be enabled with LOP for data alignment
TX must have LOP enabled when using data buffering
Certain configurations require SOF to detect ID byte
AMI Semiconductor – Aug. 05, Rev. 1.0
84
www.amis.com