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).
27 lines
753 B
C++
27 lines
753 B
C++
#ifndef DCC_PASSTHROUGH_HPP_GSDFESAE
|
|
#define DCC_PASSTHROUGH_HPP_GSDFESAE
|
|
|
|
#include "time_trigger.hpp"
|
|
#include <vanetza/access/interface.hpp>
|
|
#include <vanetza/dcc/data_request.hpp>
|
|
#include <vanetza/dcc/interface.hpp>
|
|
#include <vanetza/net/cohesive_packet.hpp>
|
|
|
|
class DccPassthrough : public vanetza::dcc::RequestInterface
|
|
{
|
|
public:
|
|
DccPassthrough(vanetza::access::Interface&, TimeTrigger& trigger);
|
|
|
|
void request(const vanetza::dcc::DataRequest& request, std::unique_ptr<vanetza::ChunkPacket> packet) override;
|
|
|
|
void allow_packet_flow(bool allow);
|
|
bool allow_packet_flow();
|
|
|
|
private:
|
|
vanetza::access::Interface& access_;
|
|
TimeTrigger& trigger_;
|
|
bool allow_packet_flow_ = true;
|
|
};
|
|
|
|
#endif /* DCC_PASSTHROUGH_HPP_GSDFESAE */
|