Searched refs:application (Results 1 – 25 of 1547) sorted by relevance
12345678910>>...62
| /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/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-Core-3.7.0/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-Core-3.7.0/samples/application_development/ |
| D | application_development.rst | 6 For application development you should also consider looking at
7 `example-application`_. Among others, you will find on it out of tree driver
16 .. _example-application: https://github.com/zephyrproject-rtos/example-application
|
| /Zephyr-Core-3.7.0/samples/modules/lvgl/demos/ |
| D | Kconfig | 8 Demo application to build.
14 Build music player demo application.
20 Build benchmarking demo application.
26 Build stress testing demo application.
32 Build stress testing demo application.
|
| /Zephyr-Core-3.7.0/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-Core-3.7.0/samples/boards/nrf/nrf53_sync_rtc/ |
| D | README.rst | 9 Sample is showing how RTC clocks used for system clock on application and network
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
71 [00:00:00.657,043] <inf> main: Local timestamp: 21530, application core timestamp: 21529
[all …]
|
| /Zephyr-Core-3.7.0/samples/bluetooth/mesh_demo/ |
| D | README.rst | 9 This sample is a Bluetooth Mesh application intended for demonstration
10 purposes only. The application provisions and configures itself (i.e. no
11 external provisioner needed) with hard-coded network and application key
16 Because of the hard-coded values, the application is not suitable for
20 The application has some features especially designed for the BBC
28 A special address, 0x000f, will make the application become a heart-beat
47 For other boards, build and flash the application as follows:
58 To run the application on an :ref:`nrf5340dk_nrf5340`, a Bluetooth controller application
60 application may be used. Build this sample with configuration
|
| /Zephyr-Core-3.7.0/samples/bluetooth/mesh_provisioner/ |
| D | README.rst | 16 The application provisions itself and loads the CDB with an application
19 ``sw0`` :ref:`devicetree <dt-guide>` alias, the application then waits
24 application will notice the unconfigured node and start configuring it.
27 The configuration of a node involves adding an application key, getting
28 the composition data, and binding all its models to the application key.
45 For other boards, build and flash the application as follows:
56 To run the application on an :ref:`nrf5340dk_nrf5340`, a Bluetooth controller application
58 application may be used. Build this sample with configuration
|
| /Zephyr-Core-3.7.0/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-Core-3.7.0/doc/develop/application/ |
| D | index.rst | 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.
40 Here are the files in a simple Zephyr application:
[all …]
|
| /Zephyr-Core-3.7.0/samples/net/stats/ |
| D | README.rst | 5 Query and display network statistics from a user application.
11 application.
13 The source code for this sample application can be found at:
24 A good way to run this sample application is with QEMU or native_sim board
27 Follow these steps to build the network statistics sample application:
36 If everything is configured correctly, the application will periodically print
|
| /Zephyr-Core-3.7.0/samples/net/ptp/ |
| D | Kconfig | 6 mainmenu "PTP sample application"
11 int "Run the application this many seconds"
14 A value of zero means that the sample application is run forever.
|
| /Zephyr-Core-3.7.0/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-Core-3.7.0/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-Core-3.7.0/samples/subsys/ipc/openamp/ |
| D | README.rst | 10 This application demonstrates how to use OpenAMP with Zephyr. It is designed to
15 Building the application for lpcxpresso54114_m4
24 Building the application for lpcxpresso55s69/lpc55s69/cpu0
33 Building the application for mps2/an521/cpu0
42 Building the application for v2m_musca_b1/musca_b1
51 Building the application for mimxrt1170_evk_cm7
74 Starting application thread!
88 Starting application thread!
|
| /Zephyr-Core-3.7.0/samples/net/sockets/echo_async/ |
| D | README.rst | 10 The sockets/echo-async sample application for Zephyr implements an
13 the :zephyr:code-sample:`sockets-echo` sample. It's a more involved application,
17 The source code for this sample application can be found at:
29 Build the Zephyr version of the sockets/echo_async application like this:
45 After a connection is made, the application will echo back any line sent to
46 it. Unlike the above-mentioned :zephyr:code-sample:`sockets-echo` sample, this application
52 Running application on POSIX Host
55 The same application source code can be built for a POSIX system, e.g.
79 As can be seen, the behavior of the application is the same as the Zephyr
|
| /Zephyr-Core-3.7.0/samples/net/sockets/net_mgmt/ |
| D | README.rst | 10 The net-mgmt-socket sample application for Zephyr implements a listener
13 The source code for this sample application can be found at:
24 There are multiple ways to use this application. One of the most common
25 usage scenario is to run echo-server application inside QEMU. This is
28 Build net-mgmt socket sample application like this:
|
| /Zephyr-Core-3.7.0/doc/connectivity/networking/api/ |
| 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-Core-3.7.0/samples/subsys/ipc/rpmsg_service/ |
| D | README.rst | 12 This application demonstrates how to use RPMsg Service in Zephyr. It is designed
18 Building the application for nrf5340dk/nrf5340/cpuapp
26 Building the application for mps2/an521/cpu0
34 Building the application for v2m_musca_b1/musca_b1
56 Starting application thread!
70 Starting application thread!
80 Building the application for bl5340_dvk/nrf5340/cpuapp
101 When you reset the development kit after having flashed both the application
108 Starting application thread!
122 Starting application thread!
[all …]
|
| /Zephyr-Core-3.7.0/boards/nordic/nrf5340dk/doc/ |
| D | index.rst | 16 the **application core**
20 The ``nrf5340dk/nrf5340/cpuapp`` build target provides support for the application
161 - Implementation Defined Attribution Unit (`IDAU`_) on the application core.
171 nRF5340 application core supports the Armv8-M Security Extension.
184 image for the application core. The Secure image can be built using either
190 By default the Secure image for nRF5340 application core is built
200 1. Build the Non-Secure Zephyr application
201 for the application core using ``-DBOARD=nrf5340dk/nrf5340/cpuapp/ns``.
204 default when building Zephyr as a Non-Secure application.
207 * Build the Non-Secure firmware image as a regular Zephyr application
[all …]
|
| /Zephyr-Core-3.7.0/samples/net/sockets/echo_async_select/ |
| D | README.rst | 10 The sockets/echo_async_select sample application for Zephyr implements an
15 The source code for this sample application can be found at:
27 Build the Zephyr version of the sockets/echo_async application like this:
43 After a connection is made, the application will echo back any line sent to
44 it. Unlike the :zephyr:code-sample:`sockets-echo` sample, this application
50 Running application on POSIX Host
53 The same application source code can be built for a POSIX system, e.g.
77 As can be seen, the behavior of the application is the same as the Zephyr
|
| /Zephyr-Core-3.7.0/samples/net/sockets/socketpair/ |
| D | README.rst | 10 The sockets/socketpair sample application for Zephyr demonstrates a
11 multi-threaded application communicating over pairs of unnamed,
16 application portable to both POSIX and Zephyr.
18 The source code for this sample application can be found at:
29 Build the Zephyr version of the sockets/echo application like this:
59 Running application on POSIX Host
62 The same application source code can be built for a POSIX system, e.g.
92 As can be seen, the behavior of the application is approximately the same as
|
| /Zephyr-Core-3.7.0/samples/subsys/mgmt/mcumgr/smp_svr/ |
| D | CMakeLists.txt | 2 # Top-level CMakeLists.txt for the skeleton application.
8 # This provides a basic application structure suitable for communication using
11 # Standard Zephyr application boilerplate.
|
| /Zephyr-Core-3.7.0/samples/drivers/charger/ |
| D | README.rst | 12 The sample application performs a simple charging task loop.
14 - The application will first poll for external power provided to the charger device.
15 - If power is provided to the charger, then the sample application will attempt to enable the charge
17 - After the charge cycle is initiated, the sample application will check the status property of the
19 - Once the charger device reports that the charge cycle has completed, the application returns.
|
12345678910>>...62
