Searched refs:project (Results 1 – 25 of 42) sorted by relevance
12
| /docs/integration_guide/platform/ |
| A D | platform_deprecation.rst | 19 having interest in the platform, then the project maintainer can work
29 4. The project should strive to keep the `deprecated` platforms
31 still actively involved with the project and maintaining the platform.
36 due to evolving project and market requirements. This is left to
37 consensus between project maintainers and platform owner/s.
|
| /docs/contributing/standards/ |
| A D | misra.rst | 9 The project checks for MISRA-C violations and cautions in the code base by running the Eclair
13 The project, is not fully MISRA-C compliant. However, it aims to be MISRA-C-friendly by:
20 While the project's intention is to keep violations and cautions to a minimum, it will not block new
22 violations. Currently, the project is not equipped with necessary fast-feedback-loop tooling to
23 inform contributors about the MISRA-C violations/cautions they introduce. The project welcomes
45 further in the table. The project is not actively prioritizing their resolution; however, as
|
| /docs/configuration/ |
| A D | header_file_system.rst | 22 The ``config_tfm.h`` includes a customized project config file provided via compile definition
23 ``PROJECT_CONFIG_HEADER_FILE``. Customized Component options in the project config file overrides
25 The project config header file can be
|
| A D | index.rst | 17 TF-M is highly configurable project with many configuration options to meet
25 global to a project. These option set shall be considered while adopting TF-M
82 A project configuration performed in multiple steps with priorities.
94 provided explicitly via a project configuration file. Default values
|
| /docs/contributing/ |
| A D | contributing_process.rst | 4 Contributions to the TF-M project need to follow the process below.
23 :doc:`Coding Guide </contributing/coding_guide>` for the TF-M project.
35 information. Files that entirely consist of contributions to this project
44 to reflect the community ownership of the project. Individual copyrights
51 The original form of the project copyright note as
|
| A D | doc_guidelines.rst | 5 The Trusted Firmware-M project uses `Sphinx`_ to generate the Official
229 Trusted Firmware-M project is spread among multiple repositories: Trusted Firmware-M, TF-M Tests,
246 is preceded with the external project name. For TF-M Tests, it is ``TF-M-Tests``. The names of
|
| A D | python_scripting.rst | 65 [project.scripts]
|
| A D | coding_guide.rst | 9 The coding style of TF-M project is based on
|
| /docs/introduction/ |
| A D | readme.rst | 56 TF-M is comprised of multiple repositories that supplement each other in making the project both cu…
77 Contributions to this project are accepted under the same license with developer
80 This project contains code from other projects as listed below. The code from
84 - The ``bl2`` folder contains files imported from MCUBoot project and the files
102 the external project and the files may have different licenses.
|
| /docs/ |
| A D | index.rst | 36 <p>As an open-source project, we welcome and encourage the community
37 to submit patches directly to the project.</p>
59 is addressed within the TF-M project.</p>
|
| A D | conf.py | 22 project = 'Trusted Firmware-M' variable
|
| A D | CMakeLists.txt | 20 project("Trusted Firmware M. Documentation" LANGUAGES)
|
| /docs/releases/ |
| A D | release_process.rst | 4 The project aims to do a release once every 9 months.
66 an adhoc release for specific project requirements.
89 From v2.1.0, TF-M project will provide LTS branches. Every alternate release
93 project to be aligned with LTS releases cadence. Mbed TLS is used as the
|
| /docs/integration_guide/source_structure/ |
| A D | platform_folder.rst | 87 The code in this folder is created as a part of the TF-M project therefore it
93 have licenses other than the BSD 3.0 used by the TF-M project.
|
| A D | platform_ext_folder.rst | 9 to BSD 3.0 license applied to the parent TF-M project.
46 ``CMSIS_5`` project.
67 that TF-M project expects a target to provide.
|
| /docs/building/ |
| A D | documentation_generation.rst | 54 # Setup python venv for the project
96 # Setup python venv for the project
|
| A D | tfm_build_instruction.rst | 100 TF-M supports 4 toolchains for cross-compiling and building the project binaries:
167 for the project config header file is in :ref:`Header_configuration`.
172 The command below shows a general template for building TF-M as a typical CMake project:
|
| /docs/doxygen/ |
| A D | Doxyfile.in | 11 # doxygen (www.doxygen.org) for a project.
38 # project for which the documentation is generated. This name is used in the
44 # The PROJECT_NUMBER tag can be used to enter a project or revision number. This
51 # for a project that appears at the top of each page and should give viewer a
52 # quick idea about the purpose of the project. Keep the description short.
278 # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL
346 # Set the SIP_SUPPORT tag to YES if your project consists of sip (see:
1325 # and project file content.
1363 # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
1396 # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
[all …]
|
| /docs/getting_started/ |
| A D | tfm_getting_started.rst | 38 contribute to this project.
126 # Setup python venv for the project
153 # Setup python venv for the project
|
| /docs/platform/nxp/lpcxpresso55s69/ |
| A D | README.rst | 61 See: `PyOCD <https://pypi.org/project/pyocd/>`_
|
| /docs/design_docs/services/ |
| A D | tfm_crypto_design.rst | 21 project, which provides a reference implementation of the PSA Crypto APIs as a
153 defined by the Mbed TLS project, i.e. its implementation defined aspects are
157 in TF-M are a copy of those distributed by the Mbed TLS project. TF-M just
159 discussed in the scope of the Mbed TLS project.
|
| /docs/platform/stm/stm32l562e_dk/ |
| A D | readme.rst | 60 There are scripts that help users to build the TF-M project on all STM platforms
|
| /docs/platform/stm/b_u585i_iot02a/ |
| A D | readme.rst | 55 There are scripts that help users to build the TF-M project on all STM platforms
|
| /docs/platform/stm/stm32h573i_dk/ |
| A D | readme.rst | 63 There are scripts that help users to build the TF-M project on all STM platforms
|
| /docs/platform/arm/rse/ |
| A D | rse_integration_guide.rst | 147 `pyhsslms <https://pypi.org/project/pyhsslms/>`_ Python package by calling its
183 Generate an ECDSA-P256 key using the `imgtool <https://pypi.org/project/imgtool/>`_
|
Completed in 60 milliseconds
12