Update docs/docs/development/new-shield.md
Co-authored-by: Cem Aksoylar <caksoylar@users.noreply.github.com>
This commit is contained in:
parent
a83c6d950b
commit
364638d6bb
1 changed files with 1 additions and 1 deletions
|
@ -55,7 +55,7 @@ config SHIELD_MY_BOARD
|
||||||
def_bool $(shields_list_contains,my_board)
|
def_bool $(shields_list_contains,my_board)
|
||||||
```
|
```
|
||||||
|
|
||||||
This will make sure that a new configuration value named `SHIELD_MY_BOARD` is set to true whenever `my_board` is added as a shield in your `build.yaml` file. This configuration value will be used in Kconfig.defconfig to set other properties about your shield, so make sure that you use the same name for the configuration value in both places.
|
This will make sure that a new configuration value named `SHIELD_MY_BOARD` is set to true whenever `my_board` is used as the shield name, either as the `SHIELD` variable [in a local build](build-flash.md) or in your `build.yaml` file [when using Github Actions](../customization). Note that this configuration value will be used in `Kconfig.defconfig` to set other properties about your shield, so make sure that they match.
|
||||||
|
|
||||||
**For split boards**, you will need to add configurations for the left and right sides, and check for the sibling you're building. For example, if your board's `id` is `my_board` and your `siblings` are named `my_board_left` and `my_board_right`, it would look like this:
|
**For split boards**, you will need to add configurations for the left and right sides, and check for the sibling you're building. For example, if your board's `id` is `my_board` and your `siblings` are named `my_board_left` and `my_board_right`, it would look like this:
|
||||||
|
|
||||||
|
|
Loading…
Add table
Reference in a new issue