Searched refs:log (Results 1 – 12 of 12) sorted by relevance
| /lvgl-latest/tests/micropy_test/ |
| D | __init__.py | 49 def log(*args): function
92 log('<---', cmd)
101 log('MARKER', marker)
119 log('--->', micropy_data)
125 log('---> ERROR: ', error_data.decode('utf-8'))
127 log('---> ERROR: ', error_data)
133 log('--->', micropy_data)
139 log('---> ERROR: ', error_data.decode('utf-8'))
141 log('---> ERROR: ', error_data)
144 log('--EXIT EVENT SET')
[all …]
|
| /lvgl-latest/docs/details/debugging/ |
| D | log.rst | 22 - :c:macro:`LV_LOG_LEVEL_NONE`: Do not log anything
24 The events which have a higher level than the set log level will be logged
37 Custom log function
40 If you can't use ``printf`` or want to use a custom function to log, you
61 You can also use the log module via the
|
| D | profiler.rst | 20 When the buffer is full, the trace system prints the log information through the provided user inte…
99 …f you want to use another interface to output log information (e.g., file stream), you can redirec…
125 Save the output log as `my_trace.txt`, use `trace_filter.py` for filtering and preprocessing:
159 If the log parsing is successful, you will see the following screen:
221 Perfetto log parsing fails
227 …ace logs. You need to disable the log output of other threads or refer to the configuration above …
240 …LV_PROFILER_BUILTIN_BUF_SIZE`. A larger buffer can reduce the frequency of log printing, but it al…
241 2. Optimize the execution time of log printing functions, such as increasing the serial port baud r…
246 …lly printed when the buffer is not full, you can try the following methods to force the log output:
249 … or use a timer to call the :cpp:func:`lv_profiler_builtin_flush` function to force the log output.
|
| D | index.rst | 11 log
|
| /lvgl-latest/docs/details/integration/framework/ |
| D | arduino.rst | 88 section ``log settings``:
93 #define USE_LV_LOG 1 /* Enable/disable the log module */
95 /* How important log should be added:
100 * LV_LOG_LEVEL_NONE Do not log anything
104 After enabling the log module and setting :c:macro:`LV_LOG_LEVEL` accordingly, the
105 output log is sent to the ``Serial`` port @ 115200 bps.
|
| /lvgl-latest/src/libs/thorvg/ |
| D | tvgMath.h | 166 static inline void log(const Matrix& m) in log() function
252 static inline void log(const Point& pt) in log() function
|
| /lvgl-latest/docs/details/integration/driver/ |
| D | wayland.rst | 178 This will create a log file called ``debug`` in the ``/tmp`` directory, copy-paste the content of t…
179 The log file contains LVGL logs and the wayland messages.
|
| /lvgl-latest/docs/details/integration/ide/ |
| D | pc-simulator.rst | 18 - Better developer experience: On PC Debuggers are usually faster and better, you can log to files,
|
| /lvgl-latest/ |
| D | Kconfig | 504 bool "Enable the log module"
507 bool "Default log verbosity" if LV_USE_LOG
510 Specify how important log should be added.
523 bool "Do not log anything"
536 bool "Print the log with 'printf'" if LV_USE_LOG
538 Use printf for log output.
1462 bool "Prints performance data using log"
|
| /lvgl-latest/docs/details/other-components/ |
| D | obj_id.rst | 180 This can be useful in the event of a UI crash. From that log you can examine the
|
| /lvgl-latest/docs/ |
| D | CHANGELOG.rst | 116 - **feat(log): add LV_LOG_PRINT_CB to set a default log print cb** `6095 <https://github.com/lvgl/l…
450 - **chore(decoder): use trace level of log** `6361 <https://github.com/lvgl/lvgl/pull/6361>`__
456 - **chore(log): remove \n from log message** `6276 <https://github.com/lvgl/lvgl/pull/6276>`__
|
| /lvgl-latest/docs/intro/ |
| D | introduction.rst | 121 Change log
|
