Searched refs:using (Results 1526 – 1550 of 1710) sorted by relevance
1...<<616263646566676869
| /Zephyr-4.1.0/dts/arm/nxp/ |
| D | nxp_lpc55S2x_common.dtsi | 271 /* Enabling cs-gpios below will allow using GPIO CS,
|
| /Zephyr-4.1.0/boards/nxp/frdm_rw612/doc/ |
| D | index.rst | 144 The bus used to access the SRAM is determined using two separate memory mapped address spaces.
|
| /Zephyr-4.1.0/doc/kernel/data_structures/ |
| D | mpsc_pbuf.rst | 35 memory usage, header can be added on top of the user header using
|
| /Zephyr-4.1.0/doc/hardware/arch/ |
| D | x86.rst | 81 using the kernel image produced by the first linker pass. Additional
|
| /Zephyr-4.1.0/doc/services/device_mgmt/ |
| D | mcumgr.rst | 140 limiting the maximum packet size (most likely to occur when using image
|
| /Zephyr-4.1.0/boards/ezurio/pinnacle_100_dvk/doc/ |
| D | index.rst | 12 Develop your application directly on the M4F controller using Zephyr RTOS to
|
| /Zephyr-4.1.0/boards/fanke/fk7b0m1_vbt6/doc/ |
| D | index.rst | 144 To begin, connect the ST-Link Debug Programmer to the FK7B0M1-VBT6 board using the SWD
|
| /Zephyr-4.1.0/doc/kernel/services/data_passing/ |
| D | lifos.rst | 62 A LIFO is defined using a variable of type :c:struct:`k_lifo`.
|
| /Zephyr-4.1.0/boards/st/stm32f469i_disco/doc/ |
| D | index.rst | 130 First, connect the STM32F469I-DISCO Discovery kit to your host computer using
|
| /Zephyr-4.1.0/boards/adafruit/nrf52_adafruit_feather/doc/ |
| D | index.rst | 101 #. Connect the Adafruit nRF52 Feather to your host computer using USB
|
| /Zephyr-4.1.0/arch/arm/core/ |
| D | Kconfig | 131 bool "Compile C/C++ functions using Thumb-2 instruction set"
136 using the Thumb-2 instruction set.
|
| /Zephyr-4.1.0/doc/develop/west/ |
| D | west-apis.rst | 219 Since west v1.0, west commands should print output using methods like
512 The *abspath* attribute is created using ``os.path.abspath()``
|
| D | config.rst | 90 -- and thus the behavior of commands like ``west update`` -- using:
98 of the zephyr repository specified in the manifest. (You can go back to using
|
| /Zephyr-4.1.0/doc/connectivity/networking/api/ |
| D | sockets.rst | 28 BSD Sockets compatible API is enabled using :kconfig:option:`CONFIG_NET_SOCKETS`
188 descriptor using :c:func:`zvfs_reserve_fd` function. Any additional actions,
|
| /Zephyr-4.1.0/boards/nxp/frdm_k64f/doc/ |
| D | index.rst | 13 card slot, and connectivity using onboard Ethernet port and headers for use
254 Alternatively, pyOCD can be used to flash and debug the board by using the
|
| /Zephyr-4.1.0/arch/arc/ |
| D | Kconfig | 352 call arc_vpx_lock() before using them, and call arc_vpx_unlock()
353 when done using them.
|
| /Zephyr-4.1.0/boards/nxp/imx95_evk/doc/ |
| D | index.rst | 52 - MIPI CSI interface: Connects to one 36-pin miniSAS connector using x4 lane
54 - MIPI CSIDSI interface: Connects to one 36-pin miniSAS connector using x4 lane
|
| /Zephyr-4.1.0/cmake/modules/ |
| D | extensions.cmake | 602 # Note: Ensure the given partition has been defined using
970 # and user will be printed with an error if using
1441 # Note, files can also be passed as a comma separated list to support using
1526 # using set_property(APPEND) to produce a ";"-separated CMake list. This way,
1542 # using
1790 # Verify blobs fetched using west. If the sha256 checksum isn't valid, a warning/
2414 # the file paths are short, split these up into multiple elements using regex
2543 # can be specified by using shell-like quoting along with a 'SHELL:' prefix.
2747 to absolute path using `\${CMAKE_CURRENT_SOURCE_DIR}/${path}` or similar. \n \
2958 # When using CMake version 3.21 or newer 'zephyr_file_copy()' simply calls
[all …]
|
| /Zephyr-4.1.0/doc/connectivity/usb/device/ |
| D | usb_device.rst | 115 devicetree to describe CDC ACM UART. The motivation behind using devicetree
227 and the report descriptor must be registered using :c:func:`usb_hid_register_device`.
380 Applications using RNDIS support should enable :kconfig:option:`CONFIG_USB_DEVICE_OS_DESC`
389 using :c:func:`usb_bos_register_cap`. Registered descriptors are added to the root
|
| /Zephyr-4.1.0/arch/xtensa/core/ |
| D | README_MMU.txt | 107 needs to tell the hardware how to find a physical address using the
134 mechanism using the data TLB, and so need the refill mechanism for the
215 data, and leave any existing mappings in place in the TLB using the
|
| /Zephyr-4.1.0/samples/boards/renesas/openamp_linux_zephyr/ |
| D | README.rst | 6 and the real-time core running Zephyr, using the OpenAMP library.
|
| /Zephyr-4.1.0/samples/subsys/usb/dfu/ |
| D | README.rst | 5 Implement device firmware upgrade using the USB DFU class driver.
|
| /Zephyr-4.1.0/samples/drivers/counter/maxim_ds3231/ |
| D | README.rst | 5 Interact with a DS3231 real-time clock using the counter API and dedicated driver API.
|
| /Zephyr-4.1.0/samples/boards/nxp/adsp/number_crunching/ |
| D | README.rst | 2 :name: Number crunching using optimized library
|
| /Zephyr-4.1.0/share/zephyr-package/cmake/ |
| D | ZephyrConfigVersion.cmake | 90 # Temporary set local Zephyr base to allow using version.cmake to find this Zephyr repository curre…
|
1...<<616263646566676869
