You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| MaixCAM || Refer to `MaixCAM-Pro`| 1. `UART0` is system log + default serial port<br>WiFi (SDIO1 + A26)<br>2. `A14` is system status LED; after setting to `GPIO`, it can be used as normal output<br>3. User button already has a system `key` driver; not recommended to read via `GPIO`<br>4. IO is `3.3V` — do not connect `5V` directly |
142
142
| MaixCAM-Pro || 1. Refer to silkscreen, e.g. `29` = GPIO, `RX` = UART<br>2. `6pin` defaults to UART and I2C | 1. Same as `MaixCAM`<br>2. `B3` drives a lighting LED, active high |
143
-
| MaixCAM2 || 1. Refer to silkscreen, e.g. `A4` = GPIO, `U2R` = UART<br>2. `6pin` defaults to UART and I2C | 1. `B25` drives a lighting LED, active high<br>2. `A6` drives system status LED; can be used as GPIO output after init<br>3. IO is `3.3V` — do not connect `5V` directly |
143
+
| MaixCAM2 || 1. Refer to silkscreen, e.g. `A4` = GPIO, `U2R` = UART<br>2. `6pin` defaults to UART and I2C | 1. `B25` drives a lighting LED, active high<br>2. `A6` drives system status LED; can be used as GPIO output after init<br>3. IO is `3.3V` — do not connect `5V` directly |
Copy file name to clipboardExpand all lines: docs/doc/en/peripheral/pwm.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ First, we need to know which pins and PWM channels the device provides, as shown
32
32
| ------- | ------- | --- |
33
33
| MaixCAM || On the silkscreen, for example, `A19` is the pin name and `PWM7` is the function name |
34
34
| MaixCAM-Pro || The first name, such as `A19`, is the pin name; the corresponding `PWM7` is the function name |
35
-
| MaixCAM2 || The first name, such as `B25`, is the pin name; the corresponding `PWM6` is the function name |
35
+
| MaixCAM2 || The first name, such as `B25`, is the pin name; the corresponding `PWM6` is the function name |
36
36
37
37
Note that pins may be used for other purposes by default; it’s best to avoid those pins. See the [pinmap](./pinmap.md) documentation for details.
Copy file name to clipboardExpand all lines: docs/doc/en/peripheral/spi.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ First, we need to know which pins and SPI interfaces the device provides, as sho
72
72
| ------- | ------- | --- |
73
73
| MaixCAM || On the silkscreen, `A24` is the pin name, `SPI4_CS` is the function name |
74
74
| MaixCAM-Pro || The first name, such as `A24`, is the pin name; `SPI4_CS` is the function name |
75
-
| MaixCAM2 || The first name, such as `B21`, is the pin name; `SPI2_CS1` is the function name |
75
+
| MaixCAM2 || The first name, such as `B21`, is the pin name; `SPI2_CS1` is the function name |
76
76
77
77
Note that pins may be used for other purposes by default; it’s best to avoid those pins. See the [pinmap](./pinmap.md) documentation for details.
| MaixCAM || The board’s silkscreen shows the pin name (e.g., `A19`) and function name (e.g., `UART1_TX`). |
43
43
| MaixCAM-Pro || The first label (e.g., `A19`) is the pin name, corresponding to the function name (e.g., `UART1_TX`). |
44
-
| MaixCAM2 || The first label (e.g., `A21`) is the pin name, corresponding to the function name (e.g., `UART4_TX`). |
44
+
| MaixCAM2 || The first label (e.g., `A21`) is the pin name, corresponding to the function name (e.g., `UART4_TX`). |
45
45
46
46
Note: Pins may be used for other purposes by default. It’s best to avoid these pins—see the [pinmap](./pinmap.md) documentation.
47
47
@@ -305,7 +305,7 @@ print(content)
305
305
306
306
### Binary Communication Protocol
307
307
308
-
The character protocol above has a clear characteristic of using visible characters to transmit data. The advantage is simplicity and human readability. However, it uses an inconsistent number of characters and larger data volumes. For example, `$10,20*` and `$1000,2000*` have varying lengths, with `1000` using 4 characters, which means 4 bytes. We know an unsigned short integer (`uint16`) can represent values ranging from `0~65535` using only two bytes. This reduces the transmission data.
308
+
The character protocol above has a clear characteristic of using visible characters to transmit data. The advantage is simplicity and human readability. However, it uses an inconsistent number of characters and larger data volumes. For example, `$10,20*` and `$1000,2000*` have varying lengths, with `1000` using 4 characters, which means 4 bytes. We know an unsigned short integer (`uint16`) can represent values ranging from `0~65535` using only two bytes. This reduces the transmission data.
309
309
310
310
We also know visible characters can be converted to binary via ASCII tables, such as `$1000` being `0x24 0x31 0x30 0x30 0x30` in binary, requiring 5 bytes. If we directly encode `1000` in binary as `0x03E8`, we can send `0x24 0x03 0xE8` in just 3 bytes, reducing communication overhead.
0 commit comments