zephyr

118699 Commits

82 Branches

204 Tags

1.7 GiB

Branch: main

Commit Graph

Author	SHA1	Message	Date
Galen Krulce	1cfe90d825	tracing: full reset during init 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>	1 year ago
Gerard Marull-Paretas	5113c1418d	subsystems: migrate includes to <zephyr/...> In order to bring consistency in-tree, migrate all subsystems code to the new prefix <zephyr/...>. Note that the conversion has been scripted, refer to zephyrproject-rtos#45388 for more details. Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>	3 years ago
Julien Massot	80402f7f8b	tracing: add RAM backend If Zephyr is running on a coprocessor we might lack I/O such as uart or usb to output tracing datas but we might have gigabytes of RAM available. This patch allows to output trace datas to a ram buffer, which then may be retrieved using gdb. e.g: (gdb) dump binary memory channel0_0 <ram_tracing_start> \ <ram_tracing_end> Signed-off-by: Julien Massot <julien.massot@iot.bzh>	4 years ago

Author

SHA1

Message

Date

Galen Krulce

1cfe90d825

tracing: full reset during init

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>

1 year ago

Gerard Marull-Paretas

5113c1418d

subsystems: migrate includes to <zephyr/...>

In order to bring consistency in-tree, migrate all subsystems code to
the new prefix <zephyr/...>. Note that the conversion has been scripted,
refer to zephyrproject-rtos#45388 for more details.

Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>

3 years ago

Julien Massot

80402f7f8b

tracing: add RAM backend

If Zephyr is running on a coprocessor we might lack I/O
such as uart or usb to output tracing datas but we might
have gigabytes of RAM available.

This patch allows to output trace datas to a ram buffer, which then
may be retrieved using gdb.

e.g:
(gdb) dump binary memory channel0_0 <ram_tracing_start> \
<ram_tracing_end>

Signed-off-by: Julien Massot <julien.massot@iot.bzh>

4 years ago

3 Commits (main)