Searched +full:application +full:- +full:specific (Results 1 – 25 of 482) sorted by relevance
12345678910>>...20
| /Zephyr-Core-3.7.0/doc/services/tfm/ |
| D | testsuites.rst | 4 TF-M includes two sets of test suites:
6 * tf-m-tests - Standard TF-M specific regression tests
7 * psa-arch-tests - Test suites for specific PSA APIs (secure storage, etc.)
9 These test suites can be run from Zephyr via an appropriate sample application
12 TF-M Regression Tests
20 application (TF-M).
27 being followed by the secure application, TF-M being an implementation of
37 your specific board, RTOS (Zephyr here), and PSA implementation (TF-M in this
41 changes to TF-M, such as enabling a new TF-M board target, or making changes
42 to the core TF-M module(s). They should generally be run as a coherence check
|
| /Zephyr-Core-3.7.0/samples/boards/arc_secure_services/ |
| D | README.rst | 10 demonstrate how a secure zephyr application runs together with a normal
11 Zephyr application.
15 * Secure application will be in the secure memory space defined in
19 * Memory not allocated to the secure application is allocated to
20 the normal application.
41 * secure application: em_starterkit_em7d_secure
42 * normal application: em_starterkit_em7d_normal
44 * secure application: nsim_sem
45 * normal application: nsim_sem_normal
53 Secure application
[all …]
|
| /Zephyr-Core-3.7.0/samples/bluetooth/hci_spi/ |
| D | README.rst | 1 .. _bluetooth-hci-spi-sample:
20 You then need to ensure that your :ref:`devicetree <dt-guide>` defines a node
22 :dtcompatible:`zephyr,bt-hci-spi-slave`. This node sets an interrupt line to
23 the host and associates the application with a SPI bus to use.
29 You can then build this application and flash it onto your board in
30 the usual way; see :ref:`boards` for board-specific building and
34 application is compatible with the HCI SPI master driver provided by
38 Refer to :ref:`bluetooth-samples` for general Bluetooth information, and
39 to :ref:`96b_carbon_nrf51_bluetooth` for instructions specific to the
|
| /Zephyr-Core-3.7.0/drivers/input/ |
| D | Kconfig.kbd_matrix | 2 # SPDX-License-Identifier: Apache-2.0
34 If enabled, the actual-key-mask devicetree property data is stored in
56 Call an application specific hook after the driver specific
57 drive_column implementation. The application must implement the
|
| /Zephyr-Core-3.7.0/doc/services/input/ |
| D | index.rst | 7 devices to the application.
16 The :c:struct:`input_event` structure describes the specific event, and
19 multi-axis device have been reported.
25 or any related function; for example buttons or other on-off input entities
33 to only receive events from a specific device. If there's no actual device
37 Application API
40 An application can register a callback using the
42 callback is only invoked for events from the specific device, otherwise the
53 The synchronous mode can be used in a simple application to keep a minimal
54 footprint, or in a complex application with an existing event model, where the
[all …]
|
| /Zephyr-Core-3.7.0/include/zephyr/bluetooth/mesh/ |
| D | dfu_metadata.h | 4 * SPDX-License-Identifier: Apache-2.0
42 /** Application core. */
46 /** Application-specific BLOB. */
62 /** Application-specific data for new firmware. This field is optional. */
64 /** Length of the application-specific field. */
93 * @param key 128-bit key to be used in the hash computation.
102 * @param key 128-bit key to be used in the hash computation.
|
| /Zephyr-Core-3.7.0/doc/services/ |
| D | notify.rst | 7 operation is initiated and the application needs to be informed when it
9 often a good method, but some application architectures may be more
12 available so a busy-wait for completion may be needed.
14 This API is intended to be embedded within specific subsystems such as
17 operation-specific data from requests that include a notification
27 * neither the spin-wait nor callback notification methods can be
|
| /Zephyr-Core-3.7.0/include/zephyr/net/ |
| D | dhcpv4.h | 8 * SPDX-License-Identifier: Apache-2.0
74 * @brief Define the application callback handler function signature
78 * greater than cb->max_length, only cb->max_length bytes
79 * will be available in cb->data
129 * @param callback A valid Application's callback structure pointer.
145 callback->handler = handler; in net_dhcpv4_init_option_callback()
146 callback->option = option; in net_dhcpv4_init_option_callback()
147 callback->data = data; in net_dhcpv4_init_option_callback()
148 callback->max_length = max_length; in net_dhcpv4_init_option_callback()
152 * @brief Add an application callback.
[all …]
|
| /Zephyr-Core-3.7.0/samples/userspace/prod_consumer/ |
| D | README.rst | 6 This is a sample application that exercises some user mode concepts.
12 and generates interrupts with pointers to this data. The application needs
18 - Multiple logical applications, each with their own memory domain
19 - Creation of a sys_heap and assignment to a memory partition
20 - Use of APIs like ``k_queue_alloc_append()`` which require thread resource
22 - Management of permissions for kernel objects and drivers
23 - Show how application-specific system calls are defined
24 - Show IPC between ISR and application (using ``k_msgq``) and
25 application-to-application IPC (using ``k_queue``)
26 - Show how to create application-specific system calls
[all …]
|
| /Zephyr-Core-3.7.0/doc/develop/application/ |
| D | index.rst | 3 Application Development
10 …- your **application directory**, :file:`<app>`, is something like :file:`<home>/zephyrproject/app`
11 - its **build directory** is :file:`<app>/build`
16 Keeping your application inside the workspace (:file:`<home>/zephyrproject`)
18 put your application anywhere as long as :ref:`ZEPHYR_BASE
19 <important-build-vars>` is set appropriately, though.)
26 The build system is application-centric, and requires Zephyr-based applications
27 to initiate building the Zephyr source code. The application build controls
28 the configuration and build process of both the application and Zephyr itself,
36 The files in the **application directory** link Zephyr and any modules with the
[all …]
|
| /Zephyr-Core-3.7.0/lib/posix/options/ |
| D | Kconfig.pthread | 5 # SPDX-License-Identifier: Apache-2.0
10 Select 'y' here to enable POSIX threads, mutexes, condition variables, and thread-specific
22 Maximum simultaneously active threads in a POSIX application.
31 Maximum simultaneously active mutexes in a POSIX application.
37 Maximum simultaneously active condition variables in a POSIX application.
40 int "Maximum number of POSIX thread-specific-storage keys"
43 Maximum simultaneously active thread-specific-storage keys in a POSIX application.
71 This option was removed in IEEE 1003.1-2017 in favour of
100 Enabling this option allows the application to configure different priorities and
107 https://man7.org/linux/man-pages/man7/posixoptions.7.html
[all …]
|
| /Zephyr-Core-3.7.0/samples/sensor/mcux_lpcmp/ |
| D | README.rst | 3 NXP MCUX Low-power Analog Comparator (LPCMP)
11 In this application, the negative input port of the LPCMP is set to 7 which
13 voltage of the DAC is set to 0 (for the specific chip, the user needs to
18 manual and board schematic to confirm which specific port is used and can
27 Building and Running for NXP FRDM-MCXN947
29 Build the application for the :ref:`frdm_mcxn947` board, and adjust the
30 LPCMP positive input port voltage by changing the voltage input to J2-17.
32 .. zephyr-app-commands::
33 :zephyr-app: samples/sensor/mcux_lpcmp
|
| /Zephyr-Core-3.7.0/tests/drivers/gpio/gpio_basic_api/ |
| D | README.txt | 1 GPIO 2-Pin Test
4 This application tests the GPIO subsystem using a hardware configuration
6 identified through a test-specific devicetree binding in the `dts/`
7 subdirectory, implemented for specific boards by overlay files in the
|
| /Zephyr-Core-3.7.0/doc/develop/ |
| D | beyond-GSG.rst | 1 .. _beyond-gsg:
6 The :ref:`getting_started` gives a straight-forward path to set up
11 .. _python-pip:
22 ``--user`` flag to the ``pip3`` command when installing new packages. This is
25 information about pip\ [#pip]_, including `information on -\\-user`_.
27 - On Linux, make sure ``~/.local/bin`` is at the front of your :envvar:`PATH`
28 :ref:`environment variable <env_vars>`, or programs installed with ``--user``
29 won't be found. Installing with ``--user`` avoids conflicts between pip
30 and the system package manager, and is the default on Debian-based
33 - On macOS, `Homebrew disables -\\-user`_.
[all …]
|
| /Zephyr-Core-3.7.0/doc/connectivity/networking/api/ |
| D | http_server.rst | 19 The server operation is generally transparent for the application, running in a
20 background thread. The application can control the server activity with
23 Certain resource types (for example dynamic resource) provide resource-specific
24 application callbacks, allowing the server to interact with the application (for
29 * Static resources - content defined compile-time, cannot be modified at runtime
32 * Dynamic resources - content provided at runtime by respective application
35 * Websocket resources - allowing to establish Websocket connections with the
39 resource types usage. See :zephyr:code-sample:`sockets-http-server` for more
46 the application.
51 .. code-block:: cfg
[all …]
|
| /Zephyr-Core-3.7.0/doc/hardware/peripherals/sensor/ |
| D | power_management.rst | 4 Power management of sensors is often a non-trivial task as sensors may have multiple power states
9 All this is to say that power management of sensors is typically application specific! Often the
10 channel states are mutable using :ref:`sensor-attribute`. While total device suspending and resume
15 :ref:`pm-device-runtime` using explicit calls at an application level to :c:func:`pm_device_runtime…
18 In the future, with :ref:`sensor-read-and-decode` its possible that automatic management of device …
19 would be possible in the streaming case as the application informs the driver of usage at all times
|
| /Zephyr-Core-3.7.0/samples/bluetooth/hci_ipc/ |
| D | README.rst | 1 .. _bluetooth-hci-ipc-sample:
23 To use this application, you need a board with a Bluetooth controller
25 You can then build this application and flash it onto your board in
26 the usual way. See :ref:`boards` for board-specific building and
36 compatible with the peer application. For example, :kconfig:option:`CONFIG_BT_MAX_CONN`
37 must be equal to the maximum number of connections supported by the peer application.
39 Refer to :ref:`bluetooth-samples` for general information about Bluetooth samples.
|
| /Zephyr-Core-3.7.0/doc/ |
| D | glossary.rst | 12 (Application Program Interface) A defined set of routines and protocols for
13 building application software.
15 application
16 The set of user-supplied files that the Zephyr build system uses
17 to build an application image for a specified board configuration.
18 It can contain application-specific code, kernel configuration settings,
20 The application's kernel configuration settings direct the build system
23 An application can sometimes be built for more than one type of board
25 if it does not require any board-specific capabilities.
27 application image
[all …]
|
| /Zephyr-Core-3.7.0/soc/arm/mps2/ |
| D | soc.c | 5 * Copyright (c) 2013-2015 Wind River Systems, Inc.
7 * SPDX-License-Identifier: Apache-2.0
12 #include <zephyr/linker/linker-defs.h>
22 /* We expect there to be 3 arm,mps2-fpgaio-gpio devices:
35 /* The base address that the application image will start at on the secondary
36 * (non-TrustZone) Cortex-M33 mcu.
40 /* The memory map offset for the application image, which is used
46 * @brief Wake up CPU 1 from another CPU, this is platform specific.
53 CPU1_FLASH_ADDRESS - in wakeup_cpu1()
61 * @brief Get the current CPU ID, this is platform specific.
|
| /Zephyr-Core-3.7.0/boards/nxp/lpcxpresso55s16/ |
| D | lpcxpresso55s16.dts | 5 * SPDX-License-Identifier: Apache-2.0
8 /dts-v1/;
19 * Default for this board is to allocate SRAM0-2 for data. But the
20 * application can have an application specific device tree to
34 tx-d-cal = <5>;
35 tx-cal-45-dp-ohms = <10>;
36 tx-cal-45-dm-ohms = <10>;
|
| /Zephyr-Core-3.7.0/subsys/bluetooth/host/ |
| D | Kconfig.gatt | 4 # SPDX-License-Identifier: Apache-2.0
72 bool "Automatic re-subscription to characteristics"
77 Quirk: upon re-establishing a bonded connection, assumes the remote
81 This also means that upon a reconnection, the application will get an
85 bool "Automatic security re-establishment request as a peripheral"
89 This option requests security re-establishment automatically whenever
94 When disabled, it is the application's responsibility to call
95 bt_conn_set_security() to re-establish security prior to sending any
157 bool "GATT Enforce change-unaware state"
164 a client until it becomes change-aware."
[all …]
|
| /Zephyr-Core-3.7.0/doc/build/sysbuild/ |
| D | index.rst | 6 Sysbuild is a higher-level build system that can be used to combine multiple
7 other build systems together. It is a higher-level layer that combines one
11 For example, you can use sysbuild to build a Zephyr application together
15 Sysbuild works by configuring and building at least a Zephyr application and, optionally, as many
27 Single-image build
28 When sysbuild is used to create and manage just one Zephyr application's
31 Multi-image build
34 application images from each build system.
39 Multi-domain
50 :figclass: align-center
[all …]
|
| /Zephyr-Core-3.7.0/doc/hardware/emulator/ |
| D | bus_emulators.rst | 20 been completed. This allows for testing that high-level code can
27 The diagram below shows application code / high-level tests at the top.
28 This is the ultimate application we want to run.
43 Putting the two together, we can test the application and peripheral code
45 works, we should expect the application and peripheral drivers to work on the
48 Using the above framework we can test an entire application (e.g. Embedded
49 Controller) on native_sim using emulators for all non-chip drivers.
62 * Write a complex application that ties together all of these pieces and runs on
63 native_sim. We can develop on a host, use source-level debugging, etc.
65 * Transfer the application to any board which provides the required features
[all …]
|
| /Zephyr-Core-3.7.0/soc/nxp/imxrt/ |
| D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0
15 DT_COMPAT_FLEXSPI := nxp,imx-flexspi
54 # Note- When SECOND_CORE_MCUX is set, the dependencies for this Kconfig
56 # requires the boot header is SOC specific.
63 application from an external flash device.
94 FlexSPI configuration block consists of parameters regarding specific
105 the application entry point and device configuration data. The boot
113 useful if your application expects components like SDRAM to be
134 placed in a specific address location to be pointed by the boot ROM.
142 setting should be enabled when the application uses SDRAM, or
[all …]
|
| /Zephyr-Core-3.7.0/tests/drivers/i2c/i2c_target_api/ |
| D | README.txt | 9 controllers on a common bus. The test is supported by a test-specific
11 is pre-loaded into the simulated devices outside the I2C API, and the
12 Zephyr application issues commands to one controller that are responded
17 I2C controllers, so this behavior is now opt-in using
23 * Use API specific to the simulated EEPROM to pre-populate the simulated
24 devices with device-specific content.
|
12345678910>>...20
