| /Zephyr-latest/doc/safety/ |
| D | safety_requirements.rst | 3 Safety Requirements
9 The safety committee leads the effort to gather requirements that reflect the **actual** state of
11 approach of the project's safety effort. The goal is **NOT** to create new requirements to request
14 The requirements are gathered in the separate repository:
21 Below are the guidelines for the requirements repository and the expectations of the safety
22 committee when adding requirements to the repository.
27 The scope of the requirements covers the KERNEL functionalities.
32 Maintain consistency across all requirements. The language and choice of words shall be consistent.
35 Levels of requirements in the repository
38 System Requirements
[all …]
|
| D | safety_overview.rst | 26 This document is a living document and may evolve over time as new requirements, guidelines, or
50 *Compliant development. Compliance with the requirements of this standard for the avoidance and
69 includes the identification of safety requirements, the development of a safety plan, and the
74 safety-related system to ensure that it meets the specified SIL and other safety requirements.
80 documented and that there is full traceability from the safety requirements to the final system
120 b. :ref:`safety_requirements` and requirements tracing
150 Requirements and requirements tracing
153 Requirements and requirement management are not only important for software development, but also
157 purpose, tracing the requirements down to the code level is used. With the requirements management
162 requirements and requirements tracing.
[all …]
|
| /Zephyr-latest/scripts/ |
| D | requirements.txt | 1 -r requirements-base.txt
2 -r requirements-build-test.txt
3 -r requirements-run-test.txt
4 -r requirements-extras.txt
5 -r requirements-compliance.txt
|
| /Zephyr-latest/scripts/west_commands/ |
| D | packages.py | 83 The output is compatible with the requirements file format itself.
91 help="Install pip requirements instead of listing them. "
125 requirements = []
128 requirements.append(ZEPHYR_BASE / "scripts/requirements.txt")
144 # Add requirements files
145 requirements += [Path(module.project) / r for r in pip.get("requirement-files", [])]
151 if len(requirements) > 0:
154 + list(chain.from_iterable([("-r", r) for r in requirements]))
164 self.inf("\n".join([f"-r {r}" for r in requirements]))
|
| /Zephyr-latest/subsys/pm/policy/ |
| D | Kconfig | 37 bool "Allow gathering latency requirements in standalone mode"
41 requirements on systems that do not support PM (e.g. systems whithout
44 requirements gathered from multiple system components.
|
| /Zephyr-latest/tests/arch/arm/arm_thread_swap_tz/ |
| D | Kconfig | 8 Redefine this with looser requirements, so the EXC_RETURN value can
10 requirements are sane.
|
| /Zephyr-latest/doc/project/ |
| D | documentation.rst | 17 Reference to Requirements
20 APIs for the most part document the implementation of requirements or advertised
23 using custom _doxygen_ tags that reference requirements maintained somewhere
34 the original requirements.
48 and trace back to them from requirements.
90 requirements, we use the ``satisfy`` alias in doxygen::
|
| /Zephyr-latest/doc/security/standards/ |
| D | index.rst | 12 standards provide guidelines and outline requirements that products have to follow
16 by security standards requirements and provide the right information to enable
|
| /Zephyr-latest/doc/services/ |
| D | secure_storage.rst | 50 …ted Storage requirements <https://arm-software.github.io/psa-api/storage/1.0/overview/requirements…
70 …ted Storage requirements <https://arm-software.github.io/psa-api/storage/1.0/overview/requirements…
|
| /Zephyr-latest/.github/workflows/ |
| D | twister_tests.yml | 54 …pip install -r scripts/requirements-base.txt -r scripts/requirements-build-test.txt -r scripts/req…
|
| D | twister_tests_blackbox.yml | 70 …hon3 -m pip install -U -r scripts/requirements-base.txt -r scripts/requirements-build-test.txt -r …
|
| D | pylib_tests.yml | 47 pip install -r scripts/requirements-base.txt -r scripts/requirements-build-test.txt
|
| /Zephyr-latest/samples/boards/st/power_mgmt/stop3/ |
| D | README.rst | 12 .. _stm32-pm-stop3-requirements:
14 Requirements chapter
|
| /Zephyr-latest/doc/develop/west/ |
| D | why.rst | 6 West was added to the Zephyr project to fulfill two fundamental requirements:
15 Requirements section in History and Motivation
19 repositories is outside of the scope of this page, the fundamental requirements,
23 The basic requirements are:
44 None were found suitable for Zephyr's requirements. In particular, these were
|
| /Zephyr-latest/samples/subsys/debug/debugmon/ |
| D | README.rst | 17 .. _debugmon-sample-requirements:
19 Requirements chapter
|
| /Zephyr-latest/samples/basic/fade_led/ |
| D | README.rst | 18 Requirements and Wiring
21 This sample has the same requirements and wiring considerations as the
|
| /Zephyr-latest/samples/boards/st/power_mgmt/adc/ |
| D | README.rst | 13 .. _stm32-pm-adc-sample-requirements:
15 Requirements chapter
|
| /Zephyr-latest/samples/boards/st/power_mgmt/wkup_pins/ |
| D | README.rst | 16 .. _gpio-as-a-wkup-pin-src-sample-requirements:
18 Requirements chapter
|
| /Zephyr-latest/samples/drivers/i2c/rtio_loopback/ |
| D | README.rst | 14 Requirements chapter
32 Any board which meets the requirements must use an overlay to specify which
|
| /Zephyr-latest/scripts/west_commands/tests/ |
| D | test_bossac.py | 172 Requirements:
205 Requirements:
242 Requirements:
280 Requirements:
317 Requirements:
362 Requirements:
396 Requirements:
430 Requirements:
465 Requirements:
500 Requirements:
[all …]
|
| /Zephyr-latest/dts/bindings/clock/ |
| D | nuvoton,npcx-pcc.yaml | 58 dividing OFMCLK(MCLK) and needs to meet the following requirements.
88 OFMCLK(MCLK) and needs to meet the following requirements.
119 OFMCLK(MCLK) and needs to meet the following requirements.
150 OFMCLK(MCLK) and needs to meet the following requirements.
180 OFMCLK(MCLK) and needs to meet the following requirements.
|
| /Zephyr-latest/samples/boards/st/power_mgmt/suspend_to_ram/ |
| D | README.rst | 16 .. _stm32-pm-suspend-to-ram-sample-requirements:
18 Requirements chapter
|
| /Zephyr-latest/samples/boards/st/power_mgmt/standby_shutdown/ |
| D | README.rst | 18 .. _stm32-pm-standby_shutdown-sample-requirements:
20 Requirements chapter
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 22 blobs if they cannot meet the requirements described in this page.
120 reasons on a case by case basis (see library-specific requirements below).
124 Precompiled library-specific requirements
127 This section contains additional requirements specific to precompiled library
131 meets these requirements. The project may remove a blob from the upstream
132 distribution if it is discovered that the blob fails to meet these requirements
145 This section defines requirements related to external symbols that a library
158 Toolchain requirements argument
|
| /Zephyr-latest/samples/subsys/usb_c/source/ |
| D | README.rst | 18 .. _usb-c-source-sample-requirements:
20 Requirements chapter
|
