Added documents related to PM5.
This commit is contained in:
1 parent
32e2e414cd
commit
bcbe1afac0
14 files changed
+1339
-1
No files matched your search
@@ -0,0 +1,299 @@
|
||||
# Antenna Controller Technical Manual
|
||||
|
||||
> Intended audience: host-side (integration) developers who need to communicate with this antenna controller over the I2C bus.
|
||||
> This document describes only the external interface and business logic, not the internal hardware or implementation details.
|
||||
|
||||
- Author: DXL
|
||||
- Document version: v1.0
|
||||
- Date: 2026-08-24
|
||||
|
||||
## Table of Contents
|
||||
|
||||
1. [Overview](#1-overview)
|
||||
2. [I2C Communication Basics](#2-i2c-communication-basics)
|
||||
3. [Register Map Overview](#3-register-map-overview)
|
||||
4. [Register Details](#4-register-details)
|
||||
5. [Operation Methods](#5-operation-methods)
|
||||
6. [Register Mutual Exclusion and Constraint Conditions](#6-register-mutual-exclusion-and-constraint-conditions)
|
||||
7. [Business Logic Feature Summary](#7-communication-and-register-defaults-summary)
|
||||
8. [Flowcharts](#8-flowcharts)
|
||||
|
||||
## 1. Overview
|
||||
|
||||
This controller's communication interface is a standard I2C **slave**, used to control the antenna's operating frequency, Q value, and LED indication. The host can perform all control and status queries by reading and writing several I2C registers. Supported capabilities are as follows:
|
||||
|
||||
| Capability | Description |
|
||||
|------|------|
|
||||
| Operating frequency | Five levels: 125 kHz / 134 kHz / 250 kHz / 375 kHz / 500 kHz |
|
||||
| LED indication | HF (high-frequency) LED and LF (low-frequency) LED, each independently controllable on/off |
|
||||
| Q value | High Q / low Q switching |
|
||||
|
||||
## 2. I2C Communication Basics
|
||||
|
||||
### 2.1 Slave Address
|
||||
|
||||
| Item | Value |
|
||||
|----|----|
|
||||
| 7-bit slave address | `0x51` |
|
||||
| 8-bit write address | `0xA2` (`0x51 << 1 | 0`) |
|
||||
| 8-bit read address | `0xA3` (`0x51 << 1 | 1`) |
|
||||
|
||||
### 2.2 Communication Rate
|
||||
|
||||
It is recommended to keep the I2C clock rate at **around 10 kHz**; an excessively high rate may cause communication failures.
|
||||
|
||||
### 2.3 Communication Model
|
||||
|
||||
Register operations follow the **"write the register address first, then read/write data"** convention:
|
||||
|
||||
- Before any register operation, a **write** operation must be performed first to tell the slave which register is to be operated on subsequently;
|
||||
- **Read operation**: first perform a write operation passing only 1 byte (the register address), then initiate a read transaction;
|
||||
- **Write operation**: perform one write operation where byte 1 is the register address and the subsequent bytes are the register data.
|
||||
|
||||
## 3. Register Map Overview
|
||||
|
||||
| Address | Name | Access | Data Length | Description |
|
||||
|------|------|------|:---:|------|
|
||||
| `0x00` | Invalid register (default) | — | — | Power-on default address; not readable, and rejected if written as an address |
|
||||
| `0x01` | IO data register | Read / Write | 1 byte | Directly reads/writes the raw levels of the antenna control lines (low-level pass-through interface) |
|
||||
| `0x02` | IO mapping register | Read / Write | 1 byte | Logical control of frequency / LED / Q value (recommended) |
|
||||
| `0xFE` | Device identification register | Read-only | 8 bytes | Device identity signature |
|
||||
| `0xFF` | Firmware version register | Read-only | 2 bytes | Major version + minor version |
|
||||
|
||||
## 4. Register Details
|
||||
|
||||
### 4.1 `0x00` — Invalid Register
|
||||
|
||||
- The default "current register" address after power-on;
|
||||
- Before a valid register address is written, any **read** operation will be rejected (NACK);
|
||||
- Writing `0x00` as a register address is also rejected.
|
||||
|
||||
### 4.2 `0x01` — IO Data Register (Read / Write, 1 byte)
|
||||
|
||||
- Directly reads/writes the 8-bit raw levels of the antenna control I/O group;
|
||||
- **Read**: returns the real-time state of the current 8 control lines;
|
||||
- **Write**: directly sets these 8 control lines, **without** going through the arbitration and constraint logic of `0x02`;
|
||||
- The 8 bits logically cover the same group of control signals as `0x02` (frequency selection, Q value, HF/LF LED), but the bit ordering is a hardware implementation detail and is not publicly guaranteed;
|
||||
- ⚠️ This register is a low-level "pass-through" interface; for normal control, use `0x02`.
|
||||
- ⚠️ Unless for debugging purposes, do not operate this register; otherwise, if the antenna hardware is revised, writing incompatible data could cause anomalies.
|
||||
|
||||
> **Relationship note**: writing `0x02` updates both the internal logical mapping and the actual control lines; writing `0x01` only directly changes the actual control lines and does **not** write back to the internal logical mapping. If the two are mixed, a subsequent read of `0x02` may return an old value inconsistent with what was written to `0x01`.
|
||||
|
||||
### 4.3 `0x02` — IO Mapping Register (Read / Write, 1 byte)
|
||||
|
||||
8-bit mapping:
|
||||
|
||||
| Bit | Meaning | Value |
|
||||
|:---:|------|------|
|
||||
| 7 | 125 kHz enable | 1 = enabled / 0 = disabled |
|
||||
| 6 | 134 kHz enable | 1 = enabled / 0 = disabled |
|
||||
| 5 | 250 kHz enable | 1 = enabled / 0 = disabled |
|
||||
| 4 | 375 kHz enable | 1 = enabled / 0 = disabled |
|
||||
| 3 | 500 kHz enable | 1 = enabled / 0 = disabled |
|
||||
| 2 | HF LED | 1 = on / 0 = off |
|
||||
| 1 | LF LED | 1 = on / 0 = off |
|
||||
| 0 | Q value | 1 = high Q / 0 = low Q |
|
||||
|
||||
See Section 6 for constraint conditions.
|
||||
|
||||
### 4.4 `0xFE` — Device Identification Register (Read-only, 8 bytes)
|
||||
|
||||
- Returns a fixed 8-byte identity signature: `0x70 0x6D 0x35 0x5F 0x61 0x6E 0x74 0x78`
|
||||
- Purpose: after reading, the host compares it with the expected value to confirm that the currently connected device is this antenna controller (rather than another I2C device);
|
||||
- Circular reading: after the 8th byte is read, continued reading wraps back to the 1st byte.
|
||||
|
||||
### 4.5 `0xFF` — Firmware Version Register (Read-only, 2 bytes)
|
||||
|
||||
- Byte 1: major version
|
||||
- Byte 2: minor version
|
||||
- Current version: **v1.2** (major 1 / minor 2)
|
||||
- Purpose: the host can use it for version adaptation and problem localization; after the 2nd byte is read, continued reading wraps back to the 1st byte.
|
||||
|
||||
## 5. Operation Methods
|
||||
|
||||
### 5.1 Write Register
|
||||
|
||||
```
|
||||
START | write address 0xA2 | ACK | register address | ACK | data | ACK | STOP
|
||||
```
|
||||
|
||||
1. Host sends `START`;
|
||||
2. Host sends the 8-bit write address `0xA2`;
|
||||
3. Slave replies `ACK`;
|
||||
4. Host sends the register address (1 byte);
|
||||
5. Slave replies `ACK`;
|
||||
6. Host sends the data (each writable register of this controller has a 1-byte data body);
|
||||
7. Slave replies `ACK`;
|
||||
8. Host sends `STOP`.
|
||||
|
||||
> If a read-only register (`0xFE` / `0xFF`) or an illegal address is written, the slave terminates the communication with **NACK**.
|
||||
|
||||
### 5.2 Read Register
|
||||
|
||||
A read operation consists of two stages: "set address" and "read".
|
||||
|
||||
```
|
||||
Set address: START | write address 0xA2 | ACK | register address | ACK | STOP
|
||||
Read data: START | read address 0xA3 | ACK | data0 | ACK | ... | dataN | NACK | STOP
|
||||
```
|
||||
|
||||
1. Host sends `START`, then the write address `0xA2`; slave replies `ACK`;
|
||||
2. Host sends the register address (1 byte); slave replies `ACK`;
|
||||
3. Host sends `STOP` (or switches to a `repeated START`);
|
||||
4. Host sends `START`, then the read address `0xA3`; slave replies `ACK`;
|
||||
5. The slave sends data bytes in sequence; the host replies `ACK` for each intermediate byte and `NACK` for the last byte to end;
|
||||
6. Host sends `STOP`.
|
||||
|
||||
> In a single read transaction, the slave sends data continuously (`0xFE` up to 8 bytes, `0xFF` 2 bytes, `0x01` / `0x02` 1 byte); the host terminates it actively with `NACK`.
|
||||
|
||||
### 5.3 Operation Examples
|
||||
|
||||
| Operation | Byte sequence |
|
||||
|------|---------|
|
||||
| Set 125 kHz, HF LED on, low Q | Write `0x02` = `0x84` (0b10000100) |
|
||||
| Set 250 kHz, both LEDs on, low Q | Write `0x02` = `0x26` (0b00100110) |
|
||||
| Read firmware version | Write address `0xFF`, then read 2 bytes |
|
||||
|
||||
## 6. Register Mutual Exclusion and Constraint Conditions
|
||||
|
||||
1. **Frequency bit mutual exclusion** (`0x02` bit7~bit3):
|
||||
- At most 1 bit may be 1 at a time;
|
||||
- If multiple bits are set simultaneously, priority follows **frequency from low to high**: 125k → 134k → 250k → 375k → 500k;
|
||||
- If all 5 bits are 0, **125 kHz** is automatically enabled as a fallback.
|
||||
|
||||
2. **Q value and frequency linkage** (`0x02` bit0):
|
||||
- High Q takes effect only when the frequency is **125 kHz or 134 kHz**;
|
||||
- Set bit0 = 1 with frequency 125/134 → high Q;
|
||||
- All other cases (other frequencies, or bit0 = 0) are forced to low Q.
|
||||
|
||||
3. **Read-only register protection**: `0xFE` and `0xFF` are read-only; writing data to them is rejected (NACK and communication terminated).
|
||||
|
||||
4. **Invalid address protection**: `0x00` is not a valid register; both writing and reading are rejected.
|
||||
|
||||
## 7. Communication and Register Defaults Summary
|
||||
|
||||
- **Power-on default**: 125 kHz + low Q + both LEDs off (`0x02` default value `0x80`).
|
||||
- **Device identification**: the 8-byte signature `0x70 6D 35 5F 61 6E 74 78` identifies this device as a multi-frequency, full-featured antenna controller.
|
||||
- **Firmware version**: major 1 / minor 2 (v1.2).
|
||||
- **Multi-byte register wraparound**: `0xFE` (8 bytes) and `0xFF` (2 bytes) wrap back to the first byte after reaching the end.
|
||||
- **Register address retained across transactions**: the register address is retained after `STOP` until the next write transaction resets it, so when reading the same register consecutively, the address only needs to be written once.
|
||||
- **`0x01` and `0x02` are not synchronized**: `0x01` is the pass-through physical control lines, while `0x02` is the arbitrated logical mapping (see 4.2 for details).
|
||||
|
||||
## 8. Flowcharts
|
||||
|
||||
### 8.1 Power-on Initialization Flow
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
A([Power-on / reset]) --> B[Delay about 3ms to wait for power stabilization]
|
||||
B --> C[Configure the 8 antenna control lines as outputs]
|
||||
C --> D[Set default mapping: 125 kHz + low Q + LEDs off]
|
||||
D --> E[Apply the default mapping to the control lines]
|
||||
E --> F[Initialize I2C slave]
|
||||
F --> G([Enter main loop: poll the I2C lines])
|
||||
```
|
||||
|
||||
### 8.2 IO Mapping Update Flow
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
Start([Write / update IO mapping register]) --> C125{125k bit = 1?}
|
||||
C125 -->|Yes| F125[Select 125 kHz]
|
||||
C125 -->|No| C134{134k bit = 1?}
|
||||
C134 -->|Yes| F134[Select 134 kHz]
|
||||
C134 -->|No| C250{250k bit = 1?}
|
||||
C250 -->|Yes| F250[Select 250 kHz]
|
||||
C250 -->|No| C375{375k bit = 1?}
|
||||
C375 -->|Yes| F375[Select 375 kHz]
|
||||
C375 -->|No| C500{500k bit = 1?}
|
||||
C500 -->|Yes| F500[Select 500 kHz]
|
||||
C500 -->|No| F125
|
||||
|
||||
F125 --> HF{HF LED bit = 1?}
|
||||
F134 --> HF
|
||||
F250 --> HF
|
||||
F375 --> HF
|
||||
F500 --> HF
|
||||
HF -->|Yes| HFON[Turn on HF LED]
|
||||
HF -->|No| HFOFF[Turn off HF LED]
|
||||
|
||||
HFON --> LF{LF LED bit = 1?}
|
||||
HFOFF --> LF
|
||||
LF -->|Yes| LFON[Turn on LF LED]
|
||||
LF -->|No| LFOFF[Turn off LF LED]
|
||||
|
||||
LFON --> Q{High Q required and\nfrequency is 125/134?}
|
||||
LFOFF --> Q
|
||||
Q -->|Yes| QH[High Q]
|
||||
Q -->|No| QL[Low Q]
|
||||
QH --> Done([Done])
|
||||
QL --> Done
|
||||
```
|
||||
|
||||
### 8.3 I2C Communication Handling Flow
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
Idle([Idle wait]) --> ST{START detected?}
|
||||
ST -- No --> Idle
|
||||
ST -- Yes --> Addr[Receive 7-bit slave address]
|
||||
Addr --> Mt{Address matches 0x51?}
|
||||
Mt -- No --> Idle
|
||||
Mt -- Yes --> Op[Receive read/write bit]
|
||||
Op --> Rdw{Read / write?}
|
||||
Rdw -- Write --> Wr1[Receive 1 byte as register address]
|
||||
Wr1 --> Vr{Address valid?}
|
||||
Vr -- No --> Nk[Respond NACK]
|
||||
Nk --> Idle
|
||||
Vr -- Yes --> Wr2[Receive data byte]
|
||||
Wr2 --> Vd{Target register writable?}
|
||||
Vd -- No --> Nk
|
||||
Vd -- Yes --> Apply[Apply data / update control lines]
|
||||
Apply --> Wr2
|
||||
Rdw -- Read --> Chk{Valid address already set?}
|
||||
Chk -- No --> Nk
|
||||
Chk -- Yes --> Rd[Send data byte]
|
||||
Rd --> Rsp{Host ACK?}
|
||||
Rsp -- ACK --> Rd
|
||||
Rsp -- NACK --> Idle
|
||||
```
|
||||
|
||||
> Note: regardless of the current processing stage, detecting a STOP (SDA↑ while SCL is high) immediately returns to the idle state.
|
||||
|
||||
### 8.4 Write Register Timing
|
||||
|
||||
```mermaid
|
||||
sequenceDiagram
|
||||
participant M as Host (Master)
|
||||
participant S as Slave
|
||||
M->>S: START
|
||||
M->>S: 0xA2 (write address)
|
||||
S-->>M: ACK
|
||||
M->>S: 0x02 (register address)
|
||||
S-->>M: ACK
|
||||
M->>S: 0x84 (data: 125kHz + HF LED on)
|
||||
S-->>M: ACK
|
||||
M->>S: STOP
|
||||
```
|
||||
|
||||
### 8.5 Read Register Timing (reading the firmware version as an example)
|
||||
|
||||
```mermaid
|
||||
sequenceDiagram
|
||||
participant M as Host (Master)
|
||||
participant S as Slave
|
||||
M->>S: START
|
||||
M->>S: 0xA2 (write address)
|
||||
S-->>M: ACK
|
||||
M->>S: 0xFF (register address)
|
||||
S-->>M: ACK
|
||||
M->>S: STOP
|
||||
M->>S: START
|
||||
M->>S: 0xA3 (read address)
|
||||
S-->>M: ACK
|
||||
S-->>M: 0x01 (major version)
|
||||
M->>S: ACK
|
||||
S-->>M: 0x02 (minor version)
|
||||
M->>S: NACK
|
||||
M->>S: STOP
|
||||
```
|
||||
@@ -0,0 +1,266 @@
|
||||
# Button Controller Technical Manual
|
||||
|
||||
> This document is intended for product users and integrators. It describes the button actions, timing parameters, and related business logic of this chip.
|
||||
|
||||
- Author: DXL
|
||||
- Document version: v1.0
|
||||
- Date: 2026-08-24
|
||||
|
||||
---
|
||||
|
||||
## Table of Contents
|
||||
|
||||
1. [Overview](#1-overview)
|
||||
2. [External Signals and Key Actions](#2-external-signals-and-key-actions)
|
||||
3. [Button Actions and Timing](#3-button-actions-and-timing)
|
||||
4. [Effects of Various Conditions on Button Business Logic](#4-effects-of-various-conditions-on-button-business-logic)
|
||||
5. [Detailed Flowcharts](#5-detailed-flowcharts)
|
||||
6. [Typical Operation Scenarios](#6-typical-operation-scenarios)
|
||||
7. [FAQ and Notes](#7-faq-and-notes)
|
||||
8. [Appendix](#appendix)
|
||||
|
||||
---
|
||||
|
||||
## 1. Overview
|
||||
|
||||
This chip is used to assist the host MCU. It is primarily responsible for:
|
||||
|
||||
- **Reset control**: resetting (rebooting) the host MCU under specific conditions;
|
||||
- **ISP mode management**: guiding the host MCU into or out of ISP (In-System Programming) mode through operations such as long presses, for firmware updates;
|
||||
- **Factory test mode**: detecting the factory test signal at power-on and guiding the host MCU into a programming state, for production-line flashing.
|
||||
|
||||
> **Terminology**
|
||||
> - **Host MCU**: the target chip managed by this chip, which runs the main application firmware.
|
||||
> - **ISP (In-System Programming)**: in-system programming, used to update the host MCU firmware.
|
||||
|
||||
---
|
||||
|
||||
## 2. External Signals and Key Actions
|
||||
|
||||
### 2.1 External Signals
|
||||
|
||||
| Signal | Direction | Meaning | Active Level |
|
||||
| --- | --- | --- | --- |
|
||||
| `BTN_IN` | Input | Physical button | High = pressed, Low = not pressed |
|
||||
| `USB_VBUS` | Input | USB connection / power detection | High = USB connected, Low = not connected |
|
||||
| `MCU_RST` | Output | Host MCU reset control | Low = reset, High = normal operation |
|
||||
| `MCU_BOOT0` | Output | Host MCU boot mode selection | High = programming (ISP) mode, Low = normal operation |
|
||||
|
||||
### 2.2 Key Actions
|
||||
|
||||
| Action | Behavior |
|
||||
| --- | --- |
|
||||
| Reset host MCU | Pull `MCU_RST` low, hold for about 5ms, then release (pull high), causing the host MCU to restart |
|
||||
| Exit ISP | Stop the auto-exit timer → end the ISP state → pull `MCU_BOOT0` low → reset the host MCU |
|
||||
|
||||
---
|
||||
|
||||
## 3. Button Actions and Timing
|
||||
|
||||
### 3.1 Three Core Actions
|
||||
|
||||
| Scenario | Trigger Condition | Result |
|
||||
| --- | --- | --- |
|
||||
| ① Long press to enter ISP / reset (non-ISP mode) | Long press exceeding **6 seconds** | See the "USB connected?" branch below |
|
||||
| ② Long press to exit ISP (ISP mode) | Long press exceeding **3 seconds** | Exit ISP, host MCU resets back to normal operation |
|
||||
| ③ Idle auto-exit ISP (ISP mode) | No button operation for more than **5 minutes** | Automatically exit ISP, host MCU resets |
|
||||
|
||||
> The business logic of this chip currently only handles **long-press events**, not short-press events.
|
||||
> The timing may have **errors** and is not entirely accurate; this is caused by the precision of this chip's internal oscillator.
|
||||
|
||||
### 3.2 USB Branch of Action ①
|
||||
|
||||
When a long press exceeds 6 seconds in non-ISP mode:
|
||||
|
||||
- **USB connected** (`USB_VBUS` high): first pull `MCU_BOOT0` high, then reset the host MCU → the host MCU enters **ISP (programming) mode**;
|
||||
- **USB not connected** (`USB_VBUS` low): only reset the host MCU (equivalent to a **restart**), without entering ISP.
|
||||
|
||||
### 3.3 Timing Parameter Summary
|
||||
|
||||
| Parameter | Value | Meaning |
|
||||
| --- | --- | --- |
|
||||
| Button debounce | 10ms | Duration for stable button-state determination |
|
||||
| Timing base | 100ms | Minimum timing unit for long-press / idle duration |
|
||||
| Non-ISP long-press threshold | 6 seconds | Long-press threshold in non-ISP mode |
|
||||
| ISP long-press exit threshold | 3 seconds | Long-press exit threshold in ISP mode |
|
||||
| ISP idle timeout | 5 minutes | Idle auto-exit duration in ISP mode |
|
||||
|
||||
---
|
||||
|
||||
## 4. Effects of Various Conditions on Button Business Logic
|
||||
|
||||
### 4.1 Key Conditions Affecting Button Behavior
|
||||
|
||||
The final behavior of the button is jointly determined by the following three conditions:
|
||||
|
||||
1. **Whether the device is currently in ISP mode**;
|
||||
2. **Whether USB is connected** (`USB_VBUS`);
|
||||
3. **Which processing stage the button is currently in**.
|
||||
|
||||
### 4.2 Decision Table
|
||||
|
||||
**Non-ISP mode:**
|
||||
|
||||
| Button State | Duration | USB | Action |
|
||||
| --- | --- | --- | --- |
|
||||
| Long-pressing | Released before reaching 6 seconds | — | Cancelled, no action |
|
||||
| Long-pressing | Exceeds 6 seconds | Connected | Enter ISP mode (pull `MCU_BOOT0` high, then reset) |
|
||||
| Long-pressing | Exceeds 6 seconds | Not connected | Only reset the host MCU |
|
||||
|
||||
**ISP mode:**
|
||||
|
||||
| Button State | Duration | Action |
|
||||
| --- | --- | --- |
|
||||
| Long-pressing | Exceeds 3 seconds | Exit ISP (pull `MCU_BOOT0` low, then reset) |
|
||||
| No press | Idle for more than 5 minutes | Automatically exit ISP |
|
||||
| Holding | Any | ISP idle timing paused (not counted toward timeout) |
|
||||
|
||||
### 4.3 Button Processing Stage State Machine
|
||||
|
||||
```mermaid
|
||||
stateDiagram-v2
|
||||
[*] --> Released
|
||||
Released --> Pressed : stable press (debounce passed)
|
||||
Pressed --> LongPressTriggered : threshold reached (6s or 3s)
|
||||
Pressed --> Released : released (before threshold, cancelled)
|
||||
LongPressTriggered --> Released : released
|
||||
```
|
||||
|
||||
### 4.4 Two Important Details
|
||||
|
||||
1. **After entering ISP, you must "release and then long-press again" to exit**: the long press used to enter ISP has already been marked as "processed" for that press. Therefore, to exit ISP via long press, you must **first release the button**, and then **long-press again for 3 seconds**.
|
||||
|
||||
2. **Starting point of the 5-minute idle timeout**: when entering ISP, the idle timing is cleared, but it only accumulates while the button is in the "released" state. Therefore, the 5-minute timeout actually begins counting **from the moment the button is released after entering ISP**; while the button is held, the timeout timing is paused.
|
||||
|
||||
---
|
||||
|
||||
## 5. Detailed Flowcharts
|
||||
|
||||
### 5.1 Overall Power-on Flow
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
A([Power-on startup]) --> B[Power-on initialization]
|
||||
B --> C{Factory test mode detection}
|
||||
C -->|Reset signal pulled low within 10ms after power-on, and held for more than 100ms| D[Enter factory ISP mode]
|
||||
D --> E{USB disconnected?}
|
||||
E -->|No| E
|
||||
E -->|Yes| F[Exit ISP, reset host MCU]
|
||||
F --> G[Enter operating-mode main loop]
|
||||
C -->|No| G
|
||||
```
|
||||
|
||||
### 5.2 Factory Test Mode Detection Flow
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
S([Start detection]) --> A[Begin monitoring the reset signal]
|
||||
A --> B{Within 10ms of power-on<br>was the reset signal pulled low?}
|
||||
B -->|No, held high within 10ms| R1[Do not enter factory mode, return]
|
||||
B -->|Yes| C{Reset signal held low<br>for more than 100ms?}
|
||||
C -->|No, recovered high early| R2[Do not enter factory mode, return]
|
||||
C -->|Yes| D[Wait for reset signal to release high]
|
||||
D --> E[Wait another 100ms]
|
||||
E --> F[Pull boot mode signal high, reset host MCU<br>enter ISP programming mode]
|
||||
F --> G{USB disconnected?}
|
||||
G -->|No| G
|
||||
G -->|Yes| H[Pull boot mode signal low, reset host MCU]
|
||||
H --> I([Return, enter operating mode])
|
||||
```
|
||||
|
||||
### 5.3 Operating-mode Main Loop Flow
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
L([Loop start]) --> RD[Read button level]
|
||||
RD --> DB[Delay 10ms debounce]
|
||||
DB --> P{Button stably pressed?}
|
||||
P -->|Yes| S0{First press<br>and long-press timing not started?}
|
||||
S0 -->|Yes| S1[Enter long-press detection<br>clear button timing and start timing]
|
||||
S0 -->|No| REL
|
||||
S1 --> REL
|
||||
P -->|No| REL{Button stably released?}
|
||||
REL -->|Yes, and a prior button processing exists| RA[Stop timing when not in ISP<br>clear button timing<br>reset button processing stage]
|
||||
RA --> L1
|
||||
REL -->|No| L1
|
||||
L1{Not in ISP and long-press timing exceeds 6 seconds?}
|
||||
L1 -->|Yes| S2[Mark this long press as processed<br>stop timing]
|
||||
S2 --> USB{USB connected?}
|
||||
USB -->|Yes| EI[Pull boot mode signal high<br>enter ISP mode]
|
||||
EI --> RST[Reset host MCU]
|
||||
USB -->|No| RST
|
||||
RST --> RT{Entered ISP mode?}
|
||||
RT -->|Yes| TO[Clear idle timing<br>start idle timeout timing]
|
||||
RT -->|No| L2
|
||||
TO --> L2
|
||||
L1 -->|No| L2
|
||||
L2{In ISP and long-press timing exceeds 3 seconds?}
|
||||
L2 -->|Yes| X[Mark this long press as processed<br>exit ISP]
|
||||
X --> L3
|
||||
L2 -->|No| L3
|
||||
L3{In ISP and no button press<br>and idle timing exceeds 5 minutes?}
|
||||
L3 -->|Yes| X2[Exit ISP]
|
||||
X2 --> L
|
||||
L3 -->|No| L
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 6. Typical Operation Scenarios
|
||||
|
||||
### 6.1 Enter ISP to Flash Firmware
|
||||
|
||||
1. Confirm that USB is connected (`USB_VBUS` high);
|
||||
2. Long-press the button for **more than 6 seconds**;
|
||||
3. The host MCU is reset and enters ISP (programming) mode, at which point firmware can be flashed via the host PC.
|
||||
|
||||
### 6.2 Exit ISP and Return to Normal Operation
|
||||
|
||||
- **Manual exit**: first release the button, then long-press again for **more than 3 seconds**;
|
||||
- **Automatic exit**: keep 5 minutes without button operation, and ISP is exited automatically.
|
||||
|
||||
### 6.3 Manually Restart the Host MCU
|
||||
|
||||
- Without USB connected, long-press the button for **more than 6 seconds**; the host MCU will be reset (restarted) without entering ISP.
|
||||
|
||||
### 6.4 Production-line Flashing (Factory Test Mode)
|
||||
|
||||
- Within **10ms** after power-on, pull the host MCU reset line low and hold it for **more than 100ms**;
|
||||
- This chip and the host MCU enter factory ISP mode and remain there until **USB is disconnected**, after which the host MCU is automatically reset back to normal operation mode.
|
||||
|
||||
---
|
||||
|
||||
## 7. FAQ and Notes
|
||||
|
||||
| Question | Explanation |
|
||||
| --- | --- |
|
||||
| No ISP entry after a long press? | Confirm whether USB is connected; without a connection, a long press only restarts the host MCU. |
|
||||
| Once in ISP, a continuous long press cannot exit? | You must first release the button, then long-press again for 3 seconds (the long press that entered ISP does not re-trigger the exit). |
|
||||
| How is the long-press time calculated? | Timing starts from when the button is stably recognized as pressed, and is cleared if released midway. |
|
||||
| Does ISP exit automatically? | Yes. If there is no button operation within 5 minutes after entering ISP, it exits and resets automatically. |
|
||||
| The timing seems inaccurate? | That is expected, because this chip's internal oscillator is not highly precise and may have errors. |
|
||||
|
||||
---
|
||||
|
||||
## Appendix
|
||||
|
||||
### Appendix A: Timing Parameter Summary
|
||||
|
||||
| Parameter | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| Debounce time | 10ms | Stable determination of button state |
|
||||
| Non-ISP long-press threshold | 6 seconds | Triggers reset or ISP entry when exceeded |
|
||||
| ISP long-press exit threshold | 3 seconds | Exits ISP when exceeded |
|
||||
| ISP idle timeout | 5 minutes | Auto-exit ISP with no button operation |
|
||||
| Reset pulse width | About 5ms | Low-level time required to reset the host MCU |
|
||||
|
||||
> Note: the times described above are not highly precise.
|
||||
|
||||
### Appendix B: Glossary
|
||||
|
||||
| Term | Meaning |
|
||||
| --- | --- |
|
||||
| This chip | The button controller chip, the subject of this manual |
|
||||
| Host MCU | The target chip managed by this chip, which runs the main application firmware |
|
||||
| ISP | In-System Programming, used to update the host firmware |
|
||||
| Long press | A button held down continuously beyond the configured threshold |
|
||||
@@ -0,0 +1,350 @@
|
||||
# RGB Controller Technical Manual
|
||||
|
||||
> This document is intended for host-side (Host) development and integration personnel. It describes the I2C communication interface, register model, and business behavior provided by this chip.
|
||||
> This document describes only the **externally visible interface and business logic**.
|
||||
|
||||
- Author: DXL
|
||||
- Document version: v1.0
|
||||
- Date: 2026-08-25
|
||||
|
||||
---
|
||||
|
||||
## 1. Overview
|
||||
|
||||
This chip acts as an **I2C slave** and drives a chain of single-wire, daisy-chained RGB LEDs. The host sends LED color data and configuration commands to the chip over the I2C bus; the chip maintains a color buffer internally and automatically, continuously refreshes the data onto the LED strip.
|
||||
|
||||
Core capabilities:
|
||||
|
||||
| Capability | Description |
|
||||
|------|------|
|
||||
| Color setting | Set the RGB888 color value of each LED individually |
|
||||
| Index management | Supports setting a start index, automatic index increment, and index locking |
|
||||
| One-command lights off | Turn off all LEDs with a single command |
|
||||
| Controllable blink | Hardware-timed on/off flashing, freeing the host CPU |
|
||||
| Firmware version | Reads the firmware major/minor version for compatibility adaptation |
|
||||
|
||||
---
|
||||
|
||||
## 2. I2C Communication Interface
|
||||
|
||||
### 2.1 Slave Address
|
||||
|
||||
The chip supports selecting the slave address via the level state of an **address-select pin**:
|
||||
|
||||
| Address-select pin state | 7-bit slave address | Remarks |
|
||||
|----------------|--------------|------|
|
||||
| High level (tied to VCC) | `0x48` | Currently available |
|
||||
| Low level (tied to GND) | `0x49` | Currently available |
|
||||
| Tied to SCL | `0x68` | Reserved, not yet enabled |
|
||||
| Tied to SDA | `0x69` | Reserved, not yet enabled |
|
||||
|
||||
> Note: the address-select pin performs a level detection with debounce during the **power-on initialization phase**; a high level uses `0x48`, a low level uses `0x49`.
|
||||
> The two dynamic-detection schemes "tied to SCL / tied to SDA" in the table are currently reserved designs that are not yet enabled in the actual firmware — do not rely on them.
|
||||
|
||||
### 2.2 Register Addressing Method (Register Pointer)
|
||||
|
||||
The chip uses the "register pointer" addressing method: **before every operation, one byte of register address must be written first**. Once the chip remembers this address, subsequent reads and writes target that register.
|
||||
|
||||
- **Write operation**: when writing the data body, byte 1 is the register address, and the subsequent bytes are that register's data.
|
||||
- **Read operation**: you must **first perform a write operation** (writing only 1 byte of register address) to set the target register, then initiate the read operation.
|
||||
|
||||
> Key point: the register address is **retained across transactions**. The register address set by the previous write operation remains valid in subsequent read transactions until the next write operation writes a new register address.
|
||||
|
||||
### 2.3 Read/Write Operation Timing
|
||||
|
||||
**Write register:**
|
||||
|
||||
```
|
||||
START → 7-bit address + W(0) → ACK → [register address] → [data bytes…] → STOP
|
||||
```
|
||||
|
||||
**Read register:**
|
||||
|
||||
```
|
||||
Step 1 (set pointer): START → 7-bit address + W(0) → ACK → [register address] → STOP
|
||||
Step 2 (read data) : START → 7-bit address + R(1) → ACK → [data bytes…] → host NACK → STOP
|
||||
```
|
||||
|
||||
### 2.4 Recommended Communication Rate
|
||||
|
||||
It is recommended to use a communication clock rate of **around 10K**; an excessively high rate may cause communication failures.
|
||||
|
||||
### 2.5 Abnormal Acknowledge (NACK) Behavior
|
||||
|
||||
The chip replies NACK and terminates the current communication in the following cases:
|
||||
|
||||
| Case | Description |
|
||||
|------|------|
|
||||
| Address mismatch | The received 7-bit address differs from the configured slave address |
|
||||
| Reading an invalid address | A read operation is initiated when no register address has been set (default `0x00`) |
|
||||
| Reading a write-only register | Reading the lights-off register (`0x04`) |
|
||||
| Writing a read-only register | Writing the firmware version register (`0xFF`) |
|
||||
| Writing an invalid address | The register address is `0x00` |
|
||||
| Index out of range | The written index value ≥ the current valid LED count |
|
||||
|
||||
---
|
||||
|
||||
## 3. Register Map
|
||||
|
||||
### 3.1 Register Overview Table
|
||||
|
||||
| Address | Name | Access | Data Length | Description |
|
||||
|------|------|------|----------|------|
|
||||
| `0x00` | Invalid address | — | — | Power-on default address; not readable or writable |
|
||||
| `0x01` | Count register | Read / Write | 1 byte | Number of LEDs actually mounted on the hardware |
|
||||
| `0x02` | Index register | Read / Write | 1 byte | Index of the LED currently being operated on |
|
||||
| `0x03` | Data register | Read / Write | 3×N bytes | LED color value (RGB888) |
|
||||
| `0x04` | Lights-off register | Write-only | No data body | Turn off all LEDs |
|
||||
| `0x05` | Index lock register | Read / Write | 1 byte | Whether to lock the operation index |
|
||||
| `0x06` | Blink enable register | Read / Write | 1 byte | Whether to enable controllable blink |
|
||||
| `0x07` | Blink duration register | Read / Write | 2 bytes | On duration + off duration |
|
||||
| `0xFF` | Firmware version register | Read-only | 2 bytes | Major version + minor version |
|
||||
|
||||
### 3.2 Register Detailed Descriptions
|
||||
|
||||
#### 0x00 — Invalid Address (Reserved)
|
||||
|
||||
Power-on default value. No read operation can be performed at this address; writing this address causes NACK and terminates the communication.
|
||||
|
||||
#### 0x01 — Count Register (Read/Write)
|
||||
|
||||
Indicates the number of LEDs actually mounted on the current hardware.
|
||||
|
||||
- **Write**: writes 1 byte. If multiple bytes are written, the **last byte** takes effect. If the written value exceeds the chip's supported upper limit, it is **clamped** to the upper limit.
|
||||
- **Read**: returns the current valid LED count.
|
||||
- **Default**: the chip's supported upper-limit count after power-on.
|
||||
|
||||
#### 0x02 — Index Register (Read/Write)
|
||||
|
||||
Indicates the LED index to be operated on (starting from 0).
|
||||
|
||||
- **Write**: writes 1 byte. If multiple bytes are written, the last byte takes effect. If the written value ≥ the current valid LED count, it is an illegal operation; the chip replies NACK and terminates the communication.
|
||||
- **Read**: returns the current operation index.
|
||||
- **Side effect**: writing **triggers blink disable**.
|
||||
- **Constraint**: the legal index range is `0 ~ (valid count - 1)`.
|
||||
|
||||
#### 0x03 — Data Register (Read/Write)
|
||||
|
||||
LED color data. **Every 3 bytes is the RGB888 color value of one LED**, in the byte order **R, G, B**.
|
||||
|
||||
- **Write**: writes a multiple of 3 bytes consecutively. Each time 3 bytes (one complete LED) are written, the index auto-increments by 1 (unless locked, see `0x05`).
|
||||
- **Read**: reads consecutively; every 3 bytes returns one LED's R, G, B, and the index auto-increments by 1.
|
||||
- **Index wraparound**: when the index increments to the valid count, it resets to zero, enabling circular read/write of the buffer.
|
||||
- **Persistence**: the index does **not** reset to zero after communication ends; the next operation continues from the current index.
|
||||
- **Side effect**: both read and write **trigger blink disable**.
|
||||
|
||||
> Example: after setting count = 8 and index = 0, writing 24 bytes (8 LEDs) each time covers the entire LED strip.
|
||||
|
||||
#### 0x04 — Lights-off Register (Write-only)
|
||||
|
||||
Turns off all LEDs (all colors set to R0-G0-B0).
|
||||
|
||||
- **Write**: no data body required; writing triggers it.
|
||||
- **Read**: not supported; reading causes NACK.
|
||||
- **Deferred effect**: the lights-off action actually executes after the current I2C communication **ends (STOP)**.
|
||||
- **Side effect**: also disables blink.
|
||||
- **Note**: after writing, allow about **10ms** to ensure the lights-off completes; if the data or index register is written again during this period, the lights-off may fail (color disorder or some LEDs not properly turned off).
|
||||
|
||||
#### 0x05 — Index Lock Register (Read/Write)
|
||||
|
||||
Controls whether the index auto-increments when writing the data register.
|
||||
|
||||
- **Write**: writing `0` means unlocked (index auto-increments when writing data); writing a non-`0` value means locked (index does not increment when writing data).
|
||||
- **Read**: returns the current lock state (`0` / `1`).
|
||||
- **Purpose**: when locked, it is suitable for repeatedly writing data commands to **refresh a single LED** (index unchanged).
|
||||
- **Note**: locking affects only the index auto-increment of **write** operations; the index of **read** operations still increments.
|
||||
|
||||
#### 0x06 — Blink Enable Register (Read/Write)
|
||||
|
||||
Controls the controllable blink function.
|
||||
|
||||
- **Write**: writing a non-`0` value enables blink (blink applies to the LED selected by the current index); writing `0` disables blink.
|
||||
- **Read**: returns the current enable state (`0` / `1`).
|
||||
- **Blink behavior**: once enabled, the selected LED automatically cycles through "on duration → off duration → on duration…".
|
||||
- **Mutual exclusion**: see Section 4.
|
||||
|
||||
#### 0x07 — Blink Duration Register (Read/Write)
|
||||
|
||||
Sets the on and off durations of the blink.
|
||||
|
||||
- **Write**: byte 1 is the **on duration**, byte 2 is the **off duration**.
|
||||
- **Read**: returns the on duration and off duration bytes in sequence.
|
||||
- **Unit**: both are 10ms; a single byte ranges from 0 to 255, i.e., up to 2.55 seconds can be set.
|
||||
- **Default**: 500ms each for on and off.
|
||||
|
||||
#### 0xFF — Firmware Version Register (Read-only)
|
||||
|
||||
- **Read**: byte 1 is the major version, byte 2 is the minor version.
|
||||
- **Write**: not supported; writing causes NACK.
|
||||
- **Purpose**: it is recommended that the host read the firmware version during specific flows, so that when compatibility issues arise they can be adapted and fixed accordingly.
|
||||
|
||||
---
|
||||
|
||||
## 4. Register Mutual Exclusion Conditions
|
||||
|
||||
Controllable blink (after `0x06` is enabled) is **mutually exclusive** with the following operations; performing these operations **automatically disables blink**:
|
||||
|
||||
| Triggering operation | Register | Disables blink? |
|
||||
|----------|--------|--------------|
|
||||
| Write index | `0x02` | ✅ Yes |
|
||||
| Write data | `0x03` | ✅ Yes |
|
||||
| Read data | `0x03` | ✅ Yes |
|
||||
| Write lights-off | `0x04` | ✅ Yes (and turns off all LEDs) |
|
||||
| Write blink enable (value 0) | `0x06` | ✅ Yes |
|
||||
|
||||
> Design rationale: blink applies to the "LED selected by the current index", while index, data, and lights-off operations all change that LED's state, conflicting with blink. Therefore blink must be disabled first before performing these operations.
|
||||
|
||||
**Other read/write restrictions (mutual exclusion / constraints)**:
|
||||
|
||||
| Restriction | Description |
|
||||
|------|------|
|
||||
| `0x04` write-only | Reading causes NACK |
|
||||
| `0xFF` read-only | Writing causes NACK |
|
||||
| `0x00` invalid | Both reading and writing cause NACK |
|
||||
| Index out of range | Writing an index ≥ valid count causes NACK |
|
||||
| Count clamping | Writing a count above the upper limit is clamped to the upper limit |
|
||||
|
||||
---
|
||||
|
||||
## 5. Business Flowcharts
|
||||
|
||||
### 5.1 Power-on Initialization Flow
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
A([Power-on reset]) --> B[Controller internal initialization]
|
||||
B --> C[RGB initialization<br/>clear color buffer<br/>turn off all LEDs by default]
|
||||
C --> D[Blink timer initialization<br/>default on/off 500ms each]
|
||||
D --> E[I2C slave initialization]
|
||||
E --> F{Address-select pin<br/>level detection and debounce}
|
||||
F -->|High level| G[Slave address = 0x48]
|
||||
F -->|Low level| H[Slave address = 0x49]
|
||||
G --> I[Enter main loop]
|
||||
H --> I
|
||||
```
|
||||
|
||||
### 5.2 Main Loop Overall Flow
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
A([Main loop entry]) --> B[Sample I2C bus<br/>detect SCL / SDA transitions]
|
||||
B --> C{SCL transition?}
|
||||
C -->|Yes| D[I2C state machine handling]
|
||||
C -->|No| E{SDA transition?}
|
||||
E -->|Yes| F[START / STOP signal handling]
|
||||
E -->|No| G[Cache bus state]
|
||||
D --> G
|
||||
F --> G
|
||||
G --> H{10ms timer reached?}
|
||||
H -->|Yes| I[Blink timing accumulation +1]
|
||||
H -->|No| K{I2C communication in progress?}
|
||||
I --> K
|
||||
K -->|Yes| A
|
||||
K -->|No| L{Waiting for strip reset?}
|
||||
L -->|Yes| A
|
||||
L -->|No| M[Blink on / off switching decision]
|
||||
M --> N{Data updated?}
|
||||
N -->|No| A
|
||||
N -->|Yes| O[Refresh LED colors]
|
||||
O --> A
|
||||
```
|
||||
|
||||
### 5.3 I2C Communication State Machine
|
||||
|
||||
```mermaid
|
||||
stateDiagram-v2
|
||||
[*] --> IDLE
|
||||
IDLE --> ADDR: START received
|
||||
ADDR --> OP: 7-bit address matches
|
||||
ADDR --> IDLE: address mismatch
|
||||
OP --> IACK1: parse read/write bit and prepare response
|
||||
IACK1 --> IACK2: SCL falling edge
|
||||
IACK2 --> WRITEDATA: write operation
|
||||
IACK2 --> READDATA: read operation
|
||||
WRITEDATA --> WACK1: 8 bits received
|
||||
WACK1 --> WACK2: SCL falling edge
|
||||
WACK2 --> WRITEDATA: continue receiving
|
||||
READDATA --> RACK: 8 bits sent
|
||||
RACK --> READDATA: host ACK received
|
||||
RACK --> IDLE: host NACK received
|
||||
WRITEDATA --> IDLE: STOP received
|
||||
READDATA --> IDLE: STOP received
|
||||
```
|
||||
|
||||
### 5.4 Write Operation Data Flow
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
A([Host write operation]) --> B[START + address + write bit]
|
||||
B --> C[Slave replies ACK]
|
||||
C --> D[Receive byte 1 = register address]
|
||||
D --> E{Address valid?}
|
||||
E -->|Invalid 0x00| F[Reply NACK to terminate]
|
||||
E -->|Valid| G[Save register address]
|
||||
G --> H[Receive subsequent data bytes]
|
||||
H --> I[Write by register type<br/>count / index / data / lock / blink …]
|
||||
I --> J[STOP]
|
||||
J --> K[Execute deferred actions<br/>lights off / disable blink]
|
||||
K --> L([Done])
|
||||
```
|
||||
|
||||
### 5.5 Read Operation Data Flow
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
A([Read operation preamble]) --> B[First write 1 byte to set register address]
|
||||
B --> C[START + address + read bit]
|
||||
C --> D{Register readable?}
|
||||
D -->|0x00 or 0x04| E[Reply NACK to terminate]
|
||||
D -->|Readable| F[Slave ACK]
|
||||
F --> G[Return data per current register<br/>multi-byte registers auto-advance]
|
||||
G --> H{Host continues reading?}
|
||||
H -->|ACK| G
|
||||
H -->|NACK + STOP| I([End])
|
||||
```
|
||||
|
||||
### 5.6 Blink On/Off Logic
|
||||
|
||||
```mermaid
|
||||
flowchart TD
|
||||
A[Blink enabled<br/>refreshed to target LED] --> B{Currently in on phase?}
|
||||
B -->|Yes| C{On duration reached?}
|
||||
C -->|Yes| D[Switch to off<br/>set color to 0<br/>restart timing]
|
||||
C -->|No| E[Keep waiting]
|
||||
B -->|No| F{Off duration reached?}
|
||||
F -->|Yes| G[Switch to on<br/>take color from buffer<br/>restart timing]
|
||||
F -->|No| H[Keep waiting]
|
||||
D --> A
|
||||
G --> A
|
||||
```
|
||||
|
||||
---
|
||||
|
||||
## 6. Key Business Feature Summary
|
||||
|
||||
1. **Deferred effect of changes**: actions such as lights-off and blink-disable are not executed immediately when the command arrives; instead they are processed uniformly **after the I2C communication ends (STOP)**, avoiding refresh operations interfering with bus communication stability.
|
||||
|
||||
2. **Index management**:
|
||||
- When writing data, the index auto-increments after every 3 bytes (lockable).
|
||||
- When reading data, the index always auto-increments.
|
||||
- The index wraps around to 0 after reaching the valid count.
|
||||
- The index is retained across transactions and does not reset when communication ends.
|
||||
|
||||
3. **Data refresh mechanism**: when data changes, a refresh-enable flag is set, and the main loop refreshes all LEDs once in a **full pass**; when there is no change, it refreshes only once, avoiding unnecessary refresh overhead.
|
||||
|
||||
4. **Blink frees the host**: blink is driven by the chip's internal timer; the host only needs to set the on/off durations and enable it, without continuously sending commands, thereby freeing the host CPU.
|
||||
|
||||
5. **Safety protection**:
|
||||
- Out-of-range protection: a count above the upper limit is automatically clamped; an out-of-range index returns NACK.
|
||||
- Communication priority: while I2C communication is in progress, LED refresh is skipped, reducing the probability of communication failure.
|
||||
|
||||
---
|
||||
|
||||
## 7. Usage Notes
|
||||
|
||||
1. It is recommended that the host first read the firmware version register (`0xFF`) after power-on, to adapt when compatibility issues arise.
|
||||
2. After executing lights-off (`0x04`), allow about 10ms; do not write the data/index register during this period.
|
||||
3. After setting the count (`0x01`), the legal range of the index (`0x02`) changes accordingly; be careful to avoid out-of-range writes.
|
||||
4. Before using the blink function, confirm that the current index points to the target LED; index/data/lights-off operations disable blink.
|
||||
5. It is recommended to keep the communication rate at around 10K; an excessively high rate may cause communication failures.
|
||||
6. The current slave address supports only two static selections, `0x48` (high level) and `0x49` (low level); `0x68`/`0x69` are reserved.
|
||||
Reference in new issue
Block a user