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
config SHIELD_RPI_PICO_UNO_FLEXYPIN
def_bool $(shields_list_contains,rpi_pico_uno_flexypin)
``` | /content/code_sandbox/boards/shields/rpi_pico_uno_flexypin/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 34 |
```unknown
/*
*
*/
/ {
arduino_header: connector {
compatible = "arduino-header-r3";
#gpio-cells = <2>;
gpio-map-mask = <0xffffffff 0xffffffc0>;
gpio-map-pass-thru = <0 0x3f>;
gpio-map =
<0 0 &pico_header 26 0>, /* A0 */
<1 0 &pico_header 27 0>, /* A1 */
<2 0 &pico_header 28 0>, /* A2 */
<3 0 &pico_header 13 0>, /* A3 */
<4 0 &pico_header 14 0>, /* A4 */
<5 0 &pico_header 15 0>, /* A5 */
<6 0 &pico_header 1 0>, /* D0 */
<7 0 &pico_header 0 0>, /* D1 */
<8 0 &pico_header 4 0>, /* D2 */
<9 0 &pico_header 5 0>, /* D3 */
<10 0 &pico_header 6 0>, /* D4 */
<11 0 &pico_header 7 0>, /* D5 */
<12 0 &pico_header 8 0>, /* D6 */
<13 0 &pico_header 9 0>, /* D7 */
<14 0 &pico_header 2 0>, /* D8 */
<15 0 &pico_header 3 0>, /* D9 */
<16 0 &pico_header 17 0>, /* D10 */
<17 0 &pico_header 19 0>, /* D11 */
<18 0 &pico_header 16 0>, /* D12 */
<19 0 &pico_header 18 0>, /* D13 */
<20 0 &pico_header 20 0>, /* D14 */
<21 0 &pico_header 21 0>; /* D15 */
};
};
arduino_spi: &pico_spi {};
arduino_i2c: &pico_i2c0 {};
arduino_serial: &pico_serial {};
``` | /content/code_sandbox/boards/shields/rpi_pico_uno_flexypin/rpi_pico_uno_flexypin.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 531 |
```restructuredtext
.. _dvp_fpc24_mt9m114:
DVP FPC-24 MT9M114 Camera Module
################################
Overview
********
This shield supports mt9m114 camera modules which use a 24-pin FPC connector and a DVP
(Digital Video Port), aka parallel interface. These camera modules are compatible and provided
together with the i.MX RT1050, RT1060 and RT1064 EVKs as specified here `Camera iMXRT`_.
Pins assignment of the DVP FPC-24 MT9M114 camera module
=======================================================
+-------------------+--------------+
| FPC Connector Pin | Function |
+===================+==============+
| 1 | NC |
+-------------------+--------------+
| 2 | AGND |
+-------------------+--------------+
| 3 | SDA |
+-------------------+--------------+
| 4 | AVDD |
+-------------------+--------------+
| 5 | SCL |
+-------------------+--------------+
| 6 | Reset |
+-------------------+--------------+
| 7 | Vsync |
+-------------------+--------------+
| 8 | Powerdown |
+-------------------+--------------+
| 9 | Hsync |
+-------------------+--------------+
| 10 | DVDD |
+-------------------+--------------+
| 11 | DOVDD |
+-------------------+--------------+
| 12 | Data 9 |
+-------------------+--------------+
| 13 | Master Clock |
+-------------------+--------------+
| 14 | Data 8 |
+-------------------+--------------+
| 15 | DGND |
+-------------------+--------------+
| 16 | Data 7 |
+-------------------+--------------+
| 17 | Pixel Clock |
+-------------------+--------------+
| 18 | Data 6 |
+-------------------+--------------+
| 19 | Data 2 |
+-------------------+--------------+
| 20 | Data 5 |
+-------------------+--------------+
| 21 | Data 3 |
+-------------------+--------------+
| 22 | Data 4 |
+-------------------+--------------+
| 23 | Data 1 |
+-------------------+--------------+
| 24 | Data 0 |
+-------------------+--------------+
Requirements
************
This shield can only be used with a board which provides a configuration for a 24-pins FPC
connector with DVP (parallel) interface, such as the i.MX RT1050, RT1060, RT1064 EVKs.
Programming
***********
Set ``--shield dvp_fpc24_mt9m114`` when you invoke ``west build``. For example:
.. zephyr-app-commands::
:zephyr-app: samples/subsys/video/capture
:board: mimxrt1064_evk
:shield: dvp_fpc24_mt9m114
:goals: build
References
**********
.. target-notes::
.. _Camera iMXRT:
path_to_url
``` | /content/code_sandbox/boards/shields/dvp_fpc24_mt9m114/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 674 |
```unknown
config SHIELD_REYAX_LORA
def_bool $(shields_list_contains,reyax_lora)
``` | /content/code_sandbox/boards/shields/reyax_lora/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 24 |
```unknown
/*
*/
#include <zephyr/dt-bindings/gpio/gpio.h>
/{
aliases {
lora0 = &rylr_lora_modem;
};
};
&arduino_serial {
current-speed = <115200>;
status = "okay";
rylr_lora_modem: rylr_lora_modem {
compatible = "reyax,rylrxxx";
status = "okay";
reset-gpios = <&arduino_header 16 GPIO_ACTIVE_LOW>;
};
};
``` | /content/code_sandbox/boards/shields/reyax_lora/reyax_lora.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 105 |
```unknown
CONFIG_LORA=y
CONFIG_LORA_RYLRXXX=y
CONFIG_UART_INTERRUPT_DRIVEN=y
``` | /content/code_sandbox/boards/shields/reyax_lora/boards/cy8ckit_062s4.conf | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 23 |
```restructuredtext
.. _rpi_pico_uno_flexypin:
RaspberryPi Pico to UNO FlexyPin Adapter
########################################
Overview
********
Raspberry Pi Pico to Uno `FlexyPin Adapter` is a converter-PCB to Arduino UNO form-factor
from Raspberry Pi Pico that is released in Open Source Hardware.
This board design to use with `FlexyPin`.
The FlexyPin holds Pico and contacts to castellated through-hole.
With simple soldering, it can also be used as a board to convert the RapsberryPi Pico
o the Arduino UNO form factor.
.. image:: img/rpi_pico_uno_flexypin.png
:align: center
:alt: RaspberryPi Pico to UNO FlexyPin Adapter
Pins Assignment of the RaspberryPi Pico to UNO FlexyPin Adapter
===============================================================
+---------------------+------------+
| Rpi-Pico Pin | UNO Header |
+=====================+============+
| GP0 (UART0 TX) | D1 |
+---------------------+------------+
| GP1 (UART0 RX) | D0 |
+---------------------+------------+
| GP2 | D8 |
+---------------------+------------+
| GP3 | D9 |
+---------------------+------------+
| GP4 | D2 |
+---------------------+------------+
| GP5 | D3 |
+---------------------+------------+
| GP6 | D4 |
+---------------------+------------+
| GP7 | D5 |
+---------------------+------------+
| GP8 | D6 |
+---------------------+------------+
| GP9 | D7 |
+---------------------+------------+
| GP13 | A3 |
+---------------------+------------+
| GP14 (I2C1 SDA) | A4 |
+---------------------+------------+
| GP15 (I2C1 SCL) | A5 |
+---------------------+------------+
| GP16 (SPI0 RX/CIPO) | D12 |
+---------------------+------------+
| GP17 (SPI0 CS) | D10 |
+---------------------+------------+
| GP18 (SPI0 SCK) | D13 |
+---------------------+------------+
| GP19 (SPI0 TX/COPI) | D11 |
+---------------------+------------+
| GP20 | D14 |
+---------------------+------------+
| GP21 (I2C0 SCL) | D15 |
+---------------------+------------+
| GP26 (I2C0 SDA) | A0 |
+---------------------+------------+
| GP27 | A1 |
+---------------------+------------+
| GP28 | A2 |
+---------------------+------------+
Programming
***********
Set ``--shield rpi_pico_uno_flexypin`` when you invoke ``west build``.
This shield is just a converter, so it is usually used with other Arduino shield.
For example,
.. zephyr-app-commands::
:zephyr-app: samples/net/wifi
:board: rpi_pico
:shield: rpi_pico_uno_flexypin,esp_8266_arduino
:goals: build
References
**********
.. target-notes::
.. _FlexyPin:
path_to_url
.. _FlexyPin Adapters:
path_to_url
``` | /content/code_sandbox/boards/shields/rpi_pico_uno_flexypin/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 746 |
```unknown
/*
*/
&p0_2_scb0_uart_rx {
input-enable;
};
&p0_3_scb0_uart_tx {
drive-push-pull;
};
&arduino_serial {
pinctrl-0 = <&p0_2_scb0_uart_rx &p0_3_scb0_uart_tx>;
pinctrl-names = "default";
};
&gpio_prt0 {
status = "okay";
};
&gpio_prt2 {
status = "okay";
};
``` | /content/code_sandbox/boards/shields/reyax_lora/boards/cy8ckit_062s4.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 99 |
```restructuredtext
.. _reyax_lora:
Reyax LoRa RYLR896 and RYLR915 Modules
######################################
Overview
********
These modules expose a simple uart interface for the Semtech SX1276 chip,which implements the LoRa PHY.
More information about the board can be found at the
`Reyax RYLR page`_.
Hardware Description
********************
The Module contains 4 pins
- VDD: Power Supply
- NRST: Active low reset
- RXD: Serial data input
- TXD: Serial data output
- GND: Ground
References
**********
.. target-notes::
.. _Reyax RYLR page:
path_to_url
``` | /content/code_sandbox/boards/shields/reyax_lora/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 148 |
```unknown
/*
*
*/
/ {
aliases {
accel0 = &adxl362_0_boostxl_ulpsense;
};
};
&boosterpack_spi {
adxl362_0_boostxl_ulpsense: adxl362@0 {
compatible = "adi,adxl362";
reg = <0>;
spi-max-frequency = <8000000>;
int1-gpios = <&boosterpack_header 36 0>;
};
};
``` | /content/code_sandbox/boards/shields/boostxl_ulpsense/boostxl_ulpsense.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 100 |
```unknown
config SHIELD_BOOSTXL_ULPSENSE
def_bool $(shields_list_contains,boostxl_ulpsense)
``` | /content/code_sandbox/boards/shields/boostxl_ulpsense/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 27 |
```restructuredtext
.. _boostxl-ulpsense:
BOOSTXL-ULPSENSE: Ultra-low Power Sensor BoosterPack
####################################################
Overview
********
The Ultra-low Power Sensor BoosterPack (BOOSTXL-ULPSENSE) adds analog and
digital sensors to a TI LaunchPad |trade| development kit. The plug-in module
features inductive flow meter measurement circuits, two capacitive touch
buttons, a light sensor, a reed switch, and an ultra-low power accelerometer.
More information about the board can be found at the
`BOOSTXL_ULPSENSE website`_.
Requirements
************
This shield can be used with any TI LaunchPad |trade| development kit with
BoosterPack connectors.
Programming
***********
Set ``--shield boostxl_ulpsense`` when you invoke ``west build``. For example:
.. zephyr-app-commands::
:zephyr-app: samples/sensor/accel_polling/
:board: cc1352r1_launchxl
:shield: boostxl_ulpsense
:goals: build
References
**********
.. target-notes::
.. _BOOSTXL_ULPSENSE website:
path_to_url
``` | /content/code_sandbox/boards/shields/boostxl_ulpsense/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 247 |
```unknown
/*
*
*/
/* Common assignments for any nRF70 shield */
/* D0 */
iovdd-ctrl-gpios = <&arduino_header 6 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>;
/* D1 */
bucken-gpios = <&arduino_header 7 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>;
/* D7 */
host-irq-gpios = <&arduino_header 13 GPIO_ACTIVE_HIGH>;
/* Short-range (SR) co-existence */
/* D2 */
status0-gpios = <&arduino_header 8 GPIO_ACTIVE_HIGH>;
/* D3 */
req-gpios = <&arduino_header 9 GPIO_ACTIVE_HIGH>;
/* D4 */
grant-gpios = <&arduino_header 10 (GPIO_PULL_DOWN | GPIO_ACTIVE_LOW)>;
/* D6 */
swctrl1-gpios = <&arduino_header 12 GPIO_ACTIVE_HIGH>;
/* D8 */
srrf-switch-gpios = <&arduino_header 14 GPIO_ACTIVE_HIGH>;
/* Maximum TX power limits for 2.4 GHz */
wifi-max-tx-pwr-2g-dsss = <21>;
wifi-max-tx-pwr-2g-mcs0 = <16>;
wifi-max-tx-pwr-2g-mcs7 = <16>;
/* List of interfaces */
wlan0: wlan0 {
compatible = "nordic,wlan";
};
``` | /content/code_sandbox/boards/shields/nrf7002ek/nrf7002ek_common.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 280 |
```unknown
config SHIELD_NRF7002EK
def_bool $(shields_list_contains,nrf7002ek)
config SHIELD_NRF7002EK_NRF7001
def_bool $(shields_list_contains,nrf7002ek_nrf7001)
config SHIELD_NRF7002EK_NRF7000
def_bool $(shields_list_contains,nrf7002ek_nrf7000)
``` | /content/code_sandbox/boards/shields/nrf7002ek/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 84 |
```unknown
/*
*
*/
wifi-max-tx-pwr-5g-low-mcs0 = <13>;
wifi-max-tx-pwr-5g-low-mcs7 = <13>;
wifi-max-tx-pwr-5g-mid-mcs0 = <13>;
wifi-max-tx-pwr-5g-mid-mcs7 = <13>;
wifi-max-tx-pwr-5g-high-mcs0 = <12>;
wifi-max-tx-pwr-5g-high-mcs7 = <12>;
``` | /content/code_sandbox/boards/shields/nrf7002ek/nrf7002ek_common_5g.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 108 |
```unknown
/*
*
*/
#include <freq.h>
/ {
chosen {
zephyr,wifi = &wlan0;
};
};
&arduino_spi {
status = "okay";
nrf70: nrf7002-spi@0 {
compatible = "nordic,nrf7002-spi";
status = "okay";
reg = <0>;
spi-max-frequency = <DT_FREQ_M(8)>;
/* Include common nRF70 overlays */
#include "nrf7002ek_common.dtsi"
#include "nrf7002ek_common_5g.dtsi"
};
};
``` | /content/code_sandbox/boards/shields/nrf7002ek/nrf7002ek.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 136 |
```unknown
/*
*
*/
#include <freq.h>
/ {
chosen {
zephyr,wifi = &wlan0;
};
};
&arduino_spi {
status = "okay";
nrf70: nrf7001-spi@0 {
compatible = "nordic,nrf7001-spi";
status = "okay";
reg = <0>;
spi-max-frequency = <DT_FREQ_M(8)>;
/* Include common nRF70 overlays */
#include "nrf7002ek_common.dtsi"
};
};
``` | /content/code_sandbox/boards/shields/nrf7002ek/nrf7002ek_nrf7001.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 119 |
```unknown
*
*/
#include <nrf9151dk_leds_on_io_expander.dtsi>
``` | /content/code_sandbox/boards/shields/nrf7002ek/boards/nrf9151dk_nrf9151.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 20 |
```unknown
/*
*
*/
#include <freq.h>
/ {
chosen {
zephyr,wifi = &wlan0;
};
};
&arduino_spi {
status = "okay";
nrf70: nrf7002-spi@0 {
compatible = "nordic,nrf7000-spi";
status = "okay";
reg = <0>;
spi-max-frequency = <DT_FREQ_M(8)>;
/* Include common nRF70 overlays */
#include "nrf7002ek_common.dtsi"
#include "nrf7002ek_common_5g.dtsi"
};
};
``` | /content/code_sandbox/boards/shields/nrf7002ek/nrf7002ek_nrf7000.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 136 |
```unknown
*
*/
#include <nrf9151dk_leds_on_io_expander.dtsi>
``` | /content/code_sandbox/boards/shields/nrf7002ek/boards/nrf9151dk_nrf9151_ns.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 20 |
```unknown
*
*/
#include <nrf9161dk_leds_on_io_expander.dtsi>
``` | /content/code_sandbox/boards/shields/nrf7002ek/boards/nrf9161dk_nrf9161_ns.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 20 |
```unknown
/*
*
*/
/* Disabled because of conflicts on P0.00 and P0.01 - Arduino pins D0 and D1
* (iovdd-ctrl-gpios and bucken-gpios in nrf7002ek, respectively).
*/
&uart1 {
status = "disabled";
};
/* Typically we use GPIO extender to resolve these conflicts but the
* GPIO pin used by extender itself conflicts with Wi-Fi (0.6), so,
* disable LEDs and Button0/1.
*/
&led0 {
status = "disabled";
};
&led1 {
status = "disabled";
};
&led2 {
status = "disabled";
};
&led3 {
status = "disabled";
};
&button0 {
status = "disabled";
};
&button1 {
status = "disabled";
};
``` | /content/code_sandbox/boards/shields/nrf7002ek/boards/nrf9160dk_nrf9160_ns.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 164 |
```unknown
*
*/
#include <nrf9161dk_leds_on_io_expander.dtsi>
``` | /content/code_sandbox/boards/shields/nrf7002ek/boards/nrf9161dk_nrf9161.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 20 |
```unknown
*
*/
/* This node by default forwards the UART1 pins to CPUNET, but as UART1 uses
* same pins as bucken and iovdd-ctrl, we need these pins to be controlled by
* the CPUAPP. Since a child node of gpio_fwd cannot be disabled, hence
* the entire node is disabled. If the application needs to forward other pins
* to the CPUNET, it should create a separate instance of nrf-gpio-forwarder
* and use it instead.
*/
&gpio_fwd {
status = "disabled";
};
``` | /content/code_sandbox/boards/shields/nrf7002ek/boards/nrf5340dk_nrf5340_cpuapp.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 115 |
```unknown
/*
*
*/
&arduino_serial {
status = "okay";
wifi0: iwin {
status = "okay";
compatible = "inventek,eswifi-uart";
/* D7 */
wakeup-gpios = <&arduino_header 13 GPIO_ACTIVE_HIGH>;
/* D6 */
resetn-gpios = <&arduino_header 12 GPIO_ACTIVE_HIGH>;
};
};
``` | /content/code_sandbox/boards/shields/inventek_eswifi/inventek_eswifi_arduino_uart.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 87 |
```unknown
config SHIELD_INVENTEK_ESWIFI
def_bool $(shields_list_contains,inventek_eswifi)
config SHIELD_INVENTEK_ESWIFI_ARDUINO_SPI
def_bool $(shields_list_contains,inventek_eswifi_arduino_spi)
config SHIELD_INVENTEK_ESWIFI_ARDUINO_UART
def_bool $(shields_list_contains,inventek_eswifi_arduino_uart)
``` | /content/code_sandbox/boards/shields/inventek_eswifi/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 87 |
```unknown
/*
*
*/
&arduino_spi {
status = "okay";
/* D10 */
cs-gpios = <&arduino_header 16 GPIO_ACTIVE_LOW>;
wifi0_inventek_eswifi_arduino_spi: iwin@0 {
status = "okay";
compatible = "inventek,eswifi";
spi-max-frequency = <2000000>;
reg = <0>;
/* D9 */
data-gpios = <&arduino_header 15 GPIO_ACTIVE_HIGH>;
/* D7 */
wakeup-gpios = <&arduino_header 13 GPIO_ACTIVE_HIGH>;
/* D6 */
resetn-gpios = <&arduino_header 12 GPIO_ACTIVE_HIGH>;
/* D5 */
boot0-gpios = <&arduino_header 11 GPIO_ACTIVE_HIGH>;
};
};
``` | /content/code_sandbox/boards/shields/inventek_eswifi/inventek_eswifi_arduino_spi.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 175 |
```restructuredtext
.. _nrf7002ek:
nRF7002 EK
##########
Overview
********
The nRF7002 EK is a versatile evaluation kit in the form of an Arduino shield that can be used in
Nordic and non-Nordic host boards.
The nRF7002 EK unlocks low-power Wi-Fi 6 capabilities for your host device. It support dual-band Wi-Fi
2.4GHz and 5GHz, and is based on the nRF7002 SoC.
Seamlessly connect to Wi-Fi networks and leverage Wi-Fi-based locationing, enabling advanced
features such as SSID sniffing of local Wi-Fi hubs
.. figure:: nrf7002ek.png
:alt: nRF7002 EK
:align: center
nRF7002 EK
Requirements
************
The nRF7002 EK board is designed to fit straight into an Arduino connector and uses SPI as the
communication interface. Any host board that supports the Arduino connector can be used with
the nRF7002 EK.
Prerequisites
-------------
the nRF70 driver requires firmware binary blobs for Wi-Fi operation. Run the command
below to retrieve those files.
.. code-block:: console
west update
west blobs fetch hal_nordic
Usage
*****
The shield can be used in any application by setting ``--shield nrf7002ek`` when invoking ``west build``.
SR Co-existence
###############
The nRF7002 EK supports SR co-existence provided the host board supports it. The SR co-existence
pins are connected to the host board's GPIO pins.
Two Kconfig options are available to enable SR co-existence:
- :kconfig:option:`CONFIG_NRF70_SR_COEX`: Enables SR co-existence.
- :kconfig:option:`CONFIG_NRF70_SR_COEX_RF_SWITCH`: Control SR side RF switch.
Shield Variants
###############
The nRF7002 EK is available in three variants:
- ``nrf7002ek``: The default variant.
- ``nrf7002ek_nrf7001``: Variant for the nRF7001 SoC or nRF7002 SoC emulating nRF7001
that supports only 2.4GHz Wi-Fi.
- ``nrf7002ek_nrf7000``: Variant for the nRF7000 SoC or nRF7002 SoC emulating nRF7000
that supports only 2.4GHz Wi-Fi.
References
**********
- `nRF7002 EK product page <path_to_url`_
- `nRF7002 product specification <path_to_url`_
- `nRF7002 EK Co-existence <path_to_url`_
``` | /content/code_sandbox/boards/shields/nrf7002ek/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 569 |
```unknown
/*
*
*/
/*
* This file is intentionally empty. Please refer to shield documentation for
* instructions how to use this shield.
*/
``` | /content/code_sandbox/boards/shields/inventek_eswifi/inventek_eswifi.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 28 |
```unknown
#
#
if BOARD_NUCLEO_F767ZI
config NET_L2_ETHERNET
default n
endif # BOARD_NUCLEO_F767ZI
``` | /content/code_sandbox/boards/shields/inventek_eswifi/boards/nucleo_f767zi.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 37 |
```unknown
if SHIELD_INVENTEK_ESWIFI || \
SHIELD_INVENTEK_ESWIFI_ARDUINO_SPI || \
SHIELD_INVENTEK_ESWIFI_ARDUINO_UART
if NETWORKING
orsource "boards/*.defconfig"
choice WIFI_ESWIFI_BUS
default WIFI_ESWIFI_BUS_SPI if SHIELD_INVENTEK_ESWIFI_ARDUINO_SPI
default WIFI_ESWIFI_BUS_UART if SHIELD_INVENTEK_ESWIFI_ARDUINO_UART
depends on WIFI_ESWIFI
endchoice
endif # NETWORKING
endif # SHIELD_INVENTEK_ESWIFI || \
# SHIELD_INVENTEK_ESWIFI_ARDUINO_SPI || \
# SHIELD_INVENTEK_ESWIFI_ARDUINO_UART
``` | /content/code_sandbox/boards/shields/inventek_eswifi/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 170 |
```unknown
#
#
if BOARD_FRDM_K64F
config NET_L2_ETHERNET
default n
endif # BOARD_FRDM_K64F
``` | /content/code_sandbox/boards/shields/inventek_eswifi/boards/frdm_k64f.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 31 |
```unknown
/*
*
*/
/*
* This file is intentionally empty. Please confer with shield documentation
* for instructions to use this shield.
*/
``` | /content/code_sandbox/boards/shields/esp_8266/esp_8266.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 28 |
```unknown
config SHIELD_ESP_8266
def_bool $(shields_list_contains,esp_8266)
config SHIELD_ESP_8266_ARDUINO
def_bool $(shields_list_contains,esp_8266_arduino)
config SHIELD_ESP_8266_MIKROBUS
def_bool $(shields_list_contains,esp_8266_mikrobus)
``` | /content/code_sandbox/boards/shields/esp_8266/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 82 |
```unknown
/*
*
*/
&mikrobus_serial {
status = "okay";
current-speed = <115200>;
esp8266 {
compatible = "espressif,esp-at";
status = "okay";
};
};
``` | /content/code_sandbox/boards/shields/esp_8266/esp_8266_mikrobus.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 48 |
```unknown
/*
*
*/
&arduino_serial {
status = "okay";
current-speed = <115200>;
esp8266 {
compatible = "espressif,esp-at";
status = "okay";
};
};
``` | /content/code_sandbox/boards/shields/esp_8266/esp_8266_arduino.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 46 |
```unknown
if SHIELD_ESP_8266 || \
SHIELD_ESP_8266_ARDUINO || \
SHIELD_ESP_8266_MIKROBUS
if NETWORKING
choice WIFI_ESP_AT_VERSION
default WIFI_ESP_AT_VERSION_1_7
depends on WIFI_ESP_AT
endchoice
orsource "boards/*.defconfig"
endif # NETWORKING
endif # SHIELD_ESP_8266 || \
# SHIELD_ESP_8266_ARDUINO || \
# SHIELD_ESP_8266_MIKROBUS
``` | /content/code_sandbox/boards/shields/esp_8266/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 126 |
```unknown
#
#
if BOARD_SAM4E_XPRO
config NET_L2_ETHERNET
default n
config ETH_SAM_GMAC
default n
config USART_SAM
default y
endif # BOARD_SAM4E_XPRO
``` | /content/code_sandbox/boards/shields/esp_8266/boards/sam4e_xpro.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 51 |
```unknown
/*
*
*/
&pinctrl {
usart1_esp_wifi: usart1_esp_wifi {
group1 {
pinmux = <PA21A_USART1_RXD>,
<PA22A_USART1_TXD>;
};
};
};
&usart1 {
status = "okay";
current-speed = <115200>;
pinctrl-0 = <&usart1_esp_wifi>;
pinctrl-names = "default";
esp8266 {
compatible = "espressif,esp-at";
status = "okay";
};
};
``` | /content/code_sandbox/boards/shields/esp_8266/boards/sam4e_xpro.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 122 |
```unknown
#
#
if BOARD_DISCO_L475_IOT1
config WIFI_ESWIFI
default n
endif # BOARD_DISCO_L475_IOT1
``` | /content/code_sandbox/boards/shields/esp_8266/boards/disco_l475_iot1.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 33 |
```unknown
/*
*
*/
/* ENET MUST be disabled because share
* pins with UART-3
*/
&enet_mac {
status = "disabled";
};
&enet_mdio {
status = "disabled";
};
&enet_ptp_clock {
status = "disabled";
};
``` | /content/code_sandbox/boards/shields/esp_8266/boards/frdm_k64f.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 54 |
```unknown
/*
*
*/
&pinctrl {
uart2_esp8266: uart2_esp8266 {
group0 {
pinmux = <PC1MFP_UART2_TXD>,
<PC0MFP_UART2_RXD>,
<PC3MFP_UART2_nRTS>,
<PC2MFP_UART2_nCTS>;
};
};
};
&uart2 {
status = "okay";
current-speed = <115200>;
hw-flow-control;
pinctrl-0 = <&uart2_esp8266>;
pinctrl-names = "default";
esp8266: esp8266 {
compatible = "espressif,esp-at";
reset-gpios = <&gpioc 4 GPIO_ACTIVE_LOW>;
status = "okay";
};
};
&gpioc {
status = "okay";
};
``` | /content/code_sandbox/boards/shields/esp_8266/boards/numaker_pfm_m467.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 183 |
```restructuredtext
.. _inventek_eswifi_shield:
Inventek es-WIFI Shield
#######################
Overview
********
The es-WIFI (embedded Serial-to-WiFi) modules are devices developed by Inventek
Systems. It integrates WIFI and optionally Bluetooth Low Energy. The es-WIFI
devices can run Cypress WICED or Inventek's IWIN (Inventek Systems Wireless
Interoperability Network) AT commands set. The current es-WIFI driver is able
to use one of two serial interfaces: SPI or UART.
The Zephyr es-WIFI drivers was implemented using ISM43362-M3G-L44 with SPI
interface. The UART was implemented with ISM4343-WBM-L151. Besides that,
user can reprogram the modules to switch from one interface type to another
by the JTAG pin header.
ISMART4343C-EVB
===============
The `ISMART4343C-EVB`_ is a development Kit with Arduino Uno R3 compatible
shield. It allows evaluate es-WIFI modules with SPI or UART interface. For
UART interface the `inventek_eswifi_arduino_uart`_ must be selected. For
SPI interface the `inventek_eswifi_arduino_spi`_ must be enabled. The EVB
can use 5V from Arduino header, if board provide it, J17 position 1-2.
Otherwise, J17 2-3 will select USB-5V. More information can be found at
`ISMART4343C-EVB Users Manual`_.
.. note::
The Inventek's EVBs signals are 3.3V only.
.. image:: ismart4343c-evb.jpg
:align: center
:alt: ISMART4343C-EVB
Pins Assignment of the ISMART EVBs
==================================
The below table presents signals by interface. The UART switch SW3 must be on
position 3 to enable RX/TX signals when using es-WIFI with UART firmware.
To enable full control by Arduino header user should do some manual wiring.
The signals from D3 up to D7 are not connected by default on the Inventek's
shield. These signals marked as optional can help on development. The current
driver do not handle that signals and are simple suggestions and can be left
as is. Some arduino boards don't have NRST pin connected to a GPIO pin. The
recommendation is bend the NRST pin and make a wire to D6. WAKE-UP signal is
available at header J26 pin 1 and shield configuration uses D7 to control that
signal, user need do a wire connecting these two terminals. On the below
image is possible see suggested wiring connections.
.. image:: ismart4343c-evb-wiring.jpg
:align: center
:alt: ISMART4343C-EVB Wiring
+-----------------------+-----------+---------------------+
| Arduino Connector Pin | Function | Serial Connection |
+=======================+===========+=====================+
| D0 | UART RX | UART |
+-----------------------+-----------+---------------------+
| D1 | UART TX | UART |
+-----------------------+-----------+---------------------+
| D3 | CFG-1 | UART/SPI [optional] |
+-----------------------+-----------+---------------------+
| D4 | CFG-0 | UART/SPI [optional] |
+-----------------------+-----------+---------------------+
| D5 | BOOT-0 | UART/SPI [optional] |
+-----------------------+-----------+---------------------+
| D6 | NRST | UART/SPI [wiring] |
+-----------------------+-----------+---------------------+
| D7 | WAKE-UP | UART/SPI [wiring] |
+-----------------------+-----------+---------------------+
| D9 | CMD/RDY | SPI |
+-----------------------+-----------+---------------------+
| D10 | SPI CS | SPI |
+-----------------------+-----------+---------------------+
| D11 | SPI MOSI | SPI |
+-----------------------+-----------+---------------------+
| D12 | SPI MISO | SPI |
+-----------------------+-----------+---------------------+
| D13 | SPI SCK | SPI |
+-----------------------+-----------+---------------------+
Supported variations
====================
The below table suggests shield variation accordingly with end user
application. When a standard Arduino R3 connector is available on board, user
should select the matching shield configuration based on the serial interface
(SERIAL or SPI). The inventek_eswifi is available to allow users testing a
built-in module with dedicated <board>.overlay and <board>.defconfig files.
+-----------------------------+---------------------------------+-----------+
| Connector Standard | Shield Designation | Variation |
+=============================+=================================+===========+
| Without standard (overlay) | `inventek_eswifi`_ | 1 |
+-----------------------------+---------------------------------+-----------+
| Arduino by UART | `inventek_eswifi_arduino_uart`_ | 2 |
+-----------------------------+---------------------------------+-----------+
| Arduino by SPI | `inventek_eswifi_arduino_spi`_ | 3 |
+-----------------------------+---------------------------------+-----------+
Requirements
************
This shield requires a board which provides a configuration that allows an
UART or SPI interface and two or three GPIO. (see :ref:`shields` for more
details).
.. note::
Some boards may already have a network interface: Check network
documentation to understand how properly configure both interfaces.
To keep simple, you can keep only the WIFI interface enabled at
Networking -> Link Layer Options. This will avoid problems running
Zephyr samples.
Tested Boards
=============
+------------------------------+------------------------------+-----------+
| Board | Disabled Interface | Variation |
+==============================+==============================+===========+
| ATMEL sam_v71_xult/samv71q21 | Ethernet | 2 , 3 |
+------------------------------+------------------------------+-----------+
| ST nucleo_f767zi | Ethernet | 2 , 3 |
+------------------------------+------------------------------+-----------+
| ST disco_l475_iot1 | | - |
+------------------------------+------------------------------+-----------+
.. note::
ST disco_l475_iot1 already have an ISM43362 module with IWIN SPI
firmware. It doesn't need this shield to expose es-WIFI. It is only
used here as reference to demonstrate how configure an on-board
module.
Sample usage
************
The reference sample for WIFI is :zephyr:code-sample:`wifi-shell`. It allows you to use WIFI
shell to scan local Wireless networks. With the password you can pick,
connect and send ping.
Build and Programming
*********************
Set ``--shield <shield designator>`` when you invoke ``west build``.
.. zephyr-app-commands::
:zephyr-app: samples/net/wifi
:host-os: unix
:board: [sam_v71_xult/samv71q21 | nucleo_f767zi]
:shield: inventek_eswifi_arduino_uart
:goals: build flash
:compact:
.. zephyr-app-commands::
:zephyr-app: samples/net/wifi
:host-os: unix
:board: [sam_v71_xult/samv71q21 | nucleo_f767zi]
:shield: inventek_eswifi_arduino_spi
:goals: build flash
:compact:
.. zephyr-app-commands::
:zephyr-app: samples/net/wifi
:host-os: unix
:board: disco_l475_iot1
:goals: build flash
:compact:
References
**********
.. target-notes::
.. _ISMART4343C-EVB:
path_to_url
.. _ISMART4343C-EVB Users Manual:
path_to_url
.. _inventek_eswifi:
path_to_url
.. _inventek_eswifi_arduino_uart:
path_to_url
.. _inventek_eswifi_arduino_spi:
path_to_url
``` | /content/code_sandbox/boards/shields/inventek_eswifi/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,776 |
```unknown
/*
*
*/
/* File meant to be empty */
``` | /content/code_sandbox/boards/shields/wnc_m14a2a/wnc_m14a2a.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 11 |
```unknown
config SHIELD_WNC_M14A2A
def_bool $(shields_list_contains,wnc_m14a2a)
``` | /content/code_sandbox/boards/shields/wnc_m14a2a/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 28 |
```unknown
if SHIELD_WNC_M14A2A
if NETWORKING
config MODEM
default y
config MODEM_SHELL
default y
config MODEM_WNCM14A2A
default y
config UART_INTERRUPT_DRIVEN
default y
# extend retry timing to 20 seconds for LTE/LTE-M
config COAP_INIT_ACK_TIMEOUT_MS
default 20000
# Hack: disable IPv6 for now
config NET_IPV6
default n
config NET_CONFIG_NEED_IPV6
default n
endif # NETWORKING
endif # SHIELD_WNC_M14A2A
``` | /content/code_sandbox/boards/shields/wnc_m14a2a/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 127 |
```unknown
/*
*
*/
&pinctrl {
uart1_default_alt: uart1_default_alt {
group1 {
psels = <NRF_PSEL(UART_TX, 1, 14)>,
<NRF_PSEL(UART_RX, 1, 13)>,
<NRF_PSEL(UART_RTS, 1, 12)>,
<NRF_PSEL(UART_CTS, 1, 15)>;
};
};
uart1_sleep_alt: uart1_sleep_alt {
group1 {
psels = <NRF_PSEL(UART_TX, 1, 14)>,
<NRF_PSEL(UART_RX, 1, 13)>,
<NRF_PSEL(UART_RTS, 1, 12)>,
<NRF_PSEL(UART_CTS, 1, 15)>;
low-power-enable;
};
};
};
/*
* WNC-M14A2A shield uses an odd UART available on *some* Arduino-R3-compatible
* headers. It needs to be defined individually.
*/
&uart1 {
current-speed = <115200>;
hw-flow-control;
status = "okay";
pinctrl-0 = <&uart1_default_alt>;
pinctrl-1 = <&uart1_sleep_alt>;
pinctrl-names = "default", "sleep";
wnc_m14a2a: wncm14a2a {
status = "okay";
compatible = "wnc,m14a2a";
mdm-boot-mode-sel-gpios = <&arduino_header 7 GPIO_ACTIVE_HIGH>; /* D1 */
mdm-power-gpios = <&arduino_header 8 GPIO_ACTIVE_LOW>; /* D2 */
mdm-keep-awake-gpios = <&arduino_header 12 GPIO_ACTIVE_HIGH>; /* D6 */
mdm-reset-gpios = <&arduino_header 14 GPIO_ACTIVE_HIGH>; /* D8 */
mdm-shld-trans-ena-gpios = <&arduino_header 15 GPIO_ACTIVE_HIGH>; /* D9 */
};
};
``` | /content/code_sandbox/boards/shields/wnc_m14a2a/boards/nrf52840dk_nrf52840.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 453 |
```restructuredtext
.. _module_esp_8266:
ESP-8266 Modules
################
Overview
********
ESP-8266 radio is a cost-effective Wi-Fi SOC module which allows any
microcontrollers to easily access to WiFi network. This module supports
the standard IEEE802.11 b/g/n protocol, built-in complete TCP/IP protocol
stack. Users can use this series of modules to add networking capabilities
to existing devices.
The simplest module that uses ESP-8266 is ESP-01. This is a generic shield
configuration that allows any ESP-8266 module variation including ESP-12E/F.
.. image:: esp-01.jpg
:align: center
:alt: ESP-01
Pins Assignment of the ESP-01 Module
====================================
+---------------+-------------------------------------+
| Connector Pin | Function |
+===============+=====================================+
| GND | POWER GND |
+---------------+-------------------------------------+
| GPIO1 | U0_TXD |
+---------------+-------------------------------------+
| GPIO2 | |
+---------------+-------------------------------------+
| CHIP_EN | ENABLE (VDD = RUN, GND = LOW POWER) |
+---------------+-------------------------------------+
| GPIO0 | |
+---------------+-------------------------------------+
| EXT_RST | |
+---------------+-------------------------------------+
| GPIO3 | U0_RXD |
+---------------+-------------------------------------+
| VDD | POWER +3.3V |
+---------------+-------------------------------------+
Requirements
************
This shield requires a board which provides a configuration that allows an
UART interface. (see :ref:`shields` for more details).
.. note::
Sometimes boards declare standard headers like Arduino R3 but not define
all connections. Make sure that the board you are using have all
definitions to avoid build errors.
The ESP-8266 should be loaded with the `ESP8266 AT Bin`_ software which is
available at Espressif Systems web site. The ESP-01 module have up to 1MB of
flash and the last available stack that fits on this device is ESP8266 AT Bin
V1.6.2. This version is command compatible with ESP8266 AT Bin 1.7.x which is
the minimal version supported by the ESP WIFI driver.
The ESP-8266 Modules that have 2MB or more is highly recommended upgrade to
version 1.7.x for better future compatibility.
This tutorial won't explain how firmware must be upgraded. However, it will
present some tips to easily success. The ESP WIFI was tested with an ESP-01
with 1MB flash using Boot Mode and with Flash size 8Mbit: 512KB + 512KB. The
ESP8266 AT Bin 1.7.x available requires the following partition configuration
to works:
.. image:: esp_at_173.jpg
:align: center
:alt: ESP8266 AT Bin V1.7.3
- Tips
- Don't forget to erase Flash before upgrade
- Upgrade all binaries at same time.
- ESP-8266 bootloader won't send garbage. Try connect at 74880 bps if
you module have 26MHz crystal to detect boot fails.
.. note::
Boards that already have a network interface: Check network
documentation to understand how properly configure both interfaces.
To keep simple, make sure WiFi is the only interface enabled at
Networking -> Link Layer Options. This will avoid problems running
Zephyr samples.
Supported variations
====================
The below table suggests shield variation accordingly with end user
application. When a standard connector (arduino, mikrobus) is available on
board, user should select the matching shield configuration. When esp_8266
shield is used with a board that doesn't feature a standard connector, a
dedicated <board>.overlay file should be provided. The remaining
configurations should be used based on the board standard headers available.
+-----------------------------+------------------------------+-----------+
| Connector Standard | Shield Designation | Variation |
+=============================+==============================+===========+
| Without standard (overlay) | `esp_8266`_ | 1 |
+-----------------------------+------------------------------+-----------+
| Arduino | `esp_8266_arduino`_ | 2 |
+-----------------------------+------------------------------+-----------+
| MikroBus | `esp_8266_mikrobus`_ | 3 |
+-----------------------------+------------------------------+-----------+
Build and Programming
*********************
Set ``--shield <shield designation>`` when you invoke ``west build``.
To build shield with specific overlay:
.. zephyr-app-commands::
:zephyr-app: samples/net/wifi
:board: sam4e_xpro
:shield: esp_8266
:goals: build flash
To build shield with standard headers:
.. zephyr-app-commands::
:zephyr-app: samples/net/wifi
:board: [disco_l475_iot1 | frdm_k64f | lpcxpresso55s69_ns | nucleo_f767zi]
:shield: [esp_8266_arduino | esp_8266_mikrobus]
:goals: build flash
References
**********
.. target-notes::
.. _ESP8266 AT Bin:
path_to_url
.. _esp_8266:
path_to_url
.. _esp_8266_arduino:
path_to_url
.. _esp_8266_mikrobus:
path_to_url
``` | /content/code_sandbox/boards/shields/esp_8266/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,186 |
```unknown
/*
*
*/
/*
* WNC-M14A2A shield uses an odd UART available on *some* Arduino-R3-compatible
* headers. It needs to be defined individually.
*/
&uart2 {
current-speed = <115200>;
hw-flow-control;
status = "okay";
wnc_m14a2a: wncm14a2a {
status = "okay";
compatible = "wnc,m14a2a";
mdm-boot-mode-sel-gpios = <&arduino_header 7 GPIO_ACTIVE_HIGH>; /* D1 */
mdm-power-gpios = <&arduino_header 8 GPIO_ACTIVE_LOW>; /* D2 */
mdm-keep-awake-gpios = <&arduino_header 12 GPIO_ACTIVE_HIGH>; /* D6 */
mdm-reset-gpios = <&arduino_header 14 GPIO_ACTIVE_HIGH>; /* D8 */
mdm-shld-trans-ena-gpios = <&arduino_header 15 GPIO_ACTIVE_HIGH>; /* D9 */
};
};
``` | /content/code_sandbox/boards/shields/wnc_m14a2a/boards/frdm_k64f.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 219 |
```unknown
config SHIELD_SEMTECH_SX1272MB2DAS
def_bool $(shields_list_contains,semtech_sx1272mb2das)
``` | /content/code_sandbox/boards/shields/semtech_sx1272mb2das/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_sx1272mb2das;
};
};
&arduino_spi {
status = "okay";
cs-gpios = <&arduino_header 16 GPIO_ACTIVE_LOW>; /* D10 */
lora_semtech_sx1272mb2das: lora@0 {
compatible = "semtech,sx1272";
reg = <0x0>;
spi-max-frequency = <3000000>;
reset-gpios = <&arduino_header 0 GPIO_ACTIVE_HIGH>; /* A0 */
dio-gpios = <&arduino_header 8 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>, /* DIO0 is D2 */
<&arduino_header 9 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>, /* DIO1 is D3 */
<&arduino_header 10 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>, /* DIO2 is D4 */
<&arduino_header 11 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>; /* DIO3 is D5 */
power-amplifier-output = "rfo";
};
};
``` | /content/code_sandbox/boards/shields/semtech_sx1272mb2das/semtech_sx1272mb2das.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 250 |
```unknown
/*
*
*
*/
&arduino_i2c {
lsm6dsl_x_nucleo_iks01a2_shub: lsm6dsl@6b {
compatible = "st,lsm6dsl";
reg = <0x6b>;
irq-gpios = <&arduino_header 10 GPIO_ACTIVE_HIGH>; /* D4 */
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_iks01a2/x_nucleo_iks01a2_shub.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 79 |
```unknown
config SHIELD_X_NUCLEO_IKS01A2
def_bool $(shields_list_contains,x_nucleo_iks01a2)
``` | /content/code_sandbox/boards/shields/x_nucleo_iks01a2/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 33 |
```restructuredtext
.. _semtech_sx1272mb2das:
Semtech SX1272MB2DAS LoRa Shield
################################
Overview
********
The Semtech SX1272MB2DAS LoRa shield is an Arduino
compatible shield based on the SX1272 LoRa transceiver
from Semtech.
More information about the shield can be found
at the `mbed SX1272MB2xAS website`_.
Pins Assignment of the Semtech SX1272MB2DAS LoRa Shield
=======================================================
+-----------------------+-----------------+
| Shield Connector Pin | Function |
+=======================+=================+
| A0 | SX1272 RESET |
+-----------------------+-----------------+
| D2 | SX1272 DIO0 |
+-----------------------+-----------------+
| D3 | SX1272 DIO1 |
+-----------------------+-----------------+
| D4 | SX1272 DIO2 |
+-----------------------+-----------------+
| D5 | SX1272 DIO3 |
+-----------------------+-----------------+
| D10 | SX1272 SPI NSS |
+-----------------------+-----------------+
| D11 | SX1272 SPI MOSI |
+-----------------------+-----------------+
| D12 | SX1272 SPI MISO |
+-----------------------+-----------------+
| D13 | SX1272 SPI SCK |
+-----------------------+-----------------+
The SX1272 signals DIO4 and DIO5 are not available at the shield connector.
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 semtech_sx1272mb2das`` when you invoke ``west build``. For
example:
.. zephyr-app-commands::
:zephyr-app: samples/subsys/lorawan/class_a
:board: nucleo_f429zi
:shield: semtech_sx1272mb2das
:goals: build
References
**********
.. target-notes::
.. _mbed SX1272MB2xAS website:
path_to_url
``` | /content/code_sandbox/boards/shields/semtech_sx1272mb2das/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 483 |
```unknown
/*
*
*
*/
/ {
aliases {
magn0 = &lsm303agr_magn_1e_x_nucleo_iks01a2;
accel0 = &lsm303agr_accel_19_x_nucleo_iks01a2;
accel1 = &lsm6dsl_6b_x_nucleo_iks01a2;
};
};
&arduino_i2c {
hts221_x_nucleo_iks01a2: hts221@5f {
compatible = "st,hts221";
reg = <0x5f>;
};
lps22hb_press_x_nucleo_iks01a2: lps22hb-press@5d {
compatible = "st,lps22hb-press";
reg = <0x5d>;
};
lsm6dsl_6b_x_nucleo_iks01a2: lsm6dsl@6b {
compatible = "st,lsm6dsl";
reg = <0x6b>;
irq-gpios = <&arduino_header 10 GPIO_ACTIVE_HIGH>; /* D4 */
};
lsm303agr_magn_1e_x_nucleo_iks01a2: lsm303agr-magn@1e {
compatible = "st,lis2mdl","st,lsm303agr-magn";
reg = <0x1e>;
irq-gpios = <&arduino_header 3 GPIO_ACTIVE_HIGH>; /* A3 */
};
lsm303agr_accel_19_x_nucleo_iks01a2: lsm303agr-accel@19 {
compatible = "st,lis2dh", "st,lsm303agr-accel";
reg = <0x19>;
irq-gpios = <&arduino_header 3 GPIO_ACTIVE_HIGH>; /* A3 */
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_iks01a2/x_nucleo_iks01a2.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 408 |
```unknown
/*
*
*/
/*
* On stm32mp157c_dk2 pin A3 is not mapped on a GPIO pin.
* Delete this optional property for shield/board compatibility
*/
&arduino_i2c {
lsm303agr_magn_1e_x_nucleo_iks01a2: lsm303agr-magn@1e {
/delete-property/ irq-gpios; /* A3 */
};
lsm303agr_accel_19_x_nucleo_iks01a2: lsm303agr-accel@19 {
/delete-property/ irq-gpios; /* A3 */
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_iks01a2/boards/stm32mp157c_dk2.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 131 |
```unknown
/*
*
*/
&arduino_spi {
status = "okay";
cs-gpios = <&arduino_header 16 GPIO_ACTIVE_LOW>; /* D10 */
zephyr_uhc0: max3421e@0 {
compatible = "maxim,max3421e_spi";
spi-max-frequency = <26000000>;
int-gpios = <&arduino_header 15 GPIO_ACTIVE_LOW>; /* D9 */
reset-gpios = <&arduino_header 13 GPIO_ACTIVE_LOW>; /* D7 */
status = "okay";
reg = <0>;
};
};
``` | /content/code_sandbox/boards/shields/max3421e/sparkfun_max3421e.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 125 |
```unknown
config SHIELD_SPARKFUN_MAX3421E
def_bool $(shields_list_contains,sparkfun_max3421e)
``` | /content/code_sandbox/boards/shields/max3421e/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 28 |
```restructuredtext
.. _x-nucleo-iks01a2:
X-NUCLEO-IKS01A2: MEMS Inertial and Environmental Multi sensor shield
#####################################################################
Overview
********
The X-NUCLEO-IKS01A2 is a motion MEMS and environmental sensor expansion board
for the STM32 Nucleo. It is equipped with Arduino UNO R3 connector layout, and
is designed around the LSM6DSL 3D accelerometer and 3D gyroscope, the LSM303AGR
3D accelerometer and 3D magnetometer, the HTS221 humidity and temperature sensor
and the LPS22HB pressure sensor.
The X-NUCLEO-IKS01A2 interfaces with the STM32 microcontroller via the I2C pin,
and it is possible to change the default I2C port.
.. image:: img/x-nucleo-iks01a2.jpg
:align: center
:alt: X-NUCLEO-IKS01A2
More information about the board can be found at the
`X-NUCLEO-IKS01A2 website`_.
Hardware
********
X-NUCLEO-IKS01A2 provides the following key features:
- LSM6DSL MEMS 3D accelerometer (2/4/8/16 g) and
3D gyroscope (125/245/500/1000/2000 dps)
- LM303AGR MEMS 3D accelerometer (2/4/8/16 g) and
MEMS3D magnetometer (50 gauss)
- LPS22HB MEMS pressure sensor, 260-1260 hPa absolute digital output barometer
- HTS221: capacitive digital relative humidity and temperature
- DIL24 socket for additional MEMS adapters and other sensors
- IC sensor hub features on LSM6DSL available
- Equipped with Arduino UNO R3 connector
- RoHS compliant
More information about X-NUCLEO-IKS01A2 can be found here:
- `X-NUCLEO-IKS01A2 databrief`_
Hardware Configuration
**********************
X-NUCLEO-IKS01A2 board connects the various devices on two separate I2C bus:
- LSM6DL is on I2C2
- LSM303AGR, LPS22HB, HTS221 are on I2C1
X-NUCLEO-IKS01A2 board can be configured in two different ways: Mode 1 and Mode 2
Mode 1: Standard Mode
=====================
In standard I2C mode the two buses are connected together. As a consequence, all devices on the shield
reside on the same I2C bus and are accessible from the main board through I2C bus.
The jumper configuration to activate this mode is:
- JP7 => 1-2, 3-4 (I2C1 = I2C2, I2Cx=GND)
- JP8 => 1-2, 3-4 (I2C1 = I2C2, I2Cx=GND)
Mode 2: SensorHub Mode
======================
In SensorHub mode LSM6DSL is connected to I2C2 and is accessible from the main board.
All the other devices are connected to LSM6DSL master through I2C1.
The jumper configuration to activate this mode is:
- JP7 => 2-3 (I2C1 = I2Cx)
- JP8 => 2-3 (I2C1 = I2Cx)
More information about X-NUCLEO-IKS01A2 configuration modes can be found in the
`X-NUCLEO-IKS01A2 databrief`_
Programming
***********
Two samples are provided as examples for ``x-nucleo-iks01a2`` shield:
- :zephyr:code-sample:`x-nucleo-iks01a2-std` sample application, to be used when the shield is configured
in Standard Mode
- :zephyr:code-sample:`x-nucleo-iks01a2-shub` sample application, to be used when the shield is configured
in SensorHub Mode
See also :ref:`shields` for more details.
References
**********
.. target-notes::
.. _X-NUCLEO-IKS01A2 website:
path_to_url
.. _X-NUCLEO-IKS01A2 databrief:
path_to_url
``` | /content/code_sandbox/boards/shields/x_nucleo_iks01a2/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 945 |
```unknown
config SHIELD_X_NUCLEO_IKS01A1
def_bool $(shields_list_contains,x_nucleo_iks01a1)
``` | /content/code_sandbox/boards/shields/x_nucleo_iks01a1/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 33 |
```restructuredtext
.. _max3421e_shield:
MAX3421E Shield
###############
Overview
********
Support for expansion boards (shields) based on MAX3421E USB Peripheral/Host
controller.
Sparkfun USB Host Shield
************************
Pins Assignment of the Shield Connector
=======================================
+-----------------------+-----------------------+-----------------------------+
| Shield Connector Pin | Function | MAX3421E Pin |
+=======================+=======================+=============================+
| D0 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D1 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D2 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D3 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D4 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D5 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D6 | not connected | |
+-----------------------+-----------------------+-----------------------------+
| D7 | RESET pin | |
+-----------------------+-----------------------+-----------------------------+
| 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 connected | |
+-----------------------+-----------------------+-----------------------------+
| D15 | not connected | |
+-----------------------+-----------------------+-----------------------------+
Programming
***********
Set ``--shield sparkfun_max3421e`` when you invoke ``west build`` or ``cmake``
in your Zephyr application.
``` | /content/code_sandbox/boards/shields/max3421e/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 508 |
```unknown
/*
*
*
*/
&arduino_i2c {
hts221_x_nucleo_iks01a1: hts221@5f {
compatible = "st,hts221";
reg = <0x5f>;
};
lps25hb_press_x_nucleo_iks01a1: lps25hb-press@5d {
compatible = "st,lps25hb-press";
reg = <0x5d>;
};
lis3mdl_magn_x_nucleo_iks01a1: lis3mdl-magn@1e {
compatible = "st,lis3mdl-magn";
reg = <0x1e>;
irq-gpios = <&arduino_header 5 GPIO_ACTIVE_HIGH>; /* DRDY on A5 */
};
lsm6ds0_x_nucleo_iks01a1: lsm6ds0@6b {
compatible = "st,lsm6ds0";
reg = <0x6b>;
};
};
``` | /content/code_sandbox/boards/shields/x_nucleo_iks01a1/x_nucleo_iks01a1.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 223 |
```unknown
config SHIELD_V2C_DAPLINK
def_bool $(shields_list_contains,v2c_daplink)
config SHIELD_V2C_DAPLINK_CFG
def_bool $(shields_list_contains,v2c_daplink_cfg)
``` | /content/code_sandbox/boards/shields/v2c_daplink/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 52 |
```unknown
/*
*
*/
/delete-node/ &itcm;
/ {
chosen {
zephyr,flash = &daplink_flash0_v2c_daplink_cfg;
};
soc {
daplink_flash0_v2c_daplink_cfg: flash@0 {
compatible = "soc-nv-flash";
reg = <0x00000000 DT_SIZE_M(1)>;
};
itcm_v2c_daplink_cfg: memory@10000000 {
compatible = "arm,itcm";
reg = <0x10000000 DT_SIZE_K(64)>;
};
};
};
&daplink_single_spi0 {
status = "okay";
sdhc0_v2c_daplink_cfg: sdhc@0 {
compatible = "zephyr,sdhc-spi-slot";
reg = <0>;
spi-max-frequency = <25000000>;
mmc {
compatible = "zephyr,sdmmc-disk";
status = "okay";
};
};
};
``` | /content/code_sandbox/boards/shields/v2c_daplink/v2c_daplink_cfg.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 227 |
```restructuredtext
.. _x-nucleo-iks01a1:
X-NUCLEO-IKS01A1: MEMS Inertial and Environmental Multi sensor shield
#####################################################################
Overview
********
The X-NUCLEO-IKS01A1 is a motion MEMS and environmental sensor
evaluation board system, compatible with the Arduino UNO R3 connector
layout. It includes an STMicroelectronics LSM6DS0 3-axis accelerometer
and 3-axis gyroscope, the LIS3MDL 3-axis magnetometer, the HTS221
humidity and temperature sensor, and the LPS25HB pressure sensor.
The X-NUCLEO-IKS01A1 interfaces with the main board via an I2C interface.
.. image:: img/x-nucleo-iks01a1.jpg
:align: center
:alt: X-NUCLEO-IKS01A
More information about the board can be found at the
`X-NUCLEO-IKS01A1 website`_.
Hardware
********
X-NUCLEO-IKS01A1 provides the following key features:
- LSM6DS0: MEMS 3D accelerometer (2/4/8 g) + 3D gyroscope (245/500/2000
dps)
- LIS3MDL: MEMS 3D magnetometer (4/ 8/ 12/ 16 gauss)
- LPS25HB: MEMS pressure sensor, 260-1260 hPa absolute digital output barometer
- HTS221: capacitive digital relative humidity and temperature
- DIL 24-pin socket available for additional MEMS adapters and other sensors
(UV index)
- Equipped with Arduino UNO R3 connector
- RoHS compliant
More information about X-NUCLEO-IKS01A1 can be found here:
- `X-NUCLEO-IKS01A1 data sheet`_
Programming
***********
An example on how to use the ``x-nucleo-iks01a1`` shield is available
in the :zephyr:code-sample:`x-nucleo-iks01a1` sample application documentation
(see :ref:`shields` for more details).
References
**********
.. target-notes::
.. _X-NUCLEO-IKS01A1 website:
path_to_url
.. _X-NUCLEO-IKS01A1 data sheet:
path_to_url
``` | /content/code_sandbox/boards/shields/x_nucleo_iks01a1/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 517 |
```unknown
/*
*
*/
&daplink_gpio0 {
status = "okay";
};
&daplink_qspi_mux {
status = "okay";
};
&flash0 {
/*
* Disable the on-board flash until the jedec,spi-nor driver supports
* multiple instances.
*/
status = "disabled";
};
&daplink_quad_spi0 {
status = "okay";
daplink_flash0_v2c_daplink: flash@0 {
compatible = "spansion,s25fl128s", "jedec,spi-nor";
reg = <0>;
spi-max-frequency = <80000000>;
size = <DT_SIZE_M(128)>;
jedec-id = [01 20 18];
};
};
&daplink_single_spi0 {
status = "okay";
sdhc0_v2c_daplink: sdhc@0 {
compatible = "zephyr,sdhc-spi-slot";
reg = <0>;
spi-max-frequency = <25000000>;
mmc {
compatible = "zephyr,sdmmc-disk";
status = "okay";
};
};
};
``` | /content/code_sandbox/boards/shields/v2c_daplink/v2c_daplink.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 249 |
```unknown
/*
*
*/
&arduino_spi {
status = "okay";
cs-gpios = <&arduino_header 16 GPIO_ACTIVE_LOW>; /* D10 */
mcp2515_keyestudio_can_bus_ks0411: can@0 {
compatible = "microchip,mcp2515";
spi-max-frequency = <1000000>;
int-gpios = <&arduino_header 14 GPIO_ACTIVE_LOW>; /* D8 */
status = "okay";
reg = <0x0>;
osc-freq = <16000000>;
can-transceiver {
max-bitrate = <1000000>;
};
};
};
/ {
chosen {
zephyr,canbus = &mcp2515_keyestudio_can_bus_ks0411;
};
};
``` | /content/code_sandbox/boards/shields/mcp2515/keyestudio_can_bus_ks0411.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 168 |
```restructuredtext
.. _v2c_daplink_shield:
ARM V2C-DAPLink for DesignStart FPGA
####################################
Overview
********
The `ARM V2C-DAPLink for DesignStart FPGA`_ shield can be used to provide
DAPLink debug access to the ARM DesignStart FPGA reference designs implemented
on the :ref:`arty`.
.. figure:: v2c_daplink.jpg
:align: center
:alt: V2C-DAPLink
V2C-DAPLink (Credit: ARM Ltd.)
In addition to DAPLink debug access, the V2C-DAPLink shield provides the
following hardware features:
- QSPI NOR flash
- Micro-SD card slot
Programming
***********
When using the V2C-DAPLink shield with the ``Cfg`` jumper (``J2``) open, the CPU
will boot from ITCM and flashing can be performed automatically. The console is
routed to USB connector ``J10`` on the :ref:`arty`. For example:
.. zephyr-app-commands::
:zephyr-app: samples/hello_world
:board: arty_a7_arm_designstart_m1
:shield: v2c_daplink
:goals: flash
When using the V2C-DAPLink shield with the ``Cfg`` jumper (``J2``) closed, the
CPU will boot from the V2C-DAPLink QSPI NOR flash. The console is routed to USB
connector ``J1`` on the V2C-DAPLink. Flashing needs to be done
manually by copying the resulting ``zephyr/zephyr.bin`` file to the USB mass
storage device provided by the V2C-DAPLink shield:
.. zephyr-app-commands::
:zephyr-app: samples/hello_world
:board: arty_a7_arm_designstart_m1
:shield: v2c_daplink_cfg
:goals: build
.. _ARM V2C-DAPLink for DesignStart FPGA:
path_to_url
``` | /content/code_sandbox/boards/shields/v2c_daplink/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 446 |
```unknown
config SHIELD_DFROBOT_CAN_BUS_V2_0
def_bool $(shields_list_contains,dfrobot_can_bus_v2_0)
config SHIELD_KEYESTUDIO_CAN_BUS_KS0411
def_bool $(shields_list_contains,keyestudio_can_bus_ks0411)
config SHIELD_ADAFRUIT_CAN_PICOWBELL
def_bool $(shields_list_contains,adafruit_can_picowbell)
``` | /content/code_sandbox/boards/shields/mcp2515/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 91 |
```unknown
/*
*
*/
&arduino_spi {
status = "okay";
cs-gpios = <&arduino_header 16 GPIO_ACTIVE_LOW>; /* D10 */
mcp2515_dfrobot_can_bus_v2_0: can@0 {
compatible = "microchip,mcp2515";
spi-max-frequency = <1000000>;
int-gpios = <&arduino_header 8 GPIO_ACTIVE_LOW>; /* D2 */
status = "okay";
reg = <0x0>;
osc-freq = <16000000>;
can-transceiver {
min-bitrate = <60000>;
max-bitrate = <1000000>;
};
};
};
/ {
chosen {
zephyr,canbus = &mcp2515_dfrobot_can_bus_v2_0;
};
};
``` | /content/code_sandbox/boards/shields/mcp2515/dfrobot_can_bus_v2_0.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 175 |
```unknown
/*
*
*/
&pico_spi {
status = "okay";
cs-gpios = <&pico_header 20 GPIO_ACTIVE_LOW>;
mcp2515_adafruit_can_picowbell: can@0 {
compatible = "microchip,mcp2515";
spi-max-frequency = <1000000>;
int-gpios = <&pico_header 21 GPIO_ACTIVE_LOW>;
status = "okay";
reg = <0x0>;
osc-freq = <16000000>;
can-transceiver {
max-bitrate = <1000000>;
};
};
};
/ {
chosen {
zephyr,canbus = &mcp2515_adafruit_can_picowbell;
};
};
``` | /content/code_sandbox/boards/shields/mcp2515/adafruit_can_picowbell.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 158 |
```unknown
config SHIELD_MIKROE_MCP2518FD_CLICK
def_bool $(shields_list_contains,mikroe_mcp2518fd_click)
``` | /content/code_sandbox/boards/shields/mikroe_mcp2518fd_click/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 33 |
```unknown
&mikrobus_spi {
cs-gpios = <&mikrobus_header 2 GPIO_ACTIVE_LOW>;
mcp2518fd_mikroe_mcp2518fd_click: mcp2518fd@0 {
compatible = "microchip,mcp251xfd";
status = "okay";
spi-max-frequency = <18000000>;
int-gpios = <&mikrobus_header 7 GPIO_ACTIVE_LOW>;
reg = <0x0>;
osc-freq = <40000000>;
};
};
/ {
chosen {
zephyr,canbus = &mcp2518fd_mikroe_mcp2518fd_click;
};
};
``` | /content/code_sandbox/boards/shields/mikroe_mcp2518fd_click/mikroe_mcp2518fd_click.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 148 |
```restructuredtext
.. _mikroe_mcp2518fd_click_shield:
MikroElektronika MCP2518FD Click shield
#######################################
Overview
--------
MCP2518FD Click shield has a MCP2518FD CAN FD controller via a SPI
interface and a high-speed ATA6563 CAN transceiver.
More information about the shield can be found at
`Mikroe MCP2518FD click`_.
Requirements
************
The shield uses a mikroBUS interface. The target board must define
a `mikrobus_spi` and `mikrobus_header` node labels
(see :ref:`shields` for more details). The target board must also
support level triggered interrupts.
Programming
***********
Set ``--shield mikroe_mcp2518fd_click`` when you invoke ``west build``,
for example:
.. zephyr-app-commands::
:zephyr-app: samples/drivers/can/counter
:board: lpcxpresso55s28
:shield: mikroe_mcp2518fd_click
:goals: build flash
References
**********
.. target-notes::
.. _Mikroe MCP2518FD click:
path_to_url
``` | /content/code_sandbox/boards/shields/mikroe_mcp2518fd_click/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 257 |
```unknown
config SHIELD_LS013B7DH03
def_bool $(shields_list_contains,ls013b7dh03)
``` | /content/code_sandbox/boards/shields/ls0xx_generic/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 27 |
```unknown
/*
*
*/
/ {
chosen {
zephyr,display = &ls0xx_ls013b7dh03;
};
};
&arduino_spi {
status = "okay";
cs-gpios = <&arduino_header 16 GPIO_ACTIVE_HIGH>; /* D10 */
ls0xx_ls013b7dh03: ls0xx@0 {
compatible = "sharp,ls0xx";
spi-max-frequency = <2000000>;
reg = <0>;
width = <128>;
height = <128>;
extcomin-gpios = <&arduino_header 14 GPIO_ACTIVE_HIGH>; /* D8 */
extcomin-frequency = <60>; /* required if extcomin-gpios is defined */
disp-en-gpios = <&arduino_header 12 GPIO_ACTIVE_HIGH>; /* D6 */
};
};
``` | /content/code_sandbox/boards/shields/ls0xx_generic/ls013b7dh03.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 179 |
```unknown
if SHIELD_LS013B7DH03
if DISPLAY
if LVGL
config LV_Z_VDB_SIZE
default 16
config LV_DPI_DEF
default 150
config LV_Z_BITS_PER_PIXEL
default 1
choice LV_COLOR_DEPTH
default LV_COLOR_DEPTH_1
endchoice
endif # LVGL
endif # DISPLAY
endif # SHIELD_LS013B7DH03
``` | /content/code_sandbox/boards/shields/ls0xx_generic/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 86 |
```restructuredtext
.. _ls0xx_generic_shield:
Sharp memory display generic shield
###################################
Overview
********
This is a generic shield for Sharp memory pixel LCD. It supports
displays of LS0XX type. These displays have an SPI interface and
few other pins. Note that the SCS is active high for this display.
The DISP pin controls whether to display memory
contents or show all white pixels, this can be connected
directly to VDD, to always display memory contents or connected
to a gpio. If devicetree contains ``disp-en-gpios`` then it will be set to
high during driver initialization. Display blanking apis can be used
to control it.
Sharp memory displays require toggling the VCOM signal periodically
to prevent a DC bias occurring in the panel as mentioned in the `appnote`_
and `datasheet`_. The DC bias can damage the LCD and reduce the life.
This signal must be supplied from either serial input (sw) or an external
signal on the EXTCOMIN pin.
Currently the driver only supports VCOM toggling using the EXTCOMIN pin
(EXTMODE pin is connected to VDD).
When ``extcomin-gpios`` is defined, driver starts a thread which will
toggle EXTCOMIN at ``extcomin-frequency`` frequency. Higher frequency
gives better contrast while lower frequency saves power.
To use a different method of toggling for example pwm, user may not
define ``extcomin-gpios`` and implement their preferred method in
application code.
Pins Assignment of the Generic Sharp memory Display Shield
==========================================================
+---------------+---------------------------------------------------------+
| Pin | Function |
+===============+=========================================================+
| SCS | Serial Slave Select |
+---------------+---------------------------------------------------------+
| SI | Serial Data Input |
+---------------+---------------------------------------------------------+
| SCLK | Serial Clock Input |
+---------------+---------------------------------------------------------+
| EXTCOMIN | VCOM Inversion Polarity Input (VCOM can be controlled |
| | through SW) |
+---------------+---------------------------------------------------------+
| DISP | Display ON/OFF switching signal (Can be connected |
| | directly to VDD) |
+---------------+---------------------------------------------------------+
| EXTMODE | COM Inversion Selection |
+---------------+---------------------------------------------------------+
Current supported displays
==========================
Following displays are supported but shield only exists
for LS013B7DH03. Other shields can be added by using the LS013B7DH03 as
a reference and changing the width, height, etc configurations.
LS012B7DD01
LS012B7DD06
LS013B7DH03
LS013B7DH05
LS013B7DH06
LS027B7DH01A
LS032B7DD02
LS044Q7DH01
+----------------------+------------------------------+
| Display | Shield Designation |
| | |
+======================+==============================+
| LS013B7DH03 | ls013b7dh03 |
+----------------------+------------------------------+
Requirements
************
This shield can only be used with a board that provides a configuration
for Arduino connectors and defines node aliases for SPI and GPIO interfaces
(see :ref:`shields` for more details).
Programming
***********
Set ``--shield ls013b7dh03`` when you invoke ``west build``. For example:
.. zephyr-app-commands::
:zephyr-app: samples/subsys/display/lvgl
:board: nrf52840dk/nrf52840
:shield: ls013b7dh03
:goals: build
References
**********
.. target-notes::
.. _appnote:
path_to_url
.. _datasheet:
path_to_url
``` | /content/code_sandbox/boards/shields/ls0xx_generic/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 797 |
```unknown
config SHIELD_SPARKFUN_CARRIER_ASSET_TRACKER
def_bool $(shields_list_contains,sparkfun_carrier_asset_tracker)
``` | /content/code_sandbox/boards/shields/sparkfun_carrier_asset_tracker/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 30 |
```unknown
if SHIELD_SPARKFUN_CARRIER_ASSET_TRACKER
config SERIAL
default y
config UART_INTERRUPT_DRIVEN
default y
config UART_ASYNC_API
default y
config I2C
default y
config SPI
default y
endif # SHIELD_SPARKFUN_CARRIER_ASSET_TRACKER
``` | /content/code_sandbox/boards/shields/sparkfun_carrier_asset_tracker/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 66 |
```unknown
/*
*
*/
/ {
aliases {
modem-uart = µmod_1_uart;
modem = &modem;
};
};
µmod_1_uart {
current-speed = <115200>;
hw-flow-control;
status = "okay";
modem: sara_r5 {
compatible = "u-blox,sara-r5";
mdm-power-gpios = <µmod_header 7 0>; /* G2 */
mdm-reset-gpios = <µmod_header 12 0>; /* D6 */
status = "okay";
};
};
µmod_0_spi {
status = "okay";
/* G0 (SD_CS) */
cs-gpios = <µmod_header 5 GPIO_ACTIVE_LOW>;
sdhc0: sdhc@0 {
compatible = "zephyr,sdhc-spi-slot";
reg = <0>;
status = "okay";
mmc {
compatible = "zephyr,sdmmc-disk";
status = "okay";
};
spi-max-frequency = <DT_FREQ_M(8)>;
};
};
µmod_0_i2c {
max17048: max17048@36 {
compatible = "maxim,max17048";
reg = <0x36>;
status = "okay";
};
};
``` | /content/code_sandbox/boards/shields/sparkfun_carrier_asset_tracker/sparkfun_carrier_asset_tracker.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 300 |
```restructuredtext
.. _mcp2515_shield:
Microchip MCP2515 CAN bus shields
#################################
Zephyr supports a couple of different shields carrying the Microchip `MCP2515`_
Stand-Alone CAN Controller with SPI Interface.
DFRobot CAN BUS Shield V2.0
***************************
Overview
--------
The DFRobot CAN BUS shield supports the Microchip MCP2515 stand-alone CAN
controller and JTA1050 high speed CAN transceiver. The shield has an Arduino
Uno R3 compatible hardware interface.
.. figure:: dfrobot_can_bus_v2_0.jpg
:align: center
:alt: DFRobot_CAN_BUS_V2_0_SHIELD
Hardware
--------
- MCP2515
- Stand-Alone CAN 2.0B Controller
- Up to 1Mb/s baud rate
- Standard and extended data and remote frames
- 3x Tx Buffers
- 2x Rx Buffers
- 6x 29-bit Filters
- 2x 29-bit Masks
- Interrupt output
- One shot mode
- High speed SPI interface (10 MHz)
- TJA1050
- Fully compatible with the ISO 11898 standard
- High speed (up to 1 Mbaud)
- Connectivity
- Industrial standard DB9 terminal (CAN)
- Screw terminals (CAN)
- Integrated MicroSD socket for data storage (SPI)
- Arduino Uno R3 compatible (SPI)
+-------+-----------------------+---------------------------+
| Name | Function | Usage |
+=======+=======================+===========================+
| A0 | None | |
+-------+-----------------------+---------------------------+
| A1 | None | |
+-------+-----------------------+---------------------------+
| A2 | None | |
+-------+-----------------------+---------------------------+
| A3 | None | |
+-------+-----------------------+---------------------------+
| A4 | None | |
+-------+-----------------------+---------------------------+
| A5 | None | |
+-------+-----------------------+---------------------------+
| D0 | RX | Ext. header only |
+-------+-----------------------+---------------------------+
| D1 | TX | Ext. header only |
+-------+-----------------------+---------------------------+
| D2 | GPIO_ACTIVE_LOW | MCP2515 - INT |
+-------+-----------------------+---------------------------+
| D3 | None | |
+-------+-----------------------+---------------------------+
| D4 | SPI-CS | MicroSD |
+-------+-----------------------+---------------------------+
| D5 | None | |
+-------+-----------------------+---------------------------+
| D6 | None | |
+-------+-----------------------+---------------------------+
| D7 | None | |
+-------+-----------------------+---------------------------+
| D8 | None | |
+-------+-----------------------+---------------------------+
| D9 | None | |
+-------+-----------------------+---------------------------+
| D10 | SPI-CS | MCP2515 |
+-------+-----------------------+---------------------------+
| D11 | SPI-MOSI | MCP2515 / MicroSD |
+-------+-----------------------+---------------------------+
| D12 | SPI-MISO | MCP2515 / MicroSD |
+-------+-----------------------+---------------------------+
| D13 | SPI-CLK | MCP2515 / MicroSD |
+-------+-----------------------+---------------------------+
| D14 | I2C-SDA | Ext. header only |
+-------+-----------------------+---------------------------+
| D15 | I2C_SCL | Ext. header only |
+-------+-----------------------+---------------------------+
- Power Supply
- 3.3V ~ 5V
- Components
- Power switch
- Power LED
- RX0BF LED
- RX1BF LED
For more information about the DFRobot CAN-BUS V2.0 shield:
- `DFRobot Website`_
- `DFRobot CAN BUS Shield V2.0 schematic`_
- `MCP2515 Datasheet`_
- `TJA1050 Datasheet`_
Keyestudio CAN-BUS Shield (KS0411)
**********************************
Overview
--------
The Keyestudio CAN BUS shield supports the Microchip MCP2515 stand-alone CAN
controller and MCP2551 high speed CAN transceiver. The shield has an Arduino
Uno R3 compatible hardware interface.
.. figure:: keyestudio_can_bus_ks0411.jpg
:align: center
:alt: Keyestudio CAN-BUS Shield (KS0411)
Keyestudio CAN-BUS Shield (KS0411) (Credit: Keyestudio)
Hardware
--------
- MCP2515
- Stand-Alone CAN 2.0B Controller
- Up to 1Mb/s baud rate
- Standard and extended data and remote frames
- 3x Tx Buffers
- 2x Rx Buffers
- 6x 29-bit Filters
- 2x 29-bit Masks
- Interrupt output
- One shot mode
- High speed SPI interface (10 MHz)
- MCP2551
- Fully compatible with the ISO 11898 standard
- High speed (up to 1 Mbaud)
- Connectivity
- Industrial standard DB9 terminal (CAN)
- Pin headers (CAN)
- Integrated MicroSD socket for data storage (SPI)
- Arduino Uno R3 compatible (SPI)
+-------+-----------------------+---------------------------+
| Name | Function | Usage |
+=======+=======================+===========================+
| A0 | None | |
+-------+-----------------------+---------------------------+
| A1 | None | |
+-------+-----------------------+---------------------------+
| A2 | None | |
+-------+-----------------------+---------------------------+
| A3 | None | |
+-------+-----------------------+---------------------------+
| A4 | None | |
+-------+-----------------------+---------------------------+
| A5 | None | |
+-------+-----------------------+---------------------------+
| D0 | RX | Ext. header only |
+-------+-----------------------+---------------------------+
| D1 | TX | Ext. header only |
+-------+-----------------------+---------------------------+
| D2 | None | |
+-------+-----------------------+---------------------------+
| D3 | None | |
+-------+-----------------------+---------------------------+
| D4 | None | |
+-------+-----------------------+---------------------------+
| D5 | None | |
+-------+-----------------------+---------------------------+
| D6 | None | |
+-------+-----------------------+---------------------------+
| D7 | None | |
+-------+-----------------------+---------------------------+
| D8 | GPIO_ACTIVE_LOW | MCP2515 - INT |
+-------+-----------------------+---------------------------+
| D9 | SPI-CS | MicroSD |
+-------+-----------------------+---------------------------+
| D10 | SPI-CS | MCP2515 |
+-------+-----------------------+---------------------------+
| D11 | SPI-MOSI | MCP2515 / MicroSD |
+-------+-----------------------+---------------------------+
| D12 | SPI-MISO | MCP2515 / MicroSD |
+-------+-----------------------+---------------------------+
| D13 | SPI-CLK | MCP2515 / MicroSD |
+-------+-----------------------+---------------------------+
| D14 | I2C-SDA | Ext. header only |
+-------+-----------------------+---------------------------+
| D15 | I2C_SCL | Ext. header only |
+-------+-----------------------+---------------------------+
- Power Supply
- 5.0VDC
For more information about the Keyestudio CAN-BUS shield:
- `Keyestudio Website`_
- `Keyestudio Wiki`_
- `MCP2515 Datasheet`_
- `MCP2551 Datasheet`_
Adafruit PiCowbell CAN Bus Shield for Pico
******************************************
Overview
--------
The Adafruit PiCowbell CAN Bus Shield uses the Microchip MCP2515 controller
with an TJA1051/3 transceiver. This shield is built for the Raspberry Pi Pico
and uses the SPI interface. It also contains a Qwiic connector to add support
for a sensor.
.. figure:: adafruit_can_picowbell.jpg
:align: center
:alt: Adafruit PiCowbell CAN Bus Shield
Adafruit PiCowbell CAN Bus Shield
Hardware
--------
- MCP2515
- Stand-Alone CAN 2.0B Controller
- Up to 1Mb/s baud rate
- Standard and extended data and remote frames
- 3x Tx Buffers
- 2x Rx Buffers
- 6x 29-bit Filters
- 2x 29-bit Masks
- Interrupt output
- One shot mode
- High speed SPI interface (10 MHz)
- TJA1051
- Fully compatible with the ISO 11898-2:2016, "SAE J2284-1" & "SAE J2284-5" standards
- Supports CAN FD
- Fast data rates (up to 5 Mbit/s)
- Connectivity
- Terminal Block - 3-pin 3.5mm (CAN)
- Raspberry Pi Pico compatible (SPI)
+-------+-----------------------+---------------------------+
| Name | Function | Usage |
+=======+=======================+===========================+
| GP0 | None | |
+-------+-----------------------+---------------------------+
| GP1 | None | |
+-------+-----------------------+---------------------------+
| GP2 | None | |
+-------+-----------------------+---------------------------+
| GP3 | None | |
+-------+-----------------------+---------------------------+
| GP4 | None | |
+-------+-----------------------+---------------------------+
| GP5 | None | |
+-------+-----------------------+---------------------------+
| GP6 | None | |
+-------+-----------------------+---------------------------+
| GP7 | None | |
+-------+-----------------------+---------------------------+
| GP8 | None | |
+-------+-----------------------+---------------------------+
| GP9 | None | |
+-------+-----------------------+---------------------------+
| GP10 | None | |
+-------+-----------------------+---------------------------+
| GP11 | None | |
+-------+-----------------------+---------------------------+
| GP12 | None | |
+-------+-----------------------+---------------------------+
| GP13 | None | |
+-------+-----------------------+---------------------------+
| GP14 | None | |
+-------+-----------------------+---------------------------+
| GP15 | None | |
+-------+-----------------------+---------------------------+
| GP16 | SPI-MISO | MCP2515 |
+-------+-----------------------+---------------------------+
| GP17 | None | |
+-------+-----------------------+---------------------------+
| GP18 | SPI-SCK | MCP2515 |
+-------+-----------------------+---------------------------+
| GP19 | SPI-MOSI | MCP2515 |
+-------+-----------------------+---------------------------+
| GP20 | SPI-CS | MCP2515 |
+-------+-----------------------+---------------------------+
| GP21 | GPIO_ACTIVE_LOW | MCP2515 - INT |
+-------+-----------------------+---------------------------+
| GP22 | None | |
+-------+-----------------------+---------------------------+
| GP23 | None | |
+-------+-----------------------+---------------------------+
| GP24 | None | |
+-------+-----------------------+---------------------------+
| GP25 | None | |
+-------+-----------------------+---------------------------+
| GP26 | None | |
+-------+-----------------------+---------------------------+
| GP27 | None | |
+-------+-----------------------+---------------------------+
| GP28 | None | |
+-------+-----------------------+---------------------------+
- Power Supply
- 3.3V ~ 5V
For more information about the Adafruit PiCowbell CAN Bus shield:
- `Adafruit Website`_
- `MCP2515 Datasheet`_
- `TJA1051 Datasheet`_
Programming
***********
Set ``--shield dfrobot_can_bus_v2_0`` or ``--shield keyestudio_can_bus_ks0411``
or ``--shield adafruit_can_picowbell`` when you invoke ``west build`` or ``cmake`` in your Zephyr application. For
example:
.. zephyr-app-commands::
:zephyr-app: samples/drivers/can/counter
:tool: all
:board: nrf52dk/nrf52832
:shield: dfrobot_can_bus_v2_0
:goals: build flash
.. zephyr-app-commands::
:zephyr-app: samples/drivers/can/counter
:tool: all
:board: nrf52840dk/nrf52840
:shield: keyestudio_can_bus_ks0411
:goals: build flash
.. zephyr-app-commands::
:zephyr-app: samples/drivers/can/counter
:tool: all
:board: rpi_pico
:shield: adafruit_can_picowbell
:goals: build
.. _DFRobot Website:
path_to_url
.. _DFRobot CAN BUS Shield V2.0 schematic:
path_to_url
.. _MCP2515:
path_to_url
.. _Keyestudio Website:
path_to_url
.. _Keyestudio Wiki:
path_to_url
.. _MCP2515 Datasheet:
path_to_url
.. _TJA1050 Datasheet:
path_to_url
.. _MCP2551 Datasheet:
path_to_url
.. _Adafruit Website:
path_to_url#technical-details
.. _TJA1051 Datasheet:
path_to_url
``` | /content/code_sandbox/boards/shields/mcp2515/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 3,153 |
```unknown
config SHIELD_PMOD_ACL
def_bool $(shields_list_contains,pmod_acl)
``` | /content/code_sandbox/boards/shields/pmod_acl/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 20 |
```unknown
/*
*
*/
&pmod_spi {
status = "okay";
adxl345_pmod_acl: adxl345@0 {
compatible = "adi,adxl345";
reg = <0x0>;
spi-max-frequency = <DT_FREQ_M(1)>;
status = "okay";
};
};
``` | /content/code_sandbox/boards/shields/pmod_acl/pmod_acl.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 68 |
```unknown
/*
*
*/
/ {
aliases {
accel0 = &adxl345_pmod_acl;
};
};
``` | /content/code_sandbox/boards/shields/pmod_acl/boards/apard32690_max32690_m4.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 25 |
```restructuredtext
.. _sparkfun_carrier_asset_tracker:
Sparkfun SparkFun MicroMod Asset Tracker Shield
###############################################
Overview
********
The SparkFun MicroMod Asset Tracker Carrier Shield is part of the Sparkfun
Micromod standard, a modular interface ecosystem that uses the M.2 standard
to mix and match your choice of processor with specific Functions Boards.
The Asset Tracker Carrier Shield is built around the u-blox SARA-R510M8S
module, which offers Secure Cloud LTE-M and NB-IoT data communication for
multi-regional use and GNSS capabilities via an integrated u-blox M8 GNSS
receiver for accurate positioning information.
Besides, this shield has an integrated ICM-20948 Inertial Measurement Unit
(IMU) for Nine Degree-Of-Freedom, a built-in micro-SD card socket for data
logging as well as a nano SIM card port.
.. figure:: img/sparkfun_carrier_asset_tracker.webp
:align: center
:alt: Sparkfun SparkFun MicroMod Asset Tracker Shield
Sparkfun SparkFun MicroMod Asset Tracker Shield (Credit: Sparkfun)
More information about the shield can be found at the `SparkFun MicroMod
Asset Tracker guide website`_.
Pins Assignment of Sparkfun SparkFun MicroMod Asset Tracker Shield
==================================================================
The SparkFun MicroMod Asset Tracker Carrier Shield uses a 76 pins M.2
connector. The following table depicts the interfaces and pins supported:
by Zephyr:
+-----------------------+---------------------------------+
| Shield Connector Pin | Function |
+=======================+=================================+
| micromod_1_uart alias | UART 1 (with CTS and RTS pins) |
+-----------------------+---------------------------------+
| micromod_2_uart alias | UART 2 |
+-----------------------+---------------------------------+
| micromod_0_i2c alias | i2c 0 |
+-----------------------+---------------------------------+
| micromod_1_i2c alias | i2c 1 |
+-----------------------+---------------------------------+
| micromod_0_spi alias | SPI 0 |
+-----------------------+---------------------------------+
| A0 | Analog pin |
+-----------------------+---------------------------------+
| A1 | Analog pin |
+-----------------------+---------------------------------+
| D0 | Digital pin |
+-----------------------+---------------------------------+
| D1/CAM_TRIG | Digital pin |
+-----------------------+---------------------------------+
| I2C_INT# | i2c interrupt pin |
+-----------------------+---------------------------------+
| G0/BUS0 | General purpose pin |
+-----------------------+---------------------------------+
| G1/BUS1 | General purpose pin |
+-----------------------+---------------------------------+
| G2/BUS2 | General purpose pin |
+-----------------------+---------------------------------+
| G3/BUS3 | General purpose pin |
+-----------------------+---------------------------------+
| G4/BUS4 | General purpose pin |
+-----------------------+---------------------------------+
| G5/BUS5 | General purpose pin |
+-----------------------+---------------------------------+
| G6/BUS6 | General purpose pin |
+-----------------------+---------------------------------+
| G7/BUS7 | General purpose pin |
+-----------------------+---------------------------------+
| G8 | General purpose pin |
+-----------------------+---------------------------------+
| G9/ADC_D-/CAM_HSYNC | General purpose pin |
+-----------------------+---------------------------------+
| G10/ADC_D+/CAM_VSYNC | General purpose pin |
+-----------------------+---------------------------------+
| G11/SWO | General purpose pin |
+-----------------------+---------------------------------+
| SPI_CS | General purpose pin |
+-----------------------+---------------------------------+
A detailed definition of the Micromod standard can be found on the
`Micromod specification website`_
Requirements
************
This shield can only be used with a board which provides a configuration for
Micromod connectors and defines node aliases for UART, I2C and SPI interfaces (see
:ref:`shields` for more details).
Programming
***********
Set ``--shield sparkfun_carrier_asset_tracker`` when you invoke ``west build``. For
example:
.. zephyr-app-commands::
:zephyr-app: samples/net/cellular_modem/
:board: micromod/nrf52840
:shield: sparkfun_carrier_asset_tracker
:goals: build
References
**********
.. target-notes::
.. _SparkFun MicroMod Asset Tracker guide website:
path_to_url
.. _Micromod specification website:
path_to_url
``` | /content/code_sandbox/boards/shields/sparkfun_carrier_asset_tracker/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 996 |
```unknown
config SHIELD_LCD_PAR_S035
def_bool $(shields_list_contains,lcd_par_s035_8080)
``` | /content/code_sandbox/boards/shields/lcd_par_s035/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 26 |
```restructuredtext
.. pmod_acl:
Digilent Pmod ACL
#################
Overview
********
The Digilent Pmod ACL is a 3-axis digital accelerometer module powered by the
Analog Devices ADXL345.
Programming
***********
Set ``--shield pmod_acl`` when you invoke ``west build``. For example:
.. zephyr-app-commands::
:zephyr-app: samples/sensor/sensor_shell
:board: apard32690/max32690/m4
:shield: pmod_acl
:goals: build
Requirements
************
This shield can only be used with a board which provides a configuration
for Pmod connectors and defines node aliases for SPI and GPIO interfaces
(see :ref:`shields` for more details).
References
**********
- `Pmod ACL product page`_
- `Pmod ACL reference manual`_
- `Pmod ACL schematic`_
- `ADXL345 product page`_
- `ADXL345 data sheet`_
.. _Pmod ACL product page:
path_to_url
.. _Pmod ACL reference manual:
path_to_url
.. _Pmod ACL schematic:
path_to_url
.. _ADXL345 product page:
path_to_url
.. _ADXL345 data sheet:
path_to_url
``` | /content/code_sandbox/boards/shields/pmod_acl/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 272 |
```unknown
if SHIELD_LCD_PAR_S035
if LVGL
# Enable double buffering
config LV_Z_DOUBLE_VDB
default y
config LV_Z_BITS_PER_PIXEL
default 16
choice LV_COLOR_DEPTH
default LV_COLOR_DEPTH_16
endchoice
# VDB size is 10% of the full screen size
config LV_Z_VDB_SIZE
default 10
# Configure LVGL to use touchscreen
config INPUT
default y
config INPUT_GT911_INTERRUPT
default y
endif # LVGL
endif # SHIELD_LCD_PAR_S035
``` | /content/code_sandbox/boards/shields/lcd_par_s035/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 117 |
```unknown
/*
*
*/
#include <zephyr/dt-bindings/mipi_dbi/mipi_dbi.h>
/{
chosen {
zephyr,display = &st7796s;
};
lvgl_pointer {
compatible = "zephyr,lvgl-pointer-input";
input = <>911_lcd_par_s035>;
swap-xy;
invert-y;
};
};
&nxp_8080_touch_panel_i2c {
status = "okay";
gt911_lcd_par_s035: gt911-lcd_par_s035@5d {
compatible = "goodix,gt911";
reg = <0x5d>;
alt-addr = <0x14>;
irq-gpios = <&nxp_lcd_8080_connector 9 GPIO_ACTIVE_HIGH>;
};
};
&nxp_flexio_lcd {
status = "okay";
#address-cells = <1>;
#size-cells = <0>;
st7796s: st7796s@0 {
compatible = "sitronix,st7796s";
reg = <0>;
/* Baud rate on each pin is 1MHz */
mipi-max-frequency = <10000000>;
mipi-mode = <MIPI_DBI_MODE_8080_BUS_16_BIT>;
height = <320>;
width = <480>;
invert-mode = "1-dot";
frmctl1 = [80 10];
bpc = [1F 50 00 20];
dfc = [8A 07 3B];
pwr1 = [80 64];
pwr2 = <0x13>;
pwr3 = <0xA7>;
vcmpctl = <0x09>;
doca = [40 8A 00 00 29 19 A5 33];
pgc = [F0 06 0B 07 06 05 2E 33 47 3A 17 16 2E 31];
ngc = [F0 09 0D 09 08 23 2E 33 46 38 13 13 2C 32];
madctl = <0x28>;
color-invert;
};
};
``` | /content/code_sandbox/boards/shields/lcd_par_s035/lcd_par_s035_8080.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 499 |
```unknown
config SHIELD_NPM1100_EK
def_bool $(shields_list_contains,npm1100_ek)
``` | /content/code_sandbox/boards/shields/npm1100_ek/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 26 |
```restructuredtext
.. _lcd_par_s035:
NXP LCD_PAR_S035 TFT LCD Module
###############################
Overview
********
The LCD-PAR-S035 is a 3.5 480x320 IPS TFT LCD module with wide viewing angle
and 5-point capacitive touch functionality. The LCD module can be controlled
through either SPI or parallel (8/16bit) 8080/6800.
More information about the shield can be found
at the `LCD-PAR-S035 product page`_.
Requirements
************
This shield can only be used with FRDM-X evaluation kits with a parallel LCD
connector or a PMOD connector. Currently only the parallel LCD connector is
enabled.
Programming
***********
Set ``--shield lcd_par_s035_8080`` when you invoke ``west build``. For
example:
.. zephyr-app-commands::
:zephyr-app: samples/drivers/display
:board: frdm_mcxn947/mcxn947/cpu0
:shield: lcd_par_s035_8080
:goals: build
References
**********
.. target-notes::
.. _LCD-PAR-S035 product page:
path_to_url
``` | /content/code_sandbox/boards/shields/lcd_par_s035/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 248 |
```unknown
/*
*/
/ {
npm1100_ek_pmic: pmic {
compatible = "nordic,npm1100";
nordic,iset-gpios = <&arduino_header 8 GPIO_ACTIVE_HIGH>; /* D2 */
npm1100_ek_buck: BUCK {
nordic,mode-gpios = <&arduino_header 9 GPIO_ACTIVE_HIGH>; /* D3 */
};
};
};
``` | /content/code_sandbox/boards/shields/npm1100_ek/npm1100_ek.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 95 |
```unknown
*/
&arduino_spi {
status = "okay";
eth_w5500_arceli_eth_w5500: eth_w5500@0 {
compatible = "wiznet,w5500";
reg = <0x0>;
spi-max-frequency = <80000000>;
int-gpios = <&arduino_header 15 GPIO_ACTIVE_LOW>; /* D9 */
reset-gpios = <&arduino_header 14 GPIO_ACTIVE_LOW>; /* D8 */
};
};
``` | /content/code_sandbox/boards/shields/arceli_eth_w5500/arceli_eth_w5500.overlay | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 105 |
```restructuredtext
.. _npm1100_ek:
nPM1100 EK
##########
Overview
********
The nPM1100 EK lets you test different functions and features of the nPM1100
Power Management Integrated Circuit (PMIC).
.. figure:: npm1100_ek.jpg
:alt: nPM1100 EK
:align: center
nPM1100 EK
Requirements
************
The nPM1100 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 pins. This allows to use the shield with any host board that
supports the Arduino connector. The connections are:
+-----------+--------------+
| PMIC Pin | Arduino Pin |
+===========+==============+
| ISET | D2 |
| MODE | D3 |
+-----------+--------------+
Usage
*****
The shield can be used in any application by setting ``--shield npm1100_ek``
when invoking ``west build``.
References
**********
- `nPM1100 EK Manual <path_to_url`_
``` | /content/code_sandbox/boards/shields/npm1100_ek/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 235 |
```unknown
config SHIELD_ARCELI_ETH_W5500
def_bool $(shields_list_contains,arceli_eth_w5500)
``` | /content/code_sandbox/boards/shields/arceli_eth_w5500/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 29 |
```unknown
if SHIELD_ARCELI_ETH_W5500
if NETWORKING
config NET_L2_ETHERNET
default y
endif # NETWORKING
endif # SHIELD_ARCELI_ETH_W5500
``` | /content/code_sandbox/boards/shields/arceli_eth_w5500/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 45 |
```unknown
config SHIELD_ST_B_LCD40_DSI1_MB1166
def_bool $(shields_list_contains,st_b_lcd40_dsi1_mb1166)
config SHIELD_ST_B_LCD40_DSI1_MB1166_A09
def_bool $(shields_list_contains,st_b_lcd40_dsi1_mb1166_a09)
``` | /content/code_sandbox/boards/shields/st_b_lcd40_dsi1_mb1166/Kconfig.shield | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 70 |
```restructuredtext
.. _arceli_eth_w5500:
ARCELI W5500 ETH
################
Overview
********
ARCELI W5500 Ethernet is breakout board with SPI bus access over 10 pin header.
`W5500`_ is 10/100 MBPS stand alone Ethernet controller with on-board MAC & PHY,
16 KiloBytes for FIFO buffer and SPI serial interface.
Pins Assignment of the W5500 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/breakout board can be used with any board with SPI interfaces in
Arduino header or custom header (by adjusting the overlay).
Programming
***********
Set ``--shield arceli_eth_w5500`` when you invoke ``west build``. For example:
.. zephyr-app-commands::
:zephyr-app: samples/net/dhcpv4_client
:board: nrf52840dk/nrf52840
:shield: arceli_eth_w5500
:goals: build
References
**********
.. target-notes::
.. _W5500:
path_to_url
``` | /content/code_sandbox/boards/shields/arceli_eth_w5500/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 373 |
```unknown
if SHIELD_ST_B_LCD40_DSI1_MB1166 || SHIELD_ST_B_LCD40_DSI1_MB1166_A09
# Double frame buffer maintained by lvgl.
if LVGL
config STM32_LTDC_FB_NUM
default 0
config INPUT
default y
config LV_Z_VDB_SIZE
default 100
config LV_Z_DOUBLE_VDB
default y
config LV_Z_VBD_CUSTOM_SECTION
default y
config LV_Z_FULL_REFRESH
default y
config LV_Z_BITS_PER_PIXEL
default 32
config LV_DPI_DEF
default 128
config LV_Z_FLUSH_THREAD
default y
choice LV_COLOR_DEPTH
default LV_COLOR_DEPTH_32
endchoice
endif # LVGL
endif # SHIELD_ST_B_LCD40_DSI1_MB1166 || SHIELD_ST_B_LCD40_DSI1_MB1166_A09
``` | /content/code_sandbox/boards/shields/st_b_lcd40_dsi1_mb1166/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 183 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.