feat: identify the board and lock the technical baseline
This commit is contained in:
+32
-18
@@ -2,12 +2,11 @@
|
||||
|
||||
## Identification status
|
||||
|
||||
The target board has not been identified. No photograph of the physical
|
||||
markings is available in the repository, no `sources/` directory is present,
|
||||
and no serial device is exposed to the build environment. Consequently, the
|
||||
manufacturer, exact board model and revision, module variant, flash size,
|
||||
PSRAM, USB connection, built-in LED, and board-specific pinout cannot be
|
||||
confirmed without guessing.
|
||||
The target PCB has not been identified from physical markings. No photograph
|
||||
of the markings is available in the repository and no `sources/` directory is
|
||||
present. A read-only `esptool.py flash_id` probe did identify the installed SoC
|
||||
and flash, but it cannot identify the PCB manufacturer, board model/revision,
|
||||
built-in LED, or board-specific pinout.
|
||||
|
||||
Required evidence to unblock Milestone 000:
|
||||
|
||||
@@ -15,8 +14,22 @@ Required evidence to unblock Milestone 000:
|
||||
markings;
|
||||
- the manufacturer's product page, schematic, and pinout matching those
|
||||
markings;
|
||||
- the flash/module ordering code, or an `esptool.py flash_id` report from the
|
||||
connected board.
|
||||
- the PCB/model ordering code that matches the photographs.
|
||||
|
||||
## Confirmed electronically
|
||||
|
||||
On 2026-08-27, the board appeared as `/dev/ttyACM0` with USB VID:PID
|
||||
`303a:1001` and product name `Espressif USB JTAG/serial debug unit`.
|
||||
`esptool.py` 4.11.0 reported:
|
||||
|
||||
- ESP32-C6FH4 in QFN32, chip revision 0.2;
|
||||
- 4 MB embedded flash, with 4 MB detected;
|
||||
- 40 MHz crystal;
|
||||
- native USB-Serial/JTAG mode.
|
||||
|
||||
The ESP32-C6FH4 ordering code and probe establish the 4 MB in-package flash.
|
||||
No PSRAM was reported. These are chip-level facts; they do not establish the
|
||||
carrier PCB model or its LED and pin routing.
|
||||
|
||||
## Current repository baseline (not hardware confirmation)
|
||||
|
||||
@@ -28,12 +41,13 @@ Required evidence to unblock Milestone 000:
|
||||
| Arduino Core | Not installed | Cannot be pinned and verified against this board yet |
|
||||
| PlatformIO board | `esp32-c6-devkitm-1` | Unverified candidate, not evidence of the physical model |
|
||||
| Board-profile flash size | 4 MB | Unverified; profile metadata only |
|
||||
| Generated SDK flash size | 2 MB | Conflicts with the board profile |
|
||||
| Detected physical flash size | 4 MB | Confirmed by `esptool.py flash_id` |
|
||||
| Generated SDK flash size | 2 MB | Conflicts with the detected hardware and board profile |
|
||||
| Generated partition table | Single application, no LittleFS | Does not meet Milestone 000 |
|
||||
|
||||
The current configuration is not a safe flashing baseline. It must not be used
|
||||
to upload firmware until the physical flash size and board identity are
|
||||
confirmed.
|
||||
The current configuration is not yet a reproducible baseline: its generated
|
||||
SDK configuration must be changed from 2 MB to the confirmed 4 MB and its
|
||||
partition table must add LittleFS before firmware is uploaded.
|
||||
|
||||
## Candidate reference only
|
||||
|
||||
@@ -52,16 +66,16 @@ as the target specifications until the markings match.
|
||||
|
||||
## Memory map and partition status
|
||||
|
||||
No partition CSV has been selected because the physical flash capacity is
|
||||
unknown. The eventual layout must reserve, at minimum, NVS, PHY initialization,
|
||||
one application partition, and one LittleFS data partition, with offsets and
|
||||
sizes validated against the confirmed flash capacity. Selecting a 4 MB layout
|
||||
now could make flashing unsafe on a smaller device.
|
||||
No partition CSV has been selected yet. The confirmed 4 MB capacity permits a
|
||||
layout reserving, at minimum, NVS, PHY initialization, one application
|
||||
partition, and one LittleFS data partition. Exact offsets and sizes still need
|
||||
to be defined and checked against the framework's bootloader and partition
|
||||
alignment requirements.
|
||||
|
||||
## Risks carried to the next action
|
||||
|
||||
- A generic “ESP32-C6 Mini” may not match Espressif's DevKitM-1 pinout, LED
|
||||
polarity/type, USB bridge, or flash capacity.
|
||||
polarity/type, or USB bridge. The flash capacity is confirmed independently.
|
||||
- GPIO8, GPIO12, GPIO13, GPIO16, and GPIO17 must not be assigned from the
|
||||
candidate documentation until the exact board is confirmed.
|
||||
- Official `platformio/espressif32` 7.0.1 exposes the C6 DevKitM profile only
|
||||
|
||||
Reference in New Issue
Block a user