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).
24 lines
714 B
C++
24 lines
714 B
C++
#include <vanetza/asn1/cam.hpp>
|
|
#include <vanetza/asn1/cpm.hpp>
|
|
#include <vanetza/asn1/denm.hpp>
|
|
#include <vanetza/asn1/ivim.hpp>
|
|
#include <vanetza/asn1/mapem.hpp>
|
|
#include <vanetza/asn1/rtcmem.hpp>
|
|
#include <vanetza/asn1/spatem.hpp>
|
|
#include <vanetza/asn1/srem.hpp>
|
|
#include <vanetza/asn1/ssem.hpp>
|
|
#include <vanetza/asn1/vam.hpp>
|
|
|
|
// just make sure wrappers are compilable
|
|
static vanetza::asn1::Cam cam;
|
|
static vanetza::asn1::Cpm cpm;
|
|
static vanetza::asn1::Denm denm;
|
|
static vanetza::asn1::Ivim ivim;
|
|
static vanetza::asn1::Mapem mapem;
|
|
static vanetza::asn1::Rtcmem rtcmem;
|
|
static vanetza::asn1::Spatem spatem;
|
|
static vanetza::asn1::Srem srem;
|
|
static vanetza::asn1::Ssem ssem;
|
|
static vanetza::asn1::r2::Vam vam;
|
|
|