Home
last modified time | relevance | path

Searched refs:analyze (Results 1 – 23 of 23) sorted by relevance

/Zephyr-latest/doc/services/debugging/
Dthread-analyzer.rst30 Thread analyze:
43 Thread analyze:
56 Thread analyze:
/Zephyr-latest/cmake/sca/eclair/ECL/
Danalysis_first_analysis.ecl2 # argument of analyze.sh.
Danalysis_heavy_STU.ecl2 # argument of analyze.sh.
Danalysis_HIS.ecl2 # argument of analyze.sh.
Danalysis_std_lib.ecl2 # argument of analyze.sh.
Danalysis_WP.ecl2 # argument of analyze.sh.
Danalysis_STU.ecl2 # argument of analyze.sh.
/Zephyr-latest/cmake/sca/polyspace/
Dsca.cmake102 add_custom_target(polyspace-analyze ALL
127 add_dependencies(polyspace-results polyspace-analyze)
/Zephyr-latest/tests/benchmarks/sched_queues/
DKconfig37 analyze it, it is recommended to redirect the output to a file.
/Zephyr-latest/tests/benchmarks/wait_queues/
DKconfig37 analyze it, it is recommended redirect or copy the data to a file.
/Zephyr-latest/doc/security/
Dhardening-tool.rst18 To simplify this process, Zephyr offers a **hardening tool** designed to analyze an application's
Dreporting.rst58 response team will analyze the issue, determine a responsible
/Zephyr-latest/doc/develop/sca/
Dcodechecker.rst47 - Arguments passed to the ``analyze`` command directly. (e.g. ``--timeout;360``)
/Zephyr-latest/cmake/sca/codechecker/
Dsca.cmake77 COMMAND ${CODECHECKER_EXE} analyze
/Zephyr-latest/doc/develop/test/
Dcoverage.rst6 With Zephyr, you can generate code coverage reports to analyze which parts of
21 used together with the GCC compiler to analyze and create test coverage reports
/Zephyr-latest/drivers/ieee802154/
DKconfig.nrf580 It can be helpful for the network traffic analyze but it generates also
/Zephyr-latest/scripts/west_commands/completion/
Dwest-completion.zsh313 '--analyze-includes[also analyze included header files]'
Dwest-completion.fish497 complete -c west -n "__zephyr_west_seen_subcommand_from spdx" -l analyze-includes -d "also analyze
/Zephyr-latest/doc/develop/west/
Dzephyr-cmds.rst134 - ``--analyze-includes``: in addition to recording the compiled source code
142 - ``--include-sdk``: with ``--analyze-includes``, also create a fourth SPDX
/Zephyr-latest/samples/shields/x_nucleo_iks02a1/microphone/
DREADME.rst163 After the file is imported you can analyze and play the 1sec audio file:
/Zephyr-latest/samples/net/sockets/http_server/
DREADME.rst233 we can stop the recording and analyze the data using:
/Zephyr-latest/doc/contribute/
Dguidelines.rst599 projects. It is based on Coverity's commercial product and is able to analyze
/Zephyr-latest/doc/services/zbus/
Dindex.rst381 arise. ZBus will not solve every problem, so it is necessary to analyze the situation to be sure