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).
This commit is contained in:
Vendored
+6
@@ -0,0 +1,6 @@
|
||||
EA/AA on http://127.0.0.1:8092/ (ea/enrolment, aa/authorization), EC store C:\bachelorthesis_micrOBU\implementation\external\vanetza-idf\build-host-sec\pki-demo\http_issued
|
||||
3666B72008FC582D HashedId8 3666B72008FC582D -> http_issued/3666B72008FC582D.oer
|
||||
EnrolmentResponse written: 314 octets -> C:\Users\nikla\AppData\Local\Temp\tmpssj1vf9b\response.bin
|
||||
127.0.0.1 "POST /ea/enrolment HTTP/1.1" 200 -
|
||||
AuthorizationResponse written: 306 octets -> C:\Users\nikla\AppData\Local\Temp\tmphrzvtqg0\response.bin
|
||||
127.0.0.1 "POST /aa/authorization HTTP/1.1" 200 -
|
||||
Reference in New Issue
Block a user