1cfe90d825
I am using the tracing module using the RAM backend on a system with limited RAM & a buffer that can only store 300ms of tracing data. Current tracing module starts recording during boot-up & we run out of memory prior to executing code we actually want to trace. By reseting buffer metadata here, I can call init() at an arbitrary point of program execution & the tracing module will reset & start tracing. I tested on E2E on an ARM M-class MCU by calling init & then reading buffered tracing data via GDB Signed-off-by: Galen Krulce <gkrulce@meta.com>
48 lines
980 B
C
48 lines
980 B
C
/*
|
|
* Copyright (c) 2021 IoT.bzh
|
|
*
|
|
* SPDX-License-Identifier: Apache-2.0
|
|
*/
|
|
|
|
#include <ctype.h>
|
|
#include <zephyr/kernel.h>
|
|
#include <string.h>
|
|
#include <tracing_core.h>
|
|
#include <tracing_buffer.h>
|
|
#include <tracing_backend.h>
|
|
|
|
uint8_t ram_tracing[CONFIG_RAM_TRACING_BUFFER_SIZE];
|
|
static uint32_t pos;
|
|
static bool buffer_full;
|
|
|
|
static void tracing_backend_ram_output(
|
|
const struct tracing_backend *backend,
|
|
uint8_t *data, uint32_t length)
|
|
{
|
|
if (buffer_full) {
|
|
return;
|
|
}
|
|
|
|
if ((pos + length) > CONFIG_RAM_TRACING_BUFFER_SIZE) {
|
|
buffer_full = true;
|
|
return;
|
|
}
|
|
|
|
memcpy(ram_tracing + pos, data, length);
|
|
pos += length;
|
|
}
|
|
|
|
static void tracing_backend_ram_init(void)
|
|
{
|
|
memset(ram_tracing, 0, CONFIG_RAM_TRACING_BUFFER_SIZE);
|
|
pos = 0;
|
|
buffer_full = false;
|
|
}
|
|
|
|
const struct tracing_backend_api tracing_backend_ram_api = {
|
|
.init = tracing_backend_ram_init,
|
|
.output = tracing_backend_ram_output
|
|
};
|
|
|
|
TRACING_BACKEND_DEFINE(tracing_backend_ram, tracing_backend_ram_api);
|