Searched refs:using (Results 76 – 100 of 1710) sorted by relevance
12345678910>>...69
| /Zephyr-latest/boards/nxp/mimxrt1170_evk/ |
| D | CMakeLists.txt | 11 message(WARNING "It appears you are using the board definition for "
39 message(WARNING "You are using SDRAM as RAM but no external memory"
46 message(WARNING "You appear to be using the GPT hardware timer. "
|
| /Zephyr-latest/boards/nxp/mimxrt1064_evk/ |
| D | CMakeLists.txt | 16 message(WARNING "It appears you are using the board definition for "
39 message(WARNING "You are using SDRAM as RAM but no device "
46 message(WARNING "You appear to be using the GPT hardware timer. "
|
| /Zephyr-latest/cmake/compiler/host-gcc/ |
| D | generic.cmake | 3 # Configures CMake for using GCC
|
| /Zephyr-latest/boards/microchip/m2gl025_miv/support/ |
| D | m2gl025_miv.repl | 3 using "platforms/cpus/miv.repl"
|
| /Zephyr-latest/tests/drivers/can/host/ |
| D | README.rst | 22 * The CAN controller to be used is set using the ``zephyr,canbus`` chosen devicetree node.
23 * The CAN bitrates are set using :kconfig:option:`CONFIG_CAN_DEFAULT_BITRATE` and
24 :kconfig:option:`CONFIG_CAN_DEFAULT_BITRATE_DATA`, but can be overridden on a board level using
27 phase when using bitrate switching (BRS).
39 * The configuration context can be overridden using the ``--can-context`` test suite argument
71 be launched using Twister:
87 adapter must be supported by python-can. The examples below assumes using a Linux SocketCAN
112 Once the SocketCAN interface has been brought up and configured the test suite can be launched using
|
| /Zephyr-latest/doc/services/debugging/ |
| D | cs_trace_defmt.rst | 7 single output stream. Formatter is using 16 byte frames which wraps up to 15 bytes of
16 Deformatter is initialized with a user callback. Data is decoded using
|
| /Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/ |
| D | README.rst | 16 - Establishing network connectivity using a DHCPv4 lease
17 - Establishing a secure MQTT connection (using TLS 1.2) to MQTT broker
37 without security, using a static IP address.
41 If using Ethernet, connect the board to the MQTT broker. This may be your host PC
80 to securely connect to an MQTT broker using TLS 1.2.
85 - Connecting securely using TLS, requires the inclusion of the broker's CA certificate
90 an IPv4 address using DHCP.
99 This can be done using Kconfig or using a custom MbedTLS config file
144 - Start a Mosquitto broker using the configuration file:
186 subscriptions can be configured using Kconfig.
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | index.rst | 61 - You can configure sysbuild or any of the build systems it manages using
66 - Sysbuild itself is also configured using Kconfig. For example, you can
68 link your main Zephyr application as an MCUboot-bootable image, using sysbuild's
80 for running things like menuconfig with the prefix, for example (if using
81 ninja) ``ninja sysbuild_menuconfig`` to configure sysbuild or (if using make)
131 Here is an example using CMake and Ninja.
149 control the build process when using sysbuild with CMake and ninja.
177 application managed by sysbuild using the information in these sections.
212 CMake variable settings can be passed to CMake using ``-D<var>=<value>`` on the
287 This allows you to build the same application with or without sysbuild using
[all …]
|
| /Zephyr-latest/doc/hardware/peripherals/eeprom/ |
| D | shell.rst | 40 which also supports tab-completion. A list of all devices available can be obtained using the
47 The size of an EEPROM can be inspected using the ``eeprom size`` subcommand as shown below:
57 Data can be written to an EEPROM using the ``eeprom write`` subcommand. This subcommand takes at
69 It is also possible to fill a portion of the EEPROM with the same pattern using the ``eeprom fill``
83 Data can be read from an EEPROM using the ``eeprom read`` subcommand. This subcommand takes three
|
| /Zephyr-latest/samples/modules/mctp/ |
| D | mctp.rst | 5 These samples demonstrate how to build communicating firmwares using MCTP in Zephyr.
|
| /Zephyr-latest/drivers/ipm/ |
| D | Kconfig | 39 Interprocessor driver for ESP32 when using AMP.
48 Interprocessor driver using IVSHMEM Doorbell mechanism.
64 IPM driver using a MBOX driver as the backend mechanism.
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | charger.rst | 26 A charge cycle is initiated or terminated using :c:func:`charger_charge_enable`.
37 Properties are fetched by the client one at a time using :c:func:`charger_get_prop`.
38 Properties are set by the client one at a time using :c:func:`charger_set_prop`.
|
| /Zephyr-latest/boards/nxp/mimxrt1050_evk/ |
| D | CMakeLists.txt | 20 message(WARNING "It appears you are using the board definition for "
45 message(WARNING "You are using SDRAM as RAM but no device "
52 message(WARNING "You appear to be using the GPT hardware timer. "
|
| /Zephyr-latest/boards/nxp/mimxrt1010_evk/ |
| D | CMakeLists.txt | 12 message(WARNING "It appears you are using the board definition for "
30 message(WARNING "You appear to be using the GPT hardware timer. "
|
| /Zephyr-latest/boards/nxp/mimxrt1015_evk/ |
| D | CMakeLists.txt | 11 message(WARNING "It appears you are using the board definition for "
29 message(WARNING "You appear to be using the GPT hardware timer. "
|
| /Zephyr-latest/samples/drivers/led/is31fl3194/ |
| D | README.rst | 5 Cycle colors on an RGB LED connected to the IS31FL3194 using the LED API.
10 This sample cycles several colors on an RGB LED forever using the LED API.
|
| /Zephyr-latest/samples/modules/lvgl/ |
| D | lvgl.rst | 5 These samples demonstrate how to build graphical user interfaces using LVGL in Zephyr.
|
| /Zephyr-latest/tests/application_development/code_relocation/ |
| D | README.rst | 9 using a custom linker script.
|
| /Zephyr-latest/doc/develop/west/ |
| D | without-west.rst | 6 This page provides information on using Zephyr without west. This is
20 If you have previously installed west and want to stop using it,
52 You can build a Zephyr application using CMake and Ninja (or make) directly
74 Similarly, if your application requires binary blobs and you are not using
76 instead of using ``west blobs``. See :ref:`bin-blobs` for more details.
85 those targets will fail. You can of course still flash and debug using
90 install west on your system using ``pip``, it is possible to do so
|
| /Zephyr-latest/samples/bluetooth/mesh_provisioner/ |
| D | README.rst | 5 Provision a node and configure it using the Bluetooth Mesh APIs.
11 provisioning and using the Configuration Database (CDB). It is intended
19 board has a push button connected via GPIO and configured using the
21 for the user to press the button, which will trigger provisioning using
|
| /Zephyr-latest/boards/common/ |
| D | stub.dts | 6 /* empty stub file provided for systems not using devicetree */
|
| /Zephyr-latest/boards/nordic/nrf7002dk/doc/ |
| D | index.rst | 188 image for the application core. The Secure image can be built using either
190 images are always built using Zephyr. The two alternatives are described below.
194 By default, SPE for the nRF5340 application core is built using TF-M.
199 The process to build the Secure firmware image using TF-M and the Non-Secure
200 firmware image using Zephyr requires the following steps:
203 for the application core using ``-DBOARD=nrf7002dk/nrf5340/cpuapp/ns``.
220 2. Build the application firmware for the network core using
223 Building the Secure firmware using Zephyr
227 using Zephyr requires the following steps:
230 using ``-DBOARD=nrf7002dk/nrf5340/cpuapp`` and
[all …]
|
| /Zephyr-latest/boards/96boards/argonkey/doc/ |
| D | index.rst | 158 96Boards Argonkey can be flashed by two methods, one using the ROM
159 bootloader and another using the SWD debug port (which requires additional
162 Flashing using the ROM bootloader requires a special activation pattern,
163 which can be triggered by using the BOOT0 pin. The ROM bootloader supports
172 flashing on a Linux PC using UART as communication channel.
174 1. Connect ArgonKey UART to your Linux PC using, for example, a USB-TTL serial
175 cable. The flashing procedure has been tested using a `TTL-232RG`_ cable with
204 The ArgonKey has been tested using the `ST-LINK/V2`_ tool. Once that the tool
|
| /Zephyr-latest/samples/basic/custom_dts_binding/boards/ |
| D | nucleo_l073rz.overlay | 10 /* using built-in LED pin for demonstration */
|
| /Zephyr-latest/samples/net/sockets/echo_service/ |
| D | README.rst | 5 Implements a simple IPv4/IPv6 TCP echo server using BSD sockets and socket service API.
11 echo server supporting both IPv4 and IPv6 and using a BSD Sockets compatible API.
49 to it. The application implements a single-threaded server using blocking
|
12345678910>>...69
