Searched full:application (Results 1 – 25 of 2647) sorted by relevance
12345678910>>...106
| /Zephyr-latest/subsys/portability/cmsis_rtos_v2/ |
| D | Kconfig | 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"
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"
49 Mention dynamic stack size threads are allocated in CMSIS RTOS V2 application.
52 int "Maximum timer count in CMSIS RTOS V2 application"
56 Mention maximum number of timers in CMSIS RTOS V2 compliant application.
[all …]
|
| /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.
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.
43 * secure application: em_starterkit_em7d_secure
44 * normal application: em_starterkit_em7d_normal
46 * secure application: nsim_sem
47 * normal application: nsim_sem_normal
55 Secure application
[all …]
|
| /Zephyr-latest/samples/modules/lvgl/demos/ |
| D | Kconfig | 8 Demo application to build.
14 Build music player demo application.
21 Build benchmarking demo application.
27 Build stress testing demo application.
33 Build widgets demo application.
39 Build flex layout demo application.
45 Build keypad and encoder demo application.
51 Build render demo application.
57 Build scroll demo application.
64 Build multilang demo application.
|
| /Zephyr-latest/share/sysbuild/images/bootloader/ |
| D | Kconfig | 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.
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
60 MCUBOOT_BOOTLOADER_NO_DOWNGRADE should also be selected in main application if MCUboot
77 can boot from either partition and will select one with higher application image version,
81 to swap back to older version of application.
[all …]
|
| /Zephyr-latest/subsys/portability/cmsis_rtos_v1/ |
| D | Kconfig | 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/doc/develop/application/ |
| D | index.rst | 3 Application Development
10 …- your **application directory**, :file:`<app>`, is something like :file:`<home>/zephyrproject/app`
16 Keeping your application inside the workspace (:file:`<home>/zephyrproject`)
18 put your application anywhere as long as :ref:`ZEPHYR_BASE
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
37 application. This directory contains all application-specific files, such as
38 application-specific configuration files and source code.
[all …]
|
| /Zephyr-latest/samples/application_development/ |
| D | application_development.rst | 2 :name: Application Development
5 These samples illustrate some useful application development patterns and techniques.
7 For application development you should also consider looking at
8 `example-application`_. Among others, you will find on it out of tree driver
11 .. _example-application: https://github.com/zephyrproject-rtos/example-application
|
| /Zephyr-latest/tests/boot/with_mcumgr/pytest/ |
| D | test_upgrade.py | 47 Verify that the application can be updated
48 1) Device flashed with MCUboot and an application that contains SMP server
49 2) Prepare an update of an application containing the SMP server
50 3) Upload the application update to slot 1 using mcumgr
51 4) Flag the application update in slot 1 as 'pending' by using mcumgr 'test'
53 6) Verify that the updated application is booted
55 8) Restart the device, and verify that the new application is still booted
73 output = dut.readlines_until('Launching primary slot application')
88 output = dut.readlines_until('Launching primary slot application')
99 1) Device flashed with MCUboot and an application that contains SMP server
[all …]
|
| D | test_downgrade_prevention.py | 19 Verify that the application is not downgraded
20 1) Device flashed with MCUboot and an application that contains SMP server.
22 2) Prepare an update of an application containing the SMP server, where
24 3) Upload the application update to slot 1 using mcumgr
25 4) Flag the application update in slot 1 as 'pending' by using mcumgr 'test'
28 6) Verify that the original application is booted (version 1.1.1)
51 output = dut.readlines_until('Launching primary slot application')
|
| /Zephyr-latest/samples/bluetooth/mesh_demo/ |
| D | README.rst | 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
17 Because of the hard-coded values, the application is not suitable for
21 The application has some features especially designed for the BBC
29 A special address, 0x000f, will make the application become a heart-beat
48 For other boards, build and flash the application as follows:
59 To run the application on an :ref:`nrf5340dk_nrf5340`, a Bluetooth controller application
61 application may be used. Build this sample with configuration
|
| /Zephyr-latest/tests/benchmarks/app_kernel/ |
| D | testcase.yaml | 11 benchmark.kernel.application:
15 benchmark.kernel.application.objcore.stats:
22 benchmark.kernel.application.user:
28 benchmark.kernel.application.user.objcore.stats:
37 benchmark.kernel.application.timeslicing:
43 benchmark.kernel.application.user.timeslicing:
|
| /Zephyr-latest/modules/ |
| D | Kconfig.mcuboot | 33 the application. This removes the need by MCUboot to reset
59 for your application which is to be loaded by MCUboot. The MCUboot
136 prompt "Application assumed MCUboot mode of operation"
139 Informs application build on assumed MCUboot mode of operation.
140 This is important for validataing application against DT configuration,
147 MCUboot will only boot slot0_partition placed application and does
148 not care about other slots. In this mode application is not able
157 in DT and application will boot from slot0_partition.
166 to be present in DT, and application will boot from slot0_partition.
168 MCUboot swaps application from the secondary slot to the primary
[all …]
|
| /Zephyr-latest/samples/bluetooth/mesh_provisioner/ |
| D | README.rst | 17 The application provisions itself and loads the CDB with an application
20 ``sw0`` :ref:`devicetree <dt-guide>` alias, the application then waits
25 application will notice the unconfigured node and start configuring it.
28 The configuration of a node involves adding an application key, getting
29 the composition data, and binding all its models to the application key.
46 For other boards, build and flash the application as follows:
57 To run the application on an :ref:`nrf5340dk_nrf5340`, a Bluetooth controller application
59 application may be used. Build this sample with configuration
|
| /Zephyr-latest/samples/userspace/prod_consumer/ |
| D | README.rst | 10 and generates interrupts with pointers to this data. The application needs
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
26 In this example, we have an Application A whose job is to talk to the
28 Application B.
30 Application B simply processes the data. Let's pretend this data is
31 untrusted and possibly malicious, so Application B is sandboxed from
43 monitored by application B.
[all …]
|
| /Zephyr-latest/tests/boot/test_mcuboot/ |
| D | README.rst | 4 Tests MCUBoot's image swap support. This application is built in three parts
5 using sysbuild. The first application is the MCUBoot bootloader. The second
6 application is the main sysbuild target, and will request an image swap
7 from MCUBoot when booted. The third application is build with a load address
8 adjustment using CONFIG_BUILD_OUTPUT_ADJUST_LMA, and will be the application
|
| /Zephyr-latest/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
24 application callbacks, allowing the server to interact with the application (for
32 * Dynamic resources - content provided at runtime by respective application
46 the application.
57 The linker section for services is predefined locally, however the application
72 Finally, the linker file and linker section have to be added to your application
94 The application needs to define an HTTP service (or multiple services), with
133 Application can enable resource wildcard support by enabling
156 in the application:
[all …]
|
| D | net_config.rst | 26 config library is not used for initialization and the application needs to
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
44 ":kconfig:option:`CONFIG_NET_CONFIG_NEED_IPV6`", "The network application needs IPv6
45 support to function properly. This option makes sure the network application
50 this option tells that the network application needs IPv6 router to exists
51 before continuing. This means in practice that the application wants to wait
56 useful in testing setups where the application can connect to a pre-defined host."
64 useful in testing setups where the application can connect to a pre-defined host."
71 the library will call ``net_config_init()`` automatically and the application
[all …]
|
| /Zephyr-latest/samples/net/gptp/ |
| D | Kconfig | 6 # This sample application will have three network interfaces.
9 # how to do this kind of setup. See also VLAN sample application
13 mainmenu "gPTP sample application"
34 application.
53 application.
56 int "Run the application this many seconds"
59 A value of zero means that the sample application is run forever.
|
| /Zephyr-latest/samples/net/sockets/echo/ |
| D | README.rst | 10 The sockets/echo sample application for Zephyr implements a TCP echo
13 application portable to both POSIX and Zephyr. As such, it is kept minimal
16 The source code for this sample application can be found at:
28 Build the Zephyr version of the sockets/echo application like this:
43 After a connection is made, the application will echo back any line sent
44 to it. The application implements a single-threaded server using blocking
48 Running application on POSIX Host
51 The same application source code can be built for a POSIX system, e.g.
73 As can be seen, the behavior of the application is the same as the Zephyr
83 application.
|
| /Zephyr-latest/subsys/bluetooth/mesh/ |
| D | app_keys.h | 16 /** @brief Initialize a new application key with the given parameters.
19 * @param net_idx NetIndex the application is bound to.
20 * @param old_key Current application key.
21 * @param new_key Updated application key, or NULL if not known.
37 * @param app_key Application return parameter.
38 * @param aid Application ID return parameter.
46 /** @brief Iterate through all matching application keys and call @c cb on each.
49 * @param aid 7 bit application ID to match.
62 /** @brief Store pending application keys in persistent storage. */
|
| /Zephyr-latest/samples/net/sockets/txtime/ |
| D | README.rst | 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
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
31 application cannot be used as a peer.
|
| /Zephyr-latest/include/zephyr/net/ |
| D | net_config.h | 33 * @brief Application needs routers to be set so that connectivity to remote
40 * @brief Application needs IPv6 subsystem configured and initialized.
46 * @brief Application needs IPv4 subsystem configured and initialized.
52 * @brief Initialize this network application.
57 * @param app_info String describing this application.
67 * @brief Initialize this network application using a specific network
74 * @param app_info String describing this application.
85 * @brief Initialize this network application.
90 * application starts.
95 * @param app_info String describing this application.
|
| /Zephyr-latest/samples/boards/nordic/nrf53_sync_rtc/ |
| D | README.rst | 9 Sample is showing how RTC clocks used for system clock on application and network
14 both cores. Application core periodically reads current system tick and stores it in
25 Building the application for nrf5340dk/nrf5340/cpuapp
63 [00:00:00.054,534] <inf> main: Local timestamp: 1787, application core timestamp: 10056
64 [00:00:00.104,553] <inf> main: Local timestamp: 3426, application core timestamp: 11695
65 [00:00:00.154,571] <inf> main: Local timestamp: 5065, application core timestamp: 13334
66 [00:00:00.204,589] <inf> main: Local timestamp: 6704, application core timestamp: 14973
67 [00:00:00.254,608] <inf> main: Local timestamp: 8343, application core timestamp: 16612
69 [00:00:00.557,006] <inf> main: Local timestamp: 18252, application core timestamp: 18251
70 [00:00:00.607,025] <inf> main: Local timestamp: 19891, application core timestamp: 19890
[all …]
|
| /Zephyr-latest/subsys/net/lib/config/ |
| D | Kconfig | 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.
45 This option makes sure the network application is initialized properly
49 bool "This application wants IPv6 router to exists"
52 The network application needs IPv6 router to exists before continuing.
53 What this means that the application wants to wait until it receives
57 bool "This application wants IPv4 support"
60 The network application needs IPv4 support to function properly.
[all …]
|
| /Zephyr-latest/include/zephyr/bluetooth/classic/ |
| D | hfp_hf.h | 33 * Command complete types for the application
48 /** @brief HFP profile application callback */
50 /** HF connected callback to application
58 /** HF disconnected callback to application
87 * This callback provides service indicator value to the application
95 * This callback provides call indicator value to the application
103 * This callback provides call setup indicator value to the application
111 * This callback provides call held indicator value to the application
119 * This callback provides signal indicator value to the application
127 * This callback provides roaming indicator value to the application
[all …]
|
12345678910>>...106
