Home
last modified time | relevance | path

Searched refs:sure (Results 26 – 50 of 371) sorted by relevance

12345678910>>...15

/Zephyr-latest/subsys/ipc/ipc_service/backends/
DKconfig.icmsg_me12 function. If you are sure that your application never sends data
/Zephyr-latest/samples/boards/st/power_mgmt/serial_wakeup/boards/
Db_u585i_iot02a.overlay35 /* Make sure HSI is enabled */
Dnucleo_wb55rg.overlay36 /* Make sure HSI is enabled */
/Zephyr-latest/doc/develop/tools/
Dclion.rst21 same for macOS and Linux, but make sure to select the correct environment file and to adjust the
36 Before you start, make sure you have a working Zephyr development environment, as per the
136 your setup is different, make sure to adjust the configuration settings accordingly.
162 from Zephyr SDK. Make sure to pick a version with Python support
197 #. Make sure that **Zephyr-threads** is selected in the configuration switcher and click the bug
Dstm32cubeide.rst19 #. Before you start, make sure you have a working Zephyr development environment, as per the
95 #. First, make sure to compile your project and have the ``zephyr.elf`` available.
134 making sure that you can run ``west`` in the shell that you start STM32CubeIDE
/Zephyr-latest/samples/sensor/accel_polling/
DREADME.rst26 Make sure the aliases are in devicetree, then build and run with:
/Zephyr-latest/drivers/adc/
DKconfig.tla202x21 Fine tune the priority for the driver initialization. Make sure it's
/Zephyr-latest/boards/renesas/da1469x_dk_pro/
DKconfig.defconfig44 # Make sure the serial device has higher
/Zephyr-latest/samples/sensor/magn_trig/
DREADME.rst23 Make sure the aliases are in devicetree, then build and run with:
/Zephyr-latest/boards/waveshare/open103z/
Dwaveshare_open103z.dts154 * make sure CAN and USB are not enabled at the same time
163 * make sure CAN and USB are not enabled at the same time
/Zephyr-latest/samples/subsys/logging/ble_backend/
DREADME.rst15 transmission size of the mtu set with :kconfig:option:`CONFIG_BT_L2CAP_TX_MTU`. Be sure
/Zephyr-latest/samples/sensor/ds18b20/
DREADME.rst38 Make sure this node has ``status = "okay";``, then build and run with:
48 Make sure that you have an external circuit to provide an open-drain interface
/Zephyr-latest/tests/boards/espressif/cache_coex/
DREADME.rst24 Make sure you have the target connected over USB port.
/Zephyr-latest/samples/boards/st/backup_sram/
DREADME.rst25 In order to run this sample, make sure to enable ``backup_sram`` node in your
/Zephyr-latest/drivers/serial/
DKconfig.ns1655024 Says n if not sure.
32 Says n if not sure.
/Zephyr-latest/samples/subsys/console/getchar/
DREADME.rst40 hex values and in character form. Be sure to press Enter, Up/Down, etc.
/Zephyr-latest/samples/boards/st/power_mgmt/wkup_pins/
DREADME.rst24 Make sure that wake-up pins are configured in SoC dtsi file.
/Zephyr-latest/samples/boards/espressif/spiram_test/
DREADME.rst26 Make sure you have your board connected over USB port.
/Zephyr-latest/boards/nxp/mimxrt685_evk/doc/
Dindex.rst224 1. Install the :ref:`linkserver-debug-host-tools` and make sure they are in your
227 2. Make sure the jumpers JP17, JP18 and JP19 are installed.
239 1. Install the :ref:`jlink-debug-host-tools` and make sure they are in your search path.
243 J-Link firmware. Please make sure you have the latest firmware for this board.
253 1. Install the :ref:`jlink-debug-host-tools` and make sure they are in your search path.
/Zephyr-latest/drivers/w1/
DKconfig40 sure to also increase SHELL_ARGC_MAX accordingly.
/Zephyr-latest/samples/net/lwm2m_client/
DKconfig48 Make sure we get DNS server addresses from the network
/Zephyr-latest/samples/boards/st/mco/
DREADME.rst18 Make sure that the output clock is enabled in dts overlay file.
/Zephyr-latest/samples/subsys/lorawan/class_a/
DREADME.rst18 Before building the sample, make sure to select the correct region in the
/Zephyr-latest/samples/sensor/dht_polling/
DREADME.rst28 Make sure the aliases are in devicetree.
/Zephyr-latest/boards/openisa/rv32m1_vega/doc/
Dindex.rst407 #. Make sure your J-Link is connected to your computer via USB.
412 Next, you'll need to make sure your board boots the RI5CY or ZERO-RISCY core.
417 first make sure you're booting the right core.
517 You need to make sure this happens every time you use this board.
561 Make sure you've done the :ref:`JTAG setup <rv32m1-vega-jtag>`, and
572 Make sure you've followed the above instructions to set up your board
593 - Make sure you don't have another ``openocd`` process running in the
596 - On Linux, make sure udev rules are installed, as described above.
606 Make sure you've done the :ref:`JTAG setup <rv32m1-vega-jtag>`, and
617 Make sure you've followed the above instructions to set up your board
[all …]

12345678910>>...15