mirror of
https://github.com/iNavFlight/inav.git
synced 2025-07-24 16:55:29 +03:00
dmesg documentation
This commit is contained in:
parent
826ec9d07d
commit
bd80148c6a
2 changed files with 13 additions and 1 deletions
|
@ -4,7 +4,9 @@
|
|||
|
||||
INAV offers a function to use serial `printf` style debugging.
|
||||
|
||||
This provides a simple and intuitive debugging facility. This facility is only available after the serial sub-system has been initialised, which should be adequate for all but the most hard-core debugging requirements.
|
||||
This provides a simple and intuitive debugging facility.
|
||||
This facility is only available after the serial sub-system has been initialised, but logs generated prior to serial
|
||||
initialization can be obtained via the `dmesg` functionality.
|
||||
|
||||
In order to use this feature, the source file must include `common/log.h`.
|
||||
|
||||
|
@ -137,3 +139,12 @@ The output will be formatted as follows:
|
|||
For the Configurator, debug messages are shown in the developer console log.
|
||||
|
||||
Note: The numeric value in square brackets is the FC uptime in seconds.
|
||||
|
||||
To see printf-style log messages generated prior serial initialization, reserve about 2KB-4KB RAM to buffer the
|
||||
log) by defining DMESG_SIZE:
|
||||
#define DMESG_SIZE 2048
|
||||
|
||||
Then `make clean` and `make`.
|
||||
|
||||
Then in the CLI you can run `dmesg` to see the buffered log.
|
||||
Note dmesg also requires that a serial port be defined for serial debugging.
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue