Searched +full:in +full:- +full:application (Results 1 – 25 of 1155) sorted by relevance
12345678910>>...47
| /Zephyr-latest/subsys/portability/cmsis_rtos_v2/ |
| D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0
13 This enables CMSIS RTOS v2 API support. This is an OS-integration
19 int "Maximum thread count in CMSIS RTOS V2 application"
23 Mention max number of threads in CMSIS RTOS V2 compliant application.
28 int "Maximum dynamic thread count in CMSIS RTOS V2 application"
32 Mention max number of dynamic threads in CMSIS RTOS V2 compliant
33 application. There's a limitation on the number of threads due to memory
38 int "Max stack size threads can be allocated in CMSIS RTOS V2 application"
42 Mention max stack size threads can be allocated in CMSIS RTOS V2 application.
45 int "Dynamic stack size threads are allocated in CMSIS RTOS V2 application"
[all …]
|
| /Zephyr-latest/share/sysbuild/images/bootloader/ |
| D | Kconfig | 3 # SPDX-License-Identifier: Apache-2.0
21 Do not Include a bootloader in the build
37 The operating mode of MCUboot (which will also be propagated to the application).
42 MCUboot will only boot slot0_partition placed application and does not care about other
43 slots. In this mode application is not able to DFU its own update to secondary slot and
49 MCUboot expects slot0_partition and slot1_partition to be present in DT and application
51 in main application if MCUboot has been built with MCUBOOT_DOWNGRADE_PREVENTION.
56 MCUboot expects slot0_partition, slot1_partition and scratch_partition to be present in
57 DT, and application will boot from slot0_partition. In this mode scratch_partition is
58 used as temporary storage when MCUboot swaps application from the secondary slot to the
[all …]
|
| /Zephyr-latest/subsys/portability/cmsis_rtos_v1/ |
| D | Kconfig | 2 # SPDX-License-Identifier: Apache-2.0
11 This enables CMSIS RTOS v1 API support. This is an OS-integration
18 int "Max stack size threads can be allocated in CMSIS RTOS application"
22 Mention max stack size threads can be allocated in CMSIS RTOS application.
25 int "Maximum timer count in CMSIS application"
29 Mention maximum number of timers in CMSIS compliant application.
32 int "Maximum mutex count in CMSIS application"
36 Mention maximum number of mutexes in CMSIS compliant application.
39 int "Maximum semaphore count in CMSIS application"
43 Mention maximum number of semaphores in CMSIS compliant application.
|
| /Zephyr-latest/samples/boards/arc_secure_services/ |
| D | README.rst | 12 demonstrate how a secure zephyr application runs together with a normal
13 Zephyr application.
15 In this sample:
17 * Secure application will be in the secure memory space defined in
21 * Memory not allocated to the secure application is allocated to
22 the normal application.
27 mpu entry in ``arc_mpu_regions.c``.
39 To use this sample, ARC processor should be equipped with ARC SecureShield. In
43 * secure application: em_starterkit_em7d_secure
44 * normal application: em_starterkit_em7d_normal
[all …]
|
| /Zephyr-latest/doc/develop/application/ |
| D | index.rst | 3 Application Development
8 In this document, we'll assume:
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,
[all …]
|
| /Zephyr-latest/modules/ |
| D | Kconfig.mcuboot | 3 # Copyright (c) 2014-2015 Wind River Systems, Inc.
6 # SPDX-License-Identifier: Apache-2.0
20 or in other words that the image is to be chain-loaded by MCUboot.
21 This sets several required build system and Device Tree options in
27 * Activating SW_VECTOR_RELAY_CLIENT on Cortex-M0
28 (or Armv8-M baseline) targets with no built-in vector relocation
33 the application. This removes the need by MCUboot to reset
44 by your target's MCUboot image. The file is in PEM format.
46 If set to a non-empty value, the build system tries to
47 sign the final binaries using a 'west sign -t imgtool' command.
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_config.rst | 13 The network configuration library sets up networking devices in a
14 semi-automatic way during the system boot, based on user-supplied
20 .. csv-table:: Kconfig options for network configuration library
26 config library is not used for initialization and the application needs to
29 first network interface in the system. Typically setting static IP addresses
30 is only usable in testing and should not be used in production code. See
39 ":kconfig:option:`CONFIG_NET_CONFIG_NEED_IPV4`", "The network application needs IPv4
40 support to function properly. This option makes sure the network application
41 is initialized properly in order to use IPv4.
44 ":kconfig:option:`CONFIG_NET_CONFIG_NEED_IPV6`", "The network application needs IPv6
[all …]
|
| 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
45 A few prerequisites are needed in order to enable HTTP server functionality in
46 the application.
[all …]
|
| /Zephyr-latest/samples/net/sockets/txtime/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
6 mainmenu "Networking TXTIME sample application"
25 Can be used to select whether the application will use UDP
37 Use AF_PACKET socket. Note that currently the application sends
40 important for this sample application.
45 int "How long to wait between sent packets (in milliseconds)"
49 The application will send network packets between this
50 interval. The value is in milliseconds.
53 int "What is the TXTIME (in microseconds)"
58 packet by the network device driver. The value is in microseconds.
[all …]
|
| D | README.rst | 1 .. zephyr:code-sample:: so_txtime
3 :relevant-api: bsd_sockets ethernet
12 the data when the TX time is expected. The application requires
17 User can control how long the application should wait between packets sent by
19 Also the TXTIME value can be specified in the config file by setting the
20 :kconfig:option:`CONFIG_NET_SAMPLE_PACKET_TXTIME` option. In this case the value is
26 When the application is run, it starts to send UDP packets. You can start
27 ``echo-server`` application from `net-tools`_ project to catch these and
28 send the data back to this application. Optionally you can set
29 :kconfig:option:`CONFIG_NET_SAMPLE_PACKET_SOCKET` option, which makes the application
[all …]
|
| /Zephyr-latest/samples/net/gptp/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
6 # This sample application will have three network interfaces.
7 # gPTP protocol will run in the non-VLAN interface and then there
9 # how to do this kind of setup. See also VLAN sample application
10 # for vlan-setup-linux.sh script that can be used to setup the
11 # VLAN IP addressing in Linux side (if that is desired).
13 mainmenu "gPTP sample application"
33 Set VLAN (virtual LAN) tag (id) that is used in the sample
34 application.
52 Set VLAN (virtual LAN) tag (id) that is used in the sample
[all …]
|
| /Zephyr-latest/subsys/net/lib/config/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
7 module-dep = NET_LOG
8 module-str = Log level for network config library
9 module-help = Enables net config library to output debug messages.
17 Allow IP addresses to be set in config file for
19 some link-layer dedicated settings like the channel.
32 this, then disable this and call net_config_init() in your application.
37 int "Startup priority for the network application init"
41 bool "This application wants IPv6 support"
44 The network application needs IPv6 support to function properly.
[all …]
|
| /Zephyr-latest/samples/userspace/prod_consumer/ |
| D | README.rst | 1 .. zephyr:code-sample:: userspace_prod_consumer
10 and generates interrupts with pointers to this data. The application needs
16 - Multiple logical applications, each with their own memory domain
17 - Creation of a sys_heap and assignment to a memory partition
18 - Use of APIs like ``k_queue_alloc_append()`` which require thread resource
20 - Management of permissions for kernel objects and drivers
21 - Show how application-specific system calls are defined
22 - Show IPC between ISR and application (using ``k_msgq``) and
23 application-to-application IPC (using ``k_queue``)
24 - Show how to create application-specific system calls
[all …]
|
| /Zephyr-latest/samples/net/sockets/http_client/ |
| D | README.rst | 1 .. zephyr:code-sample:: sockets-http-client
3 :relevant-api: bsd_sockets http_client tls_credentials secure_sockets_options
10 This sample application implements an HTTP(S) client that will do an HTTP
13 The source code for this sample application can be found at:
19 - :ref:`networking_with_host`
24 You can use this application on a supported board, including
25 running it inside QEMU as described in :ref:`networking_with_qemu`.
27 Build the http-client sample application like this:
29 .. zephyr-app-commands::
30 :zephyr-app: samples/net/sockets/http_client
[all …]
|
| /Zephyr-latest/samples/bluetooth/direction_finding_peripheral/ |
| D | README.rst | 1 .. zephyr:code-sample:: bluetooth_direction_finding_peripheral
3 :relevant-api: bluetooth
5 Implement Bluetooth LE Direction Finding peripheral transmitting CTE in connected mode.
10 A simple application demonstrating the Bluetooth LE Direction Finding CTE transmission in
26 By default the application supports Angle of Arrival and Angle of Departure mode.
28 To use Angle of Arrival mode only, build this application as follows,
31 .. zephyr-app-commands::
32 :zephyr-app: samples/bluetooth/direction_finding_peripheral
33 :host-os: unix
35 :gen-args: -DEXTRA_CONF_FILE=overlay-aoa.conf
[all …]
|
| /Zephyr-latest/samples/bluetooth/direction_finding_connectionless_tx/ |
| D | README.rst | 1 .. zephyr:code-sample:: ble_direction_finding_connectionless_tx
3 :relevant-api: bt_gap bluetooth
10 A simple application demonstrating the Bluetooth LE Direction Finding CTE Broadcaster
26 By default the application supports Angle of Arrival (AoA) and Angle of
29 To use Angle of Arrival mode only, build this application as follows, changing
32 .. zephyr-app-commands::
33 :zephyr-app: samples/bluetooth/direction_finding_connectionless_tx
34 :host-os: unix
36 :gen-args: -DEXTRA_CONF_FILE=overlay-aoa.conf
40 To run the application on nRF5340DK, a Bluetooth controller application must
[all …]
|
| /Zephyr-latest/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
19 Like Zephyr's :ref:`build system <build_overview>`, sysbuild is written in
25 The following are some key concepts used in this document:
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.
[all …]
|
| /Zephyr-latest/samples/net/sockets/websocket_client/ |
| D | README.rst | 1 .. zephyr:code-sample:: sockets-websocket-client
3 :relevant-api: bsd_sockets websocket
10 This sample application implements a Websocket client that will do an HTTP
14 The source code for this sample application can be found at:
20 - :ref:`networking_with_host`
25 You can use this application on a supported board, including
26 running it inside QEMU as described in :ref:`networking_with_qemu`.
28 Build websocket-client sample application like this:
30 .. zephyr-app-commands::
31 :zephyr-app: samples/net/sockets/websocket_client
[all …]
|
| /Zephyr-latest/samples/bluetooth/direction_finding_central/ |
| D | README.rst | 1 .. zephyr:code-sample:: bluetooth_direction_finding_central
3 :relevant-api: bluetooth
10 A simple application demonstrating the Bluetooth LE Direction Finding CTE reception in
27 By default the application supports Angle of Arrival and Angle of Departure mode.
29 To use Angle of Departure mode only, build this application as follows,
32 .. zephyr-app-commands::
33 :zephyr-app: samples/bluetooth/direction_finding_central
34 :host-os: unix
36 :gen-args: -DEXTRA_CONF_FILE=overlay-aod.conf
40 To run the application on nRF5340DK, a Bluetooth controller application must
[all …]
|
| /Zephyr-latest/include/zephyr/bluetooth/mesh/ |
| D | cdb.h | 4 * SPDX-License-Identifier: Apache-2.0
101 * Remove all nodes, subnets and app-keys stored in the database and mark
109 * The IV Index stored in the CDB will be the one used during provisioning
122 * Allocate a new node in the CDB.
135 * end of the unicast address range, or if @c addr is non-zero and less
145 * @return The first unicast address in an address range that allows a node
170 * @param num_elem Updated number of elements in the node.
196 * will not give a valid value since the key is hidden in the library.
197 * The application has to import the key.
200 * @param in key value.
[all …]
|
| /Zephyr-latest/doc/build/ |
| D | zephyr_cmake_package.rst | 6 The Zephyr `CMake package`_ is a convenient way to create a Zephyr-based application.
9 The :ref:`zephyr-app-types` section introduces the application types
10 used in this page.
13 the application, whether it is a :ref:`Zephyr repository application <zephyr-repo-app>`,
14 a :ref:`Zephyr workspace application <zephyr-workspace-app>`, or a
15 :ref:`Zephyr freestanding application <zephyr-freestanding-app>`.
17 When developing a Zephyr-based application, then a developer simply needs to write
18 ``find_package(Zephyr)`` in the beginning of the application :file:`CMakeLists.txt` file.
27 .. group-tab:: Ubuntu
29 In Linux, the CMake user package registry is found in:
[all …]
|
| /Zephyr-latest/doc/build/kconfig/ |
| D | setting.rst | 7 out configurations during application development. This page explains how to
10 All Kconfig options can be searched in the :ref:`Kconfig search page
11 <kconfig-search>`.
25 - A visible symbol is a symbol defined with a prompt. Visible symbols show
26 up in the interactive configuration interfaces (hence *visible*), and can be
27 set in configuration files.
31 .. code-block:: kconfig
37 The symbol is shown like this in ``menuconfig``, where it can be toggled:
39 .. code-block:: none
43 - An *invisible* symbol is a symbol without a prompt. Invisible symbols are
[all …]
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | net-stack-architecture.rst | 26 :figclass: align-center
32 * **Network Application.** The network application can either use the provided
33 application-level protocol libraries or access the
35 connection, send or receive data, and close a connection. The application can
45 * Application-level network protocols like CoAP, LWM2M, and MQTT.
46 See :ref:`application protocols chapter <net_protocols>` for information
53 that is common in all the network interfaces, such as setting network
54 interface down, etc. There can be multiple network interfaces in the system.
68 * **Network Device Drivers.** The actual low-level device drivers handle the
74 An application typically consists of one or more :ref:`threads <threads_v2>`
[all …]
|
| /Zephyr-latest/samples/bluetooth/direction_finding_connectionless_rx/ |
| D | README.rst | 1 .. zephyr:code-sample:: ble_direction_finding_connectionless_rx
3 :relevant-api: bt_gap bluetooth
10 A simple application demonstrating the Bluetooth LE Direction Finding CTE Locator
27 By default the application supports Angle of Arrival and Angle of Departure mode.
29 To use Angle of Departure mode only, build this application as follows,
32 .. zephyr-app-commands::
33 :zephyr-app: samples/bluetooth/direction_finding_connectionless_rx
34 :host-os: unix
36 :gen-args: -DEXTRA_CONF_FILE=overlay-aod.conf
40 To run the application on nRF5340DK, a Bluetooth controller application must
[all …]
|
| /Zephyr-latest/samples/bluetooth/mesh_demo/ |
| D | README.rst | 1 .. zephyr:code-sample:: ble_mesh_demo
3 :relevant-api: bt_mesh bluetooth
5 Implement a Bluetooth Mesh demo application.
10 This sample is a Bluetooth Mesh application intended for demonstration
11 purposes only. The application provisions and configures itself (i.e. no
12 external provisioner needed) with hard-coded network and application key
15 manually editing the value in the ``board.h`` file.
17 Because of the hard-coded values, the application is not suitable for
21 The application has some features especially designed for the BBC
25 addresses in the range of 0x0001-0x0009 for the micro:bit since these
[all …]
|
12345678910>>...47
