Lines Matching refs:shield

8 In Zephyr, the shield feature provides Zephyr-formatted shield
19    boards/shields/<shield>
20    ├── <shield>.overlay
21    ├── Kconfig.shield
24 These files provides shield configuration as follows:
26 * **<shield>.overlay**: This file provides a shield description in devicetree
30 * **Kconfig.shield**: This file defines shield Kconfig symbols that will be
31   used for default shield configuration. To ease use with applications,
32   the default shield configuration here should be consistent with those in
35 * **Kconfig.defconfig**: This file defines the default shield configuration. It
37   shield configuration should be done by keeping in mind that features
42 to provide a device nodelabel is the form <device>_<shield>, for instance:
55 requirements that are specific to the shield (e.g: initialization routines,
72 Hardware shield-to-board compatibility depends on the use of well-known
79 * Pinmux: Connector pins should be correctly configured to match shield pins
89 Board specific shield configuration
92 If modifications are needed to fit a shield to a particular board or board
93 revision, you can override a shield description for a specific board by adding
94 board or board revision overriding files to a shield, as follows:
98    boards/shields/<shield>
110 Activate support for one or more shields by adding the matching ``--shield`` arguments
115      :shield: x_nucleo_idb05a1,x_nucleo_iks01a1
133    boards/shields/<shield>
139 In this case, a shield-particular revision name can be used:
143      :shield: shield_v2
146 You can also provide a board-specific configuration to a specific shield
151    boards/shields/<shield>
164 GPIOs accessed by the shield peripherals must be identified using the
165 shield GPIO abstraction, for example from the ``arduino-header-r3``