Home
last modified time | relevance | path

Searched refs:logs (Results 1 – 25 of 83) sorted by relevance

1234

/Zephyr-latest/tests/bsim/
Dci.uart.sh16 ${ZEPHYR_BASE}/scripts/twister -T tests/drivers/uart/ --force-color --inline-logs -v -M \
21 ${ZEPHYR_BASE}/scripts/twister -T tests/drivers/uart/ --force-color --inline-logs -v -M \
/Zephyr-latest/modules/uoscore-uedhoc/
DKconfig15 bool "Debug logs in the uoscore library"
30 bool "Debug logs in the uedhoc library"
/Zephyr-latest/subsys/logging/
DKconfig.mode46 When enabled, logs are redirected to a custom frontend which is the
47 fastest way of getting logs out. The logs are redirected at the function
48 level. To redirect logs at the macro level, see LOG_CUSTOM_HEADER.
DKconfig.template.log_format_config18 When enabled backend is used to output syst format logs.
/Zephyr-latest/samples/boards/nordic/coresight_stm/
DREADME.rst23 Application, Radio, PPR and FLPR cores send logs to an ETR buffer.
24 Proxy (Application core) gets logs from the ETR buffer, decodes STPv2 data
25 and prints human readable logs on UART.
30 Application, Radio, PPR and FLPR cores send logs to the ETR buffer.
32 Host tool is needed to decode the logs.
/Zephyr-latest/subsys/logging/backends/
DKconfig.fs9 When enabled, backend is using the configured file system to output logs.
63 int "Max number of files containing logs"
66 Limit of number of files with logs. It is also limited by
DKconfig.efi_console9 When enabled backend is using EFI CONSOLE to output logs.
DKconfig.uart10 When enabled backend is using UART to output logs.
/Zephyr-latest/soc/silabs/
DKconfig.defconfig17 # large, especially with logs enabled. Since it is called from IDLE task,
/Zephyr-latest/tests/subsys/logging/log_syst/
DKconfig9 log messages. It will not output any logs.
/Zephyr-latest/subsys/shell/
DKconfig.template.shell_log_queue_size10 slow shell transport may lead to situations where logs are dropped
/Zephyr-latest/lib/net_buf/
DKconfig18 Enable logs and checks for the generic network buffers.
40 Enable extra debug logs and checks for the generic network buffers.
/Zephyr-latest/tests/subsys/logging/log_switch_format/
DKconfig10 log messages. It will not output any logs.
/Zephyr-latest/subsys/logging/frontends/
DKconfig80 bool "Drop all logs except turbo logs"
83 related code except turbo logs.
/Zephyr-latest/modules/nrf_wifi/bus/
DKconfig43 bool "Maintains the verbosity of information in logs"
/Zephyr-latest/doc/services/logging/
Dcs_stm.rst108 Instead of including the format strings in the log messages, it logs the addresses (message IDs)
114 When using logs, this method has the following advantages:
131 Reading the logs
138 …Use the ``nrfutil trace stm`` command to start capturing logs from the device, specifying the data…
142 #. Capture and decode the logs.
144 …ecified UART port and use the provided dictionary databases to decode the logs into a human-readab…
145 …The decoded logs will be saved in the specified output file (the :file:`out.txt` file in the previ…
193 Reading the logs
241 * Some log messages might be dropped due to the limited size of the RAM buffer that stores STM logs.
Dindex.rst37 Kconfig options (see :ref:`logging_kconfig`) logs can be gradually removed from
38 compilation to reduce image size and execution time when logs are not needed.
39 During compilation logs can be filtered out on module basis and severity level.
69 to globally limit logs by providing maximal severity level present in the
145 :kconfig:option:`CONFIG_LOG_FRONTEND`: Direct logs to a custom frontend.
249 across the system enabling logs will lead to flooding. The logger provides the tools
340 If logs are processed from a thread (user or internal) then it is possible to enable
356 that moment all logs are processed in a blocking way.
462 logs to limit dropping.
477 time filtering, binary footprint is increased because logs are compiled in.
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-shell.rst84 * Enable error logs for *bt_att* and *bt_smp*
96 * Enable warning logs for all modules
/Zephyr-latest/doc/develop/west/
Dsign.rst29 build logs to find which exact options were used. Copying these options from the
30 build logs can be unreliable: it may produce different results because of subtle
/Zephyr-latest/samples/drivers/ht16k33/
DREADME.rst21 The sample logs keyscan events on the console.
/Zephyr-latest/boards/aspeed/ast1030_evb/doc/
Dindex.rst60 UART5 is configured for serial logs. The default serial setup is 115200 8N1.
/Zephyr-latest/subsys/bluetooth/audio/
DKconfig.bap265 Use this option to enable Bluetooth Audio Stream data debug logs for
266 the Bluetooth Audio functionality. This will enable debug logs for all
280 Use this option to enable Bluetooth Audio Stream sequence number debugging logs for
/Zephyr-latest/.github/ISSUE_TEMPLATE/
D001_bug_report.md55 If applicable, add console logs or other types of debug information
/Zephyr-latest/boards/nuvoton/npcm400_evb/doc/
Dindex.rst65 UART0 is configured for serial logs. The default serial setup is 115200 8N1.
/Zephyr-latest/tests/subsys/logging/log_blocking/
DREAME.md81 When any log backend is unable to process logs for whatever reason,
83 driver code continue to submit logs, the core log buffer approaches 100%

1234