docs: Add pointers to final Kconfig/devicetree files (#2796)
docs: Add diagnosis pointers for Kconfig/devicetree outputs docs: Add tip boxes for diagnosing config/devicetree changes
This commit is contained in:
parent
e4885d5d4c
commit
72b00b3f58
4 changed files with 56 additions and 0 deletions
|
|
@ -82,6 +82,12 @@ The list of available settings is determined by various files in ZMK whose names
|
|||
|
||||
See [Zephyr's Kconfig documentation](https://docs.zephyrproject.org/3.5.0/build/kconfig/index.html) for more details on Kconfig files.
|
||||
|
||||
:::tip
|
||||
|
||||
You can investigate the [final set of configuration settings](../troubleshooting/building-issues.md#configuration-setting-issues) that are in effect during a build to diagnose any issues with changing Kconfig settings.
|
||||
|
||||
:::
|
||||
|
||||
### KConfig Value Types
|
||||
|
||||
#### bool
|
||||
|
|
@ -131,6 +137,12 @@ Devicetree properties apply to specific nodes in the tree instead of globally. T
|
|||
|
||||
See [Zephyr's Devicetree guide](https://docs.zephyrproject.org/3.5.0/build/dts/index.html) for more details on Devicetree files.
|
||||
|
||||
:::tip
|
||||
|
||||
You can investigate the [final combined Devicetree](../troubleshooting/building-issues.md#devicetree-related-issues) produced during a build to diagnose any issues with changing Devicetree nodes.
|
||||
|
||||
:::
|
||||
|
||||
### Changing Devicetree Properties
|
||||
|
||||
Since Devicetree properties are set for specific nodes in the tree, you will first need to find the node you want to configure. You will typically need to
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue