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:
@@ -47,11 +47,6 @@ sdkconfig.old
|
||||
# and remove them on close, so they are transient and machine-local.
|
||||
~$*
|
||||
|
||||
# Colleague's standalone ESP32-C5 VRU station (signed ITS via Vanetza). It is its
|
||||
# own git repository with its own history; kept beside the project as a reference
|
||||
# for porting the signed-TX path into obu-firmware, not tracked here.
|
||||
/microbu-esp32c5/
|
||||
|
||||
# Full-flash images read back off the bench boards before reflashing them (16 MB each).
|
||||
# Restore with: esptool --chip esp32c5 -p COM<N> write-flash 0 <image>
|
||||
/firmware-backups/
|
||||
|
||||
Reference in New Issue
Block a user