Home
last modified time | relevance | path

Searched refs:reports (Results 1 – 25 of 92) sorted by relevance

1234

/Zephyr-latest/cmake/sca/eclair/ECL/
Dadopted_deviations.ecl3 -doc="Selection for reports that are fully contained in adopted code."
7 -config=MC3R1.R7.2,reports+={relied,adopted_report}
8 -config=MC3R1.R10.3,reports+={relied,adopted_report}
9 -config=MC3R1.R10.6,reports+={relied,adopted_report}
10 -config=MC3R1.R12.1,reports+={relied,adopted_report}
14 -config=MC3R1.R7.2,reports+={safe,"all_area(all_loc(any_exp(macro(^assert$))))"}
39 -config=MC3R1.R15.6,reports={relied, "all_area(context(^z_object_lookup\\(const char\\*, size_t\\)$…
Dzephyr_common_config.ecl6 -doc="Hides all reports that have all areas out of scope."
7 -reports+={hide,all_exp_external}
10 -config=MC3R1.R2.5,reports+={hide, "any_area(macro(loc(top(public()||kind(pseudo)))))"}
35 -config=MC3R1.R11.6,reports+={deliberate,"any_area(any_loc(any_exp(macro(name(__LOG_ARG_CAST)))))"}
95 -config=MC3R1.R2.1,reports+={safe,"any_area(any_loc(any_exp(macro(name(CODE_UNREACHABLE)))))"}
105 -doc="Hide reports marked as compliant."
108 -doc="Hide reports marked as safe."
111 -doc="Hide reports marked as relied."
114 -doc="Hide reports marked as questionable."
117 -doc="Hide reports marked as deliberate."
[all …]
/Zephyr-latest/doc/develop/test/
Dcoverage.rst3 Generating coverage reports
6 With Zephyr, you can generate code coverage reports to analyze which parts of
15 Test coverage reports in embedded devices or QEMU
21 used together with the GCC compiler to analyze and create test coverage reports
44 Steps to generate code coverage reports
82 #. Create an output directory for the reports::
86 #. Run ``gcovr`` to get the reports::
92 Coverage reports using the POSIX architecture
130 Coverage reports using Twister
148 Other reports might be chosen with ``--coverage-tool`` and ``--coverage-formats``
Dtwister_statuses.rst31 as it does not appear in final reports.
48 Twister typically reports its results for Instances,
107 whereas the latter is used in the JSON reports.
/Zephyr-latest/samples/bluetooth/direction_finding_central/
DKconfig9 bool "Print IQ samples for received IQ reports"
/Zephyr-latest/samples/bluetooth/direction_finding_connectionless_rx/
DKconfig9 bool "Print IQ samples for received IQ reports"
/Zephyr-latest/subsys/bluetooth/services/
DKconfig.hrs17 Used also for boot reports.
/Zephyr-latest/scripts/pylib/pytest-twister-harness/
D.gitignore27 # Unit test / coverage reports
/Zephyr-latest/doc/develop/sca/
Declair.rst108 default ecd file. Following additional reports and report formats can be generated:
122 * Detailed reports in txt format.
140 Detail level of full reports
143 The detail level of the txt and doc full reports can also be adapted by a configuration.
/Zephyr-latest/samples/bluetooth/central_hr/
DREADME.rst11 application specifically looks for heart-rate monitors and reports the
/Zephyr-latest/samples/bluetooth/central_ht/
DREADME.rst11 application specifically looks for health thermometer sensor and reports the
/Zephyr-latest/cmake/sca/eclair/
Dsca.cmake70 list(APPEND ECLAIR_REPORT_ADDITIONAL_OPTIONS "-reports_tab=${ECLAIR_OUTPUT_DIR}/reports")
73 list(APPEND ECLAIR_REPORT_ADDITIONAL_OPTIONS "-reports_sarif=${ECLAIR_OUTPUT_DIR}/reports.sarif")
137 # This command is used to generate the final reports from the database and print the overall results
/Zephyr-latest/scripts/
Drequirements-base.txt27 # for ram/rom reports
/Zephyr-latest/doc/project/
Dcommunication.rst16 In general, bug reports and other issues should be reported as `GitHub Issues
Ddocumentation.rst47 reports and using their name and identifier is the best way to identify them
54 for traceability reports. Here are a few guidelines to be followed:
Dindex.rst25 **Issues** to track feature, enhancement, and bug reports together with GitHub
/Zephyr-latest/tests/subsys/sd/sdio/
DREADME.txt17 * Configuration test: verify that the SD stack reports a valid configuration
/Zephyr-latest/samples/bluetooth/iso_broadcast/
DREADME.rst30 generate BIGInfo reports and synchronize to BIG events from this sample.
/Zephyr-latest/samples/boards/st/uart/single_wire/
DREADME.rst29 After flashing the console output should not show any failure reports,
/Zephyr-latest/samples/drivers/charger/
DREADME.rst19 - Once the charger device reports that the charge cycle has completed, the application returns.
/Zephyr-latest/tests/posix/eventfd/
DKconfig36 bool "Do not print out regular reports"
/Zephyr-latest/subsys/bluetooth/controller/
DKconfig.df314 bool "Use 16 bits signed integer IQ samples in connectionless IQ reports"
317 Direction Finging connectionless IQ reports provide a set of IQ samples collected during
320 extension to HCI layer, so that connectionless IQ reports store samples in 16 bit signed
324 bool "Use 16 bits signed integer IQ samples in connection IQ reports"
327 Direction Finging connection IQ reports provide a set of IQ samples collected during
330 extension to HCI layer, so that connection IQ reports store samples in 16 bit signed
/Zephyr-latest/doc/security/
Dreporting.rst10 vulnerabilities@zephyrproject.org mailing list. These reports will be
52 - New: This state represents new reports that have been entered
79 sensitive nature of security reports. The issues are only visible to
122 advisories), and produce regular reports of the state of security
/Zephyr-latest/samples/drivers/led/pwm/boards/
Dmec15xxevb_assy6853.overlay17 * BBLED-PWM driver get cycles API reports 32KHz/256 or 48M/256.
/Zephyr-latest/boards/gaisler/generic_leon3/doc/
Dindex.rst41 Comments or bug-reports to support@gaisler.com
94 Comments or bug-reports to support@gaisler.com

1234