Files
MicrOBU/microbu-esp32c5/external/vanetza-idf/vanetza/common/byte_sequence.cpp
T
Ashin Walpola 0e9525162d 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).
2026-09-23 17:46:40 +02:00

23 lines
473 B
C++

#include <vanetza/common/byte_sequence.hpp>
#include <algorithm>
#include <random>
namespace vanetza
{
ByteBuffer random_byte_sequence(std::size_t length, int seed)
{
ByteBuffer buffer(length);
std::generate(buffer.begin(), buffer.end(), random_byte_generator(seed));
return buffer;
}
std::function<uint8_t()> random_byte_generator(int seed)
{
std::mt19937 rng;
rng.seed(seed);
return [rng]() mutable { return rng(); };
}
} // namespace vanetza