Searched full:an (Results 1 – 25 of 3182) sorted by relevance
12345678910>>...128
| /Zephyr-Core-3.5.0/samples/basic/blinky_pwm/ |
| D | README.rst | 5 Blink an LED using the PWM API.
10 This application blinks an LED using the :ref:`PWM API <pwm_api>`. See
26 The board must have an LED connected to a PWM output channel. The PWM
35 already connected to an LED on the board.
45 - connect PWM2 (PA0) to an LED
47 - connect PWM2 (PA0) to an LED
49 - connect PWM2 (PA0) to an LED
51 - connect PWM2 (PA0) to an LED
53 - connect PWM1 (PA8) to an LED
55 - connect PWM1 (PA8) to an LED
[all …]
|
| /Zephyr-Core-3.5.0/tests/bluetooth/host/buf/bt_buf_get_rx/src/ |
| D | test_suite_invalid_inputs.c | 20 * - An assertion should be raised as an invalid parameter was used
35 * - An assertion should be raised as an invalid parameter was used
50 * - An assertion should be raised as an invalid parameter was used
65 * - An assertion should be raised as an invalid parameter was used
|
| /Zephyr-Core-3.5.0/doc/kernel/services/other/ |
| D | atomic.rst | 6 An :dfn:`atomic variable` is one that can be read and modified
7 by threads and ISRs in an uninterruptible manner. It 32-bit on
19 Using the kernel's atomic APIs to manipulate an atomic variable
24 in an array of atomic variables.
29 Defining an Atomic Variable
32 An atomic variable is defined using a variable of type :c:type:`atomic_t`.
34 By default an atomic variable is initialized to zero. However, it can be given
41 Manipulating an Atomic Variable
44 An atomic variable is manipulated using the APIs listed at the end of
47 The following code shows how an atomic variable can be used to keep track
[all …]
|
| /Zephyr-Core-3.5.0/doc/services/ipc/ipc_service/ |
| D | ipc_service.rst | 10 The IPC service API provides an interface to exchange data between two domains
16 An IPC service communication channel consists of one instance and one or
19 An instance is the external representation of a physical communication channel
23 An individual instance is not used to send data between domains/CPUs. To send
24 and receive the data, the user must create (register) an endpoint in the
32 The endpoint is an entity the user must use to send and receive data between
33 two domains (connected by the instance). An endpoint is always associated to an
41 parameters for an instance. Currently, each backend defines its own
53 To send data between domains or CPUs, an endpoint must be registered onto
54 an instance.
[all …]
|
| /Zephyr-Core-3.5.0/arch/arm/include/cortex_m/ |
| D | cmse.h | 38 * @brief Get the MPU region number of an address
41 * or -EINVAL to indicate that an invalid MPU region was retrieved.
56 * @brief Read accessibility of an address
62 * - if executed from an unprivileged mode,
75 * @brief Read and Write accessibility of an address
82 * - if executed from an unprivileged mode,
95 * @brief Read accessibility of an address range
102 * - if executed from an unprivileged mode,
105 * @param addr The base address of an address range,
117 * @brief Read and Write accessibility of an address range
[all …]
|
| /Zephyr-Core-3.5.0/include/zephyr/sys/ |
| D | onoff.h | 26 * @brief Flag indicating an error state.
41 * whether the machine has an unfixed error, or compare against
60 * @brief Value exposed by ONOFF_STATE_MASK when the service is in an
88 * @brief Signature used to notify an on-off manager that a transition
98 * non-negative on success, or a negative error code. If an error is
99 * indicated the service shall enter an error state.
110 * one to reset the service when it is in an error state.
147 * @brief State associated with an on-off manager.
188 * to an off state. Can be null.
203 * @brief Initialize an on-off service to off state.
[all …]
|
| /Zephyr-Core-3.5.0/doc/project/ |
| D | proposals.rst | 11 block a release. This is an incremental enhancement to a feature that already
21 implementation proposal and an owner. Features must go through an RFC process
25 A request or plan to port an existing feature or enhancement to a particular
27 architecture, SoC or board to adding an implementation of a peripheral driver
28 API for an existing hardware platform.
38 willingness to drive implementation of the feature in an upcoming release, and
40 If not though, an owner will be assigned after evaluation by the TSC.
55 ``feature-request`` to ``feature`` with the target milestone and an assignee.
57 All items marked as ``feature-request`` are non-binding and those without an
59 by any project member or the community. You should contact an assigned owner if
[all …]
|
| /Zephyr-Core-3.5.0/include/zephyr/devicetree/ |
| D | io-channels.h | 27 * @brief Get the node identifier for the node referenced by an
28 * io-channels property at an index
45 * @param node_id node identifier for a node with an io-channels property
54 * @brief Get the node identifier for the node referenced by an
73 * @param node_id node identifier for a node with an io-channels property
74 * @param name lowercase-and-underscores name of an io-channels element
84 * @param node_id node identifier for a node with an io-channels property
93 * property at an index
107 * @param name lowercase-and-underscores name of an io-channels element
125 * @brief Get an io-channels specifier input cell at an index
[all …]
|
| /Zephyr-Core-3.5.0/tests/subsys/mgmt/mcumgr/settings_mgmt/src/ |
| D | smp_test_util.h | 15 /* Function for creating an settings_mgmt read command */
19 /* Function for creating an settings_mgmt write command */
24 /* Function for creating an settings_mgmt delete command */
28 /* Function for creating an settings_mgmt commit command */
32 /* Function for creating an settings_mgmt load command */
36 /* Function for creating an settings_mgmt save command */
|
| /Zephyr-Core-3.5.0/include/zephyr/drivers/console/ |
| D | uart_mcumgr.h | 24 * @brief Contains an mcumgr fragment received over UART.
33 * @brief Function that gets called when an mcumgr packet is received.
35 * Function that gets called when an mcumgr packet is received. This function
44 * @brief Sends an mcumgr packet over UART.
61 * @brief Registers an mcumgr UART receive handler.
63 * Configures the mcumgr UART driver to call the specified function when an
66 * @param cb The callback to execute when an mcumgr request
|
| /Zephyr-Core-3.5.0/doc/kernel/services/synchronization/ |
| D | events.rst | 6 An :dfn:`event object` is a kernel object that implements traditional events.
17 on an event object until the desired set of events has been delivered to the
21 An event object has the following key properties:
25 An event object must be initialized before it can be used.
27 Events may be **delivered** by a thread or an ISR. When delivering events, the
42 The kernel does allow an ISR to query an event object, however the ISR must
48 Defining an Event Object
51 An event object is defined using a variable of type :c:struct:`k_event`.
54 The following code defines an event object.
62 Alternatively, an event object can be defined and initialized at compile time
[all …]
|
| /Zephyr-Core-3.5.0/doc/services/portability/ |
| D | cmsis_rtos_v2.rst | 25 not set, an error is thrown when the same thread tries to acquire
38 semaphore_id is in an invalid semaphore state) is not supported.
42 is in an invalid mutex state) is not supported.
46 is in an invalid timer state) is not supported.
50 parameter msgq_id is in an invalid message queue state)
55 parameter msgq_id is in an invalid message queue state)
60 parameter mp_id is in an invalid memory pool state) is
65 parameter mp_id is in an invalid memory pool state) is
|
| /Zephyr-Core-3.5.0/doc/connectivity/networking/api/ |
| D | mqtt.rst | 13 MQTT (Message Queuing Telemetry Transport) is an application layer protocol
18 Zephyr provides an MQTT client library built on top of BSD sockets API. The
24 MQTT clients require an MQTT server to connect to. Such a server, called an MQTT Broker,
33 To create an MQTT client, a client context structure and buffers need to be
55 An MQTT client library will notify MQTT events to the application through a
71 used. An example configuration for TCP transport is shown below:
95 establish a TCP/TLS connection, and send an ``MQTT CONNECT`` message.
124 After the connection is established, an application needs to call ``mqtt_input``
126 the connection. If an MQTT message is received, an MQTT callback function will
127 be called and an appropriate event notified.
[all …]
|
| /Zephyr-Core-3.5.0/include/zephyr/drivers/gpio/ |
| D | gpio_emul.h | 38 * An example of an appropriate Device Tree overlay file is in
41 * An example of registering a callback to emulate "wiring" as well as
42 * an example of calling @ref gpio_emul_input_set is in the file
54 * @return -EINVAL if an invalid argument is provided
67 * @return -EINVAL if an invalid argument is provided
83 * @return -EINVAL if an invalid argument is provided
95 * @return -EINVAL if an invalid argument is provided
120 * @return -EINVAL if an invalid argument is provided
|
| /Zephyr-Core-3.5.0/include/zephyr/ipc/ |
| D | ipc_rpmsg.h | 34 * This callback is defined at instance level and it is called when an endpoint
43 * Used to define an endpoint to be encapsulated in an RPMsg instance.
67 * Struct representation of an RPMsg instance.
89 /** @brief Init an RPMsg instance.
91 * Init an RPMsg instance.
119 * Deinit an RPMsg instance
130 /** @brief Register an endpoint.
132 * Register an endpoint to a provided RPMsg instance.
|
| /Zephyr-Core-3.5.0/doc/ |
| D | glossary.rst | 17 to build an application image for a specified board configuration.
23 An application can sometimes be built for more than one type of board
33 Once an application image is loaded onto a board, the image takes control
40 which can load and execute an application image. It may be an actual
64 architecture to implement an interrupt vector table. The IDT is used
68 (Interrupt Service Routine) Also known as an interrupt handler, an ISR
84 Power gating reduces power consumption by shutting off areas of an
98 An obsolete term for a :term:`west workspace` used prior to west 0.7.
|
| /Zephyr-Core-3.5.0/scripts/dts/python-devicetree/tests/test-bindings-include/ |
| D | allow-and-blocklist.yaml | 4 An include must not give both an allowlist and a blocklist.
5 This binding should cause an error.
|
| D | allow-and-blocklist-child.yaml | 4 An include must not give both an allowlist and a blocklist in a
5 child binding. This binding should cause an error.
|
| /Zephyr-Core-3.5.0/doc/services/resource_management/ |
| D | index.rst | 26 An on-off manager supports an arbitrary number of clients of a service
36 a dependency). Supporting operations are reset (to clear an error
37 state) and cancel (to reclaim client data from an in-progress
45 transition from off to on, from on to off, and optionally from an
59 a request. Improper use of the API can cause an active client to be
71 changes, including when a service begins turning off or enters an error
80 case is asynchronous. The on-off client structure may be an
|
| /Zephyr-Core-3.5.0/doc/kernel/services/ |
| D | interrupts.rst | 6 An :dfn:`interrupt service routine` (ISR) is a function that executes
8 An ISR normally preempts the execution of the current thread,
22 An ISR has the following key properties:
24 * An **interrupt request (IRQ) signal** that triggers the ISR.
26 * An **interrupt handler function** that is invoked to handle the interrupt.
27 * An **argument value** that is passed to that function.
29 An :abbr:`IDT (Interrupt Descriptor Table)` or a vector table is used
36 (usually of the same type). The argument value passed to an ISR's function
40 generates a fatal system error if an unexpected interrupt is signaled.
42 The kernel supports **interrupt nesting**. This allows an ISR to be preempted
[all …]
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/audio/ |
| D | Kconfig.ascs | 20 An ASE Sink characteristic represents the state of an ASE, which is
28 An ASE Source characteristic represents the state of an ASE, which is
66 an ASE read or dropping a notification if the ASE state is being accessed by another
|
| /Zephyr-Core-3.5.0/doc/kernel/data_structures/ |
| D | slist.rst | 37 have a node added to an interior point with :c:func:`sys_slist_insert`,
38 which inserts a new node after an existing one. Similarly
43 list. :c:func:`sys_slist_merge_slist` will append an entire list to an
45 subset of an existing list in constant time. And
54 similarly, but has a more complicated implementation that requires an
78 An slist containing three elements.
85 An empty slist
87 The specific implementation of the list code, however, is done with an
89 fields from arbitrary structures and emits an arbitrarily named set of
93 primitive operations only: an "init" step for each struct, and a "get"
|
| /Zephyr-Core-3.5.0/scripts/kconfig/ |
| D | kconfigfunctions.py | 57 to an EDT node. If it finds an EDT node, it will look to see if that node
77 that points to an enabled node, and "n" otherwise
121 The 'node' argument is a string which is either a path or an
124 If 'name' is 'dt_path_enabled', 'node' is an alias or a path. If
125 'name' is 'dt_alias_enabled, 'node' is an alias.
134 # are specifically being asked about an alias, reject paths.
198 property called 'prop' and if that 'prop' is an integer type will return
226 property called 'prop' and if that 'prop' is an array type will return
252 to an EDT node. If it finds an EDT node, it will look to see if that
276 to an EDT node. If it finds an EDT node, it will look to see if that node
[all …]
|
| /Zephyr-Core-3.5.0/ |
| D | CODE_OF_CONDUCT.md | 5 In the interest of fostering an open and welcoming environment, we as
49 when an individual is representing the project or its community. Examples of
50 representing a project or community include using an official project e-mail
51 address, posting via an official social media account, or acting as an appointed
52 representative at an online or offline event. Representation of a project may be
63 reporter of an incident. Further details of specific enforcement policies may
|
| /Zephyr-Core-3.5.0/doc/services/llext/ |
| D | index.rst | 6 The llext subsystem provides a toolbox for extending the functionality of an
14 An extension may be loaded using any implementation of a :c:struct:`llext_loader`
17 needed by the :c:func:`llext_load` function. An implementation over a buffer
18 containing an ELF in addressable memory in memory is available as
|
12345678910>>...128
