Searched full:applications (Results 1 – 25 of 892) sorted by relevance
12345678910>>...36
| /Zephyr-latest/doc/develop/languages/c/ |
| D | index.rst | 9 Zephyr is primarily written in C and natively supports applications written in
12 writing Zephyr applications in C gives the developers access to the most
16 applications run in a "hosted" environment as defined by the C
17 standard. Applications must return zero (0) from main. All non-zero return
43 effectively requires most Zephyr applications to be compiled using a compiler
59 provides the support for a number of different C libraries for the applications
113 Native Zephyr applications should use the :ref:`memory management API
119 :c:func:`malloc` should be used only by the portable applications and
|
| /Zephyr-latest/subsys/usb/device_next/app/ |
| D | Kconfig.cdc_acm_serial | 14 backend only in applications where no other USB features are
35 You must use your own VID for samples and applications outside of
42 You must use your own PID for samples and applications outside of
|
| /Zephyr-latest/subsys/retention/ |
| D | Kconfig.blinfo | 22 applications which allows applications to read the configuration of
23 MCUboot and the running image. This can be used by applications so
|
| /Zephyr-latest/boards/waveshare/open103z/doc/ |
| D | index.rst | 24 Applications for the ``waveshare_open103z`` board configuration can be built and
30 Build and flash applications as usual. Here is an example for the
41 Debug applications as usual. Here is an example for the
|
| /Zephyr-latest/doc/kernel/services/threads/ |
| D | nothread.rst | 6 Thread support is not necessary in some applications:
9 * Simple event-driven applications
111 * Applications that select :kconfig:option:`CONFIG_UART_INTERRUPT_DRIVEN` may
114 * Applications that select :kconfig:option:`CONFIG_UART_ASYNC_API` may
117 * Applications that do not select either :kconfig:option:`CONFIG_UART_ASYNC_API`
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | overview.rst | 59 that are available to applications can be configured at build time.
77 applications are implemented.
97 Applications can use the DNS API to query domain name information or IP
104 * **Network Management API.** Applications can use network management API to
108 * **Wi-Fi Management API.** Applications can use Wi-Fi management API to
120 technologies. Applications can send data according to their needs to desired
150 ethernet interface to host system (like Linux) and test applications
170 Public API header files. These are the header files applications need
178 Test applications. These applications are used to verify the
|
| /Zephyr-latest/doc/services/sensing/ |
| D | index.rst | 27 Use of the sensing subsystem is optional. Applications that only need to access simple sensors
39 Applications with different sensor expose/transfer protocols,
40 such as `CHRE <https://github.com/zephyrproject-rtos/chre>`_, HID sensors Applications,
41 MQTT sensor Applications according different products requirements. Or even support multiple
42 Applications with different up-layer sensor protocols at the same time
59 * Provide Zephyr high-level Sensing Subsystem API for Applications.
94 ``Sensing Subsystem API`` is for Applications.
117 there're two methods for Applications to identify and open an unique sensor instance:
124 Then Applications can use :c:func:`sensing_open_sensor` to
132 Applications can use :c:func:`sensing_open_sensor_by_dt` to open a sensor instance directly with
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | index.rst | 7 :zephyr_file:`include/zephyr/net/socket.h`) for the applications to
15 should not be used by applications.
|
| /Zephyr-latest/boards/makerdiary/nrf52832_mdk/doc/ |
| D | index.rst | 8 applications using the nRF52832 SoC.
12 onboard which is quite convenient to develop IoT wireless applications.
|
| /Zephyr-latest/doc/services/crypto/ |
| D | psa_crypto.rst | 54 applications can quickly adapt to new cryptographic standards and
57 Examples of Applications
135 Some environments allow applications to be multithreaded, while
136 others do not. In some environments, applications can share memory
138 multithreaded applications or shared memory, applications must be
158 that applications wipe all sensitive data from memory when it is no
|
| /Zephyr-latest/drivers/bluetooth/hci/ |
| D | Kconfig.infineon | 158 This configuration should be used with non-PAWR and non-ISOC applications.
164 This configuration should be used with non-PAwR and non-ISOC applications.
170 This configuration should be used with PAwR applications.
176 This configuration should be used with PAwR applications.
182 This configuration should be used with ISOC applications.
188 This configuration should be used with ISOC applications.
|
| /Zephyr-latest/soc/st/stm32/stm32f1x/ |
| D | Kconfig.soc | 65 microcontrollers. They are intended for applications where
67 industrial control, control panels for security applications, UPS or
|
| /Zephyr-latest/boards/makerdiary/nrf52840_mdk/doc/ |
| D | index.rst | 8 applications using the nRF52840 SoC.
17 user button, RGB LED, up to 24 GPIOs, antenna selection for custom applications.
|
| /Zephyr-latest/tests/bsim/bluetooth/ll/edtt/ |
| D | README.txt | 10 In very short, there is 2 applications in this folder:
21 These 2 particular applications are meant to be used in a simulated environment,
43 To run these sets of tests you need to compile both of these applications as any
|
| /Zephyr-latest/doc/services/portability/posix/overview/ |
| D | index.rst | 25 POSIX conformant can be ported to Zephyr kernel based applications with no changes.
28 embedded applications, as can be seen in Zephyr, AWS:FreeRTOS, TI-RTOS, and NuttX.
78 POSIX Applications in Zephyr
116 For more examples of POSIX applications, please see the
117 :zephyr:code-sample-category:`POSIX sample applications<posix>`.
162 new Zephyr applications.
|
| /Zephyr-latest/boards/sifive/hifive_unleashed/doc/ |
| D | index.rst | 15 Applications for the ``hifive_unleashed`` board configuration can be built as
40 Load applications on DDR and run as follows:
|
| /Zephyr-latest/boards/sifive/hifive_unmatched/doc/ |
| D | index.rst | 15 Applications for the ``hifive_unmatched`` board configuration can be built as
40 Load applications on DDR and run as follows:
|
| /Zephyr-latest/boards/qemu/leon3/doc/ |
| D | index.rst | 11 Applications for the ``qemu_leon3`` board configuration can be built and run in
19 configuration to run basic Zephyr applications and kernel tests in the QEMU
|
| /Zephyr-latest/boards/qemu/riscv32/doc/ |
| D | index.rst | 11 Applications for the ``qemu_riscv32`` board configuration can be built and run in
19 configuration to run basic Zephyr applications and kernel tests in the QEMU
|
| /Zephyr-latest/lib/utils/ |
| D | Kconfig | 10 applications such as the NATS client.
41 service which has a binary state. Example applications are power
|
| /Zephyr-latest/samples/cpp/ |
| D | cpp.rst | 5 These samples demonstrate how to write Zephyr applications in C++.
|
| /Zephyr-latest/boards/renode/riscv32_virtual/doc/ |
| D | index.rst | 17 Applications for the ``riscv32_virtual`` board configuration can be built as usual
28 configuration to run basic Zephyr applications and kernel tests in the Renode
|
| /Zephyr-latest/boards/ezurio/pinnacle_100_dvk/doc/ |
| D | index.rst | 83 Applications for the ``pinnacle_100_dvk`` board configuration can be
93 applications as usual (see :ref:`build_an_application` and
130 Sample Applications
132 `Pinnacle 100 Sample Applications`_ are available.
167 .. _Pinnacle 100 Sample Applications: https://github.com/LairdCP/Pinnacle_100_Sample_Applications
|
| /Zephyr-latest/boards/qemu/riscv32_xip/doc/ |
| D | index.rst | 11 Applications for the ``qemu_riscv32_xip`` board configuration can be built and run in
19 configuration to run basic Zephyr applications and kernel tests in the QEMU
|
| /Zephyr-latest/boards/qemu/riscv32e/doc/ |
| D | index.rst | 11 Applications for the ``qemu_riscv32e`` board configuration can be built and run in
19 configuration to run basic Zephyr applications and kernel tests in the QEMU
|
12345678910>>...36
