Searched refs:dictionary (Results 1 – 25 of 29) sorted by relevance
12
/Zephyr-latest/samples/subsys/logging/dictionary/ |
D | README.rst | 1 .. zephyr:code-sample:: logging-dictionary 5 Output binary log data using the dictionary-based logging API. 10 This is a sample app which utilizes :ref:`dictionary-based logging <logging_guide_dictionary>` and 19 the UART dictionary based frontend). 28 :zephyr-app: samples/subsys/logging/dictionary 59 … ./scripts/logging/dictionary/log_parser.py build/zephyr/log_dictionary.json /tmp/serial.log --hex
|
/Zephyr-latest/modules/canopennode/ |
D | Kconfig | 25 object dictionary. If data type is DOMAIN, data length is 50 bool "CANopen object dictionary storage" 54 Enable support for storing the CANopen object dictionary to 58 bool "Erase CANopen object dictionary EEPROM entries in storage handler" 61 Erase CANopen object dictionary EEPROM entries upon write to 62 object dictionary index 0x1011 subindex 1.
|
/Zephyr-latest/snippets/nordic-log-stm-dict/ |
D | README.rst | 9 This snippet allows users to build Zephyr with the dictionary-based logging to
|
/Zephyr-latest/samples/modules/canopennode/ |
D | README.rst | 18 dictionary and optionally program download over CANopen. 50 counter object at index ``0x2102`` in the object dictionary. 69 counter object at index ``0x2102`` in the object dictionary. 88 object at index ``0x2102`` in the object dictionary. 107 object at index ``0x2102`` in the object dictionary. 222 object dictionary (here index ``0x1008``, the manufacturer device 256 object dictionary (here index ``0x1017``, the producer heartbeat time) 330 of the CANopen object dictionary (here index ``0x2102``, the button 435 The CANopen object dictionary used in this sample application can be 437 the Zephyr tree. The object dictionary can be modified using any [all …]
|
/Zephyr-latest/samples/subsys/shell/shell_module/ |
D | README.rst | 25 ``dictionary`` implements subsect of dictionary commands. 93 dictionary : Dictionary commands
|
/Zephyr-latest/subsys/logging/ |
D | Kconfig.misc | 57 removing strings from final binary and should be used for dictionary 98 bool "Only generated log dictionary database from target" 101 Enable this option to make generating the log dictionary database
|
D | Kconfig.template.log_format_config | 26 Backend is in dictionary-based logging output mode.
|
D | Kconfig.formatting | 103 Enable support for dictionary based logging.
|
/Zephyr-latest/subsys/logging/frontends/ |
D | Kconfig | 7 bool "UART dictionary frontend" 14 Frontend sends data in binary dictionary mode.
|
/Zephyr-latest/doc/services/logging/ |
D | cs_stm.rst | 80 * Dictionary-based - assisted mode which is using dictionary-based logging. In this mode logging 97 If dictionary-based logging is used then proxy just sends data as-is over UART. 105 Assisted multicore logging uses dictionary-based logging to send messages without redundant strings 134 To read the dictionary-based STM log output, do the following: 144 …nrfutil will capture the log data from the specified UART port and use the provided dictionary dat… 183 messages are longer and processing is time consuming. Compared to the dictionary-based mode logging
|
D | index.rst | 703 instead of the whole strings. A dictionary created at build time contains 705 the offline parser to obtain the strings from the dictionary to parse 718 Here are kconfig options related to dictionary-based logging: 720 - :kconfig:option:`CONFIG_LOG_DICTIONARY_SUPPORT` enables dictionary-based logging 723 - The UART backend can be used for dictionary-based logging. These are 727 the UART backend to output hexadecimal characters for dictionary based 738 When dictionary-based logging is enabled via enabling related logging backends, 748 ./scripts/logging/dictionary/log_parser.py <build dir>/log_dictionary.json <log data file> 757 Please refer to the :zephyr:code-sample:`logging-dictionary` sample to learn more on how to use
|
/Zephyr-latest/samples/subsys/shell/shell_module/src/ |
D | main.c | 328 SHELL_CMD(dictionary, &sub_dict_cmds, "Dictionary commands", NULL),
|
/Zephyr-latest/samples/boards/nordic/coresight_stm/ |
D | README.rst | 29 This sample uses STM logging in dictionary mode.
|
/Zephyr-latest/tests/kernel/timer/timer_behavior/ |
D | README | 35 the external tool helper module. It should return a tuple with a dictionary
|
/Zephyr-latest/ |
D | .ruff-excludes.toml | 607 "./scripts/logging/dictionary/database_gen.py" = [ 616 "./scripts/logging/dictionary/dictionary_parser/data_types.py" = [ 620 "./scripts/logging/dictionary/dictionary_parser/log_database.py" = [ 626 "./scripts/logging/dictionary/dictionary_parser/log_parser.py" = [ 629 "./scripts/logging/dictionary/dictionary_parser/log_parser_v1.py" = [ 635 "./scripts/logging/dictionary/dictionary_parser/log_parser_v3.py" = [ 639 "./scripts/logging/dictionary/dictionary_parser/mipi_syst.py" = [ 642 "./scripts/logging/dictionary/dictionary_parser/utils.py" = [ 645 "./scripts/logging/dictionary/log_parser.py" = [ 1556 "./scripts/logging/dictionary/database_gen.py", [all …]
|
D | CMakeLists.txt | 2092 ${ZEPHYR_BASE}/scripts/logging/dictionary/database_gen.py 2099 # If not using a separate target for generating logging dictionary 2104 COMMAND ${CMAKE_COMMAND} -E echo "Generating logging dictionary database: ${LOG_DICT_DB_NAME}" 2112 # Seprate build target for generating logging dictionary database. 2118 COMMENT "Generating logging dictionary database: ${LOG_DICT_DB_NAME}"
|
/Zephyr-latest/scripts/ci/ |
D | pylintrc | 70 consider-iterating-dictionary,
|
/Zephyr-latest/doc/services/shell/ |
D | index.rst | 20 * Support for dictionary commands. 248 * :c:macro:`SHELL_SUBCMD_DICT_SET_CREATE` - Create a dictionary subcommands 290 It is a perfect place where a dictionary can be used. The dictionary would
|
/Zephyr-latest/samples/subsys/logging/syst/ |
D | README.rst | 202 Catalog messages are similar to dictionary logging where the format strings
|
/Zephyr-latest/doc/build/dts/ |
D | bindings-syntax.rst | 691 Included files are merged into bindings with a simple recursive dictionary 728 This relies on the dictionary merge to fill in the other keys for ``reg``, like
|
/Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
D | smp_group_0.rst | 334 | <pool_name> | string representing the pool name, used as a key for dictionary with |
|
/Zephyr-latest/cmake/modules/ |
D | yaml.cmake | 564 # JSON object -> YAML dictionary
|
/Zephyr-latest/doc/releases/ |
D | release-notes-3.7.rst | 1706 * Fix case when logging strings could be stripped from the binary when dictionary based logging 1707 was mixed with non-dictionary. 1709 * Fix dictionary database not being generated in certain situations. 1711 * Fix dictionary logging parser not handling long long arguments correctly.
|
D | release-notes-3.6.rst | 1037 * Added an option to remove string literals from the binary when dictionary-based logging is used. 1052 It must be avoided when dictionary-based logging is used and strings are stripped from the
|
/Zephyr-latest/scripts/ |
D | spelling.txt | 521 dictionnary||dictionary
|
12