Searched refs:using (Results 151 – 175 of 1710) sorted by relevance
12345678910>>...69
| /Zephyr-latest/boards/renode/cortex_r8_virtual/support/ |
| D | cortex_r8_virtual.resc | 6 using sysbus
|
| /Zephyr-latest/tests/drivers/pwm/pwm_api/boards/ |
| D | mimxrt1060_evk_mimxrt1062_qspi.overlay | 9 * by the test, but can be tested using the PWM shell.
|
| D | mimxrt1060_evk_mimxrt1062_qspi_C.overlay | 9 * by the test, but can be tested using the PWM shell.
|
| /Zephyr-latest/boards/ezurio/bl5340_dvk/doc/ |
| D | index.rst | 208 using either Zephyr or `Trusted Firmware M`_ (TF-M). Non-Secure
209 firmware images are always built using Zephyr. The two alternatives are
215 built using TF-M.
220 The process to build the Secure firmware image using TF-M and the
221 Non-Secure firmware image using Zephyr requires the following steps:
224 for the application core using ``-DBOARD=bl5340_dvk/nrf5340/cpuapp/ns``.
241 2. Build the application firmware for the network core using
244 Building the Secure firmware using Zephyr
248 using Zephyr requires the following steps:
251 using ``-DBOARD=bl5340_dvk/nrf5340/cpuapp`` and
[all …]
|
| /Zephyr-latest/boards/arm/mps2/doc/ |
| D | mps2_an521.rst | 29 with actual MPS2 hardware systems using AN521, or any other hardware
85 AN521, using the final 468KB code memory in the 4MB code block. This value
95 When using one of the alternative board targets (``mps2/an521/cpu0/ns`` or
397 firmware image. The Secure image can be built using either Zephyr
399 using Zephyr. The two alternatives are described below.
404 using TF-M.
409 The process to build the Secure firmware image using TF-M and the Non-Secure
410 firmware image using Zephyr requires the following steps:
413 for MPS2+ AN521 (CPU0) using ``-DBOARD=mps2/an521/cpu0/ns``.
430 Building the Secure firmware using Zephyr
[all …]
|
| /Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
| D | smp_group_1.rst | 172 | | optional when using MCUboot's serial recovery feature with one pair of |
200 | | appears if an error is returned when using SMP version 2. |
203 | | non-zero (error condition) when using SMP version 2. |
206 | | using SMP version 1 or for SMP errors when using SMP version 2. |
403 | | appears if an error is returned when using SMP version 2. |
406 | | non-zero (error condition) when using SMP version 2. |
409 | | using SMP version 1 or for SMP errors when using SMP version 2. |
505 | | appears if an error is returned when using SMP version 2. |
508 | | non-zero (error condition) when using SMP version 2. |
511 | | using SMP version 1 or for SMP errors when using SMP version 2. |
[all …]
|
| /Zephyr-latest/samples/subsys/mgmt/updatehub/ |
| D | README.rst | 5 Perform Firmware Over-The-Air (FOTA) updates using UpdateHub.
33 :zephyr:board:`Freedom-K64F <frdm_k64f>` kit using the ethernet connectivity. The
72 documentation page. Flash the resulting image file using west on
92 To start using the UpdateHub-CE simple execute the docker command with the
110 certificate using openssl on a Linux machine on terminal ``terminal 2``.
133 When using UpdateHub Cloud server it is necessary update your own
147 UpdateHub-CE server edition. If your are using a service provider a DNS name
148 is a valid option too. This option is only valid when using UpdateHub-CE.
154 Set :kconfig:option:`CONFIG_UPDATEHUB_PRODUCT_UID` with your product ID. When using
186 connectivity using, for instance, arduino headers. See :ref:`module_esp_8266`
[all …]
|
| /Zephyr-latest/doc/releases/ |
| D | migration-guide-3.5.rst | 31 error and have to be done correctly using
45 performance using some TLS variables. Zephyr places TLS variables in the
50 the default heap size depends on which C library is in use. When using the
52 will always fail. When using Picolibc, the default is 16kB with
64 * When using the standard C++ library with Picolibc, both of those must come
133 Vbat or temperature) using the ADC driver. The dedicated sensor driver should
136 determining what we want to measure using solely the ADC API.
139 using devicetree. As a result, Kconfig option :kconfig:option:`CONFIG_DISK_RAM_VOLUME_SIZE`
141 and the application using the RAM disk must instantiate it using devicetree,
164 * The :dtcompatible:`ti,bq274xx` driver was using incorrect units for capacity
[all …]
|
| /Zephyr-latest/drivers/pwm/ |
| D | Kconfig.sam0 | 12 Enable PWM driver for Atmel SAM0 MCUs using the TCC timer/counter.
|
| /Zephyr-latest/boards/silabs/dev_kits/sltb010a/ |
| D | sltb010a_2.overlay | 9 model = "Silicon Labs EFR32BG22 Thunderboard (SLTB010A) using BRD4184B";
|
| /Zephyr-latest/boards/beagle/beagleconnect_freedom/ |
| D | board.cmake | 6 # Download cc1352-flasher (https://pypi.org/project/cc1352-flasher/) using the following command:
|
| /Zephyr-latest/drivers/mipi_dbi/ |
| D | Kconfig.bitbang | 11 a MIPI-DBI mode A and B compatible controller using GPIO.
|
| /Zephyr-latest/boards/antmicro/myra_sip_baseboard/support/ |
| D | myra_sip_baseboard.resc | 6 using sysbus
|
| /Zephyr-latest/drivers/mfd/ |
| D | Kconfig.tle9104 | 8 # using select SPI at this point introduces a cyclic dependency
|
| /Zephyr-latest/subsys/logging/backends/ |
| D | Kconfig.efi_console | 9 When enabled backend is using EFI CONSOLE to output logs.
|
| /Zephyr-latest/drivers/can/ |
| D | Kconfig.numaker | 14 Enables Nuvoton NuMaker CAN FD driver, using Bosch M_CAN
|
| /Zephyr-latest/boards/others/stm32f401_mini/doc/ |
| D | index.rst | 64 There are 2 main entry points for flashing STM32F4X SoCs, one using the ROM
65 bootloader, and another by using the SWD debug port (which requires additional
66 hardware). Flashing using the ROM bootloader requires a special activation
67 pattern, which can be triggered by using the BOOT0 pin, which on this board
|
| /Zephyr-latest/drivers/ieee802154/ |
| D | Kconfig | 21 configured using net_if_set_link_addr(iface, mac, 8,
26 This option can be useful when using OpenThread or Zigbee. If you
34 This option enables using the drivers in a so-called "raw" mode,
49 OUI using IEEE802154_VENDOR_OUI. After enabling,
|
| /Zephyr-latest/doc/hardware/cache/ |
| D | index.rst | 32 For example a platform using the data cache can enable the
45 specify (using :ref:`memory region attributes<mem_mgmt_api>`) a fixed region
49 specify individual global variables as uncached using ``__nocache``. This will
55 whether the cache operations are implemented at arch level or using an
|
| /Zephyr-latest/samples/net/sockets/http_get/ |
| D | README.rst | 2 :name: HTTP GET using plain sockets
5 Implement an HTTP(S) client using plain BSD sockets.
11 HTTP GET client using a BSD Sockets compatible API. The purpose of this
48 ``overlay-tls.conf`` overlay file enabled, for example, using these commands:
|
| /Zephyr-latest/samples/subsys/zbus/benchmark/ |
| D | README.rst | 35 I: Benchmark 1 to 1 using LISTENERS to transmit with message size: 512 bytes
55 The complete benchmark command using Robot framework is:
61 An example of execution using the ``nrf52dk/nrf52832`` board would generate a file like this:
|
| /Zephyr-latest/boards/m5stack/m5stack_atoms3/doc/ |
| D | index.rst | 67 try using different values by using ``--esp-baud-rate <BAUD>`` option during
70 You can also open the serial monitor using the following command:
|
| /Zephyr-latest/boards/m5stack/m5stack_atoms3_lite/doc/ |
| D | index.rst | 65 try using different values by using ``--esp-baud-rate <BAUD>`` option during
68 You can also open the serial monitor using the following command:
|
| /Zephyr-latest/boards/m5stack/m5stack_atom_lite/doc/ |
| D | index.rst | 65 try using different values by using ``--esp-baud-rate <BAUD>`` option during
68 You can also open the serial monitor using the following command:
|
| /Zephyr-latest/samples/net/sockets/echo_async_select/ |
| D | README.rst | 2 :name: Asynchronous echo server using select()
5 Implement an asynchronous IPv4/IPv6 TCP echo server using BSD sockets and select()
11 asynchronous IPv4/IPv6 TCP echo server using a BSD Sockets compatible API
|
12345678910>>...69
