Ashin Walpola
0e9525162d
obu-firmware builds against vanetza-idf from microbu-esp32c5/external, but that tree was gitignored, so a clone of this repository could not build the firmware it ships. It is now committed here as ordinary files in its own folder, microbu-esp32c5/: the colleague's commit cf4b99f plus the V2X2MAP bridge's signature verification (--trust) used on the bench. Nothing is fetched from or pushed to the colleague's repository; this repository and its remotes carry everything. The folder's own .gitignore keeps build output, downloaded components and private key material out, as it did there; the committed file set is identical to that repository's tracked files. The ESP32-C5 is still flashed from obu-firmware/, which only takes vanetza-idf from microbu-esp32c5/, so the two stay separate folders. FLASHING.md says how to take a newer version of the colleague's tree (copy it over the folder, rebuild, test, commit).
15 lines
1.2 KiB
JSON
15 lines
1.2 KiB
JSON
{
|
|
"kind": "component-tests",
|
|
"target": "esp32c5",
|
|
"idf_version": "6.0.2",
|
|
"port": "COM11",
|
|
"status": "pass",
|
|
"reset": "none",
|
|
"checks": 747,
|
|
"backend": "BackendMbedTls (PSA Crypto, mbedTLS 4.1.0 of ESP-IDF 6.0.2) with CONFIG_MBEDTLS_HARDWARE_ECDSA_VERIFY; 747 checks = 873 host checks minus the OpenSSL-only oracle tests",
|
|
"capture": "listen-only after the esptool post-flash reset",
|
|
"verifies": "receive-side verification (test_verification), the IEEE Std 1609.2 clause 5.1.2 chain consistency (test_chain_consistency) and the clause 6.4.17 region consistency under an identifiedRegion root (test_region_consistency) on the device; verification cost line: certificate-signed 35.5 ms, digest-signed 35.1 ms end to end, raw ECDSA P-256 verify 29.8 ms on the ECDSA peripheral",
|
|
"note": "the same checks appended to test_verification failed on the device only: with a fourth receiver trust configuration the heap was too fragmented (largest free block 16 kB) and an allocation failure inside verify() surfaced as INCOMPATIBLE_PROTOCOL through the catch-all; the chain and region scenarios therefore run as their own tests with a fresh heap and at most two stations alive",
|
|
"sha256": "20abb00efc091b27e7d43bf040967ffd808ca5a5e07d9ec6f0d3d9bee3cef7ec"
|
|
}
|