Searched refs:sure (Results 1 – 25 of 371) sorted by relevance
12345678910>>...15
22 "Otherwise, be sure to define CONFIG_64BIT appropriately.\n"31 "Otherwise, be sure to define CONFIG_64BIT appropriately.\n"
10 # Make sure the remote build is using different target than host CPU28 # Make sure MCUboot is flashed first
7 # Make sure external power management setup is as indicated in documentation
11 * Sync with qemu_x86.dts on partitions to make sure
15 Says n if not sure.
13 Says n if not sure.
18 This option enables the checks to make sure the GPIO
11 Make sure we get DNS server addresses from the network
24 /* Make sure LSE clock is enabled */
27 /* Make sure HSI is enabled */
9 # Be sure to disable the bcfserial driver because it will capture /dev/ttyS4
24 Select n if not sure.
26 # address. So make sure memory mapped stack is not
10 Make sure there is a minimal heap available for BT driver.
19 # Make sure MCUboot is flashed first
42 - Make sure there are no jumpers on JP54 1-2 and JP21 4-546 - Make sure there are no jumpers on JP54 3-4 and JP21 16-1758 - Make sure there is no jumper on JP79 17-18.
13 make sure the ``protoc`` executable is installed and available.53 Make sure to include ``nanopb`` within your ``CMakeLists.txt`` file as follows:
25 Says n if not sure.
34 To make sure TF-M is supported for a board76 For Windows-based systems, please make sure you have a copy of the utility
48 ``west flash`` will by default use SEGGER JLink. Make sure that the JLinkExe binary is available on50 In this case, make sure that the commander binary is available on PATH.
14 Select ``Format...``. Make sure in ``File System``, ``FAT32`` is selected.27 Make sure the device node is the actual device node for
24 Make sure <devicetree.h> is included48 To fix it, you need to make sure that:65 **Making sure the node is enabled**:115 Make sure that you see ``status = "okay";`` in :file:`zephyr.dts` after you118 **Making sure the device driver is enabled**:157 If you find a driver, you next need to make sure the Kconfig option that158 compiles it is enabled. (If you don't find a driver, and you are sure the177 Once you know the driver you want to enable, you need to make sure its Kconfig194 making sure to :ref:`dt-trouble-try-pristine`:211 Make sure you're using the right names
