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).
38 lines
814 B
C++
38 lines
814 B
C++
#ifndef ENTITY_HPP_KUAWS3PK
|
|
#define ENTITY_HPP_KUAWS3PK
|
|
|
|
#include <vanetza/dcc/channel_probe_processor.hpp>
|
|
#include <vanetza/dcc/transmit_rate_control.hpp>
|
|
|
|
namespace vanetza
|
|
{
|
|
namespace dcc
|
|
{
|
|
|
|
class Entity
|
|
{
|
|
public:
|
|
/**
|
|
* Provide TRC interface for Facilities
|
|
*
|
|
* Cooperative Awareness adapts its message rate according to TRC (T_GenCam_Dcc).
|
|
* \see EN 302 637-2 V1.3.2 (section 6.1.3)
|
|
*/
|
|
virtual TransmitRateControl& transmit_rate_control() = 0;
|
|
|
|
/**
|
|
* Provide interface for reporting channel probes.
|
|
*
|
|
* Usually, radio hardware will generate these reports periodically.
|
|
*/
|
|
virtual ChannelProbeProcessor& channel_probe_processor() = 0;
|
|
|
|
virtual ~Entity() = default;
|
|
};
|
|
|
|
} // namespace dcc
|
|
} // namespace vanetza
|
|
|
|
#endif /* ENTITY_HPP_KUAWS3PK */
|
|
|