W6300-EVB-Pico2
Overview
W6300-EVB-Pico2 is a microcontroller evaluation board based on the Raspberry Pi RP2350A and the WIZnet W6300 hardwired TCP/IP controller. It works like the Raspberry Pi Pico2, with additional Ethernet connectivity provided by the W6300. The USB bootloader allows flashing without an adapter. SWD is supported for debugging with external adapters.
Hardware
Dual core Arm Cortex-M33 processor running up to 150 MHz
520 KB on-chip SRAM
2 MB on-board QSPI flash with XIP capabilities
26 GPIO pins
3 analog inputs
2 UART peripherals
2 I2C controllers
16 PWM channels
USB 1.1 controller (host/device)
3 programmable I/O (PIO) blocks
On-board LED
1 watchdog timer peripheral
WIZnet W6300 Ethernet MAC/PHY with IPv4/IPv6 support
Supported Features
The w6300_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.
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.
The W6300 is connected using SPI/QSPI signals on GPIO15-22:
GPIO |
W6300 Pin |
Function |
|---|---|---|
GPIO15 |
INTn |
Interrupt |
GPIO16 |
CSn |
Chip Select |
GPIO17 |
SCLK |
SPI Clock |
GPIO18 |
IO0 |
MOSI / QSPI IO0 |
GPIO19 |
IO1 |
MISO / QSPI IO1 |
GPIO20 |
IO2 |
QSPI IO2 |
GPIO21 |
IO3 |
QSPI IO3 |
GPIO22 |
RSTn |
Reset |
Programming and Debugging
The w6300_evb_pico2 board supports the runners and associated west commands listed below.
| flash | debug |
|---|
The overall explanation regarding flashing and debugging is the same as or Raspberry Pi Pico. See Programming and Debugging in Raspberry Pi Pico documentation. N.b. OpenOCD support requires using Raspberry Pi’s forked version of OpenOCD.
Below is an example of building and flashing the Blinky application.
# From the root of the zephyr repository
west build -b w6300_evb_pico2/rp2350a/m33 samples/basic/blinky
west flash --openocd /usr/local/bin/openocd