Home
last modified time | relevance | path

Searched +full:non +full:- +full:standard (Results 1 – 25 of 182) sorted by relevance

12345678

/Zephyr-latest/doc/hardware/peripherals/audio/
Di2s.rst3 Inter-IC Sound (I2S) Bus
9 The I2S (Inter-IC Sound) API provides support for the standard I2S interface
10 as well as common non-standard extensions such as PCM Short/Long Frame Sync
/Zephyr-latest/lib/utils/
DKconfig2 # SPDX-License-Identifier: Apache-2.0
30 bool "On-Off Manager"
33 An on-off manager supports an arbitrary number of clients of a
41 "windows", generally for transmit to non-Zephyr contexts that
46 bool "Use standard memcpy() in winstream"
49 environments before the standard library is usable. By
51 this to use the one from the standard library.
55 bool "UTF-8 string operation supported"
58 handle UTF-8 encoded strings.
/Zephyr-latest/dts/bindings/watchdog/
Dti,cc13xx-cc26xx-watchdog.yaml2 # SPDX-License-Identifier: Apache-2.0
6 compatible: "ti,cc13xx-cc26xx-watchdog"
17 interrupt-nmi:
20 Whether the watchdog triggers a Non-Maskable Interrupt or a standard one
/Zephyr-latest/doc/develop/languages/c/
Dindex.rst6 C is a general-purpose low-level programming language that is widely used for
17 standard. Applications must return zero (0) from main. All non-zero return
27 1999 release of the ISO C standard (ISO/IEC 9899:1999, hereinafter referred to
29 toolchain that supports the C99 standard and above:
32 * standard boolean types (``bool`` in ``<stdbool.h>``)
33 * fixed-width integer types (``[u]intN_t`` in ``<stdint.h>``)
39 release of the ISO C standard (ISO/IEC 9899:2011, hereinafter referred to as
40 C11) such as the type-generic expressions using the ``_Generic`` keyword. For
42 processor for Zephyr, makes use of the C11 type-generic expressions, and this
44 toolchain that supports the C11 standard and above.
[all …]
Dnewlib.rst13 Other 3rd-party toolchains, such as :ref:`toolchain_gnuarmemb`, also bundle
16 Zephyr implements the "API hook" functions that are invoked by the C standard
18 :file:`lib/libc/newlib/libc-hooks.c` and translate the library internal system
32 standard C library features. It is optimized for performance (prefers
37 :kconfig:option:`CONFIG_NEWLIB_LIBC` and de-selecting the
45 size-optimized version of the Newlib, and supports all features that the full
64 Newlib supports all standard C formatted input and output functions, including
68 format specifiers defined by the C standard with the following exceptions:
81 by the standard dynamic memory management interface functions (for example,
92 the Zephyr-side libc hooks is the :c:func:`sbrk` function, which is used by the
[all …]
/Zephyr-latest/drivers/ieee802154/
DKconfig.cc12003 # SPDX-License-Identifier: Apache-2.0
76 bool "Use TI CC1200 RF pre-sets"
87 bool "IEEE 802.15.4g SUN MR-FSK, 863MHz band, mode #1 - channel page 9, 34 channels, 50Kbps (ETSI)"
89 This is a legacy IEEE 802.15.4g-2012 SUN MR-FSK PHY that does no
90 longer exist in recent standards (IEEE 802.15.4-2015+).
93 bool "IEEE 802.15.4g SUN MR-FSK 920MHz band, mode #1 - channel page 9, 39 channels, 50Kbps (ARIB)"
95 This is a legacy IEEE 802.15.4g-2012 SUN MR-FSK PHY that does no
96 longer exist in recent standards (IEEE 802.15.4-2015+).
99 bool "IEEE 802.15.4 Non-Standard 2-GFSK 433MHz band - channel page 9, 15 channels, 50Kbps (ETSI)"
101 This is a non-standard PHY similar to the IEEE 802.15.4g-2012 SUN
[all …]
Dieee802154_cc13xx_cc26xx.h4 * SPDX-License-Identifier: Apache-2.0
6 * References are to the IEEE 802.15.4-2020 standard.
24 /* For O-QPSK the physical and MAC timing symbol rates are the same, see section 12.3.3. */
28 /* PHY PIB attribute phyCcaMode - CCA Mode 3: Carrier sense with energy above threshold, see
29 * section 11.3, table 11-2 and section 10.2.8
40 /* IEEE 802.15.4-2006 MAC PIB attributes (7.4.2)
43 * non-beacon enabled PANs (See IEEE 802.15.4-2006 7.5.6.4.2)
56 #define CC13XX_CC26XX_CPE0_IRQ (INT_RFC_CPE_0 - 16)
57 #define CC13XX_CC26XX_CPE1_IRQ (INT_RFC_CPE_1 - 16)
59 #define CC13XX_CC26XX_RECEIVER_SENSITIVITY -100
/Zephyr-latest/lib/posix/options/
DKconfig.spinlock3 # SPDX-License-Identifier: Apache-2.0
21 Note: this is a non-standard option.
24 module-str = POSIX Spin Locks
DKconfig.rwlock3 # SPDX-License-Identifier: Apache-2.0
6 bool "POSIX reader-writer locks"
8 Select 'y' here to enable POSIX reader-writer locks.
16 int "Maximum number of POSIX reader-writer locks"
19 Maximum simultaneously active reader-writer locks in a POSIX application.
21 Note: this is a non-standard option.
24 module-str = POSIX Reader-Writer Locks
DKconfig.barrier5 # SPDX-License-Identifier: Apache-2.0
23 Note: this is a non-standard option.
37 module-str = POSIX thread barriers
/Zephyr-latest/drivers/dma/
Ddma_xilinx_axi_dma.h2 * @brief Definitions and non-standard functions for Xilinx AXI DMA.
7 * SPDX-License-Identifier: Apache-2.0
/Zephyr-latest/doc/develop/languages/cpp/
Dindex.rst6 C++ is a general-purpose object-oriented programming language that is based on
22 The default C++ standard level (i.e. the language enforced by the
25 :kconfig:option:`CONFIG_STD_CPP98`. The oldest standard supported and
33 The C++ standard requires the ``main()`` function to have the return type of
49 * OS-specific C++ standard library classes (e.g. ``std::thread``,
62 * Standard Template Library (STL)
76 of the C++ standard library and application binary interface (ABI) functions to
84 C++ language support, and it does not implement any `Standard Template Library
86 the applications that implement their own (non-standard) class library and do
87 not rely on the Standard Template Library (STL) components.
[all …]
/Zephyr-latest/samples/tfm_integration/tfm_secure_partition/
DREADME.rst1 .. zephyr:code-sample:: tfm_secure_partition
2 :name: TF-M Secure Partition
9 A Secure Partition is an isolated module that resides in TF-M. It exposes a number of functions or
10 "secure services" to other partitions and/or to the non-secure firmware. TF-M already contains
11 standard partitions such as crypto, protected_storage, or firmware_update, but it's also possible to
14 This sample creates a dummy secure partition and secure service for TF-M and instructs the TF-M
16 main file (in the non-secure firmware).
22 build files and build configuration files. The partition is built by the TF-M build system, refer to
25 For more information on how to add custom secure partitions refer to TF-M's guide:
26 https://tf-m-user-guide.trustedfirmware.org/integration_guide/services/tfm_secure_partition_additio…
[all …]
/Zephyr-latest/doc/safety/
Dsafety_overview.rst9 This document is the safety documentation providing an overview over the safety-relevant activities
20 is, what standard we aim to achieve and what quality standards and processes need to be implemented
41 <https://en.wikipedia.org/wiki/IEC_61508>`__ standard and the Safety Integrity Level (SIL) 3 /
43 code base is pre-existing, we use the route 3s/1s approach defined by the IEC 61508 standard.
46 *Assessment of non-compliant development. Which is basically the route 1s with existing
50 *Compliant development. Compliance with the requirements of this standard for the avoidance and
53 Summarization IEC 61508 standard
56 The IEC 61508 standard is a widely recognized international standard for functional safety of
57 electrical, electronic, and programmable electronic safety-related systems. Here's an overview of
58 some of the key safety aspects of the standard:
[all …]
/Zephyr-latest/doc/connectivity/networking/api/
Dptp.rst15 The stack supports the protocol and procedures as defined in the `IEEE 1588-2019 standard`_
16 (IEEE Standard for a Precision Clock Synchronization Protocol
32 Implementation of the stack doesn't support all features specified in the standard.
35 .. csv-table:: Supported features
48 Non-volatile storage,
60 Based on Table 59 from section 15.5.2.3 of the IEEE 1588-2019 following management TLVs
63 .. csv-table:: Supported management message's IDs
70 0x0003, SAVE_IN_NON_VOLATILE_STORAGE, -
71 0x0004, RESET_NON_VOLATILE_STORAGE, -
72 0x0005, INITIALIZE, -
[all …]
/Zephyr-latest/include/zephyr/net/
Dieee802154_mgmt.h4 * SPDX-License-Identifier: Apache-2.0
11 * @note All references to the standard in this file cite IEEE 802.15.4-2020.
38 * @note All section, table and figure references are to the IEEE 802.15.4-2020
39 * standard.
94 * - MLME-ASSOCIATE.request, see section 8.2.3
95 * - MLME-DISASSOCIATE.request, see section 8.2.4
96 * - MLME-SET/GET.request, see section 8.2.6
97 * - MLME-SCAN.request, see section 8.2.11
101 * - MLME-DATA.request, see section 8.3.2
105 * Both are accessed through MLME-SET/GET primitives.
[all …]
Dptp_time.h4 * SPDX-License-Identifier: Apache-2.0
39 * Time Protocol standard ("PTP", IEEE 1588, section 5.3.3), the Generalized
40 * Precision Time Protocol standard ("gPTP", IEEE 802.1AS, section 6.4.3.4), or
41 * any other well-defined context in which precision structured timestamps are
55 * For (g)PTP the media-specific message timestamp points and reference planes
56 * are defined in the standard. In non-PTP contexts specific to Zephyr,
58 * context-specific message timestamp point and reference plane, defined below
61 * A @em "LocalClock" is a freerunning clock, embedded into a well-defined
67 * driver, counter driver, RTC API driver or low-level counter/timer peripheral
74 * See IEEE 802.15.4-2020, section 15.7 for requirements in the context of
[all …]
/Zephyr-latest/doc/services/binary_descriptors/
Dindex.rst14 .. code-block:: c
22 .. code-block:: c
28 .. code-block:: bash
57 always aligned to 32 bits. If the value of the previous descriptor had a non-aligned
63 .. code-block::
72 ID. However, it is recommended to comply with the standard tags defined in
78 3. It allows upstream-ability of descriptor generation (see Standard Descriptors)
80 To define a descriptor with a standard tag, just use the tags included from ``bindesc.h``:
82 .. code-block:: c
88 Standard Descriptors
[all …]
/Zephyr-latest/samples/tfm_integration/
Dtfm_integration.rst1 .. zephyr:code-sample-category:: tfm_integration
2 :name: TF-M Integration
3 :show-listing:
5 These TF-M integration examples can be used with a supported Armv8-M board, and demonstrate how
6 the TF-M APIs can be used with Zephyr.
12 secure processing environment (S), with Zephyr running in the non-secure
15 As part of the standard build process, the secure bootloader (BL2) is normally
16 built, in addition to the TF-M S and Zephyr NS binary images. The S and NS
23 What is Trusted Firmware-M (TF-M)?
26 Trusted Firmware-M (TF-M) is the reference implementation of `Platform Security
[all …]
/Zephyr-latest/tests/lib/c_lib/common/
DREADME.txt1 Title: Kernel Access to Standard Libraries
5 This test verifies kernel access to the standard C libraries.
7 or non-functional, and is NOT intended to be a comprehensive test suite
10 --------------------------------------------------------------------------------
19 --------------------------------------------------------------------------------
23 Problems caused by out-dated project information can be addressed by
30 # and restore pre-defined configuration info
32 --------------------------------------------------------------------------------
36 ***** BOOTING ZEPHYR OS vxxxx - BUILD: xxxx *****
38 tc_start() - limits_test
[all …]
/Zephyr-latest/drivers/serial/
DKconfig.native_posix1 # SPDX-License-Identifier: Apache-2.0
26 backend which may use the invoking shell standard input/output.
34 Note that other, non UART messages, will also be printed to the
47 ``--wait_uart``
48 When ``--wait_uart`` is used, writes to the UART will be held until a
56 This is used for example in PPP (Point-to-Point Protocol)
61 default "xterm -e screen %s &"
63 If the native executable is called with the --attach_uart
72 'gnome-terminal -- screen %s'
/Zephyr-latest/drivers/flash/
DKconfig.nor1 # Copyright (c) 2018 Savoir-Faire Linux.
4 # SPDX-License-Identifier: Apache-2.0
27 set by the page-size devicetree property) and
28 standard 4 KiBy and 64 KiBy erase instructions. Requires the size and
29 jedec-id properties in the devicetree jedec,spi-nor node.
35 sfdp-bfp property in devicetree. The size and jedec-id properties are
43 for all supported JESD216-compatible devices.
77 size (65536). Other options include the 32K-byte erase size
78 (32768), the sector size (4096), or any non-zero multiple of the
89 call, eliminating the active->idle->active transition sequence if another
/Zephyr-latest/doc/contribute/coding_guidelines/
Dindex.rst13 but not enforced. Rules are not yet enforced in CI and pull-requests cannot be
41 <https://github.com/zephyrproject-rtos/zephyr/issues/58903>`__ is being worked on.
46 The coding guideline rules are based on MISRA-C 2012 and are a **subset** of MISRA-C.
54 available through the project. If you need a copy of MISRA-C 2012, please
60 .. list-table:: Main rules
61 :header-rows: 1
64 * - Zephyr rule
65 - Description
66 - MISRA-C 2012 rule
67 - MISRA-C severity
[all …]
/Zephyr-latest/doc/services/
Dformatted_output.rst7 values for user consumption. The standard C99 library ``*printf()``
15 applications made use of either these APIs or standard libc routines
36 that behave like standard libc functions but use the selected cbprintf
40 the very space-optimized but limited formatter used for :c:func:`printk`
51 Such state forms a self-contained package which contains format string and
54 content resembles va_list stack frame thus standard formatting functions are
62 * **Self-contained** - non read-only strings appended to the package. String can be
63 formatted from such package as long as there is access to read-only string
64 locations. Package may contain information where read-only strings are located
66 self-contained package.
[all …]
/Zephyr-latest/doc/services/tfm/
Doverview.rst1 Trusted Firmware-M Overview
4 `Trusted Firmware-M (TF-M) <https://tf-m-user-guide.trustedfirmware.org/>`__
6 `IoT Security Framework <https://www.psacertified.org/what-is-psa-certified/>`__.
10 Zephyr RTOS has been PSA Certified since Zephyr 2.0.0 with TF-M 1.0, and
11 is currently integrated with TF-M 2.1.0.
13 What Does TF-M Offer?
16 Through a set of secure services and by design, TF-M provides:
18 * Isolation of secure and non-secure resources
19 * Embedded-appropriate crypto
22 * Protected off-chip data storage and retrieval
[all …]

12345678