Lines Matching full:you
45 You thus get a linker error, because you're asking for a pointer to a device
48 To fix it, you need to make sure that:
67 To find the devicetree node you need to check, use the number ``<N>`` from the
71 the node you are interested in is ``/soc/i2c@deadbeef``:
95 If the node has ``status = "disabled";`` in :file:`zephyr.dts`, then you need
106 Then you should put this into your devicetree overlay and
115 Make sure that you see ``status = "okay";`` in :file:`zephyr.dts` after you
121 your devicetree node and allocating devices for it. To do this, you need to
125 If you're not familiar with how devices are allocated from devicetree nodes
135 devicetree compatibles they are associated with. You will have to figure this
140 - Look inside that directory for relevant files until you figure out what the
143 Often, but not always, you can find the driver by looking for a file that sets
157 If you find a driver, you next need to make sure the Kconfig option that
158 compiles it is enabled. (If you don't find a driver, and you are sure the
159 compatible property is correct, then you need to write a driver. Writing
171 Then you would look inside of :zephyr_file:`drivers/i2c` for the driver file
174 ``DT_DRV_COMPAT`` is not set, you can use information like driver file names as
177 Once you know the driver you want to enable, you need to make sure its Kconfig
178 option is set to ``y``. You can figure out which Kconfig option is needed by
190 If your driver's Kconfig is not set to ``y``, you need to figure out what you
192 as you enable the devicetree node. Otherwise, it is sometimes as simple as
204 dependencies that you also have to enable before you can enable your driver.
211 Make sure you're using the right names
223 For example, if you're trying to **get** the ``clock-frequency`` property of a
241 And if you're trying to **set** that property in a devicetree overlay:
249 /* Don't do this; you'll get devicetree errors. */
273 You can then search for the file in the build directory to see what your
289 You can then open the file in your favorite editor to view the final C results
299 To prevent the compiler from doing this, you can disable the
313 If you're getting a compile error reading a node property, check your node
314 identifier and property. For example, if you get a build error on a line that
329 If you see the "whoops" error message when you rebuild, the node identifier
333 Some hints for what to check next if you don't see the "whoops" error message:
335 - did you :ref:`dt-use-the-right-names`?
354 If your binding file is not under :file:`zephyr/dts`, you may need to set
360 If you're using an API like :c:func:`DT_INST_PROP`, you must define
362 you are interested in. See :ref:`dt-create-devices-inst`.