Ashin Walpola
d107534eb2
obu-firmware builds against the vanetza-idf C-ITS library, which until now came from the colleague's microbu-esp32c5 tree beside the repository and was not tracked here, so a clone of this repository could not build the firmware it ships. The library alone is now part of obu-firmware, as obu-firmware/external/vanetza-idf: their external/vanetza-idf at commit cf4b99f, unchanged (9775 files; see its PROVENANCE.md). CMake takes it from there by default; -DVANETZA_IDF_DIR still points the build elsewhere. The rest of the colleague's tree (their own VAM firmware, PKI tooling, station-link Python tools, the V2X2MAP bridge) stays out of this repository and gitignored; nothing is pushed to their repository. NOTES.md, docs/06, TODO.md and the pcap verifier's usage line point at the new location.
19 lines
1.0 KiB
JSON
19 lines
1.0 KiB
JSON
{
|
|
"kind": "component-tests",
|
|
"target": "esp32c5",
|
|
"idf_version": "6.0.2",
|
|
"port": "COM11",
|
|
"status": "pass",
|
|
"reset": "none",
|
|
"checks": 537,
|
|
"backend": "BackendMbedTls (PSA Crypto); 537 checks = 663 host checks minus the OpenSSL-only oracle tests",
|
|
"capture": "listen-only after the esptool post-flash reset",
|
|
"verifies": "ROM UART0 clock repair moved from the test application's app_main into the component (ports/esp_idf/src/esp32c5_rom_uart_clock.c, ESP_SYSTEM_INIT_FN kept by -u): after this flash both boards (COM11, COM20) accepted a second esptool write-flash with --before default-reset; ITS time base helper (its_time.hpp) tested on the device",
|
|
"sha256": {
|
|
"application": "0e587898c3ec6b75741cadf235b62df523079976aa9c9d5c72cab0fe40b5d63b",
|
|
"bootloader": "93903cefa2bae3f5805a604ae744fabfdea78a866a1230ec3cc129190b93fe40",
|
|
"partition_table": "73c0b5c3e5fcba3a151cc70c453c93dd5f4798899e7f2f8cca76da1f32ffc501",
|
|
"sdkconfig": "caa03c6c8556d56b8ac848bc142ce68331b4a9cae3081590d4c7111338bc60a6"
|
|
}
|
|
}
|