@@ -40,21 +40,21 @@ BLE and PBLE/1.
4040
4141The current pre-v1 browser bundle contains exactly these two
4242** provisioning image profiles** . The exact audited ` v0.4.2 ` bytes may be offered
43- only as the unqualified public beta defined in §10; they are not qualified
44- profiles.
43+ only as the hardware-tested public beta defined in §10; that narrow validation
44+ does not make them qualified-release profiles.
4545A later qualified public bundle uses the same exact profile definitions:
4646
47- | Profile ID | ESP Web Tools ` chipFamily ` | Required target configuration | ESP image silicon window (` min_chip_rev_full ` …` max_chip_rev_full ` ) | Merge settings | Browser image and component map |
48- | ---| ---| ---| ---| ---| ---|
49- | ` esp32-4mb ` | ` ESP32 ` | Classic ESP32 with 4 MiB external SPI flash; no PSRAM assumption | ` 0 ` …` 399 ` | DIO, 40 MHz, 4 MiB | merged ` firmware.bin ` at ` 0x1000 ` ; bootloader ` 0x1000 ` ; partition table ` 0x8000 ` ; application ` 0x10000 ` |
50- | ` esp32-s3-n16r8 ` | ` ESP32-S3 ` | ESP32-S3 with 16 MiB flash and 8 MiB ** Octal** PSRAM (N16R8-class) | ` 0 ` …` 99 ` | DIO, 80 MHz, 16 MiB | merged ` firmware.bin ` at ` 0x0000 ` ; bootloader ` 0x0000 ` ; partition table ` 0x8000 ` ; application ` 0x10000 ` |
47+ | Profile ID | ESP Web Tools ` chipFamily ` | Required target configuration | ESP image silicon window (` min_chip_rev_full ` …` max_chip_rev_full ` ) | Merge settings | Browser image and component map |
48+ | ---------------- | -------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------ | ------------------- | ------------------------------------------------------------------------------------------------------- |
49+ | ` esp32-4mb ` | ` ESP32 ` | Classic ESP32 with 4 MiB external SPI flash; no PSRAM assumption | ` 0 ` …` 399 ` | DIO, 40 MHz, 4 MiB | merged ` firmware.bin ` at ` 0x1000 ` ; bootloader ` 0x1000 ` ; partition table ` 0x8000 ` ; application ` 0x10000 ` |
50+ | ` esp32-s3-n16r8 ` | ` ESP32-S3 ` | ESP32-S3 with 16 MiB flash and 8 MiB ** Octal** PSRAM (N16R8-class) | ` 0 ` …` 99 ` | DIO, 80 MHz, 16 MiB | merged ` firmware.bin ` at ` 0x0000 ` ; bootloader ` 0x0000 ` ; partition table ` 0x8000 ` ; application ` 0x10000 ` |
5151
5252` esp32-c3-4mb ` remains a known provisioning profile and an initial v1
5353firmware target, with this frozen future qualification:
5454
55- | Deferred profile ID | ESP Web Tools ` chipFamily ` | Required target configuration | ESP image silicon window (` min_chip_rev_full ` …` max_chip_rev_full ` ) | Merge settings | Browser image and component map |
56- | ---| ---| ---| ---| ---| ---|
57- | ` esp32-c3-4mb ` | ` ESP32-C3 ` | ESP32-C3 revision v0.3 or newer with 4 MiB external flash; no PSRAM assumption | ` 3 ` …` 199 ` | DIO, 80 MHz, 4 MiB | merged ` firmware.bin ` at ` 0x0000 ` ; bootloader ` 0x0000 ` ; partition table ` 0x8000 ` ; application ` 0x10000 ` |
55+ | Deferred profile ID | ESP Web Tools ` chipFamily ` | Required target configuration | ESP image silicon window (` min_chip_rev_full ` …` max_chip_rev_full ` ) | Merge settings | Browser image and component map |
56+ | ------------------- | -------------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------- |
57+ | ` esp32-c3-4mb ` | ` ESP32-C3 ` | ESP32-C3 revision v0.3 or newer with 4 MiB external flash; no PSRAM assumption | ` 3 ` …` 199 ` | DIO, 80 MHz, 4 MiB | merged ` firmware.bin ` at ` 0x0000 ` ; bootloader ` 0x0000 ` ; partition table ` 0x8000 ` ; application ` 0x10000 ` |
5858
5959That deferred profile is ** not** part of the current public release: it MUST
6060NOT have an entry in ` release.json ` , a public manifest or binary directory, or
@@ -246,6 +246,7 @@ block same-origin publication.
246246## 3. Same-origin, versioned layout
247247
248248The canonical public files are static and use this exact layout:
249+
249250``` text
250251https://pyble.dev/firmware/v<version>/
251252 release.json
@@ -330,9 +331,7 @@ one build for its owning profile. For example,
330331 "builds" : [
331332 {
332333 "chipFamily" : " ESP32-S3" ,
333- "parts" : [
334- { "path" : " firmware.bin" , "offset" : 0 }
335- ]
334+ "parts" : [{ "path" : " firmware.bin" , "offset" : 0 }]
336335 }
337336 ]
338337}
@@ -567,6 +566,7 @@ The following resolution rules are part of that fail-closed mapping:
567566 A missing file, unexpected basename, alternate or sibling retained tree,
568567 escaped path, near-match root, nonzero generated ELF anchor, or symlinked
569568 input is fatal.
569+
5705705 . A generated component archive has only a stable topology matcher in
571571 committed policy. An ordinary matcher contains exactly its ESP-IDF
572572 component name. A nested CMake archive produced below a ` CONFIG_ONLY `
@@ -683,6 +683,7 @@ The following resolution rules are part of that fail-closed mapping:
683683 observations. Rechecking only archive/tree digests is insufficient:
684684 project/compile/map/link documents, metadata inputs, archive sources, direct
685685 outputs, and direct sources are all race-sensitive release inputs.
686+
6866876 . An archive outside the repository and build roots is admitted only below
687688 one versioned toolchain root proven by the exact compile-command
688689 executables and the locked ESP-IDF ` tools/tools.json ` entry. The policy
@@ -732,6 +733,7 @@ The following resolution rules are part of that fail-closed mapping:
732733 only logical metadata, semantic hashes, constrained relative frontend/member
733734 paths, and distribution identity; they MUST NOT contain a host-absolute
734735 tools-home, cache, frontend, installed-root, or runtime path.
736+
7357377 . Each raw package is matched exactly once by profile/role and its complete
736738 raw property set, including name, version state, download-location state,
737739 copyright state, declared/concluded license states, checksums, annotations,
@@ -773,6 +775,7 @@ The following resolution rules are part of that fail-closed mapping:
773775 share the same SPDX ID in different profiles; a union expression MUST NOT
774776 be invented to make unlike occurrences share one review. Any unexpected
775777 property, value, package, relationship, resolution, or ambiguity is fatal.
778+
7767798 . A raw package that the pinned tool reports but that contributes no linked
777780 archive, compiled source, or aggregate project identity may be excluded
778781 from the redistribution notice only through an explicit ` not-shipped `
@@ -815,6 +818,7 @@ The following resolution rules are part of that fail-closed mapping:
815818 independent ledger says ` allow-aggregate ` . The receipt binds both the
816819 ` shipment_review ` policy record and the normalized occurrence
817820 classifications.
821+
8188229 . A redistributed dependency absent from the raw ESP-IDF package graph is a
819823 deterministic supplemental SPDX package, not misrepresented as raw tool
820824 output. In this release the exact frozen NeoPixel tree and the three linked
@@ -900,15 +904,16 @@ The following resolution rules are part of that fail-closed mapping:
900904 host-absolute path is retained. A source, metadata version, optimization
901905 level, module order, qstr header, ` .mpy ` , generator, compiler, architecture,
902906 copied-board byte, or frozen C mismatch is fatal.
903- 9 . Coverage is exact without asserting false package/archive cardinality.
904- Every observed raw package, linked archive, compiled source, frozen
905- destination, frozen source tree,
906- prebuilt blob, and compiler/runtime input is consumed by exactly one
907- resolution record; each record declares its complete many-to-many
908- package/input attribution, and aggregate packages may own no archive
909- directly only through rule 7. Every expected relationship is present, every
910- declared stable matcher is observed exactly where applicable, and no
911- unexpected record is accepted.
907+
908+ 10 . Coverage is exact without asserting false package/archive cardinality.
909+ Every observed raw package, linked archive, compiled source, frozen
910+ destination, frozen source tree,
911+ prebuilt blob, and compiler/runtime input is consumed by exactly one
912+ resolution record; each record declares its complete many-to-many
913+ package/input attribution, and aggregate packages may own no archive
914+ directly only through rule 7. Every expected relationship is present, every
915+ declared stable matcher is observed exactly where applicable, and no
916+ unexpected record is accepted.
912917
913918The initial runtime/input review explicitly includes ` libgcc.a ` and
914919` libstdc++.a ` under ` GPL-3.0-or-later WITH GCC-exception-3.1 ` ;
@@ -1114,16 +1119,16 @@ Candidate generation MUST read
11141119both its parsed JSON object and the lowercase SHA-256 of its exact source
11151120bytes. The policy object has exactly these keys:
11161121
1117- | Key | Exact value/type |
1118- | ---| ---|
1119- | ` schema_version ` | integer ` 1 ` |
1120- | ` qualification_scope ` | string ` "pre-v1" ` |
1121- | ` profile_order ` | exact string array ` ["esp32-4mb", "esp32-s3-n16r8"] ` |
1122- | ` deferred_profiles ` | exact string array ` ["esp32-c3-4mb"] ` |
1123- | ` workload ` | exact object defined below |
1124- | ` derivation ` | exact object defined below |
1125- | ` baseline_evidence ` | exact object ` {path, sha256} ` |
1126- | ` profiles ` | two policy-entry objects, in ` profile_order ` |
1122+ | Key | Exact value/type |
1123+ | --------------------- | ---------------------------------------------------- |
1124+ | ` schema_version ` | integer ` 1 ` |
1125+ | ` qualification_scope ` | string ` "pre-v1" ` |
1126+ | ` profile_order ` | exact string array ` ["esp32-4mb", "esp32-s3-n16r8"] ` |
1127+ | ` deferred_profiles ` | exact string array ` ["esp32-c3-4mb"] ` |
1128+ | ` workload ` | exact object defined below |
1129+ | ` derivation ` | exact object defined below |
1130+ | ` baseline_evidence ` | exact object ` {path, sha256} ` |
1131+ | ` profiles ` | two policy-entry objects, in ` profile_order ` |
11271132
11281133` workload ` has exactly these integer/string keys and values:
11291134
@@ -1493,7 +1498,7 @@ and a production smoke test of the disabled state; absence of staging input
14931498alone is never authorization to disable it.
14941499
14951500As a one-time transitional exception, the fresh audited ` v0.4.2 ` candidate MAY
1496- be published as an explicitly ** unqualified public beta** . The selector deployment
1501+ be published as a ** hardware-tested public beta** . The selector deployment
14971502mode MUST be ` public-beta ` , ` accessControlled ` MUST be ` false ` , both profile HIL
14981503states and the aggregate ` hilStatus ` MUST remain ` pending ` , and the
14991504` release.json ` SHA-256 MUST equal
@@ -1505,11 +1510,15 @@ license-evidence directory, its exact release-build root, and the exact
15051510firmware-source checkout recorded by the release as ` --repo-root ` . The annotated
15061511` firmware-v0.4.2 ` tag MUST exist and peel directly to the full PyBLE provenance
15071512commit recorded in ` release.json ` , and deployment MUST bind the tag object
1508- before and after the website build and before upload. Before the install control
1509- appears, the website MUST say that the exact bytes passed the audited-candidate
1510- release gate but have not passed the complete project HIL matrix, and that
1511- installation is at the user's risk. It MUST NOT call the beta access-controlled,
1512- protected, qualified, fully validated, or generally available.
1513+ before and after the website build and before upload. The exact production
1514+ browser-flashing validation recorded in
1515+ ` docs/validation/browser-flashing/v0.4.2-production.json ` supports the narrower
1516+ claim that real-board Chrome installation, interruption, recovery, and reset
1517+ passed for both enabled exact profiles. Before the install control appears, the
1518+ website MUST state that completed scope and MUST separately say that complete
1519+ release qualification remains pending. It MUST NOT call the beta
1520+ access-controlled, protected, a qualified release, fully validated,
1521+ production-ready, or generally available.
15131522
15141523The beta path MUST retain all existing audited-candidate, license, tag, schema,
15151524checksum, manifest, image, same-origin, browser-capability,
0 commit comments