text stringlengths 9 39.2M | dir stringlengths 25 226 | lang stringclasses 163 values | created_date timestamp[s] | updated_date timestamp[s] | repo_name stringclasses 751 values | repo_full_name stringclasses 752 values | star int64 1.01k 183k | len_tokens int64 1 18.5M |
|---|---|---|---|---|---|---|---|---|
```unknown
/*
*
*/
&mikrobus_i2c {
status = "okay";
bme280_mikroe_weather_click: bme280@76 {
compatible = "bosch,bme280";
reg = <0x76>;
};
};
``` | /content/code_sandbox/boards/shields/mikroe_weather_click/mikroe_weather_click.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 54 |
```unknown
config SHIELD_NXP_BTB44_OV5640
def_bool $(shields_list_contains,nxp_btb44_ov5640)
``` | /content/code_sandbox/boards/shields/nxp_btb44_ov5640/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 31 |
```restructuredtext
.. _mikroe_weather_click:
MikroElektronika Weather Click
##############################
Overview
********
The MikroElektronika `Weather Click`_ features the `BME280`_ integrated
environmental sensor in a `mikroBUS`_ |trade| form factor. The sensor can
measure relative humidity, barometric pressure, and ambient temperature.
.. figure:: weather-click.webp
:align: center
:alt: MikroElektronika Weather Click
MikroElektronika Weather Click (Credit: MikroElektronika)
Requirements
************
This shield can only be used with a board that provides a mikroBUS |trade|
socket and defines a ``mikrobus_i2c`` node label for the mikroBUS |trade| I2C
interface (see :ref:`shields` for more details).
For more information about the BME280 and the Weather Click, see the following
documentation:
- `Weather Click`_
- `Weather Click Schematic`_
- `BME280`_
- `BME280 Datasheet`_
Programming
***********
Set ``--shield mikroe_weather_click`` when you invoke ``west build``. For
example:
.. zephyr-app-commands::
:zephyr-app: samples/sensor/bme280
:board: lpcxpresso55s16
:shield: mikroe_weather_click
:goals: build
.. _Weather Click:
path_to_url
.. _Weather Click Schematic:
path_to_url
.. _BME280:
path_to_url
.. _BME280 Datasheet:
path_to_url
.. _mikroBUS:
path_to_url
``` | /content/code_sandbox/boards/shields/mikroe_weather_click/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 372 |
```unknown
/*
*
*/
/{
chosen {
zephyr,camera = &nxp_csi;
};
};
&nxp_cam_i2c {
status = "okay";
ov5640: ov5640@3c {
compatible = "ovti,ov5640";
reg = <0x3c>;
reset-gpios = <&nxp_cam_connector 9 GPIO_ACTIVE_LOW>;
powerdown-gpios = <&nxp_cam_connector 17 GPIO_ACTIVE_HIGH>;
port {
ov5640_ep_out: endpoint {
remote-endpoint = <&mipi_csi2rx_ep_in>;
};
};
};
};
&nxp_mipi_csi {
status = "okay";
sensor = <&ov5640>;
ports {
port@1 {
reg = <1>;
mipi_csi2rx_ep_in: endpoint {
remote-endpoint = <&ov5640_ep_out>;
};
};
};
};
&nxp_csi {
status = "okay";
};
``` | /content/code_sandbox/boards/shields/nxp_btb44_ov5640/nxp_btb44_ov5640.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 229 |
```unknown
config SHIELD_SSD1306_128X32
def_bool $(shields_list_contains,ssd1306_128x32)
config SHIELD_SSD1306_128X64
def_bool $(shields_list_contains,ssd1306_128x64)
config SHIELD_SSD1306_128X64_SPI
def_bool $(shields_list_contains,ssd1306_128x64_spi)
config SHIELD_SH1106_128X64
def_bool $(shields_list_contains,sh1106_128x64)
``` | /content/code_sandbox/boards/shields/ssd1306/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 118 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,display = &ssd1306_ssd1306_128x64;
};
};
&arduino_i2c {
status = "okay";
ssd1306_ssd1306_128x64: ssd1306@3c {
compatible = "solomon,ssd1306fb";
reg = <0x3c>;
width = <128>;
height = <64>;
segment-offset = <0>;
page-offset = <0>;
display-offset = <0>;
multiplex-ratio = <63>;
segment-remap;
com-invdir;
prechargep = <0x22>;
};
};
``` | /content/code_sandbox/boards/shields/ssd1306/ssd1306_128x64.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 157 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,display = &ssd1306_ssd1306_128x32;
};
};
&arduino_i2c {
status = "okay";
ssd1306_ssd1306_128x32: ssd1306@3c {
compatible = "solomon,ssd1306fb";
reg = <0x3c>;
width = <128>;
height = <32>;
segment-offset = <0>;
page-offset = <0>;
display-offset = <0>;
multiplex-ratio = <31>;
segment-remap;
com-invdir;
com-sequential;
prechargep = <0x22>;
};
};
``` | /content/code_sandbox/boards/shields/ssd1306/ssd1306_128x32.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 162 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,display = &sh1106_sh1106_128x64;
};
};
&arduino_i2c {
status = "okay";
sh1106_sh1106_128x64: ssd1306@3c {
compatible = "sinowealth,sh1106";
reg = <0x3c>;
width = <128>;
height = <64>;
segment-offset = <2>;
page-offset = <0>;
display-offset = <0>;
multiplex-ratio = <63>;
segment-remap;
com-invdir;
prechargep = <0x22>;
};
};
``` | /content/code_sandbox/boards/shields/ssd1306/sh1106_128x64.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 152 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,display = &ssd1306_ssd1306_128x64_spi;
};
};
&arduino_spi {
status = "okay";
ssd1306_ssd1306_128x64_spi: ssd1306@0 {
compatible = "solomon,ssd1306fb";
reg = <0x0>;
spi-max-frequency = <10000000>;
width = <128>;
height = <64>;
segment-offset = <0>;
page-offset = <0>;
display-offset = <0>;
multiplex-ratio = <63>;
segment-remap;
com-invdir;
prechargep = <0x22>;
data_cmd-gpios = <&arduino_header 15 0>;
/* reset-gpios = <&arduino_header 14 GPIO_ACTIVE_LOW>; */
};
};
``` | /content/code_sandbox/boards/shields/ssd1306/ssd1306_128x64_spi.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 199 |
```restructuredtext
.. _nxp_btb44_ov5640:
NXP BTB-44 OV5640 Camera Module
###############################
Overview
********
This shield supports ov5640 camera modules which use a 44-pin board-to-board connector and
a MIPI CSI or DVP (parallel) interface. These camera modules are made specifically for and
provided together with NXP's i.MX RT1160 and RT1170 EVK boards.
More information about this OV5640 camera module can be found at `Camera iMXRT`_.
Pins assignment of the NXP board-to-board 44-pin OV5640 camera module
======================================================================
+----------------------+--------------------+
| Camera Connector Pin | Function |
+======================+====================+
| 1 | AGND |
+----------------------+--------------------+
| 2 | AF_GND |
+----------------------+--------------------+
| 3 | STROBE |
+----------------------+--------------------+
| 4 | AF_VCC |
+----------------------+--------------------+
| 5 | SDA |
+----------------------+--------------------+
| 6 | VCMSINK |
+----------------------+--------------------+
| 7 | SCL |
+----------------------+--------------------+
| 8 | AVDD |
+----------------------+--------------------+
| 9 | RESETB |
+----------------------+--------------------+
| 10 | GPIO1 |
+----------------------+--------------------+
| 11 | PCLK |
+----------------------+--------------------+
| 12 | GPIO0 |
+----------------------+--------------------+
| 13 | VSYNC |
+----------------------+--------------------+
| 14 | FREX |
+----------------------+--------------------+
| 15 | HREF |
+----------------------+--------------------+
| 16 | MIPI_CSI_DP1 / D9 |
+----------------------+--------------------+
| 17 | PWDN |
+----------------------+--------------------+
| 18 | MIPI_CSI_DN1 / D8 |
+----------------------+--------------------+
| 19 | MIPI_CSI_DP1 / D9 |
+----------------------+--------------------+
| 20 | DGND |
+----------------------+--------------------+
| 21 | MIPI_CSI_DN1 / D8 |
+----------------------+--------------------+
| 22 | MIPI_CSI_CLKP / D7 |
+----------------------+--------------------+
| 23 | MIPI_CSI_CLKP / D7 |
+----------------------+--------------------+
| 24 | MIPI_CSI_CLKN / D6 |
+----------------------+--------------------+
| 25 | MIPI_CSI_CLKN / D6 |
+----------------------+--------------------+
| 26 | DGND |
+----------------------+--------------------+
| 27 | MIPI_CSI_DP0 / D5 |
+----------------------+--------------------+
| 28 | MIPI_CSI_DP0 / D5 |
+----------------------+--------------------+
| 29 | MIPI_CSI_DN0 / D4 |
+----------------------+--------------------+
| 30 | MIPI_CSI_DN0 / D4 |
+----------------------+--------------------+
| 31 | D3 |
+----------------------+--------------------+
| 32 | DGND |
+----------------------+--------------------+
| 33 | D2 |
+----------------------+--------------------+
| 34 | XCLK |
+----------------------+--------------------+
| 35 | D1 |
+----------------------+--------------------+
| 36 | DVDD |
+----------------------+--------------------+
| 37 | D0 |
+----------------------+--------------------+
| 38 | DOVDD |
+----------------------+--------------------+
| 39 | DGND |
+----------------------+--------------------+
| 40 | DGND |
+----------------------+--------------------+
| 41 | GND |
+----------------------+--------------------+
| 42 | GND |
+----------------------+--------------------+
| 43 | GND |
+----------------------+--------------------+
| 44 | AF_GND |
+----------------------+--------------------+
Requirements
************
This shield can only be used with a board which provides a 44-pin board-to-board
connector with MIPI CSI or DVP (parallel) interface where the pinouts are defined
as above, such as i.MX RT1160 and RT1170 EVK boards.
Programming
***********
Set ``--shield nxp_btb44_ov5640`` when you invoke ``west build``. For example:
.. zephyr-app-commands::
:zephyr-app: samples/subsys/video/capture
:board: mimxrt1170_evk/mimxrt1176/cm7
:shield: nxp_btb44_ov5640
:goals: build
References
**********
.. target-notes::
.. _Camera iMXRT:
path_to_url
``` | /content/code_sandbox/boards/shields/nxp_btb44_ov5640/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,031 |
```unknown
&arduino_i2c {
compatible = "nordic,nrf-twi";
};
``` | /content/code_sandbox/boards/shields/ssd1306/boards/reel_board.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 20 |
```unknown
if SHIELD_SSD1306_128X64 || SHIELD_SSD1306_128X64_SPI || SHIELD_SSD1306_128X32 || SHIELD_SH1106_128X64
if DISPLAY
if LVGL
config LV_Z_VDB_SIZE
default 64
config LV_DPI_DEF
default 116 if SHIELD_SH1106_128X64
default 148
config LV_Z_BITS_PER_PIXEL
default 1
choice LV_COLOR_DEPTH
default LV_COLOR_DEPTH_1
endchoice
endif # LVGL
endif # DISPLAY
endif # SHIELD_SSD1306_128X64 || SHIELD_SSD1306_128X64_SPI || SHIELD_SSD1306_128X32 || SHIELD_SH1106_128X64
``` | /content/code_sandbox/boards/shields/ssd1306/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 170 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,bt-hci = &spbtle_rf_x_nucleo_idb05a1;
};
};
&arduino_spi {
cs-gpios = <&arduino_header 1 GPIO_ACTIVE_LOW>; /* A1 */
spbtle_rf_x_nucleo_idb05a1: spbtle-rf@0 {
compatible = "st,hci-spi-v1";
reg = <0>;
reset-gpios = <&arduino_header 13 GPIO_ACTIVE_LOW>; /* D7 */
irq-gpios = <&arduino_header 0 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>; /* A0 */
spi-max-frequency = <DT_FREQ_M(2)>;
spi-hold-cs;
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_idb05a1/x_nucleo_idb05a1.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 170 |
```unknown
config SHIELD_X_NUCLEO_IDB05A1
def_bool $(shields_list_contains,x_nucleo_idb05a1)
``` | /content/code_sandbox/boards/shields/x_nucleo_idb05a1/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 33 |
```restructuredtext
.. _ssd1306_128_shield:
SSD1306 128x64(/32) pixels generic shield
#########################################
Overview
********
This is a generic shield for 128x64(/32) pixel resolution OLED displays
based on SSD1306 controller. These displays have an I2C interface and
usually only four pins: GND, VCC, SCL and SDA. Display pins can be
connected to the pin header of a board using jumper wires.
Current supported displays
==========================
+---------------------+---------------------+---------------------+
| Display | Controller / | Shield Designation |
| | Driver | |
+=====================+=====================+=====================+
| No Name | SSD1306 / | ssd1306_128x64 |
| 128x64 pixel | ssd1306 | |
+---------------------+---------------------+---------------------+
| No Name | SSD1306 / | ssd1306_128x32 |
| 128x32 pixel | ssd1306 | |
+---------------------+---------------------+---------------------+
| No Name | SH1106 / | sh1106_128x64 |
| 128x64 pixel | ssd1306 | |
+---------------------+---------------------+---------------------+
Requirements
************
This shield can only be used with a board which provides a configuration
for Arduino connectors and defines a node alias for the I2C interface
(see :ref:`shields` for more details).
Programming
***********
Set ``--shield ssd1306_128x64`` when you invoke ``west build``. For example:
.. zephyr-app-commands::
:zephyr-app: samples/subsys/display/lvgl
:board: frdm_k64f
:shield: ssd1306_128x64
:goals: build
``` | /content/code_sandbox/boards/shields/ssd1306/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 415 |
```unknown
if SHIELD_X_NUCLEO_IDB05A1
if BT
config SPI
default y
config BT_SPI
default y
config BT_BLUENRG_ACI
default y
# Disable Flow control
config BT_HCI_ACL_FLOW_CONTROL
default n
config BT_HCI_VS
default n
endif # BT
endif
``` | /content/code_sandbox/boards/shields/x_nucleo_idb05a1/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 76 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,bt-c2h-uart = &usart2;
};
};
&arduino_spi {
pinctrl-0 = <&spi1_sck_pb3 &spi1_miso_pa6 &spi1_mosi_pa7>;
};
``` | /content/code_sandbox/boards/shields/x_nucleo_idb05a1/boards/nucleo_l476rg.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 63 |
```unknown
/*
*
*/
&arduino_spi {
spbtle_rf_x_nucleo_idb05a1: spbtle-rf@0 {
cs-gpios = <&arduino_header 16 (GPIO_ACTIVE_HIGH | GPIO_PULL_UP)>; /* D10 */
irq-gpios = <&arduino_header 15 0>; /* D9 */
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_idb05a1/boards/stm32mp157c_dk2.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 79 |
```unknown
config SHIELD_X_NUCLEO_53L0A1
def_bool $(shields_list_contains,x_nucleo_53l0a1)
``` | /content/code_sandbox/boards/shields/x_nucleo_53l0a1/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 35 |
```unknown
/*
*
*/
&arduino_i2c {
expander1_x_nucleo_53l0a1: stmpe1600@42 {
compatible = "st,stmpe1600";
reg = <0x42>;
ngpios = <16>;
gpio-controller;
#gpio-cells = <2>;
};
expander2_x_nucleo_53l0a1: stmpe1600@43 {
compatible = "st,stmpe1600";
reg = <0x43>;
ngpios = <16>;
gpio-controller;
#gpio-cells = <2>;
};
/* Center sensor soldered on the shield */
vl53l0x_c_x_nucleo_53l0a1: vl53l0x@30 {
compatible = "st,vl53l0x";
reg = <0x30>;
xshut-gpios = <&expander1_x_nucleo_53l0a1 15 GPIO_ACTIVE_LOW>;
};
/* Satellites optional sensors */
vl53l0x_l_x_nucleo_53l0a1: vl53l0x@31 {
compatible = "st,vl53l0x";
reg = <0x31>;
xshut-gpios = <&expander2_x_nucleo_53l0a1 14 GPIO_ACTIVE_LOW>;
};
vl53l0x_r_x_nucleo_53l0a1: vl53l0x@32 {
compatible = "st,vl53l0x";
reg = <0x32>;
xshut-gpios = <&expander2_x_nucleo_53l0a1 15 GPIO_ACTIVE_LOW>;
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_53l0a1/x_nucleo_53l0a1.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 389 |
```unknown
if SHIELD_X_NUCLEO_53L0A1
config VL53L0X_RECONFIGURE_ADDRESS
default y if SENSOR
endif # SHIELD_X_NUCLEO_53L0A1
``` | /content/code_sandbox/boards/shields/x_nucleo_53l0a1/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 49 |
```restructuredtext
.. _x-nucleo-idb05a1:
X-NUCLEO-IDB05A1: BLE expansion board
#####################################
Overview
********
The X-NUCLEO-IDB05A1 is a Bluetooth Low Energy evaluation board based on the
SPBTLE-RF BlueNRG-MS RF module to allow expansion of the STM32 Nucleo boards.
The SPBTLE-RF module is FCC (FCC ID: S9NSPBTLERF) and IC certified
(IC: 8976C-SPBTLERF).
The X-NUCLEO-IDB05A1 is compatible with the ST Morpho and Arduino UNO R3
connector layout (the user can mount the ST Morpho connectors, if required). The
X-NUCLEO-IDB05A1 interfaces with the host microcontroller via the SPI pin, and
the user can change the default SPI clock, the SPI chip select and SPI IRQ by
changing one resistor on the evaluation board.
Note : This shield is compatible out of the box with Arduino UNO R3 connectors,
but CS and SCK signals are not the standard Arduino SPI_CS and SPI_SCK signals.
Please refer to "Hardware configuration" section.
.. image:: img/x-nucleo-idb05a1.jpg
:align: center
:alt: X-NUCLEO-IDB05A1
More information about the board can be found at the
`X-NUCLEO-IDB05A1 website`_.
Hardware configuration
**********************
Out of the box, X-NUCLEO-IDB05A1 shield expects SPI SCK to be available on
Arduino pin D3 instead of usual Arduino UNO R3 SPI SCK D13.
This is not a problem if SPI SCK from nucleo board is available on D3,
otherwise shield configuration can be changed (see below).
Also shield expects SPI CS to be available on Arduino pin A1 instead of usual
Arduino UNO R3 SPI CS D10.
This is not a problem as CS signal is software driven gpio on Arduino A1
see cs-gpios in x_nucleo_idb05a1.overlay
Shield configuration could be modified by moving resistors as
follows:
- SPI SCK: to use D13 instead of D3, remove R4 and add R6
Additionally, depending on your host board, some modifications of the BLE
expansion board could be made:
- CS: To use D10 instead of A1, remove R2 and add R7
- IRQ: To use D9 instead of A0, remove R1 and add R8
You could check Figure 3 in `X-NUCLEO-IDB05A1 databrief`_ for more details.
The stm32mp157c_dk2 board is known to need those CS/IRQ pin modifications
(see boards/stm32mp157c_dk2.overlay)
whereas nucleo_l476rg doesn't need hardware modifications.
Hardware
********
X-NUCLEO-IDB05A1 provides a SPBTLE-RF chip with the following key features:
- Bluetooth Low Energy FCC and IC certified module based on Bluetooth SMART
4.1 network processor BlueNRG-MS
- Integrated Balun (BALF-NRG-01D3)
- Chip antenna
More information about X-NUCLEO-IDB05A1 can be found here:
- `X-NUCLEO-IDB05A1 databrief`_
Programming
***********
You can use the X-NUCLEO-IDB05A1 as a Bluetooth Low-Energy controller
shield with an SPI host controller interface (HCI-SPI). Activate the presence
of the shield for the project build by adding the ``--shield`` arg to the
build command:
.. zephyr-app-commands::
:zephyr-app: your_app
:board: your_board_name
:shield: x_nucleo_idb05a1
:goals: build
Alternatively, set use of this shield in the project's ``CMakeLists.txt`` file:
.. code-block:: cmake
set(SHIELD x_nucleo_idb05a1)
References
**********
.. target-notes::
.. _X-NUCLEO-IDB05A1 website:
path_to_url
.. _X-NUCLEO-IDB05A1 databrief:
path_to_url
``` | /content/code_sandbox/boards/shields/x_nucleo_idb05a1/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 933 |
```unknown
/*
*
*/
#include <zephyr/dt-bindings/display/panel.h>
/{
chosen {
zephyr,display = &zephyr_lcdif;
};
lvgl_pointer {
compatible = "zephyr,lvgl-pointer-input";
input = <&ft5336_rk043fn02h_ct>;
};
};
&nxp_touch_i2c {
status = "okay";
ft5336_rk043fn02h_ct: ft5336@38 {
compatible = "focaltech,ft5336";
reg = <0x38>;
int-gpios = <&nxp_i2c_touch_fpc 2 GPIO_ACTIVE_LOW>;
};
};
&zephyr_lcdif {
status = "okay";
width = <480>;
height = <272>;
display-timings {
compatible = "zephyr,panel-timing";
hsync-len = <41>;
hfront-porch = <4>;
hback-porch = <8>;
vsync-len = <10>;
vfront-porch = <4>;
vback-porch = <2>;
de-active= <1>;
pixelclk-active = <1>;
hsync-active = <0>;
vsync-active = <0>;
clock-frequency = <9210240>;
};
pixel-format = <PANEL_PIXEL_FORMAT_BGR_565>;
data-bus-width = "16-bit";
backlight-gpios = <&nxp_parallel_lcd_connector 0 GPIO_ACTIVE_HIGH>;
};
``` | /content/code_sandbox/boards/shields/rk043fn02h_ct/rk043fn02h_ct.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 328 |
```unknown
config SHIELD_RK043FN02H_CT
def_bool $(shields_list_contains,rk043fn02h_ct)
``` | /content/code_sandbox/boards/shields/rk043fn02h_ct/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 28 |
```unknown
if SHIELD_RK043FN02H_CT
if LVGL
config INPUT
default y
config INPUT_FT5336_INTERRUPT
default y
# LVGL should allocate buffers equal to size of display
config LV_Z_VDB_SIZE
default 100
# Enable double buffering
config LV_Z_DOUBLE_VDB
default y
# Force full refresh. This prevents memory copy associated with partial
# display refreshes, which is not necessary for the eLCDIF driver
config LV_Z_FULL_REFRESH
default y
config LV_Z_BITS_PER_PIXEL
default 16
config LV_DPI_DEF
default 128
# Use offloaded render thread
config LV_Z_FLUSH_THREAD
default y
choice LV_COLOR_DEPTH
default LV_COLOR_DEPTH_16
endchoice
# Force display buffers to be aligned to cache line size (32 bytes)
config LV_Z_VDB_ALIGN
default 32
endif # LVGL
endif # SHIELD_RK043FN02H_CT
``` | /content/code_sandbox/boards/shields/rk043fn02h_ct/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 204 |
```restructuredtext
.. _x_nucleo_53l0a1_shield:
X-NUCLEO-53L0A1 ranging and gesture detection sensor expansion board
####################################################################
Overview
********
The X-NUCLEO-53L0A1 expansion board features the VL53L0X ranging and gesture
detection sensor, based on STs FlightSense, Time-of-Flight technology. It is
an evaluation board that provides an introduction to the ranging and gesture
detection capabilities of the VL53L0X module.
One VL53L0X is soldered on the expansion board itself. A set of spacers and
a cover glass are provided with the board, and can be fitted onto this center
sensor.
Two VL53L0X satellites can be connected using the two 10 pin connectors.
The expansion board is compatible with the STM32 Nucleo board family,
and with the Arduino UNO R3 connector layout.
.. figure:: x_nucleo_53l0a1.jpg
:align: center
:alt: X-NUCLEO-53L0A1
More information about the board can be found at the
`X-NUCLEO-53L0A1 website`_.
Requirements
************
This shield can only be used with a development board that provides a
configuration for Arduino connectors and defines a node alias for the
I2C interface (see :ref:`shields` for more details).
Peripherals
***********
The sensors have the following device tree labels and I2C addresses:
* **Center sensor** (soldered on the shield): ``VL53L0X_C``, 0x30
* **Left satellite sensor**: ``VL53L0X_L``, 0x31
* **Right satellite sensor**: ``VL53L0X_R``, 0x32
The 7 segment display is connected to two GPIO expanders, each of one handles
2 digits x 7 segments = 14 pins:
* **Rightmost two digits**: ``EXPANDER1``, 0x42
* **Leftmost two digits**: ``EXPANDER2``, 0x43
External links
**************
- `X-NUCLEO-53L0A1 ranging and gesture detection sensor expansion board User Manual`_
- `VL53L0X Time-of-Flight ranging and gesture detection sensor Datasheet`_
Samples
*******
The sample :ref:`vl53l0x` demonstrates how to use the ranging sensor VL53L0X
using the center sensor only.
The sample :zephyr:code-sample:`x-nucleo-53l0a1` sample demonstrates how to use the three
sensors (soldered + 2 satellites) and the 7 segments display.
Programming
***********
Set ``--shield x_nucleo_53l0a1`` when you invoke ``west build``. For example:
.. zephyr-app-commands::
:zephyr-app: samples/sensor/vl53l0x
:board: nucleo_f429zi
:shield: x_nucleo_53l0a1
:goals: build
.. _X-NUCLEO-53L0A1 website:
path_to_url
.. _X-NUCLEO-53L0A1 ranging and gesture detection sensor expansion board User Manual:
path_to_url
.. _VL53L0X Time-of-Flight ranging and gesture detection sensor Datasheet:
path_to_url
``` | /content/code_sandbox/boards/shields/x_nucleo_53l0a1/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 746 |
```unknown
config SHIELD_MIKROE_ADC_CLICK
def_bool $(shields_list_contains,mikroe_adc_click)
``` | /content/code_sandbox/boards/shields/mikroe_adc_click/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 25 |
```unknown
/*
*
*/
#include <zephyr/dt-bindings/adc/adc.h>
&mikrobus_spi {
status = "okay";
mcp3204_mikroe_adc_click: mcp3204@0 {
compatible = "microchip,mcp3204";
reg = <0x0>;
spi-max-frequency = <100000>;
#io-channel-cells = <1>;
};
};
``` | /content/code_sandbox/boards/shields/mikroe_adc_click/mikroe_adc_click.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 91 |
```unknown
if SHIELD_MIKROE_ADC_CLICK
if ADC
config ADC_INIT_PRIORITY
default 80
endif # ADC
endif # SHIELD_MIKROE_ADC_CLICK
``` | /content/code_sandbox/boards/shields/mikroe_adc_click/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 39 |
```restructuredtext
.. _rk043fn02h_ct:
RK043FN02H-CT Parallel Display
##############################
Overview
********
RK043FN02H-CT is a 4.3 inch TFT 480*272 pixels with LED backlight and
capacitive touch panel from Rocktech. This LCD panel can work with several i.MX
RT EVKs and LPC MCUs for evaluation of applications with display.
More information about the shield can be found at the `RK043FN02H-CT product
page`_.
This display uses a 40 pin parallel FPC interface plus 6 pin I2C interface,
available on many NXP EVKs. Note that this parallel FPC interface is not
compatible with the MIPI FPC interface present on other NXP EVKs.
Pins Assignment of the Rocktech RK043FN02H-CT Parallel Display
==============================================================
+-----------------------+------------------------+
| Parallel FPC Pin | Function |
+=======================+========================+
| 1 | LED backlight cathode |
+-----------------------+------------------------+
| 2 | LED backlight anode |
+-----------------------+------------------------+
| 3 | GND |
+-----------------------+------------------------+
| 4 | VDD (3v3) |
+-----------------------+------------------------+
| 5-7 | GND |
+-----------------------+------------------------+
| 8-12 | LCD D11-D15 |
+-----------------------+------------------------+
| 13-14 | GND |
+-----------------------+------------------------+
| 15-20 | LCD D5-D10 |
+-----------------------+------------------------+
| 21-23 | GND |
+-----------------------+------------------------+
| 24-28 | LCD D0-D4 |
+-----------------------+------------------------+
| 29 | GND |
+-----------------------+------------------------+
| 30 | LCD CLK |
+-----------------------+------------------------+
| 31 | LCD DISP |
+-----------------------+------------------------+
| 32 | LCD HSYNC |
+-----------------------+------------------------+
| 33 | LCD VSYNC |
+-----------------------+------------------------+
| 34 | LCD DE |
+-----------------------+------------------------+
| 35 | NC |
+-----------------------+------------------------+
| 36 | GND |
+-----------------------+------------------------+
| 37-40 | NC |
+-----------------------+------------------------+
+-----------------------+------------------------+
| I2C Connector Pin | Function |
+=======================+========================+
| 1 | VDD (3v3) |
+-----------------------+------------------------+
| 2 | LCD Touch Reset |
+-----------------------+------------------------+
| 3 | LCD Touch Interrupt |
+-----------------------+------------------------+
| 4 | LCD I2C SCL |
+-----------------------+------------------------+
| 5 | LCD I2C SDA |
+-----------------------+------------------------+
| 6 | GND |
+-----------------------+------------------------+
Requirements
************
This shield can only be used with a board which provides a configuration
for the 40+6 pin parallel/I2C FPC interface
Programming
***********
Set ``--shield rk043fn02h_ct`` when you invoke ``west build``. For
example:
.. zephyr-app-commands::
:zephyr-app: samples/drivers/display
:board: mimxrt1060_evk
:shield: rk043fn02h_ct
:goals: build
References
**********
.. target-notes::
.. _RK043FN02H-CT product page:
path_to_url
``` | /content/code_sandbox/boards/shields/rk043fn02h_ct/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 815 |
```unknown
/*
*
*/
#include <zephyr/dt-bindings/adc/adc.h>
/delete-node/ &mcp3204_mikroe_adc_click;
&mikrobus_spi {
status = "okay";
/* LPCXpresso55S16 uses SSEL1 for mikroBUS SPI */
mcp3204_mikroe_adc_click: mcp3204@1 {
compatible = "microchip,mcp3204";
reg = <0x1>;
spi-max-frequency = <100000>;
#io-channel-cells = <1>;
};
};
``` | /content/code_sandbox/boards/shields/mikroe_adc_click/boards/lpcxpresso55s16.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 123 |
```unknown
config SHIELD_SEMTECH_SX1262MB2DAS
def_bool $(shields_list_contains,semtech_sx1262mb2das)
``` | /content/code_sandbox/boards/shields/semtech_sx1262mb2das/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 36 |
```unknown
/*
*/
/ {
aliases {
lora0 = &lora_semtech_sx1262mb2das;
};
};
&arduino_spi {
status = "okay";
cs-gpios = <&arduino_header 13 GPIO_ACTIVE_LOW>;
lora_semtech_sx1262mb2das: sx1262@0 {
compatible = "semtech,sx1262";
reg = <0>;
spi-max-frequency = <16000000>;
label = "SX1262";
reset-gpios = <&arduino_header 0 GPIO_ACTIVE_LOW>;
busy-gpios = <&arduino_header 9 GPIO_ACTIVE_HIGH>;
antenna-enable-gpios = <&arduino_header 14 GPIO_ACTIVE_HIGH>;
dio1-gpios = <&arduino_header 11 GPIO_ACTIVE_HIGH>;
dio2-tx-enable;
tcxo-power-startup-delay-ms = <5>;
};
};
``` | /content/code_sandbox/boards/shields/semtech_sx1262mb2das/semtech_sx1262mb2das.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 197 |
```restructuredtext
.. _mikroe_adc_click_shield:
MikroElektronika ADC Click
##########################
Overview
********
The MikroElektronika ADC Click carries the `MCP3204`_ 12-bit
Analog-to-Digital converter in a `mikroBUS`_ |trade| form factor.
.. figure:: adc-click.jpg
:align: center
:alt: MikroElektronika ADC Click
MikroElektronika ADC Click (Credit: MikroElektronika)
Requirements
************
This shield can only be used with a development board that provides a
configuration for mikroBUS connectors and defines a node alias for the mikroBUS
SPI interface (see :ref:`shields` for more details).
For more information about interfacing the MCP3204 and the ADC Click,
see the following documentation:
- `MCP3204 Datasheet`_
- `ADC Click`_
Programming
***********
Set ``--shield mikro_adc_click`` when you invoke ``west build``. For
example:
.. zephyr-app-commands::
:zephyr-app: <my_app>
:board: lpcxpresso55s16
:shield: mikroe_adc_click
:goals: build
.. _MCP3204:
path_to_url
.. _mikroBUS:
path_to_url
.. _MCP3204 Datasheet:
path_to_url
.. _ADC Click:
path_to_url
``` | /content/code_sandbox/boards/shields/mikroe_adc_click/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 321 |
```unknown
config SHIELD_DAC80508_EVM
def_bool $(shields_list_contains,dac80508_evm)
``` | /content/code_sandbox/boards/shields/dac80508_evm/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 25 |
```unknown
/*
*
*/
&arduino_spi {
status = "okay";
cs-gpios = <&arduino_header 16 GPIO_ACTIVE_LOW>; /* D10 */
dac80508_dac80508_evm: dac80508@0 {
compatible = "ti,dac80508";
reg = <0x0>;
spi-max-frequency = <1000000>;
#io-channel-cells = <1>;
};
};
``` | /content/code_sandbox/boards/shields/dac80508_evm/dac80508_evm.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 93 |
```restructuredtext
.. _dac80508_evm_shield:
DAC80508 Evaluation Module
####################################
Overview
********
The Texas Instruments DAC80508 Evaluation Module (EVM) is a
DAC development module for the TI DAC80508 series.
.. figure:: dac80508evm-board-photo.jpg
:align: center
:alt: DAC80508 EVM
Requirements
************
This shield can only be used with a development board that provides a
configuration for Arduino connectors and defines a node alias for the
SPI interface (see :ref:`shields` for more details).
The SPI connector pins on the DAC80508 EVM can be connected to the
Arduino headers of the development board using jumper wires.
In addition, 5V must be connected to the DAC80508 EVM's TP6(VDD).
.. figure:: dac80508evm_connected.jpg
:align: center
:alt: DAC80508 EVM + STM32F746G_DISCO
For more information about interfacing the DAC80508 series and the
DACx0508 EVM in particular, see these TI documents:
- `DACx0508 Evaluation Module User's Guide`_
- `DAC80508 True 16-bit, 8-channel, SPI`_
.. _DACx0508 Evaluation Module User's Guide:
path_to_url
.. _DAC80508 True 16-bit, 8-channel, SPI:
path_to_url
``` | /content/code_sandbox/boards/shields/dac80508_evm/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 302 |
```restructuredtext
.. _semtech_sx1262mb2das:
Semtech SX1262MB2DAS LoRa Shield
################################
Overview
********
The Semtech SX1262MB2DAS LoRa shield is an Arduino
compatible shield based on the SX1262 LoRa transceiver
from Semtech.
More information about the shield can be found
at the `mbed SX1262MB2xAS website`_.
Pins Assignment of the Semtech SX1262MB2DAS LoRa Shield
=======================================================
+-----------------------+-----------------+
| Shield Connector Pin | Function |
+=======================+=================+
| A0 | SX1262 RESET |
+-----------------------+-----------------+
| D3 | SX1262 BUSY |
+-----------------------+-----------------+
| D5 | SX1262 DIO1 |
+-----------------------+-----------------+
| D7 | SX1262 SPI NSS |
+-----------------------+-----------------+
| D8 | SX1262 ANT SW |
+-----------------------+-----------------+
| D11 | SX1262 SPI MOSI |
+-----------------------+-----------------+
| D12 | SX1262 SPI MISO |
+-----------------------+-----------------+
| D13 | SX1262 SPI SCK |
+-----------------------+-----------------+
The SX1262 signals DIO2 and DIO3 are not available at the shield connector.
Requirements
************
This shield can only be used with a board which provides a configuration
for Arduino connectors (see :ref:`shields` for more details).
Programming
***********
Set ``--shield semtech_sx1262mb2das`` when you invoke ``west build``. For
example:
.. zephyr-app-commands::
:zephyr-app: samples/subsys/lorawan/class_a
:board: nucleo_f429zi
:shield: semtech_sx1262mb2das
:goals: build
References
**********
.. target-notes::
.. _mbed SX1262MB2xAS website:
path_to_url
``` | /content/code_sandbox/boards/shields/semtech_sx1262mb2das/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 451 |
```unknown
config SHIELD_X_NUCLEO_WB05KN1_UART
def_bool $(shields_list_contains,x_nucleo_wb05kn1_uart)
config SHIELD_X_NUCLEO_WB05KN1_SPI
def_bool $(shields_list_contains,x_nucleo_wb05kn1_spi)
``` | /content/code_sandbox/boards/shields/x_nucleo_wb05kn1/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 68 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,bt-hci = &bt_hci_uart;
};
};
&arduino_serial {
current-speed = <921600>;
bt_hci_uart: bt_hci_uart {
compatible = "zephyr,bt-hci-uart";
status = "okay";
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_wb05kn1/x_nucleo_wb05kn1_uart.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 72 |
```unknown
if SHIELD_X_NUCLEO_WB05KN1_UART || SHIELD_X_NUCLEO_WB05KN1_SPI
if BT
config SPI
default y
depends on SHIELD_X_NUCLEO_WB05KN1_SPI
config SPI_STM32_INTERRUPT
default y
depends on SPI
config BT_SPI
default y
depends on DT_HAS_ST_HCI_SPI_V2_ENABLED
config BT_H4
default y
depends on DT_HAS_ZEPHYR_BT_HCI_UART_ENABLED
config BT_BLUENRG_ACI
default y
# Disable Flow control
config BT_HCI_ACL_FLOW_CONTROL
default n
endif # BT
endif # SHIELD_X_NUCLEO_WB05KN1_UART || SHIELD_X_NUCLEO_WB05KN1_SPI
``` | /content/code_sandbox/boards/shields/x_nucleo_wb05kn1/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 177 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,bt-hci = &hci_spi;
};
};
&arduino_spi {
cs-gpios = <&arduino_header 16 GPIO_ACTIVE_LOW>; /* D10 */
hci_spi: wb05n@0 {
compatible = "st,hci-spi-v2";
reg = <0>;
reset-gpios = <&arduino_header 13 GPIO_ACTIVE_LOW>; /* D7 */
irq-gpios = <&arduino_header 0 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>; /* A0 */
spi-cpol; /* CPOL=1 */
spi-cpha; /* CPHA=1 */
spi-hold-cs;
spi-max-frequency = <DT_FREQ_M(8)>; /* the maximum supported SPI speed */
reset-assert-duration-ms = <6>;
status = "okay";
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_wb05kn1/x_nucleo_wb05kn1_spi.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 195 |
```unknown
/*
*
*/
&spi1_sck_pa5 {
/delete-property/ bias-pull-down;
bias-pull-up;
};
&spi1_miso_pa6 {
slew-rate = "high-speed";
};
&spi1_mosi_pa7 {
slew-rate = "high-speed";
};
&arduino_spi {
pinctrl-0 = <&spi1_sck_pa5 &spi1_miso_pa6 &spi1_mosi_pa7>;
};
/ {
chosen {
zephyr,bt-c2h-uart = &usart1;
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_wb05kn1/boards/nucleo_u575zi_q.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 121 |
```unknown
/*
*
*/
&spi1_sck_pa5 {
/delete-property/ bias-pull-down;
bias-pull-up;
};
&spi1_miso_pg9 {
slew-rate = "high-speed";
};
&spi1_mosi_pb5 {
slew-rate = "high-speed";
};
/ {
chosen {
zephyr,bt-c2h-uart = &usart3;
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_wb05kn1/boards/nucleo_h563zi.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 87 |
```unknown
config SHIELD_MIKROE_ETH_CLICK
def_bool $(shields_list_contains,mikroe_eth_click)
``` | /content/code_sandbox/boards/shields/mikroe_eth_click/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 25 |
```unknown
*/
&mikrobus_spi {
status = "okay";
eth_click_mikroe_eth_click: eth_click@0 {
compatible = "microchip,enc28j60";
reg = <0x0>;
full-duplex;
local-mac-address = [00 00 00 01 02 03];
/* Errata B7/1 specifies min 8Mhz, 20MHz max according to RM */
spi-max-frequency = <10000000>;
int-gpios = <&mikrobus_header 7 GPIO_ACTIVE_LOW>; /* INT */
};
};
``` | /content/code_sandbox/boards/shields/mikroe_eth_click/mikroe_eth_click.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 133 |
```unknown
if SHIELD_MIKROE_ETH_CLICK
if NETWORKING
# ENC28J60 is L2 chip slave on SPI
config NET_L2_ETHERNET
default y
endif # NETWORKING
endif # SHIELD_MIKROE_ETH_CLICK
``` | /content/code_sandbox/boards/shields/mikroe_eth_click/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 56 |
```restructuredtext
.. _x-nucleo-wb05kn1:
X-NUCLEO-WB05KN1: BLE expansion board
#####################################
Overview
********
The X-NUCLEO-WB05KN1 is a Bluetooth Low Energy evaluation board which allows the
expansion of the STM32 Nucleo boards.
The RF module is FCC (FCC ID: YCP-MB203202) and IC certified (IC: 8976A-MB203202).
The X-NUCLEO-WB05KN1 is compatible out of the box with the Arduino UNO R3 connector.
The board interfaces with the host microcontroller via UART (default) or SPI peripheral.
.. image:: img/x-nucleo-wb05kn1.webp
:align: center
:alt: X-NUCLEO-WB05KN1
More information about the board can be found at the
`X-NUCLEO-WB05KN1 website`_.
Configurations
**************
X-NUCLEO-WB05KN1 can be utilized as a Bluetooth Low-Energy controller shield
with a UART or SPI host controller interface (HCI-UART/HCI-SPI).
The UART default settings are:
* Baudrate: 921600 bps
* 8 bits, no parity, 1 stop bit
+----------+-----------------------+
| UART Pin | Arduino Connector Pin |
+==========+=======================+
| RX | D0 |
+----------+-----------------------+
| TX | D1 |
+----------+-----------------------+
.. note::
Please, bear in mind in order to use SPI interface you need to change the shield firmware
to ``DTM_SPI_WITH_UPDATER_CONTROLLER`` according to the SDK provided by ST at `X-CUBE-WB05N`_.
IRQ and reset pins are also necessary in addition to SPI pins.
+----------------+-----------------------+
| SPI Config Pin | Arduino Connector Pin |
+================+=======================+
| SCK | D13 |
+----------------+-----------------------+
| MISO | D12 |
+----------------+-----------------------+
| MOSI | D11 |
+----------------+-----------------------+
| CS | D10 |
+----------------+-----------------------+
| IRQ | A0 |
+----------------+-----------------------+
| RESET | D7 |
+----------------+-----------------------+
More information about X-NUCLEO-WB05KN1 can be found here:
- `X-NUCLEO-WB05KN1 datasheet`_
Programming
***********
Activate the presence of the shield for the project build by adding the
``--shield x_nucleo_wb05kn1_uart`` or ``--shield x_nucleo_wb05kn1_spi`` when you invoke
``west build`` based on UART or SPI interface:
.. zephyr-app-commands::
:zephyr-app: your_app
:board: your_board_name
:shield: x_nucleo_wb05kn1_uart
:goals: build
or
.. zephyr-app-commands::
:zephyr-app: your_app
:board: your_board_name
:shield: x_nucleo_wb05kn1_spi
:goals: build
References
**********
.. target-notes::
.. _X-NUCLEO-WB05KN1 website:
path_to_url
.. _X-CUBE-WB05N:
path_to_url
.. _X-NUCLEO-WB05KN1 datasheet:
path_to_url
``` | /content/code_sandbox/boards/shields/x_nucleo_wb05kn1/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 758 |
```unknown
/*
*
*/
/delete-node/ ð_click;
&mikrobus_spi {
status = "okay";
cs-gpios = <&gpio0 20 GPIO_ACTIVE_LOW>,
<&gpio1 1 GPIO_ACTIVE_LOW>,
<&gpio1 12 GPIO_ACTIVE_LOW>,
<&gpio1 26 GPIO_ACTIVE_LOW>;
/* LPCXpresso55xxx boards all use SSEL1. */
eth_click_mikroe_eth_click: eth_click@1 {
compatible = "microchip,enc28j60";
reg = <0x1>;
full-duplex;
local-mac-address = [00 00 00 01 02 03];
/* Errata B7/1 specifies min 8Mhz, 20MHz max according to RM */
spi-max-frequency = <10000000>;
int-gpios = <&mikrobus_header 7 GPIO_ACTIVE_LOW>; /* INT */
};
};
``` | /content/code_sandbox/boards/shields/mikroe_eth_click/boards/lpcxpresso55s69_lpc55s69_cpu0.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 204 |
```unknown
config SHIELD_X_NUCLEO_BNRG2A1
def_bool $(shields_list_contains,x_nucleo_bnrg2a1)
``` | /content/code_sandbox/boards/shields/x_nucleo_bnrg2a1/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 34 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,bt-hci = &hci_spi;
};
};
&arduino_spi {
cs-gpios = <&arduino_header 1 GPIO_ACTIVE_LOW>; /* A1 */
hci_spi: bluenrg-2@0 {
compatible = "st,hci-spi-v2";
reg = <0>;
reset-gpios = <&arduino_header 13 GPIO_ACTIVE_LOW>; /* D7 */
irq-gpios = <&arduino_header 0 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>; /* A0 */
spi-cpha; /* CPHA=1 */
spi-hold-cs;
spi-max-frequency = <DT_FREQ_M(1)>;
reset-assert-duration-ms = <6>;
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_bnrg2a1/x_nucleo_bnrg2a1.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 173 |
```restructuredtext
.. _mikroe_eth_click:
MikroElektronika ETH Click
##########################
Overview
********
ETH Click is an accessory board in mikroBus form factor. It features `ENC28J60`_,
a 28-pin, 10BASE-T stand alone Ethernet Controller with an on-board MAC & PHY,
8K Bytes of Buffer RAM and SPI serial interface.
More information at `Eth Click Shield website`_.
Pins Assignment of the Eth Click Shield
=======================================
+-----------------------+---------------------------------------------+
| Shield Connector Pin | Function |
+=======================+=============================================+
| RST# | Ethernet Controller's Reset |
+-----------------------+---------------------------------------------+
| CS# | SPI's Chip Select |
+-----------------------+---------------------------------------------+
| SCK | SPI's ClocK |
+-----------------------+---------------------------------------------+
| SDO | SPI's Slave Data Output (MISO) |
+-----------------------+---------------------------------------------+
| SDI | SPI's Slave Data Input (MISO) |
+-----------------------+---------------------------------------------+
| INT | Ethernet Controller's Interrupt Output |
+-----------------------+---------------------------------------------+
Requirements
************
This shield can only be used with a board which provides a configuration
for Mikro-BUS connectors and defines node aliases for SPI and GPIO interfaces
(see :ref:`shields` for more details).
Programming
***********
Set ``--shield mikroe_eth_click`` when you invoke ``west build``. For example:
.. zephyr-app-commands::
:zephyr-app: samples/net/dhcpv4_client
:board: lpcxpresso55s69
:shield: mikroe_eth_click
:goals: build
References
**********
.. target-notes::
.. _Eth Click Shield website:
path_to_url
.. _ENC28J60:
path_to_url
``` | /content/code_sandbox/boards/shields/mikroe_eth_click/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 400 |
```unknown
if SHIELD_X_NUCLEO_BNRG2A1
if BT
config SPI
default y
config BT_SPI
default y
config BT_BLUENRG_ACI
default y
# Disable Flow control
config BT_HCI_ACL_FLOW_CONTROL
default n
endif # BT
endif # SHIELD_X_NUCLEO_BNRG2A1
``` | /content/code_sandbox/boards/shields/x_nucleo_bnrg2a1/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 81 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,bt-c2h-uart = &usart2;
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_bnrg2a1/boards/nucleo_l476rg.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 29 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,bt-hci = &bt_hci_uart;
};
};
&mikrobus_serial {
status = "okay";
bt_hci_uart: bt_hci_uart {
compatible = "zephyr,bt-hci-uart";
};
};
``` | /content/code_sandbox/boards/shields/mikroe_ble_tiny_click/mikroe_ble_tiny_click.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 66 |
```unknown
config SHIELD_MIKROE_BLE_TINY_CLICK
def_bool $(shields_list_contains,mikroe_ble_tiny_click)
``` | /content/code_sandbox/boards/shields/mikroe_ble_tiny_click/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 29 |
```unknown
CONFIG_BT_HCI=y
CONFIG_BT_HCI_ACL_FLOW_CONTROL=n
CONFIG_BT_CTLR=n
``` | /content/code_sandbox/boards/shields/mikroe_ble_tiny_click/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 23 |
```restructuredtext
.. _x_nucleo_bnrg2a1:
X-NUCLEO-BNRG2A1: BLE expansion board
#####################################
Overview
********
The X-NUCLEO-BNRG2A1 is a Bluetooth Low Energy evaluation board based on the
BlueNRG-M2SP RF module to allow expansion of the STM32 Nucleo boards.
The BlueNRG-M2SP module is FCC (FCC ID: S9NBNRGM2SP) and IC certified
(IC: 8976C-BNRGM2SP).
The X-NUCLEO-BNRG2A1 is compatible with the ST Morpho and Arduino UNO R3
connector layout (the user can mount the ST Morpho connectors, if required). The
X-NUCLEO-BNRG2A1 interfaces with the host microcontroller via the SPI pins, and
the user can change the default SPI clock, the SPI chip select and SPI IRQ by
changing either one resistor or jumper on the evaluation board.
Note : This shield is compatible out of the box with Arduino UNO R3 connectors,
but CS signal is not the standard Arduino SPI_CS signal.
Please refer to "Hardware configuration" section.
.. image:: img/x-nucleo-bnrg2a1.webp
:align: center
:alt: X-NUCLEO-BNRG2A1
More information about the board can be found at the
`X-NUCLEO-BNRG2A1 website`_.
Hardware configuration
**********************
Out of the box, X-NUCLEO-BNRG2A1 shield expects SPI CS to be available on
Arduino pin A1 instead of usual Arduino UNO R3 SPI CS D10.
This is not a problem as CS signal is software driven gpio on Arduino A1
see cs-gpios in x_nucleo_bnrg2a1.overlay
Shield configuration could be modified by moving resistors or changing jumper as
follows:
- SPI SCK: to use D3 instead of D13, short J14 pins 2 and 3
Additionally, depending on your host board, some modifications of the BLE
expansion board could be made:
- CS: To use D1 instead of A1, unmount R76 and mount R86
nucleo_l476rg does not need hardware modifications.
Hardware
********
X-NUCLEO-BNRG2A1 provides a BlueNRG-M2SP chip with the following key features:
- Bluetooth v5.2 compliant
- Embedded BALF-NRG-02D3 integrated matched balun with harmonic filter
- BLE data packet length extension
More information about X-NUCLEO-BNRG2A1 can be found here:
- `X-NUCLEO-BNRG2A1 databrief`_
Programming
***********
You can use the X-NUCLEO-BNRG2A1 as a Bluetooth Low-Energy controller
shield with an SPI host controller interface (HCI-SPI). Activate the presence
of the shield for the project build by adding the ``--shield`` arg to the
build command:
.. zephyr-app-commands::
:zephyr-app: your_app
:board: your_board_name
:shield: x_nucleo_bnrg2a1
:goals: build
Alternatively, set use of this shield in the project's ``CMakeLists.txt`` file:
.. code-block:: cmake
set(SHIELD x_nucleo_bnrg2a1)
References
**********
.. target-notes::
.. _X-NUCLEO-BNRG2A1 website:
path_to_url
.. _X-NUCLEO-BNRG2A1 databrief:
path_to_url
``` | /content/code_sandbox/boards/shields/x_nucleo_bnrg2a1/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 795 |
```unknown
config SHIELD_LINK_BOARD_ETH
def_bool $(shields_list_contains,link_board_eth)
``` | /content/code_sandbox/boards/shields/link_board_eth/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 21 |
```restructuredtext
.. _mikroe_ble_tiny_click_shield:
MikroElektronika BLE TINY Click
###############################
Overview
********
The MikroElektronika BLE TINY Click carries the Renesas `DA14531MOD`_ Bluetooth
LE module in a `mikroBUS`_ |trade| form factor.
.. figure:: ble-tiny-click.webp
:align: center
:alt: MikroElektronika BLE TINY Click
MikroElektronika BLE TINY Click (Credit: MikroElektronika)
Requirements
************
This shield can only be used with a board that provides a mikroBUS |trade|
socket and defines the ``mikrobus_serial`` node label (see :ref:`shields`
for more details).
.. note::
The reset input on the DA14531 Module is active high and is connected to
the RST pin on the mikroBUS socket. On many host boards this RST pin is
connected to a system reset signal that is active low. This results in the
host system unintentionally holding the DA14531 Module in reset. This issue
can be overcome by removing resistor R3 on the BLE TINY Click board, see
the `BLE TINY Click Schematic`_ for further details.
The DA14531 Module contained on the shield must be programmed with a binary
file that supports the HCI interface over UART, without hardware flow control
as these signals are not supported on the Click footprint.
The `Renesas SmartBond Flash Programmer`_ tool can be used to download a
suitable binary and then program it into the DA14531 via the SWD header
present on the Click board. Once the tool has been installed, open it and
press the "Search Online" button. The required binary file can be selected
for download as follows:
.. figure:: da14531-hci-binary.webp
:align: center
:alt: DA14531 HCI Binary File Selection
Selecting the DA14531 HCI Binary File for Download
Press the "Program" button to program the binary file into the DA14531 Module.
For more information about interfacing to the DA14531 and the BLE TINY Click,
see the following documentation:
- `DA14531MOD Datasheet`_
- `BLE TINY Click`_
Programming
***********
Set ``--shield mikroe_ble_tiny_click`` when you invoke ``west build``. For
example:
.. zephyr-app-commands::
:zephyr-app: samples/bluetooth/beacon
:board: ek-ra8m1
:shield: mikroe_ble_tiny_click
:goals: build
References
**********
.. target-notes::
.. _DA14531MOD:
path_to_url
.. _mikroBUS:
path_to_url
.. _DA14531MOD Datasheet:
path_to_url
.. _BLE TINY Click:
path_to_url
.. _BLE TINY Click Schematic:
path_to_url
.. _Renesas SmartBond Flash Programmer:
path_to_url
``` | /content/code_sandbox/boards/shields/mikroe_ble_tiny_click/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 665 |
```unknown
/*
*
*/
&arduino_spi {
status = "okay";
cs-gpios = <&arduino_header 16 GPIO_ACTIVE_LOW>; /* D10 */
enc424j600_link_board_eth: enc424j600@0 {
compatible = "microchip,enc424j600";
spi-max-frequency = <14000000>;
int-gpios = <&arduino_header 15 GPIO_ACTIVE_LOW>; /* D9 */
status = "okay";
reg = <0>;
};
};
``` | /content/code_sandbox/boards/shields/link_board_eth/link_board_eth.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 107 |
```unknown
if SHIELD_LINK_BOARD_ETH
if NETWORKING
config NET_L2_ETHERNET
default y
endif # NETWORKING
endif # SHIELD_LINK_BOARD_ETH
``` | /content/code_sandbox/boards/shields/link_board_eth/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 37 |
```unknown
config SHIELD_NPM6001_EK
def_bool $(shields_list_contains,npm6001_ek)
``` | /content/code_sandbox/boards/shields/npm6001_ek/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 26 |
```unknown
/*
*/
&arduino_i2c {
npm6001_ek_pmic: pmic@70 {
compatible = "nordic,npm6001";
reg = <0x70>;
npm6001_ek_gpio: gpio-controller {
compatible = "nordic,npm6001-gpio";
gpio-controller;
#gpio-cells = <2>;
ngpios = <3>;
};
npm6001_ek_wdt: watchdog {
compatible = "nordic,npm6001-wdt";
};
regulators {
compatible = "nordic,npm6001-regulator";
/* limits are set to min/max allowed values */
npm6001_ek_buck0: BUCK0 {
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <3300000>;
};
npm6001_ek_buck1: BUCK1 {
regulator-min-microvolt = <700000>;
regulator-max-microvolt = <1400000>;
};
npm6001_ek_buck2: BUCK2 {
regulator-min-microvolt = <1200000>;
regulator-max-microvolt = <1400000>;
};
npm6001_ek_buck3: BUCK3 {
regulator-min-microvolt = <500000>;
regulator-max-microvolt = <3300000>;
};
npm6001_ek_ldo0: LDO0 {
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <3300000>;
};
npm6001_ek_ldo1: LDO1 {
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <1800000>;
};
};
};
};
``` | /content/code_sandbox/boards/shields/npm6001_ek/npm6001_ek.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 425 |
```restructuredtext
.. _npm6001_ek:
nPM6001 EK
##########
Overview
********
The nPM6001 EK lets you test different functions and features of the nPM6001
Power Management Integrated Circuit (PMIC).
.. figure:: npm6001_ek.jpg
:alt: nPM6001 EK
:align: center
nPM6001 EK
Requirements
************
The nPM6001 EK board is not designed to fit straight into an Arduino connector.
However, the Zephyr shield is designed expecting it to be connected to the
Arduino shield connectors. For example, the I2C lines need to be connected to
the ``arduino_i2c`` bus. This allows to use the shield with any host board that
supports the Arduino connector.
Usage
*****
The shield can be used in any application by setting ``--shield npm6001_ek``
when invoking ``west build``. You can check :ref:`npm6001_ek_sample` for a
comprehensive sample.
References
**********
- `nPM6001 EK Manual <path_to_url`_
``` | /content/code_sandbox/boards/shields/npm6001_ek/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 232 |
```unknown
/*
*
*/
/ {
aliases {
accel0 = &lsm6dso16is_6a_x_nucleo_iks4a1_shub;
};
};
&arduino_i2c {
lsm6dso16is_6a_x_nucleo_iks4a1_shub: lsm6dso16is@6a {
compatible = "st,lsm6dso16is";
reg = <0x6a>;
irq-gpios = <&arduino_header 5 GPIO_ACTIVE_HIGH>; /* A5 */
drdy-pin = <1>;
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_iks4a1/x_nucleo_iks4a1_shub2.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 135 |
```restructuredtext
.. _link_board_eth_shield:
PHYTEC link board ETH
#####################
Overview
********
The link board ETH is an ethernet expansion board based on ENC424J600
ethernet controller and compatible with the Arduino UNO R3 connector.
It was developed as an expansion component for the reel board.
See :ref:`reel_board` documentation for more information about
link board family and how to connect it to the reel board.
.. image:: img/link_board_eth.jpg
:align: center
:alt: link board ETH
Hardware
********
- ENC424J600
- 10/100 Base-T/TX Ethernet Controller with SPI Interface
- Factory Pre-programmed Unique MAC Address
- Connectivity
- Arduino compatible
- RJ45 Connector
- Electrical Characteristics
- Supply Voltage 3.3 V
- Supply Current 75 mA ... 147 mA
Pins Assignment of the Shield Connector
=======================================
ENC424J600 device offers a choice between an SPI based interface and
parallel slave port (PSP) interface. SPI interface is automatically selected
during startup and it requires no intervention from the MCU side.
+-----------------------+-----------------------+-----------------------------+
| Shield Connector Pin | Function | ENC424J600 Pin |
+=======================+=======================+=============================+
| D0 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D1 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D2 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D3 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D4 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D5 | alternative INTn | |
+-----------------------+-----------------------+-----------------------------+
| D6 | not populated | |
+-----------------------+-----------------------+-----------------------------+
| D7 | not populated | |
+-----------------------+-----------------------+-----------------------------+
| D8 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D9 | INTn | 24 (Interrupt Output) |
+-----------------------+-----------------------+-----------------------------+
| D10 | SPI CSn | 34 (SPI Chip Select) |
+-----------------------+-----------------------+-----------------------------+
| D11 | SPI MOSI | 36 (SPI Serial Data Input) |
+-----------------------+-----------------------+-----------------------------+
| D12 | SPI MISO | 35 (SPI Serial Data Out) |
+-----------------------+-----------------------+-----------------------------+
| D13 | SPI SCK | 37 (SPI Serial Clock Input) |
+-----------------------+-----------------------+-----------------------------+
| D14 | not populated | |
+-----------------------+-----------------------+-----------------------------+
| D15 | not populated | |
+-----------------------+-----------------------+-----------------------------+
+-----------------------+-----------------------+-----------------------------+
| Shield Connector Pin | Function | ENC424J600 Pin |
+=======================+=======================+=============================+
| A0 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| A1 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| A2 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| A3 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| A4 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| A5 | not connected | |
+-----------------------+-----------------------+-----------------------------+
For more information about the link board ETH and ENC424J600:
- `link board ETH Website`_
- `ENC424J600 Website`_
Programming
***********
Set ``--shield link_board_eth`` when you invoke ``west build`` or ``cmake`` in your
Zephyr application. For example:
.. zephyr-app-commands::
:zephyr-app: samples/net/zperf
:tool: all
:board: reel_board
:shield: link_board_eth
:goals: build
.. _link board ETH Website:
path_to_url
.. _ENC424J600 Website:
path_to_url
``` | /content/code_sandbox/boards/shields/link_board_eth/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 957 |
```unknown
/*
*
*/
/ {
aliases {
accel0 = &lsm6dsv16x_6b_x_nucleo_iks4a1;
};
};
&arduino_i2c {
lsm6dsv16x_6b_x_nucleo_iks4a1: lsm6dsv16x@6b {
compatible = "st,lsm6dsv16x";
reg = <0x6b>;
accel-odr = <0x02>;
gyro-odr = <0x02>;
int1-gpios = <&arduino_header 11 GPIO_ACTIVE_HIGH>; /* D5 */
drdy-pin = <1>;
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_iks4a1/x_nucleo_iks4a1_shub1.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 155 |
```unknown
config SHIELD_X_NUCLEO_IKS01A4
def_bool $(shields_list_contains,x_nucleo_iks4a1)
``` | /content/code_sandbox/boards/shields/x_nucleo_iks4a1/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 33 |
```unknown
/*
*
*/
/ {
aliases {
magn0 = &lis2mdl_1e_x_nucleo_iks4a1;
accel0 = &lsm6dso16is_6a_x_nucleo_iks4a1;
accel1 = &lsm6dsv16x_6b_x_nucleo_iks4a1;
press0 = &lps22df_5d_x_nucleo_iks4a1;
};
};
&arduino_i2c {
lsm6dso16is_6a_x_nucleo_iks4a1: lsm6dso16is@6a {
compatible = "st,lsm6dso16is";
reg = <0x6a>;
accel-odr = <0x1b>;
gyro-odr = <0x11>;
irq-gpios = <&arduino_header 5 GPIO_ACTIVE_HIGH>; /* A5 (PC0) */
drdy-pin = <1>;
};
lsm6dsv16x_6b_x_nucleo_iks4a1: lsm6dsv16x@6b {
compatible = "st,lsm6dsv16x";
reg = <0x6b>;
accel-odr = <0x02>;
gyro-odr = <0x02>;
int2-gpios = <&arduino_header 10 GPIO_ACTIVE_HIGH>; /* D4 (PB5) */
drdy-pin = <2>;
drdy-pulsed;
};
lis2mdl_1e_x_nucleo_iks4a1: lis2mdl@1e {
compatible = "st,lis2mdl";
reg = <0x1e>;
irq-gpios = <&arduino_header 2 GPIO_ACTIVE_HIGH>; /* A2 (PA4) */
};
lps22df_5d_x_nucleo_iks4a1: lps22df@5d {
compatible = "st,lps22df";
reg = <0x5d>;
drdy-pulsed;
drdy-gpios = <&arduino_header 12 GPIO_ACTIVE_HIGH>; /* D6 (PB10) */
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_iks4a1/x_nucleo_iks4a1.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 505 |
```unknown
/*
*
*/
/ {
aliases {
accel0 = &iis2dlpc_mikroe_accel13_click;
};
};
&mikrobus_i2c {
status = "okay";
iis2dlpc_mikroe_accel13_click: iis2dlpc@18 {
compatible = "st,iis2dlpc";
reg = <0x18>;
drdy-gpios = <&mikrobus_header 7 GPIO_ACTIVE_HIGH>;
drdy-int = <2>;
status = "okay";
};
};
``` | /content/code_sandbox/boards/shields/mikroe_accel13_click/mikroe_accel13_click.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 123 |
```unknown
config SHIELD_MIKROE_ACCEL13_CLICK
def_bool $(shields_list_contains,mikroe_accel13_click)
``` | /content/code_sandbox/boards/shields/mikroe_accel13_click/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 28 |
```restructuredtext
.. _mikroe_accel13_click_shield:
MikroElektronika ACCEL 13 Click
###############################
Overview
********
The MikroElektronika ACCEL 13 Click carries the `IIS2DLPC`_ ultra-low
power triaxial accelerometer sensor in a `mikroBUS`_ |trade| form factor.
The `IIS2DLPC`_ sensor supports both SPI and I2C bus protocols. Currently
only I2C is supported for this shield.
.. figure:: accel-13-click.jpg
:align: center
:alt: MikroElektronika ACCEL 13 Click
MikroElektronika ACCEL 13 Click (Credit: MikroElektronika)
Requirements
************
This shield can only be used with a development board that provides a
configuration for mikroBUS connectors and defines a node alias for the mikroBUS
I2C interface (see :ref:`shields` for more details).
For more information about interfacing the IIS2DLPC and the ACCEL 13 Click,
see the following documentation:
- `IIS2DLPC Datasheet`_
- `ACCEL 13 Click`_
Programming
***********
Set ``--shield mikro_accel13_click`` when you invoke ``west build``. For
example:
.. zephyr-app-commands::
:zephyr-app: test/boards/board_shell
:board: lpcxpresso55s69
:shield: mikroe_accel13_click
:goals: build
.. _IIS2DLPC:
path_to_url
.. _mikroBUS:
path_to_url
.. _IIS2DLPC Datasheet:
path_to_url
.. _ACCEL 13 Click:
path_to_url
``` | /content/code_sandbox/boards/shields/mikroe_accel13_click/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 388 |
```unknown
config SHIELD_FRDM_KW41Z
def_bool $(shields_list_contains,frdm_kw41z)
``` | /content/code_sandbox/boards/shields/frdm_kw41z/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 26 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,bt-hci = &bt_hci_uart;
};
};
&arduino_serial {
status = "okay";
current-speed = <115200>;
bt_hci_uart: bt_hci_uart {
compatible = "zephyr,bt-hci-uart";
status = "okay";
};
};
``` | /content/code_sandbox/boards/shields/frdm_kw41z/frdm_kw41z.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 77 |
```restructuredtext
.. _x-nucleo-iks4a1:
X-NUCLEO-IKS4A1: MEMS Inertial and Environmental Multi sensor shield
####################################################################
Overview
********
The X-NUCLEO-IKS4A1 is a motion MEMS and environmental sensor expansion board
for the STM32 Nucleo. It is equipped with Arduino UNO R3 connector layout, and
allows application development with features like sensor HUB (LSM6DSO16IS and
LSM6DSV16X), camera module integration and Qvar touch/swipe gestures (thanks to
the equipped electrode).
.. image:: img/x-nucleo-iks4a1.jpg
:align: center
:alt: X-NUCLEO-IKS4A1
More general information about the board can be found at the
`X-NUCLEO-IKS4A1 website`_.
Hardware Description
********************
X-NUCLEO-IKS4A1 provides the following key features:
- LSM6DSO16IS: MEMS 3D accelerometer (2/4/8/16 g) + 3D gyroscope
(125/250/500/1000/2000 dps) with ISPU (Intelligent Processing Unit)
- LIS2MDL: MEMS 3D magnetometer (50 gauss)
- LIS2DUXS12: Ultra low-power MEMS 3D accelerometer (2/4/8/16 g) with
Qvar, AI, & anti-aliasing
- LPS22DF: Low-power and high-precision MEMS pressure sensor, 260-1260 hPa
absolute digital output barometer
- SHT40AD1B: High-accuracy, ultra-low-power relative humidity and temperature
sensor (by Sensirion)
- STTS22H: Low-voltage, ultralow-power, 0.5 C accuracy temperature sensor
(40 C to +125 C)
- LSM6DSV16X: MEMS 3D accelerometer (2/4/8/16 g) + 3D gyroscope
(125/250/500/1000/2000/4000 dps) with embedded sensor fusion, AI, Qvar
- DIL 24-pin socket available for additional MEMS adapters and other sensors
- Free comprehensive development firmware library and example for all sensors
compatible with STM32Cube firmware
- Equipped with Qvar touch/swipe electrode
- IC sensor hub features on LSM6DSO and LSM6DSV16X available
- MIPI I3C compatibility for communication with LIS2DUXS12, LSM6DSV16X and
LPS22DF
- Compatible with STM32 Nucleo boards
- Equipped with Arduino UNO R3 connector
- Equipped with industrial connector for IR sensor (STHS34PF80) application
development. It can be connected at the same time of external MEMS through
DIL24 adapter
- Available interface for external camera module applications coupled with
LSM6DSV16X through aux SPI (3/4 w)
- RoHS compliant
- WEEE compliant
- UKCA compliant
Hardware Configuration
**********************
X-NUCLEO-IKS4A1 board can be configured in five different modes, which can be
selected through J4 and J5 jumpers. Additional information about X-NUCLEO-IKS4A1
configuration modes and how sensors are connected together can be found in the
`X-NUCLEO-IKS4A1 user manual`_
.. _x-nucleo-iks4a1-mode-1:
Mode 1: Standard Mode
=====================
In standard I2C mode, all devices are connected to an external main board via the
same I2C bus.
The board configuration is:
- J4: 1-2, 11-12 (STM_SDA = SENS_SDA, HUB_SDx = GND)
- J5: 1-2, 11-12 (STM_SCL = SENS_SCL, HUB_SCx = GND)
.. _x-nucleo-iks4a1-mode-2:
Mode 2: LSM6DSO16IS SensorHub Mode (SHUB2)
==========================================
In this sensor hub I2C mode, it is possible to power-up the 6-axes IMU
(Inertial Measurement Unit) functionalities by collecting external data
through a direct control of the on-board environmental sensors (temperature,
pressure and magnetometer) and external sensor (DIL24) through the auxiliary
I2Cz bus "SENS_I2C". LSM6DSV16X, LIS2DUXS12 and SHT40AD1B remains connected
to the main bus "uC_I2C" coming from the external board.
The board configuration is:
- J4: 7-8 (HUB2_SDx = SENS_SDA)
- J5: 7-8 (HUB2_SCx = SENS_SCL)
.. _x-nucleo-iks4a1-mode-3:
Mode 3: LSM6DSV16X SensorHub Mode (SHUB1)
=========================================
In this sensor hub, it is possible to power-up the 6-axes IMU (Inertial
Measurement Unit) functionalities by collecting external data through
a direct control of the on-board environmental sensors (temperature,
pressure and magnetometer) and external sensor (DIL24) through the auxiliary
I2C bus "SENS_I2C". LSM6DSO16IS, LIS2DUXS12 and SHT40AD1B remains connected
to the main bus "uC_I2C" coming from the external board.
The board configuration is:
- J4: 5-6 (HUB1_SDx = SENS_SDA)
- J5: 5-6 (HUB1_SDx = SENS_SDA)
Mode 4: DIL24 SensorHub Mode
============================
In case a sensor with sensor hub embedded functionality is mounted to the
board through DIL24 adapter, it is possible to exploit this functionality
as for LSM6DSO16IS and the LSM6DSV16X. In this configuration, may be necessary
to connect the DIL24 to the external board through SPI lines in order to
avoid an address conflict on I2C bus with the LSM6DSO16IS and the LSM6DSV16X.
This is done by changing the SBx configuration.
The board configuration is:
- J4: 9-10 (DIL_SDx = SENS_SDA)
- J5: 9-10 (DIL_SDx = SENS_SDA)
Mode 5: LSM6DSO16IS as Qvar controller
======================================
In this configuration, it is possible to use the equipped Qvar swipe electrode
(by plugging it on JP6 and JP7 connectors) through the LSM6DSO16IS.
The board configuration is:
- J4: 3-4 (HUB1_SDx = QVAR1)
- J5: 3-4 (HUB1_Scx = QVAR2)
Devicetree Overlays
*******************
There are three predefined DT overlays in the board:
- :zephyr_file:`boards/shields/x_nucleo_iks4a1/x_nucleo_iks4a1.overlay`
This overlay describes sensor connections (and matching h/w configuration to be done)
as explained in Standard Mode (:ref:`x-nucleo-iks4a1-mode-1`)
- :zephyr_file:`boards/shields/x_nucleo_iks4a1/x_nucleo_iks4a1_shub1.overlay`
This overlay describes sensor connections (and matching h/w configuration to be done)
as explained in SHUB1 Mode (:ref:`x-nucleo-iks4a1-mode-3`)
- :zephyr_file:`boards/shields/x_nucleo_iks4a1/x_nucleo_iks4a1_shub2.overlay`
This overlay describes sensor connections (and matching h/w configuration to be done)
as explained in SHUB2 Mode (:ref:`x-nucleo-iks4a1-mode-2`)
Examples
********
Three samples are provided as examples for ``x-nucleo-iks4a1`` shield, each one associated
with one of the overlays described above:
- :ref:`x-nucleo-iks4a1-std-sample` application, to be used when the shield is configured
in Standard Mode (Mode 1)
- :ref:`x-nucleo-iks4a1-shub1-sample` application, to be used when the shield is configured
in SHUB1 Mode (Mode 3)
- :ref:`x-nucleo-iks4a1-shub2-sample` application, to be used when the shield is configured
in SHUB2 Mode (Mode 2)
See also :ref:`shields` for more details.
.. _X-NUCLEO-IKS4A1 website:
path_to_url
.. _X-NUCLEO-IKS4A1 user manual:
path_to_url
``` | /content/code_sandbox/boards/shields/x_nucleo_iks4a1/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,964 |
```restructuredtext
.. _frdm_kw41z_shield:
NXP FRDM-KW41Z Shield
#####################
Overview
********
The FRDM-KW41Z is a development kit enabled by the Kinetis |reg| W series
KW41Z/31Z/21Z (KW41Z) family built on ARM |reg| Cortex |reg|-M0+ processor with
integrated 2.4 GHz transceiver supporting Bluetooth |reg| Smart/Bluetooth
|reg| Low Energy
(BLE) v4.2, Generic FSK, IEEE |reg| 802.15.4 and Thread.
The FRDM-KW41Z can be used as a standalone board or as an Arduino shield. This
document covers usage as a shield; see :ref:`frdm_kw41z` for usage as a
standalone board.
Bluetooth Controller
********************
To use the FRDM-KW41Z as a Bluetooth low energy controller shield with a serial
host controller interface (HCI):
#. Download the MCUXpresso SDK for FRDM-KW41Z from the `MCUXpresso SDK Builder
Website`_.
#. Open the MCUXpresso IDE or IAR project in
:file:`boards/frdmkw41z/wireless_examples/bluetooth/hci_black_box/bm`
#. Open :file:`source/common/app_preinclude.h` and add the following line:
.. code-block:: console
#define gSerialMgrRxBufSize_c 64
#. Build the project to generate a binary :file:`hci_black_box_frdmkw41z.bin`.
#. Connect the FRDM-KW41Z board to your computer with a USB cable. A USB mass
storage device should enumerate.
#. Program the binary to flash by copying it to the USB mass storage device.
#. Remove the USB cable to power down the board.
#. Configure the jumpers J30 and J31 such that:
- J30 pin 1 is attached to J31 pin 2
- J30 pin 2 is attached to J31 pin 1
The jumpers should be parallel to the Arduino headers. This configuration
routes the UART RX and TX signals to the Arduino header, rather than to the
OpenSDA circuit.
#. Attach the FRDM-KW41Z to the Arduino header on your selected main board,
such as :ref:`mimxrt1050_evk` or :ref:`frdm_k64f`.
#. Set ``--shield frdm_kw41z`` when you invoke ``west build`` in
your Zephyr bluetooth application. For example,
.. zephyr-app-commands::
:zephyr-app: samples/bluetooth/peripheral_hr
:board: frdm_k64f
:shield: frdm_kw41z
:goals: build
References
**********
.. target-notes::
.. _MCUXpresso SDK Builder Website:
path_to_url
``` | /content/code_sandbox/boards/shields/frdm_kw41z/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 620 |
```unknown
config SHIELD_NPM1300_EK
def_bool $(shields_list_contains,npm1300_ek)
``` | /content/code_sandbox/boards/shields/npm1300_ek/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 26 |
```restructuredtext
.. _npm1300_ek:
nPM1300 EK
##########
Overview
********
The nPM1300 EK lets you test different functions and features of the nPM1300
Power Management Integrated Circuit (PMIC).
Requirements
************
The nPM1300 EK board is not designed to fit straight into an Arduino connector.
However, the Zephyr shield is designed expecting it to be connected to the
Arduino shield connectors. For example, the I2C lines need to be connected to
the ``arduino_i2c`` bus. This allows to use the shield with any host board that
supports the Arduino connector.
Usage
*****
The shield can be used in any application by setting ``--shield npm1300_ek``
when invoking ``west build``. You can check :ref:`npm1300_ek_sample` for a
comprehensive sample.
References
**********
TBC
``` | /content/code_sandbox/boards/shields/npm1300_ek/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 188 |
```unknown
/*
*
*/
&arduino_spi {
status = "okay";
cs-gpios = <&arduino_header 16 0>; /* D10 */
winc1500_adafruit_winc1500: winc1500@0 {
status = "ok";
compatible = "atmel,winc1500";
reg = <0x0>;
spi-max-frequency = <4000000>;
irq-gpios = <&arduino_header 13 GPIO_ACTIVE_LOW>; /* D7 */
reset-gpios = <&arduino_header 11 GPIO_ACTIVE_LOW>; /* D5 */
enable-gpios = <&arduino_header 12 0>; /* D6 */
};
};
``` | /content/code_sandbox/boards/shields/adafruit_winc1500/adafruit_winc1500.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 153 |
```unknown
config SHIELD_ADAFRUIT_WINC1500
def_bool $(shields_list_contains,adafruit_winc1500)
``` | /content/code_sandbox/boards/shields/adafruit_winc1500/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 29 |
```unknown
/*
*/
#include <dt-bindings/regulator/npm1300.h>
#include <zephyr/dt-bindings/input/input-event-codes.h>
&arduino_i2c {
npm1300_ek_pmic: pmic@6b {
compatible = "nordic,npm1300";
reg = <0x6b>;
npm1300_ek_gpio: gpio-controller {
compatible = "nordic,npm1300-gpio";
gpio-controller;
#gpio-cells = <2>;
ngpios = <5>;
};
npm1300_ek_regulators: regulators {
compatible = "nordic,npm1300-regulator";
/* limits are set to min/max allowed values */
npm1300_ek_buck1: BUCK1 {
regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <3300000>;
};
npm1300_ek_buck2: BUCK2 {
regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <3300000>;
};
npm1300_ek_ldo1: LDO1 {
regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <3300000>;
};
npm1300_ek_ldo2: LDO2 {
regulator-min-microvolt = <1000000>;
regulator-max-microvolt = <3300000>;
};
};
npm1300_ek_charger: charger {
compatible = "nordic,npm1300-charger";
term-microvolt = <4150000>;
term-warm-microvolt = <4000000>;
current-microamp = <150000>;
dischg-limit-microamp = <1000000>;
vbus-limit-microamp = <500000>;
thermistor-ohms = <10000>;
thermistor-beta = <3380>;
charging-enable;
};
npm1300_ek_buttons: buttons {
compatible = "gpio-keys";
pmic_button0: pmic_button_0 {
gpios = < &npm1300_ek_gpio 0 GPIO_ACTIVE_HIGH>;
label = "Pmic button switch 0";
zephyr,code = <INPUT_KEY_0>;
};
};
npm1300_ek_leds: leds {
compatible = "nordic,npm1300-led";
nordic,led0-mode = "error";
nordic,led1-mode = "charging";
nordic,led2-mode = "host";
};
};
};
``` | /content/code_sandbox/boards/shields/npm1300_ek/npm1300_ek.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 612 |
```unknown
if SHIELD_ADAFRUIT_WINC1500
if NETWORKING
config WIFI
default y
endif #NETWORKING
endif # SHIELD_ADAFRUIT_WINC1500
``` | /content/code_sandbox/boards/shields/adafruit_winc1500/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 42 |
```unknown
config SHIELD_FRDM_STBC_AGM01
def_bool $(shields_list_contains,frdm_stbc_agm01)
``` | /content/code_sandbox/boards/shields/frdm_stbc_agm01/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 29 |
```unknown
/*
*/
/ {
aliases {
magn0 = &fxos8700_1e_frdm_stbc_agm01;
accel0 = &fxos8700_1e_frdm_stbc_agm01;
};
};
&arduino_i2c {
fxos8700_1e_frdm_stbc_agm01: fxos8700@1e {
compatible = "nxp,fxos8700";
reg = <0x1e>;
int1-gpios = <&arduino_header 8 GPIO_ACTIVE_LOW>;
int2-gpios = <&arduino_header 10 GPIO_ACTIVE_LOW>;
};
fxas21002_frdm_stbc_agm01: fxas21002@20 {
compatible = "nxp,fxas21002";
reg = <0x20>;
int1-gpios = <&arduino_header 11 GPIO_ACTIVE_LOW>;
int2-gpios = <&arduino_header 14 GPIO_ACTIVE_LOW>;
};
};
``` | /content/code_sandbox/boards/shields/frdm_stbc_agm01/frdm_stbc_agm01.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 219 |
```restructuredtext
.. _adafruit_winc1500:
Adafruit WINC1500 Wifi Shield
#############################
Overview
********
The Adafruit WINC1500 Wifi shield is an Arduino
compatible shield based on the ATWINC1500 wifi controller
from Microchip.
The shield also provides a micro SD card socket
The SD card socket is currently not supported
More information about the shield can be found
at the `Adafruit WINC1500 website`_.
Pins Assignment of the Adafruit WINC1500 WiFi Shield
====================================================
+-----------------------+---------------------------------------------+
| Shield Connector Pin | Function |
+=======================+=============================================+
| D4 | MicroSD SPI CSn (Not supported) |
+-----------------------+---------------------------------------------+
| D5 | WINC1500 RST (/Reset of winc1500) |
+-----------------------+---------------------------------------------+
| D6 (b) | WINC1500 EN (Enable of winc1500) |
+-----------------------+---------------------------------------------+
| D7 | WINC1500 IRQ (IRQ from winc1500) |
+-----------------------+---------------------------------------------+
| D10 | WINC1500 SPI CSn |
+-----------------------+---------------------------------------------+
| D11 (a) | SPI MOSI (Serial Data Input) |
+-----------------------+---------------------------------------------+
| D12 (a) | SPI MISO (Serial Data Out) |
+-----------------------+---------------------------------------------+
| D13 (a) | SPI SCK (Serial Clock Input) |
+-----------------------+---------------------------------------------+
The pins marked (a) must be jumpered to the SPI port at the shield
To enable low power support, wire the pin marked (b) to the En connector
at the shield
Requirements
************
This shield can only be used with a board which provides a configuration
for Arduino connectors and defines node aliases for SPI and GPIO interfaces
(see :ref:`shields` for more details).
Programming
***********
Set ``--shield adafruit_winc1500`` when you invoke ``west build``. For example:
.. zephyr-app-commands::
:zephyr-app: samples/net/wifi
:board: frdm_k64f
:shield: adafruit_winc1500
:goals: build
References
**********
.. target-notes::
.. _Adafruit WINC1500 website:
path_to_url
``` | /content/code_sandbox/boards/shields/adafruit_winc1500/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 526 |
```restructuredtext
.. _frdm_stbc_agm01_shield:
NXP FRDM-STBC-AGM01
###################
Overview
********
The FRDM-STBC-AGM01 is an NXP Freedom development board with
FXOS8700 and FXAS21002. This 9-axis solution (FXAS21002C Gyroscope,
+ FXOS8700CQ E-compass sensor) is compatible with any board that
provides an Arduino R3 header.
.. image:: AGM01.jpg
:align: center
:alt: FRDM-STBC-AGM01
Pin Assignment of the FRDM-STBC-AGM01 Shield
============================================
+-----------------------+---------------------+
| Shield Connector Pin | Function |
+=======================+=====================+
| A5 | I2C - SCL1 |
+-----------------------+---------------------+
| A4 | I2C - SDA1 |
+-----------------------+---------------------+
| D15 | I2C - SCL0 |
+-----------------------+---------------------+
| D14 | I2C - SDA0 |
+-----------------------+---------------------+
| D2 | INT1 - 8700 |
+-----------------------+---------------------+
| D4 | INT2 - 8700 |
+-----------------------+---------------------+
| D5 | INT1 - 21002 |
+-----------------------+---------------------+
| D8 | INT2 - 21002 |
+-----------------------+---------------------+
| A3 | RST - GPIO |
+-----------------------+---------------------+
For more information about the FXOS8700, FXAS21002, and FRDM-STBC-AGM01
board:
- :ref:`fxos8700`
- :ref:`fxas21002`
- `FRDM-STBC-AGM01 Website`_
- `FRDM-STBC-AGM01 Quick Reference Card`_
- `FRDM-STBC-AGM01 Schematics`_
Programming
***********
Set ``--shield frdm_stbc_agm01`` when you invoke ``west build``. For example:
.. zephyr-app-commands::
:zephyr-app: samples/sensor/fxas21002
:board: frdm_k22f
:shield: frdm_stbc_agm01
:goals: build
.. _FRDM-STBC-AGM01 Website:
path_to_url
.. _FRDM-STBC-AGM01 Quick Reference Card:
path_to_url
.. _FRDM-STBC-AGM01 Schematics:
path_to_url
``` | /content/code_sandbox/boards/shields/frdm_stbc_agm01/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 570 |
```unknown
/*
*
*/
/{
chosen {
zephyr,display = &rm67162_g1120b0mipi;
};
en_mipi_display_g1120b0mipi: enable-mipi-display {
compatible = "regulator-fixed";
regulator-name = "en_mipi_display";
enable-gpios = <&nxp_mipi_connector 32 GPIO_ACTIVE_HIGH>;
regulator-boot-on;
};
lvgl_pointer {
compatible = "zephyr,lvgl-pointer-input";
input = <&ft3267_g1120b0mipi>;
invert-y;
};
};
&nxp_mipi_i2c {
status = "okay";
ft3267_g1120b0mipi: ft3267@38 {
/*
* Note- the actual controller present on this IC is a FT3267,
* but the FT35336 driver in Zephyr supports this IC.
*/
compatible = "focaltech,ft5336";
reg = <0x38>;
int-gpios = <&nxp_mipi_connector 29 GPIO_ACTIVE_LOW>;
reset-gpios = <&nxp_mipi_connector 28 GPIO_ACTIVE_LOW>;
};
};
&zephyr_mipi_dsi {
status = "okay";
autoinsert-eotp;
phy-clock = <316800000>;
rm67162_g1120b0mipi: rm67162@0 {
status = "okay";
compatible = "raydium,rm67162";
reg = <0x0>;
reset-gpios = <&nxp_mipi_connector 21 GPIO_ACTIVE_HIGH>;
bl-gpios = <&nxp_mipi_connector 0 GPIO_ACTIVE_HIGH>;
te-gpios = <&nxp_mipi_connector 22 GPIO_ACTIVE_HIGH>;
data-lanes = <1>;
width = <400>;
height = <392>;
pixel-format = <MIPI_DSI_PIXFMT_RGB565>;
};
};
``` | /content/code_sandbox/boards/shields/g1120b0mipi/g1120b0mipi.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 432 |
```unknown
config SHIELD_G1120B0MIPI
def_bool $(shields_list_contains,g1120b0mipi)
``` | /content/code_sandbox/boards/shields/g1120b0mipi/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 28 |
```unknown
/*
*
*/
&rm67162_g1120b0mipi {
/* R414 is not populated on this board, so LPTE signal is not
* connected. remove the property from the display.
*/
/delete-property/ te-gpios;
};
``` | /content/code_sandbox/boards/shields/g1120b0mipi/boards/mimxrt1170_evk_mimxrt1176_cm7_B.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 56 |
```unknown
if SHIELD_G1120B0MIPI
if LVGL
# Enable input subsystem for FT5336 driver
config INPUT
default y
config INPUT_FT5336_INTERRUPT
default y
if MIPI_DSI_MCUX_2L
# Enable color swap in driver
config MIPI_DSI_MCUX_2L_SWAP16
default y
endif # MIPI_DSI_MCUX_2L
# Swap 16 bit color setting for LVGL, to send high byte first
config LV_COLOR_16_SWAP
default y if !MIPI_DSI_MCUX_2L_SWAP16
config LV_Z_VDB_SIZE
default 16
config LV_DPI_DEF
default 128
# Use offloaded render thread
config LV_Z_FLUSH_THREAD
default y
choice LV_COLOR_DEPTH
default LV_COLOR_DEPTH_16
endchoice
endif # LVGL
endif # SHIELD_G1120B0MIPI
``` | /content/code_sandbox/boards/shields/g1120b0mipi/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 198 |
```unknown
/*
*
*/
/* Change deep sleep config for suspend mode to keep SMARTDMA ram powered,
* so the SMARTDMA will continue functioning after deep sleep
*/
&suspend {
deep-sleep-config = <0xC800>,
<0x80030004>,
<0xFFFFFFFF>,
<0>;
};
``` | /content/code_sandbox/boards/shields/g1120b0mipi/boards/mimxrt595_evk_mimxrt595s_cm33.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 67 |
```unknown
/*
*
*/
&rm67162_g1120b0mipi {
/* R414 is not populated on this board, so LPTE signal is not
* connected. remove the property from the display.
*/
/delete-property/ te-gpios;
};
``` | /content/code_sandbox/boards/shields/g1120b0mipi/boards/mimxrt1160_evk_mimxrt1166_cm7.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 56 |
```unknown
# Enable DMA, so that DSI MCUX will use SMARTDMA
CONFIG_DMA=y
``` | /content/code_sandbox/boards/shields/g1120b0mipi/boards/mimxrt595_evk_mimxrt595s_cm33.conf | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 20 |
```unknown
/*
*
*/
&rm67162_g1120b0mipi {
/* R414 is not populated on this board, so LPTE signal is not
* connected. remove the property from the display.
*/
/delete-property/ te-gpios;
};
``` | /content/code_sandbox/boards/shields/g1120b0mipi/boards/mimxrt1170_evk_mimxrt1176_cm7_A.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 56 |
```unknown
config SHIELD_RK055HDMIPI4MA0
def_bool $(shields_list_contains,rk055hdmipi4ma0)
``` | /content/code_sandbox/boards/shields/rk055hdmipi4ma0/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 32 |
```unknown
if SHIELD_RK055HDMIPI4MA0
if DISPLAY
# Enable MIPI DSI, as this display controller requires it.
config MIPI_DSI
default y
endif # DISPLAY
if LVGL
# Configure LVGL to use touchscreen with KSCAN API
config INPUT
default y
config INPUT_GT911_INTERRUPT
default y
# LVGL should allocate buffers equal to size of display
config LV_Z_VDB_SIZE
default 100
# Enable double buffering
config LV_Z_DOUBLE_VDB
default y
# Force full refresh. This prevents memory copy associated with partial
# display refreshes, which is not necessary for the eLCDIF driver
config LV_Z_FULL_REFRESH
default y
config LV_Z_BITS_PER_PIXEL
default 16
config LV_DPI_DEF
default 128
# Use offloaded render thread
config LV_Z_FLUSH_THREAD
default y
choice LV_COLOR_DEPTH
default LV_COLOR_DEPTH_16
endchoice
endif # LVGL
endif # SHIELD_RK055HDMIPI4MA0
``` | /content/code_sandbox/boards/shields/rk055hdmipi4ma0/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 223 |
```restructuredtext
.. _g1120b0mipi:
G1120B0MIPI MIPI Display
##########################
Overview
********
The G1120B0MIPI is a 1.2 inch circular AMOLED display, 390x390 pixels, with a
1-lane MIPI interface. This display connects to the i.MX RT595 Evaluation Kit.
More information about the shield can be found
at the `G1120B0MIPI product page`_.
This display uses a 40 pin FPC interface, which is available on many
NXP EVKs.
Pins Assignment of the G1120B0MIPI MIPI Display
==========================================================
+-----------------------+------------------------+
| FPC Connector Pin | Function |
+=======================+========================+
| 1 | LED backlight cathode |
+-----------------------+------------------------+
| 21 | Controller reset |
+-----------------------+------------------------+
| 22 | Controller LPTE |
+-----------------------+------------------------+
| 26 | Touch ctrl I2C SDA |
+-----------------------+------------------------+
| 27 | Touch ctrl I2C SCL |
+-----------------------+------------------------+
| 28 | Touch ctrl reset |
+-----------------------+------------------------+
| 29 | Touch ctrl interrupt |
+-----------------------+------------------------+
| 32 | LCD power enable |
+-----------------------+------------------------+
| 34 | Backlight power enable |
+-----------------------+------------------------+
Requirements
************
This shield can only be used with a board which provides a configuration
for the 40 pin FPC interface
Programming
***********
Set ``--shield g1120b0mipi`` when you invoke ``west build``. For
example:
.. zephyr-app-commands::
:zephyr-app: samples/drivers/display
:board: mimxrt595_evk/mimxrt595s/cm33
:shield: g1120b0mipi
:goals: build
References
**********
.. target-notes::
.. _G1120B0MIPI product page:
path_to_url
``` | /content/code_sandbox/boards/shields/g1120b0mipi/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 465 |
```unknown
/*
*
*/
/*
* Configure FlexSPI2 to use 1KB of AHB RX buffer for GPU/Display master.
* This will improve performance when using external pSRAM.
*/
&flexspi2 {
rx-buffer-config = <1 7 11 1024>;
};
/* GT911 IRQ GPIO is active low on this board, and needs probing mode */
>911_rk055hdmipi4ma0 {
irq-gpios = <&nxp_mipi_connector 29 GPIO_ACTIVE_LOW>;
alt-addr = <0x14>;
};
``` | /content/code_sandbox/boards/shields/rk055hdmipi4ma0/boards/mimxrt595_evk_mimxrt595s_cm33.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 118 |
```unknown
#
#
#
# Use external framebuffer memory
CONFIG_MCUX_DCNANO_LCDIF_EXTERNAL_FB_MEM=y
CONFIG_LV_Z_VBD_CUSTOM_SECTION=y
# Use FlexSPI2 for framebuffer (pSRAM is present on this bus)
CONFIG_MCUX_DCNANO_LCDIF_EXTERNAL_FB_ADDR=0x38400000
# M33 core and LCDIF both access FlexSPI2 through the same cache,
# so coherency does not need to be managed.
CONFIG_MCUX_DCNANO_LCDIF_MAINTAIN_CACHE=n
``` | /content/code_sandbox/boards/shields/rk055hdmipi4ma0/boards/mimxrt595_evk_mimxrt595s_cm33.conf | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 111 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.