US 8041841 B1
Method and interface for configuring a link is described. A transceiver has configuration registers. The configuration registers are read to determine capability of the transceiver. An application is selected, and the configuration registers of the transceiver are configured responsive to the application selected. A protocol having initialization, transmit and receive portions is described to facilitate configuration operations, such as reads and writes of configuration registers, for such a link.
1. A method for configuring a communication link for transmitting data to and/or from a transceiver associated with configuration registers, the method comprising:
reading the configuration registers to determine a capability associated with the transceiver;
selecting an application within the capability associated with the transceiver;
requesting configuration data from a medium access controller (MAC) coupled for communication with the transceiver, wherein the configuration data is specific to the selected application and includes bus width and operating frequency information for the communication link; and
transmitting the configuration data received from the MAC to the transceiver.
2. The method of
3. The method of
writing the configuration data to the configuration registers associated with the transceiver; and
setting a bus width and an operating frequency of the communication link based on the configuration data.
4. The method of
5. The method of
6. The method of
receiving a data packet that includes header information; and
based on the header information, determining a channel number corresponding to a channel associated with the communication link.
7. The method of
determining that the channel number corresponds to a primary channel associated with the communication link;
selecting the primary channel;
receiving a first bit width for the primary channel; and
receiving over-the-air data via the primary channel.
8. The method of
9. The method of
determining that the channel number indicates that the data packet is associated with a configuration write operation;
receiving a second channel bit width associated with the secondary channel; and
configuring the configuration registers based on the second channel bit width.
10. The method of
determining that the channel number indicates that the data packet is not associated with a configuration write;
selecting the secondary channel;
receiving a second channel bit width for the secondary channel; and
receiving over-the-air data via the secondary channel.
11. A system for configuring a communication link, comprising:
a transceiver associated with configuration registers and configured to transmit and/or receive data via the communication link; and
an input/output (I/O) controller hub, including:
a medium access controller (MAC), and
an interface coupled to the transceiver and coupled to the MAC, the interface configured to:
read the configuration registers to determine a capability associated with the transceiver,
select an application within the capability associated with the transceiver,
request configuration data from the MAC, wherein the configuration data is specific to the selected application and includes bus width and operating frequency information for the communication link, and
transmit the configuration data received from the MAC to the transceiver.
12. The system of
13. The system of
write the configuration data to the configuration registers associated with the transceiver; and
set a bus width and an operating frequency of the communication link based on the configuration data.
14. The system of
15. The system of
16. The system of
receive a data packet that includes header information from the interface; and
based on the header information, determine a channel number corresponding to a channel associated with the communication link.
17. The system of
determine that the channel number corresponds to a primary channel associated with the communication link;
select the primary channel;
receive a first bit width for the primary channel; and
receive over-the-air data via the primary channel.
18. The system of
19. The system of
determine that the channel number indicates that the data packet is associated with a configuration write operation;
receive a second channel bit width associated with the secondary channel; and
configure the configuration registers based on the second channel bit width.
20. The system of
determine that the channel number indicates that the data packet is not associated with a configuration write operation;
select the secondary channel;
receive a second channel bit width for the secondary channel; and
receive over-the-air data via the secondary channel.
This application is a divisional of U.S. patent application Ser. No. 10/235,196, filed Sep. 4, 2002. The subject matter of this related application is hereby incorporated herein by reference.
Wireless communication is becoming more prevalent, especially with respect to data transmissions. The Institute for Electronic and Electrical Engineers (IEEE) and other organizations have promulgated wireless communication applications, which have become industry standards. However, these applications may differ by data width or frequency of operation.
Accordingly, it would be desirable to provide a protocol that facilitates configuration of a radio to accommodate different applications.
A method for configuring a link is described. Configuration of a transceiver is read to determine capability of the transceiver. An application is selected, and configuration registers of the transceiver are configured responsive to the application selected.
A method for transmitting data is described. A data-transmit time window to send over-the-air data is checked. In response to being outside the time window to send the over-the-air data, a check is made for a pending configuration write and a check is make for a pending configuration read.
A method for receiving data to a baseband processor coupled to a transceiver is described. A receive header status is instantiated. If no header is received, indicating a no operation state, a return to the receive header status is made. If header information is received, a channel number is determined responsive to the header information received. In response to the channel number being for a primary channel, the primary channel is selected. In response to the channel number being for a secondary channel, it is determined whether the channel number indicates a configuration write is pending or which secondary channel was indicated.
A digital interface between a baseband processor and a medium access controller and a transceiver is described. A transmitter module is configured to request data from the baseband processor and the medium access controller, to receive data requested from the baseband processor and the medium access controller, and to transmit the data requested responsive to a transmit clock signal. A receive module is configured to receive a receive clock signal and at least one data signal. The receive module is configured to receive data on the at least one data signal from the transceiver responsive to the receive clock signal and to transmit the data to one of a medium access controller and a baseband processor.
In the following description, numerous specific details are set forth to provide a more thorough understanding of the present invention. However, it will be apparent to one of skill in the art that the present invention may be practiced without one or more of these specific details. In other instances, well-known features have not been described in order to avoid obscuring the present invention.
With continuing reference to
Transceiver module 302 provides data, whether configuration data or data to be communicated (“over-the-air data”) via transmit data signal 310 to differential amplifiers 397 to provide transmit data signals 314. Transmit data signals 314, at least during initialization, may comprise configuration data. Transmit data signals 314 received by differential amplifiers 498 provide transmit data signals 310 to transmit module 402. Transmit module 402 converts such transmit data signals 314 into a write control signal of read/write (R/W) control signal 403, as well as an address provided via address signal 404 and configuration data via configuration data signal 405.
In response to a selected application, speed of operation, as well as time and data size parameters for channels, is written to configuration registers of configuration controller 401 at specified addresses to provide the appropriate interface for such a selected application.
Configuration controller 401 provides control signals 501, 502, and 505. Control signal 501 is provided to ND's 413 to select appropriate data channel width for analog input 412. Control signal 502 is provided to D/A's 408 to select an appropriate number of digital-to-analog converters for data channel width for analog data output 409. Control signal 505 is provided to clock generator 414 to provide a frequency of operation corresponding to an application selected. Notably, other control signals, not shown, from configuration controller 401 may be provided to disseminate other application-specific control information. Clock generator 414 provides clock signals 503 to D/A's 408A, A/D's 413 and FIFO's 407 so these circuits can be clocked at an appropriate frequency for a selected application.
Clock generator 414 receives a reference clock signal 415 from which to provide receive clock signal 315. Receive clock signal 315 is provided to differential amplifier 497 to provide receive clock signal 316 to differential amplifier 399.
For a transmit operation, transmit module 302 requests data from BBP 201 via BBP request for data signal 317. BBP 201 provides data via BBP data signal 318 to transmit module 302. Notably, transmit module 302 may optionally provide a reset signal 313 to configuration controller 401 to reset configuration controller 401 to default settings. Additionally, reset signal 313 may be used in connection with an enable bit written to configuration controller 401 as a master enable to enable a new setting of configuration registers 401. Alternatively, an “illegal” state may be used for reset. For example, both signals on a TXDATA 314 differential pair may be at a same logic level, such as both low or both high, to reset configuration registers and controller 401, for example via reset signal path 483 or with a control signal from TX module 402 to configuration registers and controller 401. Thus, TXDATA 310 may be used to set TX module 402 to reset configuration registers and controller 401. Moreover, an illegal state may be used to reset a clock.
Data requested from BBP 201 and received from BBP 201 to transmit module 302 is provided as transmit data signals 310 to differential amplifiers 397 to provide transmit data signals 314. Transmit data signals 314 are provided to differential amplifiers 498 to reconstitute transmit data signals 310 at transmit module 402 of radio interface 400. Transmit module 402 provides transmit data signals 310 as transmit data signals 406 to FIFO's 407 for buffering. Buffered data from FIFO's 407 is clocked out to D/A's 408 where it is converted from a digital format to an analog format to provide analog data output 409.
For a receive operation, analog input 412 is received to ND's 413. A/D's 413 converts analog input 412 to digital input in the form of receive data signals 415. Receive data signals 415 are provided to received module 411 which outputs such received data in the form of receive data signals 417 to differential amplifiers 496. Differential amplifiers 496 convert received data in a digital format to a differential format as data pairs 321. Data pairs 321 are provided to receive module 303 of BBP/MAC interface 300. Receive module 303 provides such data as output to BBP 201 as data output 322.
Reset signal 313 may be provided from transmit module 302 to configuration controller 401 to read configuration capabilities of transceiver 204. Read configuration data is provided as data signal 410 to receive module 411 for outputting as receive data signals 417 to differential amplifiers 496. Differential amplifiers 496 convert configuration data which is represented as receive data signals 417 to receive data pair signals 321 which are provided to receive module 303 of BBP/MAC interface 300. Receive module 303 converts received data pairs signals 321 to configuration data signal 323 for providing to MAC 202. In this manner, transceiver 204 configuration capabilities may be assessed to determine what applications transceiver 204 can support.
Transceiver 204, at power-up, may operate off of default values, such as default values for data width and frequency of operation. Configuration registers 401 are written, for example to operate with a data width or frequency of operation greater than a default setting thereof, including writing a set enable bit. Once a reset signal is received, because an enable bit is set, configuration controller 401 configures transceiver 204 for a configuration written thereto. In this manner, transceiver 204 may initially run at a first frequency or a first data width after power-up, and be stepped up to a second frequency or a second data width for a selected application.
At 701, a check is made to determine if a channel is ready to send. As mentioned above, a time parameter associated with when a channel should send is part of configuration of transceiver 204. Conventionally, a primary channel's need for bandwidth and total available bandwidth of a link dictated a strict time slice of such a link for secondary channel bandwidth. However, because primary channels or secondary channels may be configured, namely, they need not be fixed functions, an available bandwidth may be at least partially allocated for secondary channel communication. Furthermore, depending on configuration, an average guaranteed bandwidth may be made available for secondary channel communication. Thus, a channel is ready to send in accordance with configured timing. If a channel is in a ready state to send data or other information, or even no operation (NOP), a channel is selected at 702. At 703A, channel designation information associated with the selected channel is sent. At 704A data to be sent is obtained, and at 705 such obtained data is sent. Padding is sent at 712 on an as needed basis. This process repeats at 701 to determine whether another channel is in a ready state to send.
If at 701 a channel is not in a ready state to send, a check is made at 706 to determine if a configuration write is pending. If a configuration write is pending, a call to a configuration write routine is made at 707A. After such a call or if no configuration write is pending, a check is made at 708 to determine if a configuration read is pending. If a configuration read is pending at 708, then at 709A a call is made to a configuration read subroutine. If after a configuration is read after calling a configuration read subroutine at 709A or no configuration read is pending at 708, then a check is made at 710 to determine if anything was sent. If anything was sent process 700A begins again at determining whether a channel is ready to send at 701. If no information was sent then a NOP signal is provided at 711, and protocol transmit process 700A repeats at checking whether a channel is ready to send at 701.
Notably, when data is sent it will be sent with particular bit width as configured. For primary channels, a configurable bit width of N bits may be used. However, secondary channels may have a fixed bit width. A fixed bit width may be dictated by capability of transceiver 204 of
As mentioned above, there are primary and secondary channels.
It should be appreciated that multiples of reads or writes or any combination thereof may be done within an available time window for configuration reading or writing. Furthermore, it should be appreciated that at 1006 an address was sent for possibly subsequently calling configuration registers.
It should be further appreciated that because a ready state for sending for a channel is checked, secondary channels arbitrate for bandwidth, namely, use of bandwidth if available and a channel ready to send. Alternatively, a ready state for sending by a secondary channel may be done on a time slice basis, namely, each secondary channel gets an opportunity to send every so often.
At 1105, channel data is received in a predetermined width for a selected channel. Channel width is obtained by MAC/BBP query of configuration registers associated with the radio, and the result from such query is stored. At 1106A, data received is provided to BBP 201.
If a primary channel is not indicated at 1103, a sub-header is checked at 1107. A sub-header may indicate a configuration write, or a selected secondary channel. For example, at 1107 a check may be made to determine whether a sub-header is for a configuration write.
If at 1107 a configuration write is indicated, then at 1108 a register address for such a configuration write is received. Continuing the above example, such a sub-header may be a binary 0 to indicate a configuration write, where a fixed bit width of 8 bits may be used for accessing a byte of information for a configuration register. At 1109, configuration register data is received for the received address at 1108.
With respect to protocol receive process 1100A, at 1110, a check is made to determine whether the configuration register address and data received at 1108 and 1109, respectively, matches a previous configuration write. If it does not match then an error results at 1111, and if it does match then any padding is received at 1120.
With respect to protocol receive process 1100B, configuration address information and data received at 1108 and 1109, respectively, is provided to configuration registers 401 at 1123. After which, any padding is received at 1120. In addition to providing configuration address information and data at 1123, an optional overflow check of FIFOs 407 may be made.
If however a configuration write is not indicated by a received sub-header at 1107, then a check may be made to determine if a configuration read was indicated at 1115. If a configuration read was indicated at 1115, then with respect to protocol receive process 1100A data for such a configuration read is received at 1116. At 1117, such received data is provided to MAC 202. After which, any padding is received at 1120.
If a configuration read was indicated at 1115, then with respect to protocol receive process 1100B an address for such a configuration read is received at 1118. At 1119, such a received address is provided to configuration registers 401. In addition to providing configuration address information at 1119, an optional overflow check of FIFOs 407 may be made. After which, any padding is received at 1120.
If a received sub-header does not indicate a configuration read or a configuration write, then a channel is selected at 1112 in response to such a received sub-header. As indicated above, such a received sub-header is 4 bits wide in order to delineate between channels 2 to 15 at 1112, where sub-header values 0 and 1, as mentioned above, indicate configuration write and configuration read status, respectively.
At 1113, secondary channel data is received. This may be an N bit wide channel in the above example, where bit width is predetermined for secondary channels too.
With respect to
With respect to
A signaling protocol over a high-speed source-synchronous digital connection that supports wireless radio or any other application that sources and sinks data from one or more different logical streams at regular intervals has been described. Such a signaling protocol supports 802.11b with a single data wire or differential pair in each direction. This may be done while keeping link frequency low enough that it can operate in a wire-bond package, and while keeping semiconductor die size within a conventional package size. Supports for variable bus widths and link frequencies may be used to advertise capabilities of a radio and then program at least one of data width and speed. Additionally, at least two primary data streams and fourteen secondary data streams are supported. Bandwidth of each stream is described via configuration registers. Configuration access means includes support for additional vendor-specific registers.
Programmability of width/frequency of a link, for one or two primary data streams, uses a small transfer size to limit buffering on each end. A data stream model supports not only IEEE 802.11 application but other fixed-bandwidth modulator/demodulator applications. Primary and secondary channels are not fixed functions due to configuration writes for a selected application. Thus, different radios may be configured to use the same application, or different applications.
JC 61 RF/BB Proposal
Conventionally, a radio is interfaced to a baseband using an analog I/Q interface as shown in
Because most of the existing radios use an analog I/Q interface, a digital link design that has enough flexibility to support existing and future radios is desirable. By adding a glue logic section, an ordinary radio with analog I/Q interface can be converted to one with a digital interface. The subsequent section describes the data organization, packet definition, and the electrical characteristics of this digital link.
Between the radio and the baseband modem, there are two major data types that are supported by the proposed high speed serial data link. The packet structure is specifically designed to handle these data types and permit efficient packet transmission and decoding. The simplest data type, the configuration data cfg, supports data transfer that is slow and infrequent. The other data type, the stream data, supports data transfers that are periodic such as baseband IQ data. There are different kinds of stream data such as I channel, Q channel, and RSSI data. During normal operation, the two types of data packets can be mixed. For example in
A motivation for the stream data type is that many existing radios require hardwired signals from the baseband. For example, hardwired signals include all analog signals, along with some digital control bits that require low latency such as Rx signal detector or digital Rx AGC control. For these hardwired signals, it is important to be able to transfer the data at a specific rate with as low latency as possible. This link supports four types of stream data including (0) SYNC/NO_OP, (1) PRIMARY_Q, (2) PRIMARY_I, and (3) SECONDARY. The type is represented by the first two bits on the packet header. The number of bits within the payload can differ between data type and is set by the radio.
Table I is an example of one possible packet structure for headers.
The PRIMARY_I supports the I channel traffic, while the PRIMARY_Q supports the Q channel traffic. The speed and width of the channel is set by the radio in the cfg table below. In the implementation of the link, a FIFO and serializer and deserializers are needed. Therefore, there is latency between the sending of the data and the receiving of the data at the other end. However, the latency on the PRIMARY I/Q channels is usually not important.
The SECONDARY stream data supports the auxiliary converters such as RSSI and RxAGC. There are 11 channels available. The speed and the number of bits for each stream data is specified by the radio in a setup configuration table below.
Table I is an example of one possible packet structure for headers and subheaders.
In the implementation of this link, a FIFO and serializer and deserializers are needed. Therefore, there is latency between the sending of the data and the receiving of the data at the other end. The latency between the RSSI and RxAGC controls in the SECONDARY channel is important because the latency must satisfy AGC loop operational parameters. To satisfy this latency, a latency specification is used. It is defined as the round trip time between the RxAGC data entering the radio to the time the RSSI (RX_DET) data leaving as shown in
For 802.11b, it is recommended to specify the latency to be 40 reference clocks, where the reference clock frequency is 44 MHz. For 802.11a, it is recommended to specify the latency to be 2 reference clocks, where the reference clock frequency is 40 MHz.
Read/write configuration registers, cfg, define a set, for example of 4096×8b register bank, inside the radio. The cfg registers store the link configuration table and any radio specific data. If the radio does not use all the registers, the higher address can be ignored and not implemented in hardware. Since the radio is a dedicated device, the baseband always initiate a cfg access. For both read and write access, one packet is sent from the baseband to the radio, followed by a response packet sent from the radio back to the baseband. For cfg read, the baseband sends a read packet with the address to the radio, and then the radio will send back the requested data as shown in
An example of packet structure of a cfg read is defined in below, while the same for cfg write is defined below that. The cfg register table contains the link setup information as well as any user defined data. The first 32 address are for general link control and setup. The next 128 addresses are for first radio setup, followed by another 128 addresses for the second radio setup. The rest of the addresses from 288 to 4095 are for radio specific data.
Table III is an example of one possible register address/use scheme.
There are two identical banks of register definition for two radio setups for potential use in dual mode radios. For the first radio, the address is 32+offset, whereas for the second radio, the address is 160+offset. The choice of which bank to use is made in registers 5 and 6 where the base address is stored.
Table IV is one possible link setup register map.
Table V is one possible channel type configuration.
As an example, a digital interface can be added to the radio by setting up the link as follows. For the direction from radio to baseband, the PRIMARY_I and PRIMARY_Q channels are both set to 6 bits at 22 MHz for the receive ADC's. RX_DET (equivalent to RSSI) is set to SECONDARY 0010 with 6 bits at 2.2 MHz. For the direction from baseband to radio, the PRIMARY_I and PRIMARY_Q channels are both set to 8 bits at 44 MHz for the transmit DACs'. RX_AGC is set to SECONDARY 0010 with 6 bits at 2.2 MHz.
Pins TX_GC, TXON, RXON, RF_GAIN, PAENB, RX_LK, SHDNB, DIN, SCLK, DOUT, and CSB are handled by radio specific configuration bits. Table VI is one possible general setup configuration.
Table VII is one possible configuration for link setup where a base address is 32.
Table VIII is an example of some radio specific data that may be used.
The link needs a set of differential signal pins as defined below. The minimum configuration for this implementation is 8 pins where N=M=0. Table IX is a table of link signals.
As an example, a conventional 802.11b radio would use only 8 pins with RXCLK and TXCLK running at 484 MHz. For a conventional 802.11a radio, the radio would use only 8 pins with RXCLK and TXCLK running at 880 MHz.
The packets sent over the high speed serial data link are organized in a manner to efficiently handle the data types. The packet is constructed with a 2 bit header and payload size that is defined by the radio in the link setup. The payload size can be different for various data types.
The “Sync Packet” is a special packet used to define the packet boundaries. It carries null data. Table X is an example of a possible sync packet header.
As an example, for 802.11b, the packet would be 10 bits with contents “0011111111”, while for 802.11a, the packet would be 12 bits with contents “001111111111”.
The PRIMARY I or Q channel packet is data for I and Q channels. The number of bits in the payload is set by radio. An example of PRIMARY I and Q headers is shown in Table XI.
As an example, for 802.11b, the packet would be 10 bits with contents 2b(header)+8b (data), while for 802.11a, the packet would be 12 bits with contents 2b(header)+10b(data).
The secondary channel is used for auxiliary converters such as RSSI. There can be 16 secondary channels, each specified by a 4b subheader. Two channels are reserved for use by the cfg, and 3 channels are reserved for system use (see below for re-synchronization). So, 11 sub-channels are available to the user in this implementation. The sub-channel width and speed are defined in the setup cfg table. Table XII provides examples of possible packet structures.
Possible packet structures from baseband to radio are shown in Table XIII
The address of the cfg register is 12 bits. The payload will be padded until the length of the packet is an integer multiple of the minimum packet size. For example, for 802.11b, the minimum packet size is 2b+8b=10b, so the cfg read packet size is 2b (header)+4b (subheader)+12b (address)+2b (padding)=20b. For 802.11a, the minimum packet size is 2b+10b=12b, so the cfg read packet size is 2b (header)+4b (subheader)+12b (address)+6b (padding)=24b.
After the data is retrieved, the data is sent back to the baseband using another cfg read packet with the same size. However, the data is only 8 bits, so the extra space is padded with 1's.
Possible packet structures from radio to baseband are shown in Table XIV
For example, for 802.11b, the minimum packet size is 2b+8b=10b, so the cfg read packet size is 2b (header)+4b (subheader)+8b (data)+6b (padding of 1's)=20b. For 802.11a, the minimum packet size is 2b+10b=12b, so the cfg read packet size is 2b (header)+4b (subheader)+8b (address)+10b (padding of 1's)=24b.
Possible packet structures from baseband to radio for secondary channel cfg write are shown in Table XV.
The address of the cfg register is 12 bits, and the data is 8b. The payload will be padded until the length of the packet is an integer multiple of the minimum packet size. For example, for 802.11b, the minimum packet size is 2b+8b=10b, so the cfg write packet size is 2b(header)+4b(subheader)+12b(address)+8b(data)+4b (padding)=30b. For 802.11a, the minimum packet size is 2b+10b=12b, so the cfg read packet size is 2b (header)+4b (subheader)+12b (address)+8b(data)+10b (padding)=36b.
After the data is written to registers in the radio, the data written is echoed back for confirmation using another cfg write packet with the same size and content. This packet is identical to the previous packet from baseband to radio for cfg write.
In this link design, the data is sent on both edges of the clock. So, due to the double data rate nature of this data transfer, the radio must select an even number of bits for the payload for easier decoding. As a result, the serializer must take an even number of parallel bits.
Hard reset on the link will be asserted from the baseband. When the baseband pulls low both the positive and negative pins of a differential data signal TXDATA, the link will be reset. Cfg register 5 for link setup base address will be cleared to 32, and register 7 for link mode will be set to 0. Furthermore, the radio will power down and turn off any external oscillator for deep sleep mode.
Coming out of reset, the link will be set to the minimum bandwidth configuration. The link speed is set to the refclk frequency, where the refclk frequency is 44 MHz for 802.11b and 40 MHz for 802.11a. The RXDATA and TXDATA width will be set to 1 b. First, the link will need to synchronize the packet boundaries. The link will only send pairs of SYNC packets and wait for pairs of SYNC packets from the other side. Once valid SYNC packets are received, the link can synchronize the packet boundary (see below for boundary detection method).
Then the link will configure itself automatically based on link setup cfg registers. Using cfg reads, the baseband will be able to get the Device ID, the final link speed, the final data width for RXDATA and TXDATA, the speed and width for the PRIMARY I and Q channels, the speed and width for every SECONDARY channel. The cfg registers shows detailed information on the registers used to setup the link on the baseband side.
Once the baseband obtained all the required setup information, it will set the link mode register 7 to “1”. This will tell the radio to bring the link up to full speed.
Sometimes the link can get confused about the packet boundaries due to errors in the transmission. By monitoring the FIFO's on the link for overflow and underflow. The link can discover if the packet boundary is misaligned. In such cases, each side of the link will only send pairs of SYNC packets and wait for pairs of SYNC packets from the other side. Once valid SYNC packets are received, the link can synchronize the packet boundary.
The method to look for SYNC packets is as follows. As an example for 802.11b, the SYNC packet pair is “00111111110011111111”. There are only 4 possible header patterns seen by the parser since the DDR interface does not permit a single bit shift. So, the parser will choose from the following packets:
“001111”: valid sync packet
“111111”: secondary channel 1111, reserved
“111100”: secondary channel 1100, reserved
“110011”: secondary channel 0011, reserved
Since the 3 sub-channels are reserved and should never occur, the parser will be able to detect the sync packet correctly.
There is no error detection proposed for Stream I/Q or SECONDARY channel RSSI stream data because the bit error rate from the data itself is much higher than the link error rate. To prevent accidentally setting the wrong cfg bits on the radio, all cfg data that is written is echoed back to the baseband. The baseband can check for consistency and correct the mistake if necessary.
While foregoing is directed to embodiments in accordance with one or more aspects of the present invention, other and further embodiments of the present invention may be devised without departing from the scope thereof, which is determined by the claims that follow. Claims listing steps do not imply any order of the steps unless such order is expressly indicated.
All trademarks are the respective property of their owners.
Citas de patentes