-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #7 from antoniovazquezblanco/reestructure
Reorganize sections
- Loading branch information
Showing
5 changed files
with
55 additions
and
28 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,36 +1,26 @@ | ||
# Architecture | ||
|
||
## Hardware | ||
|
||
### General | ||
Wireless communications on the ESP32 chip are interfaced via an RF (Radio Frequency) [peripheral designed by Riviera-Waves](https://www.ceva-ip.com/press/espressif-licenses-and-deploys-ceva-bluetooth-in-esp32-iot-chip/) (now [Ceva-Waves](https://www.ceva-ip.com/)). | ||
## Hardware | ||
|
||
### Diagram | ||
```mermaid | ||
block-beta | ||
columns 2 | ||
wifibb["Wi-Fi Baseband"]:1 | ||
btbb["Bluetooth Baseband"]:1 | ||
adcs["ADCs"]:1 | ||
dacs["DACs"]:1 | ||
rfsynth["RF Synthesizer"]:1 | ||
rfmixer["RF Mixer"]:1 | ||
balun["Balun"]:2 | ||
antenna["Antenna"]:2 | ||
flowchart TD | ||
bb["Baseband (BB)"] | ||
rf["Radio (RF)"] | ||
bb <-- "I/Q Signals" --> rf | ||
``` | ||
**NOTE:** This diagram is an "educated" guess. If you know any better or seek someone to blame for incorrectness: [Frostie314159](https://github.com/Frostie314159). | ||
|
||
### Description | ||
The air interface on the ESP32 consists of two parts. The first is the RF frontend, which is in charge of everything analog. The second is the basebands, which implement the physical layer for WiFi and Bluetooth. Data is shared between these two, in the form of a digital quadrature signal. | ||
The above diagram is a simplified guess of the hardware structure of ESP32 wireless communication hardware. The air interface on the device consists conceptually of two main parts represented above. | ||
|
||
The first part is the RF (Radio) frontend, which is in charge of everything analog and the conversion from analog to digital and vice-versa. | ||
|
||
#### Basebands | ||
As previously stated, the basebands implement the PHY of WiFi and Bluetooth. Each baseband is it's own peripheral and is controlled individually. | ||
The second part is the BB (Baseband), which implement the physical layer for WiFi and Bluetooth. | ||
|
||
Data is shared between these two, in the form of a digital I/Q signal (In-phase and Quadrature signal) samples. | ||
|
||
#### RF Frontend | ||
The RF frontend contains a balun, RF synthesizer, RF mixer, RF switch and an analog/digital frontend consisting of two ADCs and two DACs. The reason there are two is, that the ESP32 uses complex/IQ sampling. When a signal arrives from one of the basebands, it passes through the DACs and gets converted to an IQ signal, which then passes through the RF switch and enters the mixer, where it's converted to RF. For receiving it's the whole processes in reverse. | ||
The purpose of the RF switch is to select between the TX and RX paths inside the chip. It can also be set to bridge TX and RX which is used for calibrating the IQ imbalance caused by manufacturing inaccuracies. | ||
|
||
## Software | ||
|
||
The hardware on the ESP32 is controlled by proprietary blobs, which are interfaced with through a shallow API. | ||
### WiFi | ||
The WiFi peripheral on the ES32 is controlled by two FreeRTOS tasks, one of which handles the MAC and the other one the PHY. They interface with each other through a number of message queues, on top of which an `ioctl`-interface exists. Espressif chose a SoftMAC architecture for the ESP32, with only ACKing implemented in hardware. | ||
|
||
The mentioned blobs range in complexity depending on the peripheral they control. WiFi baseband seems to be comprised from a couple of FreeRTOS tasks while Bluetooth baseband appears to include an scheduler, events, many tasks and message echange mechanisms. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
# Baseband | ||
|
||
ESP32 basebands implement the PHY (Physical Layer) of WiFi and Bluetooth. Each baseband is it's own peripheral and is controlled individually. | ||
|
||
|
||
## WiFi | ||
|
||
The WiFi peripheral on the ES32 is controlled by two FreeRTOS tasks, one of which handles the MAC (Medium Access Control) and the other one the PHY (Physical Layer). | ||
|
||
They interface with each other through a number of message queues, on top of which an `ioctl`-interface exists. | ||
|
||
Espressif chose a mostly SoftMAC architecture for the ESP32, with ACKing and MAC address filtering implemented in hardware. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
# Radio | ||
|
||
Wireless communications on the ESP32 chip are interfaced via an RF (Radio Frequency) [peripheral designed by Riviera-Waves](https://www.ceva-ip.com/press/espressif-licenses-and-deploys-ceva-bluetooth-in-esp32-iot-chip/) (now [Ceva-Waves](https://www.ceva-ip.com/)). | ||
|
||
The diagram below ilustrates the main hardware components of the RF frontend of the chip. | ||
|
||
```mermaid | ||
block-beta | ||
columns 2 | ||
iface<["I/Q Signal Interface "]>(up, down):2 | ||
adcs["ADCs"]:1 | ||
dacs["DACs"]:1 | ||
rfsynth["RF Synthesizer"]:1 | ||
rfmixer["RF Mixer"]:1 | ||
balun["Balun"]:2 | ||
antenna["Antenna"]:2 | ||
``` | ||
|
||
The RF frontend contains a balun, RF synthesizer, RF mixer, RF switch and an analog/digital frontend consisting of two ADCs and two DACs. | ||
|
||
The reason there are two is, that the ESP32 uses complex/IQ sampling. When a signal arrives from one of the basebands, it passes through the DACs and gets converted to an IQ signal, which then passes through the RF switch and enters the mixer, where it's converted to RF. For receiving it's the whole processes in reverse. | ||
|
||
The purpose of the RF switch is to select between the TX and RX paths inside the chip. It can also be set to bridge TX and RX which is used for calibrating the IQ imbalance caused by manufacturing inaccuracies. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters