W5500-EVB-Pico2
Overview
W5500-EVB-Pico2 is a microcontroller evaluation board based on the Raspberry Pi RP2350A and fully hardwired TCP/IP controller W5500 - and basically works the same as Raspberry Pi Pico2 board but with additional Ethernet via W5500. The USB bootloader allows the ability to flash without any adapter, in a drag-and-drop manner. It is also possible to flash and debug the boards with their SWD interface, using an external adapter.
Hardware
Dual core Arm Cortex-M33 or Hazard3 processor running up to 133MHz
520KB on-chip SRAM
16MB on-board QSPI flash with XIP capabilities
26 GPIO pins
3 Analog inputs
2 UART peripherals
2 SPI controllers
2 I2C controllers
16 PWM channels
USB 1.1 controller (host/device)
3 Programmable I/O (PIO) for custom peripherals
On-board LED
1 Watchdog timer peripheral
Wiznet W5500 Ethernet MAC/PHY
Supported Features
The w5500_evb_pico2 board supports the hardware features listed below.
- on-chip / on-board
- Feature integrated in the SoC / present on the board.
- 2 / 2
-
Number of instances that are enabled / disabled.
Click on the label to see the first instance of this feature in the board/SoC DTS files. -
vnd,foo -
Compatible string for the Devicetree binding matching the feature.
Click on the link to view the binding documentation.
w5500_evb_pico2/rp2350a/m33 target
Type |
Location |
Description |
Compatible |
|---|---|---|---|
CPU |
on-chip |
ARM Cortex-M33 CPU2 |
|
ADC |
on-chip |
RaspberryPi Pico ADC1 |
|
Clock control |
on-chip |
||
on-chip |
The representation of Raspberry Pi Pico’s PLL2 |
||
on-chip |
The representation of Raspberry Pi Pico ring oscillator1 |
||
on-chip |
The representation of Raspberry Pi Pico external oscillator1 |
||
on-chip |
Raspberry Pi Pico clock controller node1 |
||
Counter |
on-chip |
||
DMA |
on-chip |
Raspberry Pi Pico DMA1 |
|
Ethernet |
on-board |
W5500 standalone 10/100BASE-T Ethernet controller with SPI interface1 |
|
Flash controller |
on-chip |
Raspberry Pi Pico flash controller1 |
|
GPIO & Headers |
on-chip |
Raspberry Pi Pico GPIO1 |
|
on-chip |
|||
on-board |
GPIO pins exposed on Raspberry Pi Pico headers1 |
||
I2C |
on-chip |
||
Interrupt controller |
on-chip |
ARMv8-M NVIC (Nested Vectored Interrupt Controller)1 |
|
LED |
on-board |
Group of GPIO-controlled LEDs1 |
|
on-board |
Group of PWM-controlled LEDs1 |
||
Miscellaneous |
on-chip |
Raspberry Pi Pico PIO3 |
|
MTD |
on-chip |
Flash node1 |
|
on-board |
Fixed partitions of a flash (or other non-volatile storage) memory1 |
||
Pin control |
on-chip |
The RPi Pico pin controller is a node responsible for controlling pin function selection and pin properties, such as routing a UART0 Rx to pin 1 and enabling the pullup resistor on that pin1 |
|
PWM |
on-chip |
Raspberry Pi Pico PWM1 |
|
Reset controller |
on-chip |
Raspberry Pi Pico Reset Controller1 |
|
Sensors |
on-chip |
RaspberryPi Pico family temperature sensor node1 |
|
Serial controller |
on-chip |
||
SPI |
on-chip |
||
SRAM |
on-chip |
Generic on-chip SRAM description1 |
|
Timer |
on-chip |
ARMv8-M System Tick1 |
|
USB |
on-chip |
RaspberryPi Pico USB Device Controller1 |
|
Watchdog |
on-chip |
Raspberry Pi Pico Watchdog1 |
Pin Mapping
The peripherals of the RP2350A SoC can be routed to various pins on the board. The configuration of these routes can be modified through DTS. Please refer to the datasheet to see the possible routings for each peripheral.
External pin mapping on the W5500_EVB_PICO2 is identical to the Raspberry Pi Pico2. Since GPIO 25 is routed to the on-board LED on, similar to the Raspberry Pi Pico, the blinky example works as intended. The W5500 is routed to the SPI0 (P16-P19), with the reset and interrupt signal for the W5500 routed to P20 and P21, respectively. All of these are shared with the edge connector on the board.
Refer to W55500 Evaluation Board Pico2 Documentation [1] for a board schematic and other certifications.
Default Zephyr Peripheral Mapping:
UART0_TX : P0
UART0_RX : P1
I2C0_SDA : P4
I2C0_SCL : P5
I2C1_SDA : P14
I2C1_SCL : P15
SPI0_RX : P16
SPI0_CSN : P17
SPI0_SCK : P18
SPI0_TX : P19
W5500 Reset : P20
W5500 Interrupt : P21
ADC_CH0 : P26
ADC_CH1 : P27
ADC_CH2 : P28
ADC_CH3 : P29
Programming and Debugging
Flashing
Using OpenOCD
The overall explanation regarding flashing and debugging is the same as or
rpi_pico.
See Using OpenOCD. in rpi_pico documentation.
A typical build command for w5500_evb_pico2 is as follows.
This assumes a CMSIS-DAP adapter such as the RaspberryPi Debug Probe,
but if you are using something else, specify RPI_PICO_DEBUG_ADAPTER.
# From the root of the zephyr repository
west build -b w5500_evb_pico2 samples/basic/blinky -- -DOPENOCD=/usr/local/bin/openocd
west flash
Using UF2
If you don’t have an SWD adapter, you can flash the Raspberry Pi Pico with
a UF2 file. By default, building an app for this board will generate a
build/zephyr/zephyr.uf2 file. If the Pico is powered on with the BOOTSEL
button pressed, it will appear on the host as a mass storage device. The
UF2 file should be drag-and-dropped to the device, which will flash the Pico.
Debugging
The SWD interface can also be used to debug the board. To achieve this, you can either use SEGGER JLink or OpenOCD.
Using OpenOCD
Install OpenOCD as described for flashing the board.
Here is an example for debugging the Blinky application.
# From the root of the zephyr repository
west build -b w5500_evb_pico2 samples/basic/blinky -- -DOPENOCD=/usr/local/bin/openocd
west debug