Searched refs:requirements (Results 1 – 25 of 217) sorted by relevance
123456789
| /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/doc/safety/ |
| D | safety_requirements.rst | 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
39 System requirements describe the behaviour of the Zephyr RTOS (= the system here).
42 The purpose of the system requirements is to get an overview of the currently implemented features
[all …]
|
| D | index.rst | 6 These documents describe the processes, developer guidelines and requirements
|
| 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
190 Requirements and requirements tracing
197 purpose, tracing the requirements down to the code level is used. With the requirements management
202 requirements and requirements tracing.
211 requirements apply to safety for test coverage, and various metrics must be considered, which are
[all …]
|
| /Zephyr-latest/scripts/west_commands/ |
| D | packages.py | 133 requirements = []
136 requirements.append(ZEPHYR_BASE / "scripts/requirements.txt")
153 requirements += [Path(module.project) / r for r in pip.get("requirement-files", [])]
159 if len(requirements) > 0:
162 + list(chain.from_iterable([("-r", r) for r in requirements]))
172 self.inf("\n".join([f"-r {r}" for r in requirements]))
|
| /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/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/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/tfm/ |
| D | index.rst | 10 requirements.rst
|
| /Zephyr-latest/doc/project/ |
| D | documentation.rst | 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/ |
| D | index.rst | 6 These documents describe the requirements, processes, and developer guidelines
|
| /Zephyr-latest/doc/services/storage/secure_storage/ |
| D | index.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/arch/arm/core/ |
| D | vector_table.ld | 11 * exc_vector_table must respect the alignment requirements of VTOR.TBLOFF
44 * should be aligned in such a way so that it satisfies the requirements of
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | haptics.rst | 20 tuning the drive signal to meet the electrical requirements of their respective
|
| /Zephyr-latest/doc/develop/west/ |
| D | why.rst | 6 West was added to the Zephyr project to fulfill two fundamental requirements:
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/tfm_integration/psa_crypto/boards/ |
| D | nrf9160dk_nrf9160_ns.overlay | 7 /* Modify the SRAM partitioning to accommodate the requirements
|
| /Zephyr-latest/samples/tfm_integration/tfm_ipc/boards/ |
| D | nrf9160dk_nrf9160_ns.overlay | 7 /* Modify the SRAM partitioning to accommodate the requirements
|
| /Zephyr-latest/doc/build/dts/ |
| D | bindings.rst | 10 A devicetree binding declares requirements on the contents of nodes, and
|
| /Zephyr-latest/samples/boards/st/power_mgmt/stop3/ |
| D | README.rst | 12 .. _stm32-pm-stop3-requirements:
|
| /Zephyr-latest/kernel/ |
| D | CMakeLists.txt | 167 # Import all custom HEAP_MEM_POOL size requirements
170 # Calculate the sum of all "ADD_SIZE" requirements
187 # CONFIG_HEAP_MEM_POOL_SIZE was greater than the sum of the requirements
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_ace15_mtpm.rst | 13 System requirements
|
| D | intel_adsp_cavs25.rst | 13 System requirements
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/ |
| D | README.rst | 21 The Bluetooth Mesh tests have no extra requirements, and can be run using the
88 generic implementation does not fit with the harness requirements.
117 subsystems, so timing requirements should generally be kept fairly liberal to
|
| /Zephyr-latest/samples/net/prometheus/ |
| D | README.rst | 46 the requirements. These are the configurable parameters:
84 Make sure to adjust the configuration according to your server's setup and requirements.
|
| /Zephyr-latest/boards/st/b_u585i_iot02a/ |
| D | b_u585i_iot02a_stm32u585xx_ns.dts | 37 * Following flash partition is compatible with requirements
|
123456789
