Skip to content

Commit 3b98c1d

Browse files
Reorganize sections
1 parent 80f9c87 commit 3b98c1d

File tree

4 files changed

+51
-24
lines changed

4 files changed

+51
-24
lines changed

src/Architecture.md

Lines changed: 14 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -1,36 +1,26 @@
11
# Architecture
22

3-
## Hardware
43

5-
### General
6-
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/)).
4+
## Hardware
75

8-
### Diagram
96
```mermaid
10-
block-beta
11-
columns 2
12-
wifibb["Wi-Fi Baseband"]:1
13-
btbb["Bluetooth Baseband"]:1
14-
adcs["ADCs"]:1
15-
dacs["DACs"]:1
16-
rfsynth["RF Synthesizer"]:1
17-
rfmixer["RF Mixer"]:1
18-
balun["Balun"]:2
19-
antenna["Antenna"]:2
7+
flowchart TD
8+
bb["Baseband (BB)"]
9+
rf["Radio (RF)"]
10+
bb <-- "I/Q Signals" --> rf
2011
```
21-
**NOTE:** This diagram is an "educated" guess. If you know any better or seek someone to blame for incorrectness: [Frostie314159](https://github.com/Frostie314159).
2212

23-
### Description
24-
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.
13+
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.
14+
15+
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.
2516

26-
#### Basebands
27-
As previously stated, the basebands implement the PHY of WiFi and Bluetooth. Each baseband is it's own peripheral and is controlled individually.
17+
The second part is the BB (Baseband), which implement the physical layer for WiFi and Bluetooth.
18+
19+
Data is shared between these two, in the form of a digital I/Q signal (In-phase and Quadrature signal) samples.
2820

29-
#### RF Frontend
30-
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.
31-
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.
3221

3322
## Software
23+
3424
The hardware on the ESP32 is controlled by proprietary blobs, which are interfaced with through a shallow API.
35-
### WiFi
36-
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.
25+
26+
The mentioned blobs include a complete proprietary RTOS used to manage different tasks and events.

src/Baseband.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
# Baseband
2+
3+
ESP32 basebands implement the PHY (Physical Layer) of WiFi and Bluetooth. Each baseband is it's own peripheral and is controlled individually.
4+
5+
6+
## WiFi
7+
8+
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).
9+
10+
They interface with each other through a number of message queues, on top of which an `ioctl`-interface exists.
11+
12+
Espressif chose a SoftMAC architecture for the ESP32, with only ACKing implemented in hardware.

src/Radio.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Radio
2+
3+
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/)).
4+
5+
The diagram below ilustrates the main hardware components of the RF frontend of the chip.
6+
7+
```mermaid
8+
block-beta
9+
columns 2
10+
iface<["I/Q Signal Interface "]>(up, down):2
11+
adcs["ADCs"]:1
12+
dacs["DACs"]:1
13+
rfsynth["RF Synthesizer"]:1
14+
rfmixer["RF Mixer"]:1
15+
balun["Balun"]:2
16+
antenna["Antenna"]:2
17+
```
18+
19+
The RF frontend contains a balun, RF synthesizer, RF mixer, RF switch and an analog/digital frontend consisting of two ADCs and two DACs.
20+
21+
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.
22+
23+
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.

src/SUMMARY.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,6 @@
22

33
- [Introduction](./Introduction.md)
44
- [Architecture](./Architecture.md)
5+
- [Radio](Radio.md)
6+
- [Baseband](Baseband.md)
57
- [Glossary](./Glossary.md)

0 commit comments

Comments
 (0)