Keep the colleague's microbu-esp32c5 tree in this repository

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).
2026-09-23 17:46:40 +02:00
parent 2f60623e18
commit 0e9525162d
9881 changed files with 1582523 additions and 17 deletions
@@ -0,0 +1,7 @@
+{
+  "adapter_sha256": "091929148ecd8866d9a561fb41d7f7426a0db22cc4f81f397cf94cc76dee3ce3",
+  "binary_sha256": "253600e26949f935113a0c122d0f05ab04876fae96b1711d3be28e96bbc0a6a1",
+  "testcase_object_sha256": "e506d7762f0ce795943360eb5d685413aa70ae2059981d8b2949a30d3d32dd2d",
+  "testcase_source_sha256": "764fac9ba93c71ea8b6017f650242b1844d0c661cb058fbd7efa8b6b1f64e08b",
+  "scope": "Official BTP testcase objects; custom host/device SUT ports; no conformance verdict implied"
+}