Searched full:follow (Results 1 – 25 of 325) sorted by relevance
12345678910>>...13
/Zephyr-Core-3.5.0/doc/develop/toolchains/ |
D | crosstool_ng.rst | 14 #. Follow the steps on the crosstool-NG website to `prepare your host 17 #. Follow the `Zephyr SDK with Crosstool NG instructions 38 environment, follow these example shell sessions (the
|
D | other_x_compilers.rst | 17 Follow these steps to use one of these toolchains. 40 environment, follow these example shell sessions (the
|
/Zephyr-Core-3.5.0/drivers/flash/ |
D | flash_ite_it8xxx2.c | 113 * Enter follow mode by writing 0xf to low nibble of ECINDAR3 register, in ramcode_flash_follow_mode() 132 /* Exit follow mode, and keep the setting of selecting internal flash */ in ramcode_flash_follow_mode_exit() 220 /* enter EC-indirect follow mode */ in ramcode_flash_cmd_write_enable() 226 /* exit EC-indirect follow mode */ in ramcode_flash_cmd_write_enable() 234 /* enter EC-indirect follow mode */ in ramcode_flash_cmd_write_disable() 240 /* exit EC-indirect follow mode */ in ramcode_flash_cmd_write_disable() 275 /* enter EC-indirect follow mode */ in ramcode_flash_cmd_write() 309 /* exit EC-indirect follow mode */ in ramcode_flash_cmd_write() 325 /* enter EC-indirect follow mode */ in ramcode_flash_cmd_erase() 331 /* exit EC-indirect follow mode */ in ramcode_flash_cmd_erase() [all …]
|
/Zephyr-Core-3.5.0/samples/boards/bbc_microbit/line_follower_robot/ |
D | README.rst | 18 for the robot to follow. Build and flash the program to the BBC 36 The sample program controls the robot to follow a line track and does
|
/Zephyr-Core-3.5.0/soc/riscv/riscv-privileged/common/ |
D | soc_irq.S | 19 * SOCs that do not truly follow the riscv privilege specification. 38 * SOCs that do not truly follow the riscv privilege specification.
|
/Zephyr-Core-3.5.0/samples/subsys/fs/format/ |
D | README.rst | 25 The Flash sample for the nrf 52DK board can be build as follow: 33 The RAM disk sample for the MIMXRT1064-EVK board can be build as follow:
|
/Zephyr-Core-3.5.0/tests/net/lib/lwm2m/interop/ |
D | README.md | 7 These tests require setup that is not done in Twister run, so follow this documentation to set 15 Follow [Networking with the host system](https://docs.zephyrproject.org/latest/connectivity/network… 16 from Zephyr's documentation how to set it up, or follow [Create NAT and routing for Zephyr native n… 70 These tests require extra package that is not installed when you follow the Zephyr's setup.
|
/Zephyr-Core-3.5.0/samples/bluetooth/hci_usb_h4/ |
D | prj.conf | 12 # Host number of completed commands does not follow normal flow control.
|
/Zephyr-Core-3.5.0/samples/bluetooth/hci_spi/ |
D | prj.conf | 12 # Host number of completed commands does not follow normal flow control.
|
/Zephyr-Core-3.5.0/subsys/net/l2/ethernet/gptp/ |
D | gptp_messages.h | 229 /** Follow up TLV. */ 336 * @brief Prepare Follow Up message. 377 * @param resp Related Path Delay Follow Up. 395 * @brief Handle Follow Up message. 423 * @brief Handle Path Delay Follow Up message. 451 * @brief Send a Follow Up message. 454 * @param pkt Follow Up message. 487 * @param pkt Network Buffer containing the prepared Path Delay Follow Up.
|
D | gptp_state.h | 190 /** Pointer to the received Path Delay Follow Up. */ 199 /** Path Delay Follow Up messages received. */ 231 /** Time at which a Sync Message without Follow Up will be discarded. */ 234 /** Timer for the Follow Up discard. */ 240 /** Pointer to the received Follow Up message. */ 249 /** A Follow Up Message has been received. */ 252 /** A Follow Up Message has been received. */ 312 /** Follow Up Correction Field of the last received PortSyncSync. */
|
/Zephyr-Core-3.5.0/samples/bluetooth/hci_usb/ |
D | prj.conf | 16 # Host number of completed commands does not follow normal flow control.
|
/Zephyr-Core-3.5.0/samples/bluetooth/hci_uart/ |
D | prj.conf | 22 # Host number of completed commands does not follow normal flow control.
|
/Zephyr-Core-3.5.0/drivers/fuel_gauge/sbs_gauge/ |
D | Kconfig.emul_sbs_gauge | 13 It provides readings which follow a simple sequence, thus allowing
|
/Zephyr-Core-3.5.0/samples/bluetooth/hci_rpmsg/ |
D | prj.conf | 16 # Host number of completed commands does not follow normal flow control.
|
D | nrf5340_cpunet_bt_mesh-bt_ll_sw_split.conf | 16 # Host number of completed commands does not follow normal flow control.
|
D | nrf5340_cpunet_iso_receive-bt_ll_sw_split.conf | 16 # Host number of completed commands does not follow normal flow control.
|
D | nrf5340_cpunet_iso_broadcast-bt_ll_sw_split.conf | 16 # Host number of completed commands does not follow normal flow control.
|
/Zephyr-Core-3.5.0/drivers/charger/ |
D | Kconfig.sbs_charger | 18 It provides reading which follow a simple sequence, thus allowing
|
/Zephyr-Core-3.5.0/drivers/fuel_gauge/bq27z746/ |
D | Kconfig | 20 It provides readings which follow a simple sequence, thus allowing
|
/Zephyr-Core-3.5.0/dts/bindings/sensor/ |
D | zephyr,sensing-sensor.yaml | 13 description: sensor type id (follow HID spec definition)
|
/Zephyr-Core-3.5.0/drivers/fuel_gauge/max17048/ |
D | Kconfig | 21 It provides readings which follow a simple sequence, thus allowing
|
/Zephyr-Core-3.5.0/scripts/coccinelle/ |
D | macros.h | 12 * is expected to follow that of the Coccinelle standard.h macro file.
|
/Zephyr-Core-3.5.0/doc/connectivity/usb/device/api/ |
D | usb_dc.rst | 10 This API has some limitations by design, it does not follow :ref:`device_model_api`
|
/Zephyr-Core-3.5.0/dts/bindings/gpio/ |
D | nxp,imx-gpio.yaml | 21 IMX pin selection peripheral does not follow specific
|
12345678910>>...13