Labs / MicroPython tutorials

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

Author: Li Zisheng · Source: FreakStudio open documentation, v1.3.0 · License: CC BY 4.0

Contents

1.WIZnet W6300/W5500/W5100S-EVB-pico2 Introduction

WIZnet W6300/ W 5500/ W 5100S-EVB-Pico2 are three Ethernet evaluation development boards based on the Raspberry Pi RP2350 microcontroller and WIZnet full hardware TCP/IP controllers (W6300/W5500/W5100S). Combining the high-performance computing capability of the RP2350 and the hard-wired network protocol stack of WIZnet chips, these boards provide a complete solution for embedded network applications.

In terms of hardware, it adopts the RP2350 microcontroller chip officially designed by Raspberry Pi, which is equipped with dual-core ARM Cortex-M33 or dual RISC-V Hazard3 processors, operates at a frequency of up to 150MHz, has a built-in 520KB SRAM, and supports external QSPI flash memory up to 16MB. In terms of software, developers can choose the C/C++ SDK or MicroPython provided by Raspberry Pi for development, with complete supporting Ethernet driver libraries and development materials.

0.1.1 W5500-EVB-Pico2

W5500-EVB-Pico2 is a microcontroller evaluation board based on the Raspberry Pi RP2350 and the fully hardwired TCP/IP controller W5500, which leverages the W5500 to boost the performance of the conventional Raspberry Pi Pico2 board and add more Ethernet functionalities.

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

0.1.2 W5110S-EVB-Pico2

W5100S-EVB-Pico2 is a microcontroller evaluation board based on the Raspberry Pi RP2350 and the fully hardwired TCP/IP controller W5100S — it enhances the functionality of the traditional Raspberry Pi Pico board by adding Ethernet capability via the W5100S.

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

0.1.3 W6300-EVB-Pico2

W6300-EVB-Pico2 is a microcontroller evaluation board based on the Raspberry Pi RP2350 and the fully hardwired TCP/IP controller W6300. It essentially works the same way as the Raspberry Pi Pico board, but adds an Ethernet port via the W6300.

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

Differences between a development board and a chip:

  • What is a "chip"(taking RP2350 as an example): RP2350 is a single electronic component, an integrated circuit independently developed by Raspberry Pi:
    • It serves as the core functional carrier for the WIZnet W6300/ W 5500/ W 5100S-EVB-pico2 development board, and inherently integrates core computing/storage modules including dual-core ARM Cortex-M33 and dual-core RISC-V Hazard3 processors, 512KB SRAM, and 4MB flash memory;
    • However, the chip cannot function independently: it is merely an encapsulated integrated circuit, devoid of peripheral components such as power supply circuits, interfaces, and pin extensions. If you take the RP2350 chip alone, you can neither power it nor connect it to sensors or peripherals.
  • What is a "development board"(taking W6300-EVB-Pico2 as an example): W6300-EVB-Pico2 is a finished circuit board based on the RP2350 chip:
    • A ready-to-use finished tool that centers on the RP2350 chip and integrates peripheral components including the WIZnet Ethernet controller, USB power supply circuit, GPIO header pins, BOOTSEL button, LED indicator, and RJ45 Ethernet port.

1.1 Basic parameters of W6300/ W 5500/ W 5100S-EVB-pico2

1.1.1 Basic Parameters of W6300-EVB-pico2

1.1.2 Basic Parameters of W5500-EVB-Pico2

1.1.3 Basic Parameters of W5100S-EVB-pico2

1.2 Hardware Specifications

1.2.1 W6300-EVB-pico2

The pins of the W6300-EVB-Pico2 are directly connected to the GPIOs of the RP2350, and its pinout is identical to that of the Raspberry Pi Pico 2 board. However, GPIO15, GPIO16, GPIO17, GPIO18, GPIO19, GPIO20, GPIO21 and GPIO22 are all connected to the W6300 on the main board. These pins enable QSPI communication with the W6300 to support Ethernet functionality, and thus cannot be used for any other purposes when the Ethernet function is in use.

The RP2350 GPIOs internally used by the W6300-EVB-Pico are as follows.

Input/OutputNameDescription
OGPIO15Connected to INTn on the W6300
OGPIO16Connected to CSn on the W6300
OGPIO17Connected to SCLK on the W6300
Input/OutputGPIO18Connected to IO0 (MOSI) on the W6300 (QSPI)
Input/OutputGPIO19Connected to IO1 (MISO) on the W6300 (QSPI)
Input/OutputGPIO20Connected to IO2 on the W6300 (QSPI)
Input/OutputGPIO21Connected to IO3 on the W6300 (QSPI)
OGPIO22Connected to RSTn on the W6300
IGPIO24VBUS sense: high if VBUS is present, otherwise low
OGPIO25Connected to the user LED
IGPIO29Used in ADC mode (ADC3) to measure VSYS/3
QSPI mode IO lines

The IO lines for each QSPI mode are as follows.

ModeInput/OutputBadge nameDescription
SingleOGPIO18Connected to IO0 (MOSI) on the W6300
SingleIGPIO19Connected to IO1 (MISO) on the W6300
ModeInput/OutputBadge nameDescription
DualInput/OutputGPIO18Connected to IO0 on the W6300 (dual mode)
DualInput/OutputGPIO19Connected to IO1 on the W6300 (dual mode)
ModeInput/OutputBadge nameDescription
QuadInput/OutputGPIO18Connected to IO0 on the W6300 (quad mode)
QuadInput/OutputGPIO19Connected to IO1 on the W6300 (quad mode)
QuadInput/OutputGPIO20Connected to IO2 on the W6300 (quad mode)
QuadInput/OutputGPIO21Connected to IO3 on the W6300 (quad mode)

In addition to GPIO pins and ground pins, there are 7 other pins on the main 40-pin header:

No.Badge nameDescription
PIN40VBUSUSB Type-C input voltage, connected to pin 1 of the USB Type-C port. Nominally 5V.
PIN39VSYSMain system input voltage, which can vary within the allowed range of 4.3V to 5.5V; used by the onboard LDO to generate 3.3V.
PIN373V3_ENConnected to the onboard LDO enable pin. To disable the 3.3V (which also powers down the RP2350 and W6300), short this pin to low.
PIN363V3Main 3.3V supply for the RP2350 and W6300, generated by the onboard LDO.
PIN35ADC_VREFADC supply (and reference) voltage, generated on the W6300-EVB-Pico2 through a filtered 3.3V supply.
PIN33AGNDGround reference for GPIO26-29.
PIN30RUNRP2350 enable pin. To reset the RP2350, short this pin to low.

1.2.2 W5500-EVB-pico2

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

As shown in the figure above, the pins of the W5500-EVB-Pico2 are directly connected to the GPIOs of the RP2350, and its pin arrangement is identical to that of the Raspberry Pi Pico 2 board. However, GPIO16, GPIO17, GPIO18, GPIO19, GPIO20 and GPIO21 are all connected to the W5500 on the main board internally. These pins implement SPI communication with the W5500 to enable Ethernet functionality, so they cannot be used for other purposes if you are utilizing the Ethernet feature.

The RP2350 GPIOs internally used by the W5500-EVB-Pico are as follows.

Input/OutputNameDescription
IGPIO16Connected to MISO on the W5500
OGPIO17Connected to CSn on the W5500
OGPIO18Connected to SCLK on the W5500
OGPIO19Connected to MOSI on the W5500
OGPIO20Connected to RSTn on the W5500
IGPIO21Connected to INTn on the W5500
IGPIO24VBUS sense: high if VBUS is present, otherwise low
OGPIO25Connected to the user LED
IGPIO29Used in ADC mode (ADC3) to measure VSYS/3

In addition to GPIO pins and ground pins, there are 7 other pins on the main 40-pin header:

No.NameDescription
PIN40VBUSMicro-USB input voltage, connected to pin 1 of the micro-USB port. Nominally 5V.
PIN39VSYSMain system input voltage, which can vary within the allowed range of 4.3V to 5.5V; used by the onboard LDO to generate 3.3V.
PIN373V3_ENConnected to the onboard LDO enable pin. To disable the 3.3V (which also powers down the RP2350 and W5500), short this pin to low.
PIN363 to 3Main 3.3V supply for the RP2350 and W5500, generated by the onboard LDO.
PIN35ADC_VREFADC supply (and reference) voltage, generated on the W5500-EVB-Pico through a filtered 3.3V supply.
PIN33AGNDGround reference for GPIO26-29.
PIN30Fast runRP2350 enable pin. To reset the RP2350, short this pin to low.
Operating Conditions
ItemDescription
Upper operating temperature limit85 °C (including self-heating)
Lower operating temperature limit-20 °C
VBUS5V DC (+/- 10%)
VSYS Min4.3V DC
VSYS Max5.5V DC

The recommended maximum ambient temperature is 70 degrees Celsius.

1.2.3 W5100S-EVB-pico2

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

The pins of the W5100S-EVB-Pico2 are directly connected to the GPIOs of the RP2350, as shown in the diagram above. Its pinout is identical to that of the Raspberry Pi Pico 2 board. However, GPIO16, GPIO17, GPIO18, GPIO19, GPIO20 and GPIO21 are all connected to the onboard W5100S on the main board. These pins enable SPI communication with the W5100S to support Ethernet functionality, and thus cannot be used for any other purposes if you are utilizing the Ethernet feature.

The RP2350 GPIOs internally used by the W5100S-EVB-Pico2 are as follows.

Input/OutputPin nameDescription
IGPIO16Connected to MISO on the W5100S
OGPIO17Connected to CSn on the W5100S
OGPIO18Connected to SCLK on the W5100S
OGPIO19Connected to MOSI via W5100S
OGPIO20RSTn connected to W5100S
IGPIO21INTn connected to W5100S
IGPIO24VBUS sense: high if VBUS is present, otherwise low
OGPIO25Connected to the user LED
IGPIO29Used in ADC mode (ADC3) to measure VSYS/3

In addition to GPIO pins and ground pins, there are 7 other pins on the main 40-pin header:

No.NameDescription
PIN40VBUSMicro-USB input voltage, connected to pin 1 of the micro-USB port. Nominally 5V.
PIN39VSYSMain system input voltage, which can vary within the allowed range of 4.3V to 5.5V; used by the onboard LDO to generate 3.3V.
PIN373V3_ENConnects to the onboard LDO enable pin. To disable 3.3V (which also powers down the RP2350 and W5100S), short this pin to low.
PIN363 to 3The main 3.3V supply for the RP2350 and W5100S is generated by the onboard LDO.
PIN35ADC_VREFADC supply (and reference) voltage, generated on the W5100S-EVB-Pico from the filtered 3.3V supply.
PIN33AGNDGround reference for GPIO26-29.
PIN30Fast runRP2350 enable pin. To reset the RP2350, short this pin to low.
Operating Conditions
ItemDescription
Upper operating temperature limit85 °C (including self-heating)
Lower operating temperature limit-20 °C
VBUS5V DC (+/- 10%)
VSYS Min4.3V DC
VSYS Max5.5V DC

The recommended maximum ambient temperature is 70 degrees Celsius.

1.3 Development Board Hardware Circuit

1.3.1 W6300-EVB-pico2

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction
00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

1.3.2 W5500-EVB-pico2

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction
00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

1.3.3 W5100S-EVB-pico2

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction
00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

2. Detailed Introduction to Ethernet Controller Chips

2.1 W6300

W6300-L P1N2K-012 2433 10/100

The W6300 is a hardwired TCP/IP stack internet controller chip based on WIZnet technology, designed for high-speed Ethernet communication. It integrates a dual IPv4/IPv6 hardware stack, 10/100 Ethernet MAC and PHY into a single chip. To achieve performance exceeding 90Mbps, the W6300 supports a 150MHz system clock and QSPI interface, and is equipped with 4 data lines. It provides 8 independent sockets and 64KB internal SRAM, supporting reliable Ethernet application development through socket programming.

block diagram

W630000

Pin Diagram

W6300 37 DAT0 48

Parameters


Literature and Materials

datasheet
TitleDescriptionNotes
📄 W6300 Datasheet (English)Technical specifications and features of the W6300 chip-
Driver

The ioLibrary means "Internet Offload Library" for WIZnet chips.

It includes drivers and application protocols.

The ioLibrary can be used for W6300 and other chips’ application designs.

These will be updated continuously.

ResourceDescription
ioLibrary_DriverOfficial WIZnet driver library for W5x00/W6x00 chips
Information

The ioLibrary_Driver is an MCU-independent library designed for WIZnet W5x00 and W6x00 chips.

It implements key TCP/IP services, enabling developers to build network applications with minimal MCU dependency.

Supported Services

DHCP, DNS, MQTT, SNTP, TFTP, HTTP servers

Application Notes
Example NameDescriptionNotes
📄 Interrupt (KOR)How to use InterruptInterrupt handling guide for W6300
📄 Interrupt (ENG)How to use InterruptInterrupt handling guide for W6300
📄 IPRAW (KOR)How to use IPRAWIPRAW mode guide for raw IPv4 communication
📄 IPRAW (ENG)How to use IPRAWIPRAW mode guide for raw IPv4 communication
📄 PSAA (KOR)How to use PSAAPrefer Source IPv4/IPv6 Address handling for SOCKET & SOCKET-less modes
📄 PSAA (ENG)How to use PSAAPrefer Source IPv4/IPv6 Address handling for SOCKET & SOCKET-less modes
📄 SLC (KOR)How to use SLCSLC mode guide for Socket-less command control
📄 SLC (ENG)How to use SLCSLC mode guide for Socket-less command control
📄 AAC (KOR)How to implement Auto-ConfigurationStateless & Stateful IPv4/IPv6 address auto-configuration methods
📄 AAC (ENG)How to implement Auto-ConfigurationStateless & Stateful IPv4/IPv6 address auto-configuration methods
Information

These application notes describe how to use W6300 's core network functions, including TCP, UDP, IPRAW modes, IPv6 features and PPPoE.

hardware resources
Technical Resources
ResourcesDescriptionNotes
W6300-EVB-Pico SCH and PCB LibrarySchematic, parts list, and Gerber files-
W6300-EVB-Pico2 SCH and PCB LibrarySchematic, parts list, and Gerber files-
Design GuideTBD-
Reference Schematic (Extended)External Transformer SchematicIncludes recommended circuit design
Reference Schematic (RRJ45)TBD-
Testing and Certification
ResourcesDescriptionNotes
ESD TestTBD-
Ethernet Compliance TestTBD-
Distance TestTBD-
EMC TestTBD-
Reliability TestTBD-
CertificatesTBD-

2.2 W5500

W5500 DP308203 1321

The W5500 is a hardwired TCP/IP stack internet controller chip based on WIZnet technology, which provides convenient internet connectivity for external MCUs via an SPI interface with a maximum clock speed of 80MHz. As a single-chip solution, it integrates a 10/100 Ethernet MAC and PHY, and supports multiple protocols including TCP, UDP and IPv4. In addition, it features 8 independent SOCKETs and 32KB of internal memory, enabling Ethernet application development directly through SOCKET programming.It also reduces power consumption through WOL (Wake-on-LAN) and power-off modes.

block diagram

W5500 RJ45 32K

Pin Diagram

W5500 48LQFP VDD3V3

Parameters


Literature

datasheet
TitleDescriptionNotes
W5500 Datasheet (English)
W5500 Datasheet (KR)
Technical specifications and features of the W5500 chip-
Technical Documentation
TitleDescriptionNotes
SPI performance--

Software Resources

Driver
ResourcesDescription
ioLibrary_DriverOfficial WIZnet driver library for W5500 and other chips
ioLibrary_Driver_BSDOfficial WIZnet driver library for W5500 and other chips
Information

The ioLibrary_Driver is an MCU-independent library compatible with WIZnet W5x00 and W6x00 series chips. It provides basic TCP/IP service implementations, enabling developers to build network applications with minimal MCU dependency.

Supported Services

DHCP, DNS, MQTT, SNTP, TFTP, HTTP servers

Application Notes
Example NameDescriptionNotes
TCP FunctionHow to use TCP FunctionITCP Function handles IPv4 layer communication
UDP FunctionHow to use UDP FunctionUDP Function handles IPv4 layer communication
IPRAWHow to use IPRAW ModeIPRAW Mode handles IPv4 layer communication
PPPoEHow to use PPP/PPPoEPPP is Link-Layer protocol for point-to-point
Information

These application notes describe how to use the core network functions of the W5500, including TCP, UDP, IPRAW mode and PPPoE protocol.

hardware resources

technical resources

ResourcesDescriptionNotes
Reference Schematic (Extended)External Transformer SchematicIncludes recommended circuit design
Reference Schematic (RJ45)RJ45 with transformer schematicIncludes recommended circuit design
SCH and PCB LibraryTBD-
Design GuideTBD-

Testing and Certification

ResourcesDescriptionNotes
ESD TestESD Test Confirmation-
Ethernet Compliance TestTBD-
Distance TestTBD-
EMC TestTBD-
Reliability TestTBD-
CertificatesTBD-

2.3 W5100S

W5100S PPJQ1-012 1809 W5100S-L W5100S-Q

W5100S is a wired TCP/IP protocol stack internet controller chip based on WIZnet technology, which provides convenient internet connectivity for external MCUs via SPI or Parallel System BUS. The SPI interface supports a maximum clock frequency of 70MHz, while the Parallel System BUS delivers higher data throughput to achieve faster network communication. Integrated with embedded Ethernet MAC and PHY, the W5100S enables developers to easily build Ethernet applications through socket programming.

block diagram

W5100S 10BaseT/100BaseTX 8K RJ45

Pin Diagram

W5100S W5100 3V3D DAT0 DAT7 MOD0 MOD3

Parameters


Literature and Materials

datasheet
TitleDescriptionNotes
W5100S DatasheetTechnical specifications and features of the W5100S chip-
Technical Documentation
TitleDescriptionNotes
W5100S ErrataKnown issues and corrections for the W5100S chip-
W5100S vs. W5100 Comparison TableFeature comparison of the W5100S and W5100 chips-

software resources

Driver

ioLibrary refers to the "Internet Offload Library" for WIZnet chips, which includes drivers and application protocols. It can be used in the application design of the W5100S and other chips, and relevant information will be updated continuously.

ResourcesDescription
ioLibrary_DriverOfficial WIZnet driver library for W5100S and other chips
Information

The ioLibrary_Driver is an MCU-independent library applicable to WIZnet W5x00 and W6x00 chips. It provides basic TCP/IP service implementations, enabling developers to build network applications with minimal MCU dependency.

Supported Services

DHCP, DNS, MQTT, SNTP, TFTP, HTTP servers

Application Notes
NameDescriptionNotes
TCP FunctionsHow to Use IPRAW ModeIPRAW mode handles IPv4-layer communication
UDP FunctionsHow to Use IPRAW ModeIPRAW mode handles IPv4-layer communication
IPRAWHow to Use IPRAW ModeIPRAW mode handles IPv4-layer communication
PPPoEHow to Use PPP/PPPoEPPP is a point-to-point link-layer protocol
Socketless CommandsSocketless ARP and PING ProcedureCommand-based ARP and PING processing
InterruptsInterrupt ExamplePublish a Message to the Broker
DMAHow to Use IPRAW ModeIPRAW mode handles IPv4-layer communication

hardware resources

Technical Resources
ResourcesDescriptionNotes
Reference SchematicTypical Application SchematicIncludes recommended circuit design
Reference Schematic (Extended)External Transformer TypeIncludes recommended circuit design
Reference Schematic (International)RJ45 Transformer TypeIncludes recommended circuit design
SCH and PCB LibraryTBD
Design GuideTBD
Testing and Certification
ResourcesDescriptionNotes
Ethernet Compliance TestTBD
Distance TestTBD
EMC TestTBD
Reliability TestTBD
CertificatesTBD

2. Detailed Introduction to the RP2350A Chip

RP2350A is the second-generation self-developed microcontroller chip launched by Raspberry Pi. Building on the huge success of the RP2040, it delivers a significant leap in performance and enhanced functionality, while inheriting the features of low power consumption, high cost-effectiveness and excellent development experience.

The RP2350A chip adopts a 40nm process, which translates to a compact die size and low power consumption, and comes in a 7×7mm QFN-60 package — meaning it is a 7mm square chip with 60 small pins for easy soldering onto circuit boards:

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

The specific specifications and parameters are as follows:

What is "encapsulation"?

The core of a chip, which refers to the integrated circuit on the silicon wafer, can be understood as a "fragile die" — it is extremely thin and delicate, vulnerable to impacts and moisture, and has no directly connectable interfaces, making it impossible to use as-is. "Packaging" is the process of providing this die with "a protective enclosure plus lead-out interfaces":

  • It serves as the "protective casing" of a chip: it encloses the fragile core circuitry to guard against drops, moisture and dust, thereby preventing damage to the circuits.
  • It serves as the "external interface" of the chip: metal pins are drawn out from the core circuit to facilitate soldering the chip onto a circuit board, enabling the chip to receive power and transmit signals with external components.

Different packages feature varying shapes and pin counts; for instance, the "7×7mm QFN-56 package" used for the RP2040: QFN denotes the package type (a flat, no-lead form factor), 56 indicates that this package has 56 pins, and 7×7mm refers to the physical dimensions of the package.

Apart from the QFN package used for the RP2040, here are other common chip packages:

  • DIP package (Dual In-line Package) For example, "DIP-20": it features long metal pins arranged in two rows, which can be directly inserted into a breadboard/perforated prototype board.
    • Features: beginner-friendly, easy to insert, easy to solder, and easy to disassemble when damaged; however, it is relatively bulky.
    • Applicable scenarios: Experiments for beginners, prototype verification on breadboards (for example, early 51 single-chip microcontrollers commonly used DIP packages).
  • SOIC package (Small Outline Integrated Circuit package) For example, "SOIC-16": it is a surface-mount package with small metal pins on the surface of the circuit board, and its volume is much smaller than that of DIP.
    • Features: Compact size, suitable for tight circuit boards; however, it requires surface-mount soldering, making manual soldering more difficult for beginners than DIP packages.
    • Application scenarios: Small consumer electronics (e. g., chips for Bluetooth modules, small-sized sensors).
  • QFP package (Quad Flat Package) Take "QFP-44" as an example: its leads are arranged on all four sides of the chip, with a higher pin count than SOIC.
    • Features: It can support more functions (more pins correspond to more chip functions), with a size smaller than DIP but larger than BGA.
    • Applicable scenarios: Devices with moderate complexity (such as some feature-rich microcontrollers and small industrial control board chips).
  • BGA Package (Ball Grid Array Package) Take "BGA-100" for example: its pins are solder balls located at the bottom of the chip (rather than exposed pins), featuring an extremely compact size and a very large number of pins.
    • Features: It can accommodate a large number of pins (supporting high-performance chips) and has an extremely small size; however, it requires professional equipment for soldering and is hardly usable for beginners.
    • Application scenarios: High-end small-sized devices (e. g., processors in mobile phones and tablets, high-performance sensor chips).

The core differences between these packages lie in their size, pin configuration, and soldering difficulty: beginners typically use DIP (easy to handle) for experiments, SOIC/QFN for compact finished products, and BGA for high-end miniature devices.

USB Flashing Format (UF2) File

UF2 is a brand-new firmware update file format developed by Microsoft for PXT (also known as Microsoft MakeCode), which is particularly suitable for the firmware upgrade process of microcontrollers and embedded devices via Flash memory.

The core features of the UF2 file lie in its divisibility and easy identifiability. Each UF2 file consists of a series of fixed-size (typically 512-byte) data blocks, which can be read independently by the device. When the device detects consecutive data blocks, it will automatically combine them into a firmware image. This design allows the device to start running the update after receiving a partial file, thus improving the reliability of the update.

In addition, UF2 files feature a specific trailing structure that allows devices to easily identify their file type. This characteristic enables UF2 files to operate seamlessly across various operating systems such as Windows, Linux, or macOS, and be compatible with a wide range of development boards.

It has the following features:

  • Easy to use - Users can upload UF2 files to compatible hardware devices via simple drag-and-drop operations;
  • Cross-platform compatibility - works with multiple operating systems and is widely used in various microcontrollers and development boards;
  • Robustness - Ensures successful firmware updates even in unstable network environments;
  • Flexibility - Can be easily adapted to different hardware architectures and memory layouts.

XIP —— eXecute In Place

Memory units in a microcontroller can be roughly divided into two categories:

  1. RAM: All the modifiable variables used during program execution are stored in RAM;
  2. ROM: Mainly used to store instruction codes and certain fixed values, which cannot be modified after the program is running. For example, all the code in. c and. h files, global variables, local variables, constant data defined by the 'const' qualifier, and the code in the startup.asm file are all stored in ROM.

Flash memory, also known as flash, combines the advantages of both ROM and RAM. It not only features the electrically erasable programmable (EEPROM) performance, but also retains data without power supply while enabling fast data readout. In the past, embedded systems consistently used ROM (EPROM) as their storage device; however, in recent years, Flash has fully replaced the position of ROM in embedded systems.

During the code execution of a microcontroller unit (MCU), it is usually necessary to read the code from ROM or external flash memory into a RAM buffer before executing it sequentially. However, many modern NOR QSPI flash memories support the XIP (eXecute In Place) function. In this mode, an embedded MCU chip can directly fetch instructions from the NOR QSPI flash for subsequent use by the decoder and execution unit, without the need to preload the code into RAM..Simply put, XIP is a mechanism that enables code to be executed directly in flash memory without being loaded into RAM for execution, which reduces the time required for the kernel to be copied from flash memory to RAM.

When flashing a self-developed application to the Raspberry Pi Pico 2, the program is first written to the external Flash, and then when the chip boots up, the bootloader in its internal ROM loads and executes the program via XIP/Cache.

The specific meaning of each symbol in its name RP2350A is as follows:

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

(Note: RP stands for Raspberry Pi, 2 indicates the 2nd-generation architecture, 3 denotes the core architecture generation, 5 represents 2 to the power of 5 (i. e., 32), 0 means no built-in Flash, and A refers to the 7x7 QFN-60 package)


2.1 Block Diagram of the Chip System

For any chip, the block diagram serves as the core starting point for learning — it acts as the chip's "architecture specification" and helps you build a systematic understanding (rather than a scattered list of functions) of the chip, which is the universal approach to learning all chips. Through the block diagram, you can first grasp the information from the following general dimensions before diving into specific functions:

The RP2350A features dual M33/RISC-V processor cores, DMA, on-chip memory, and peripheral blocks connected via an AHB/APB bus structure:

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

We can regard a chip as a "miniature factory", where each module in the diagram corresponds to a distinct "workshop / position". Below, we will explain the role of each "position" in the RP2350A according to the partitions in the diagram:

A brief description is provided as follows:


2.2 Pin Mapping

For chip learning, pin mapping is the key link between "internal chip functions" and "actual physical hardware" — it is a "wiring guide" that establishes a one-to-one correspondence between the functional modules in the chip block diagram (such as GPIO, ADC, UART) and the physical pins on the chip package (i. e., the exposed metal leads of the chip).

The reason why it is necessary to understand the pin mapping is as follows:

RP2350A 1 60 I2C GPIO00 GPIO01 3 GPIO11 I2C0_SDA I2C0_SCL

NameDescription
GPIOxGeneral-purpose digital input and output. Can connect internal peripherals or be controlled directly from software.
GPIOx/ADCyGeneral-purpose digital input and output, with analogue-to-digital converter function. The RP2350 ADC has an analogue multiplexer to select these pins for voltage sampling.
QSPIxInterface to SPI, Dual-SPI, or Quad-SPI flash or PSRAM device, with execute-in-place support. Can be used as software-controlled GPIOs if not required for flash access.
USB_DM and USB_DPUSB controller, supporting Full Speed device and Full/Low Speed host. Requires 27Ω series termination resistor on each pin. Bus pullups and pulldowns are provided internally. Can be used as GPIOs if USB is not required.
XIN and XOUTConnect a crystal to RP2350’s crystal oscillator. XIN can also be a CMOS clock input. Defaults to 12 MHz crystal or clock input for USB bootloader. Configurable via OTP.
RUNGlobal asynchronous reset pin. Reset when driven low, run when driven high. Can be tied directly to IOVDD if no external reset is needed.
SWCLK and SWDIOAccess to internal Serial Wire Debug bus for debug access and code download.
GNDSingle external ground connection, bonded to internal ground pads.
IOVDDPower supply for digital GPIOs, nominal voltage 1.8V to 3.3V.
USB_OTP_VDDPower supply for internal USB Full Speed PHY and OTP storage, nominal voltage 3.3V.
ADC_AVDDPower supply for analogue-to-digital converter, nominal voltage 3.3V.
QSPI_IOVDDPower supply for QSPI IOs, nominal voltage 1.8V to 3.3V.
VREG_AVDDAnalogue power supply for internal core voltage regulator, nominal voltage 3.3V.
VREG_PGNDPower-ground connection for internal core voltage regulator, tie to ground externally.
VREG_LXSwitched-mode output for internal core voltage regulator, connected to an external inductor. Max current 200 mA, nominal voltage 1.1V after filtering.
VREG_VINPower input for internal core voltage regulator, nominal voltage 2.7V to 5.5V.
VREG_FBVoltage feedback for internal core voltage regulator, connect to filtered VREG output (e.g., to DVDD, if used to supply DVDD).
DVDDDigital core power supply, nominal voltage 1.1V. Must be connected externally, either to the voltage regulator output or an external board-level power supply.

Taking the pin mapping of this RP2350A as an example: the figure above shows the physical pin numbers (1-60) of the chip, and the table below lists the corresponding functions of each pin. Only by mastering this can you translate the information you previously learned from the table — "pins with GPIO and ADC functions" — into practical hardware connections and program development.


2.3 Pin Multiplexing Function

Put simply, pin multiplexing means "a single GPIO pin can serve multiple roles" — for instance, one GPIO pin can function as an ordinary switch (to control the on/off of an LED), or be switched to act as an "SPI interface"(to connect a sensor) or a "UART interface"(to connect to a serial port). Just like a smartphone's Type-C port, which can not only charge the device but also transfer data and connect to other peripherals, realizing multiple functions through one single port — that is exactly what "multiplexing" refers to.

Each individual GPIO pin can be connected to an internal peripheral device via the GPIO function defined below.

RP2350A GPIO0 GPIO22 F1 F11 UART0
RP2350A GPIO0 GPIO1 UART1 11
W6300/W5500/5100S-EVB RP2350A F1 F11 GPIO45 SPI1 UART0 GPIO46 GPIO47

This table is the "Role Selection Table for GPIO", and its structure and usage are very straightforward:


2.4 Brief Introduction to System Characteristics and Architecture

2.4.1 Bus Interconnection Architecture

The bus interconnection structure serves as the "data transportation system" inside a chip — it governs how data and instructions are transmitted between various functional modules (cores, memory, peripherals), making it one of the core architectures that impact the chip's operating efficiency. Understanding it clarifies how the chip "avoids data transmission congestion" and the "communication priorities of different modules", which is the key to grasping the chip's performance bottlenecks and resource scheduling logic.

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

The core logic of the "on-chip communication network" of the RP2350A is as follows:

2.4.2 Address Mapping

To understand address mapping, we must first clarify its core definition: Address mapping refers to the rules by which a chip assigns unique "numeric addresses" to all its internal resources (including ROM, SRAM, peripheral registers, etc.)— it is essentially assigning a "house number" to every memory block and functional module inside the chip; modules such as the core and DMA can use this "house number"(address) to precisely locate and access the corresponding resource.

The reason why address mapping is required is that the arithmetic and control modules of the chip (such as dual-core processors and DMA controllers) can only locate resources via "addresses": for example, when the core needs to read data from the SRAM or configure the communication parameters of the UART, it must first find the storage area of the SRAM and the control registers of the UART through the corresponding addresses — without address mapping, these modules are like "rooms without house numbers" that cannot be located or accessed at all. The essence of address mapping is to establish a unique accessible identifier for resources, which serves as the fundamental rule for internal communication within the chip.

And the address mapping works in deep coordination with the previously mentioned "SRAM partitioning" — take the SRAM of RP2040 as an example: As previously explained, the SRAM is physically divided into 6 banks (SRAM0 to SR5), which is designed to support "parallel access" by multiple modules (for instance, while Core0 is accessing SRAM0, the DMA can access SRAM1 simultaneously);The address mapping table assigns independent address ranges to these 6 banks (for example, SRAM0_BASE is 0x21000000 and SRAM1_BASE is 0x21010000).

As a result, when Core0 accesses addresses starting with "0x21000000", they actually correspond to the physical SRAM0; when DMA accesses addresses starting with "0x21010000", they correspond to the physical SRAM1 — the address mapping enables different modules to access "different physical partitions" via "different house numbers", which not only realizes precise resource positioning, but also achieves "parallel access" in coordination with the physical partitions of SRAM, avoiding resource conflicts between modules and improving data access efficiency.

The address map of the RP2350A is a significant expansion of that of the RP2040 to accommodate the increased memory and newly added peripherals:

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction
00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

...

As can be seen from the address mapping table in the figure:

2.4.3 Processor Subsystem

The RP2350A processor subsystem consists of two switchable-architecture processors (Arm Cortex-M33 or Hazard3 RISC-V) — each comes with its standard internal Arm CPU peripherals as well as external peripherals for GPIO access and inter-core communication.

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

The "working interconnect framework" of the RP2350A dual-core processor defines the communication modes between the two cores and other modules of the chip as well as external devices. It serves as the fundamental supporting structure for the dual-core collaborative operation, and the functions of the core communication interfaces are as follows:

Next, we will introduce these key components one by one.

2.4.3.1 Single-cycle IO block (SIO)
00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

SIO is the "high-speed collaboration toolbox" for the RP2350A dual-core processor — it leverages the IOPORT auxiliary bus of the Cortex-M33 to achieve "single-cycle (ultra-fast)" operations, and is specifically designed to handle tasks with stringent speed and timing requirements such as "high-speed data transfer between dual cores", "contention for shared resources", and "high-speed GPIO control".

The essence of SIO is a "fast lane module" based on the IOPORT auxiliary bus: IOPORT is a dedicated fast bus port of Cortex-M33, corresponding to the address range starting from 0xd0000000, which can be accessed with ordinary read and write instructions. Moreover, SIO is not connected to the main system bus and only uses this fast channel — this ensures that all read and write operations of SIO can be completed within 1 cycle, featuring high speed and precise timing.

SIO is accessed by using the auxiliary bus IOPORT of Cortex-M33, which is designed to save access time, execute high-speed computing tasks, and can also be used for communication between two cores.

IOPORT is an auxiliary bus port on the Cortex-M33, which is capable of performing high-speed 32-bit read and write operations.

Processors access their IOPORTs using normal load and store instructions, pointing to the special IOPORT address range 0xd0000000.. .0xdfffffff. The SIO appears as memory-mapped hardware in the IOPORT space.

SIO has a dedicated bus interface for each processor's IOPORT. Due to its strict timing requirements, SIO is not connected to the main system bus, and can only be accessed by the processor or a debugger via the processor debug port.

Read and write operations of SIO are all completed in one cycle, consisting of the following units:

Popular Explanation of SIO

The core functional units included in SIO all serve the purposes of "dual-core collaboration" and "high-speed operation":

  • Dual-Core FIFO: serves as the "high-speed express box" between the two cores
    • FIFO0 can only be written to by Core0 and read by Core1; FIFO1 can only be written to by Core1 and read by Core0.
    • Its function is to enable the dual-core to transmit data and messages quickly (for example, after Core0 processes the sensor data, it directly writes the data into FIFO0, from which Core1 can read it immediately) without going through the main bus, thus avoiding latency.
  • CPUID: The "identification tag" for dual-core processors
    • Core0 reads this register and gets "0", while Core1 reads it and gets "1".
    • At startup, the two cores run simultaneously: Core1 reads its own ID as "1" and enters sleep mode, while Core0, which reads "0", executes the bootloader. Through this "identity identifier", task division during dual-core startup is achieved to avoid conflicts.
  • hardware Mutex lock (spin lock): a "shared resource placeholder" for dual-core systems
    • When two cores need to access the same shared resource (such as the same block of memory), use this lock: a "read lock" is equivalent to "occupying the resource", while a "write lock" is equivalent to "releasing the resource".
    • Ensure that only one core can use the shared resource at the same time to avoid data confusion.
  • Hardware Division & Interpolator: The "Fast Calculation Accelerator" for Dual-Core Processors
    • A hardware divider enables division operations to be completed within a single cycle (far faster than software-based calculation); an interpolator is a piece of hardware that assists with interpolation operations.
    • Its function is to accelerate specific computing tasks and improve core computing efficiency.
  • IO Shared Access Control: It is the "high-speed control port" of GPIO
    • Accessing GPIO registers via SIO follows a "single-cycle + atomic operation" mechanism (the operation will not be interrupted), which is faster and more precise than controlling GPIOs through the main bus.
    • Suitable for scenarios with high requirements for GPIO timing (such as fast control of LED blinking and high-frequency signal output).
2.4.3.2 Interrupt

Interrupts are the core mechanism of the RP2350 for handling "sudden tasks" — for example, when a timer expires, data is received via a serial port, or a sensor triggers a signal, the core cannot wait to "finish the task at hand" before processing these events; at such times, an interrupt will "interrupt" the core's current operation to prioritize the urgent task. The NVIC (Nested Vectored Interrupt Controller) acts as the "interrupt dispatcher" for each core, responsible for managing interrupt priorities and execution sequences. The following explains its logic clearly with reference to the table and relevant rules:

IRQ and Priority

  • IRQ :short for "Interrupt Request", is an "urgent call signal" sent by peripherals (such as timers and UARTs) to the processor core. When a peripheral needs the core to process a task immediately (for example, when a timer expires or data is received via a serial port), it will trigger the corresponding IRQ, causing the core to suspend its current work and prioritize handling this urgent task.
  • Priority: refers to the sorting rule for the urgency of interrupt tasks. A chip may receive multiple IRQs at the same time, and tasks with higher priority will be processed first by the core to prevent urgent tasks from being delayed.

Each core (Core0 and Core1) has an independent NVIC (equivalent to a dedicated "interrupt dispatcher") that can receive 52 interrupt signals. On the RP2350, only the lower 46 IRQ signals are connected to system-level interrupt sources, while IRQ 46 to 51 are hardwired to zero (never triggered).These six spare interrupts (referred to as SPAREIRQ_IRQ_0 to SPAREIRQ_IRQ_5 in the table) are intentionally reserved for the kernel to use for self-interrupts (via the Arm NVIC_ISPR0 register or the Hazard3 MEIFA CSR), for example, when an interrupt handler wishes to schedule a "bottom half" handler for work that must be completed after the interrupt handler exits but before the code returning to foreground execution runs.

Hardware supports nested interrupts: a low-priority interrupt can be preempted by a higher-priority interrupt or fault, and resumed after the higher-priority handler returns. The preemption priority order is determined by the interrupt priority registers, starting from NVIC_IPR0 (for Cortex-M33) or the MEIPRA interrupt priority array CSR (for Hazard3).

When multiple interrupts enter with the same dynamic priority, the interrupt with the lowest IRQ number will be selected as the winner. For this reason, system-level IRQ numbering typically assigns higher-priority interrupts to lower IRQ numbers, although the actual priority often depends on the specific application.

The interrupt vector table of the RP2350 is as follows. This table acts as the "task list for IRQs", where each IRQ number corresponds to a specific "source of urgent task":

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction
00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

For example, IRQ0 corresponds to the "IRQ of Timer 0"(meaning Timer 0 has timed out), and IRQ33 corresponds to the "IRQ of UART0"(meaning UART0 has received data). Once the core sees the IRQ number, it can immediately identify which peripheral has sent the "urgent call" and then invoke the corresponding handler.

The meanings of the respective interrupts are as follows:

Interrupt nameInterrupt Meaning and Additional Notes
TIMER_IRQ_x (x=0~3)Interrupts related to the general-purpose timers (x is 0-3, corresponding to the interrupts of the 4 general-purpose timers)
PWM_IRQ_WRAPPWM timer wrap interrupt (triggered when the PWM counter reaches its maximum value and wraps around)
USBCTRL_IRQUSB control interrupts (triggered by events such as USB peripheral state changes and data transfers)
XIP_IRQInterrupt related to the SSI synchronous serial interface controller; the signal comes from the SSI controller of the XIP cache for external flash, and can be used in configurations where code runs from SRAM instead of flash; once enabled, the XIP block can be used as a normal SSI peripheral
PIOx_IRQ_y (x=0/1, y=0/1)Programmable IO interrupts (x is 0-1 for the 2 PIO blocks, y is 0-1 for the 2 interrupts of each PIO block)
DMA_IRQ_x (x=0/1)DMA controller interrupts (x is 0-1 for the interrupts of the 2 DMA controllers)
IO_IRQ_BANK0General-purpose GPIO interrupts (triggered by level changes on the Pico's ordinary GPIO pins)
IO_IRQ_QSPIInterrupts related to the QSPI peripheral GPIOs connected to external flash (triggered by events on the QSPI interface GPIO pins)
SIO_IRQ_PROCx (x=0/1)Single-cycle low-latency IO interrupts (x is 0-1 for the SIO interrupts of the 2 CPU cores)
CLOCKS_IRQClock system interrupts (triggered by events such as clock module state changes and frequency adjustments)
SPIx_IRQ (x=0/1)SPI peripheral interrupts (x is 0-1 for the interrupts of the 2 SPI peripherals, such as receive complete and transmit complete)
UARTx_IRQSerial port interrupts (interrupts of the UART peripheral, such as receive complete, transmit complete, and communication errors)
ADC_IRQ_FIFOInterrupts related to the FIFO memory of the ADC analog-to-digital converter (triggered by events such as the ADC FIFO buffer reaching a threshold or overflowing)
I2Cx_IRQ (x=0/1)I2C serial communication bus interrupts (x is 0-1 for the interrupts of the 2 I2C peripherals, such as receive complete and transmit complete)
RTC_IRQRTC real-time clock interrupts (triggered by RTC timing events, alarms, etc.)

Actually, interrupts can also be divided into the following two types: maskable interrupts (IRQ, Interrupt Request) and non-maskable interrupts (NMI, Non Maskable Interrupt). The core difference between the two lies in "whether they can be selectively ignored by the CPU", as summarized in the table below:

FeatureMaskable Interrupt (IRQ)Non-Maskable Interrupt (NMI)
Core DefinitionAn interrupt that can be selectively ignored through software configuration (masking)The highest-priority interrupt, which breaks through normal masking restrictions
MaskabilityCan be completely masked by the CPU's interrupt mask bit; once masked, the CPU will not respond even if the interrupt occursCannot be masked by normal means (the core meaning of the name); can only be configured in a limited way through dedicated registers
Trigger ScenariosRoutine peripheral events (such as UART data reception, GPIO button presses, timer timeouts)Severe emergency events (such as hardware faults, power loss, coprocessor errors, core hardware exceptions)
PriorityLower; multiple IRQs can be nested by setting priorities through the NVICHighest; can interrupt an IRQ being handled, and even the CPU's normal operation

Simply put:

The system interrupts of the RP2350 (such as TIMER_IRQ, UART_IRQ, GPIO_IRQ, etc.) will undergo two-step processing before being combined with core interrupts into a single NMI signal that is fed into the corresponding CPU core. This entire process can be understood as "interrupt filtering and merging":

  1. Step 1: Masking (selectively ignoring some system interrupts): First, 26 system interrupts will go through masking processing — which is equivalent to setting a "do not disturb switch" for these interrupts. You can configure the mask register to select "which system interrupts to temporarily ignore even if they occur". For example, you can set "mask UART_IRQ", then even if the UART receives data, this interrupt will not enter the subsequent processing flow.
  2. Step 2: Perform an OR operation with the kernel interrupt to merge them into an NMI: After being masked, the remaining "non-ignored system interrupts" will undergo an OR operation with the CPU's internal kernel interrupts (such as more severe internal exceptions like power loss, coprocessor operation errors, and hardware faults) — if any one of these interrupts occurs, the result will be "interrupt present". Eventually, these scattered interrupt signals will be merged into a unified NMI signal and fed into the CPU core.

The core purpose of this process is: to uniformly encapsulate all emergency events that require the highest priority processing into NMI signals, so as to ensure that the CPU can respond to these critical events first.

NMI is not absolutely non-maskable

Many beginners mistakenly assume that NMI stands for "interrupts that absolutely cannot be masked", but in reality, the true meaning of "Non-maskable" is that even when normal maskable interrupts (IRQs) are masked, such NMI interrupts can still be delivered to the CPU.

In other words, the "non-maskable" property of NMI is relative to the masking of conventional interrupts, and it is not absolutely impossible to configure: we can still perform limited configuration on the enable of NMI signals through dedicated registers (this is a special configuration for NMI, which is different from conventional interrupt masks).

On the RP2350, by setting the bit corresponding to the target IRQ number in NMI_MASK0 or NMI_MASK1, system IRQ signals can be routed to the Non-Maskable Interrupt (NMI) input of the Cortex-M33. A non-maskable interrupt ignores the processor's interrupt enable/disable state (PRIMASK) and can preempt any other active interrupt. NMIs are typically used for emergency situations that require the processor's unconditional attention, such as PLL lock loss or compromised power integrity.

The NMI mask register is core-local, so each core can route a different combination of interrupts to its NMI input. Both the NMI mask register and all other EPPB registers are reset by a warm reset of the core. This avoids a potential issue in the RP2040 where the NMI mask register might remain asserted after a processor reset.

In addition to system-level interrupts, a non-maskable interrupt is also generated when an integrity check failure occurs in the Redundant Coprocessor (RCP). This behavior cannot be disabled, but a properly programmed RCP will not trigger it under normal voltage, frequency, and temperature conditions. Likewise, the RCP will never trigger if user code does not execute any RCP instructions. When an integrity check fails, the RCP NMI outputs on both cores are asserted, and they are cleared via a processor warm reset.

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction
2.4.3.3 Event Signals

First, clarify the core concepts:

In the RP2350, the event signal serves as the core mechanism for dual-core collaboration and low-power sleep, with the logic as follows:

2.4.3.4 Debugging

Before understanding the structure of debugging, let's first clarify several core concepts:

The debug communication architecture of the RP2350A implements "unified control of the dual-core by an external debugger + debug reliability assurance". The core logic is as follows:

2.4.4 Cortex-M33 / Hazard3 Core

Here is the biggest architecture upgrade highlight of the RP2350A

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

The core is the central processing brain of a microcontroller chip. The RP2350A breaks the norm by integrating two distinct dual-core processor architectures on a single chip, which users can select at boot time via software or even OTP fuse bits:

  1. Arm Cortex-M33 processor: This is an industry-standard core. Compared with the Cortex-M0+ of the RP2040, it not only features a higher clock speed (150MHz), but also supports hardware single-precision floating-point operations (FPU) and DSP instructions, and introduces Arm TrustZone technology, which can create an isolated secure environment for sensitive code and data.
  2. Hazard3 RISC-V Processor: This is a pair of open-source RISC-V cores that allows users to experiment with and transition to the RISC-V architecture in a stable, well-supported ecosystem.

Regardless of which architecture is selected, both cores will operate at a frequency of 150MHz.

Core Features of Arm Cortex-M33:

What is a "pipeline"?

Pipelining is a parallelized working mechanism for processors to execute instructions. The 3-stage pipeline of the Cortex-M33 splits instructions into three steps: "fetch", "decode" and "execute", allowing different steps to be carried out simultaneously to further improve instruction execution efficiency.

Commonly used in the following applications:

For the normal operation of the kernel, different modules are required to provide basic guarantees such as power supply, clock, interrupt, and debugging for the kernel:

(If the RISC-V architecture is selected, its internal structure is similar to the above, but it complies with the standard instruction set and debugging specifications of RISC-V)

2.4.5 DMA

The core function of a kernel is to "perform operations and process tasks"; if it is made to manually move data, computing power will be wasted. DMA, by contrast, is a "dedicated data transfer tool" that can efficiently complete bulk transfers.

The RP2350A upgrades the DMA to 16 independent channels, is equipped with 4 system IRQs, features separate read and write master connections, and can perform bulk data transfers on behalf of the processor.

DMA can control up to 32-bit data during individual read and write operations, features 16 independent channels, and each channel monitors a series of bus transmissions.

DMA is typically used for data transmission in the following three scenarios:

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

The architecture diagram illustrates the "internal workflow" of DMA, and the functions of each module are as follows:

Next, let's take the "peripheral to memory" transfer as an example:

  1. The core writes configurations to the Control/Status Registers via the AHB-lite Slave Interface;
  2. The Address Generator automatically generates the peripheral address to be read and the memory address to be written, and stores them in the Read/Write Address FIFO respectively;
  3. The AHB-lite Read Master reads data from the peripheral and stores it into the Transfer Data FIFO buffer;
  4. The AHB-lite Write Master fetches data from the Transfer Data FIFO and writes it to the target address in the memory.
  5. During the entire process, the kernel does not need to participate, and the whole process is completed automatically by DMA.

Each channel of DMA is equipped with a corresponding status register, through which software can program and monitor the progress of data read and write operations on that channel.

The size of data transferred via DMA can be 32 bits, 16 bits or 8 bits. Each channel is configured such that the source transfer size matches the destination transfer size.

DMA channels can be combined with each other; for instance, one channel can configure another one by loading configuration data from a series of control blocks in memory, and then when reconfiguration is required, the second channel can invoke the first channel via the CHAIN_TO option.

Meanwhile, DMA can also be used in conjunction with other peripherals, and data is transmitted directly between peripherals and DMA via DREQ channels.

For the correspondence between different peripherals and DREQ channels, please refer to the DREQ table:

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

DMA can also be used in conjunction with interrupts, and an interrupt can be triggered when data reading and writing of a certain channel in DMA is completed.

The RP2350A DMA provides four system IRQs (IRQ0 to IRQ3) with individual masking and status registers. Any combination of channel interrupt requests can be routed to any of these four system IRQs:

The advantage of this design is that it can manage the interrupts of up to 16 DMA channels more flexibly and avoid interrupt signal confusion.

2.4.6 Memory

Here, we first clarify several core concepts of "mapping"(which serves as the foundation of memory access), and then explain the address mapping tables for memory and SRAM. For the resources inside a chip (including memory, registers, and peripherals) to be accessible, they must first be assigned "house numbers" — this is the essence of "mapping":

For knowledge related to address mapping, register mapping, remapping and other related concepts, please refer to the following link:

Fundamentals of the STM32 Register Version — Memory Mapping:

https://developer.aliyun.com/article/935522

【Experience Sharing】STM32 Getting Started Series - STM32 Peripheral Address Mapping

https://shequ.stmicroelectronics.cn/thread-635602-1-1.html

Microcontroller Memory and Memory Mapping (Local Address, Logical Address, Global Address)

https://blog.csdn.net/u014157109/article/details/120370973

Memory access is entirely based on address mapping. Let’s take a closer look at the memory of the RP2350A: the RP2350A has built-in ROM and SRAM, and accesses external Flash or PSRAM via the QSPI interface.

2.4.6.1 ROM

16kB Read-Only Memory (ROM) at address 0x00000000, which is equivalent to a "pre-installed toolkit built into the chip" and contains:

  1. Initialize the boot routine
  2. Flash boot sequence
  3. Flash Programming Routine
  4. USB mass storage device supporting UF2
  5. Utility libraries (e. g., fast floating-point, hardware SHA-256 acceleration interface, etc.)
  6. This ROM supports single-cycle read-only bus access and is connected to a dedicated AHB-Lite arbiter; any attempt to write to the ROM will have no effect.
2.4.6.2 SRAM

The total on-chip SRAM amounts to 520 kB. Physically, it is divided into ten banks (Bank0 to Bank9), which significantly enhances the memory bandwidth for multiple masters; for software, it can be regarded as a contiguous 520 kB memory region for read and write access operations.

Each SRAM bank can be accessed via a dedicated AHB-Lite arbiter, which means that different bus masters can access separate SRAM banks in parallel, allowing up to four 32-bit SRAM accesses per system clock cycle.

In the memory map, the start address of the SRAM is 0x20000000, and the base address of each specific bank is as follows:

[Image]

We can see that this mapping table contains the following information:

System addresses are sequentially mapped to different physical banks. The advantage of this mapping is that when multiple modules access different system addresses simultaneously, they are actually accessing separate physical banks, which enables "parallel access" and significantly improves the read and write speed of SRAM.

2.4.6.3 Flash and External Storage

Here, we first introduce two key concepts:

The core of the entire structure is to enable external storage to be accessed in the same way as internal memory, while leveraging caching to boost speed:

When the kernel needs to read program instructions from external storage, it efficiently completes this operation through this set of hardware mechanisms. In addition, the QSPI controller of the RP2350A also supports external PSRAM, which further expands the memory capacity.

2.4.6.4 OTP (One-Time Programmable Memory) — New in RP2350A

The RP2350A introduces 8kB of one-time programmable (OTP) memory.

OTP is a type of storage medium that can only be written once (or a small number of times); once written, the data is permanently retained, will not be lost even when power is cut off, and cannot be easily tampered with.

In the RP2350A, OTP is primarily used to store security-sensitive information, such as:

2.4.7 BOOT Boot Sequence

The "boot sequence" of a chip is just like the entire process of a computer from being in a "black-screen power-off state" to "entering the system and being able to run software" after it is turned on. After the RP2350A is powered on or reset, it will first execute the "boot process" built into the chip.

The startup process here can be divided into the following two stages:

  1. Hardware control (hardware controlled): The chip performs its own preparation tasks;
  2. Processor controlled: Execute the bootrom bootloader.

bootrom boot loader

The bootrom bootloader is a piece of code smaller than 16KB that runs first when the chip is powered on or reset. It consists of:

2.4.7.1 hardware-controlled boot sequence
  1. When the chip is powered on, the RUN pin is set;
  2. The on-chip voltage regulator waits for the digital chip power supply (DVDD) to stabilize;
  3. The power-on finite-state machine has been started and has completed the following tasks in sequence:
  4. a. The ROSC (Ring Oscillator) has been started, providing the initial clock source for the clock generator, with clk_sys and clk_ref operating at a relatively low frequency;
  5. b. The main clock multiplexer selects ROSC as the clock source;
  6. c. The reset controller releases the reset on the processor, and the processor starts executing code;
  7. d. Instruct the ROM (boot ROM) to start execution.

2.4.8 Power Supply System

00 WIZnet W6300/ W 5500/5100S-EVB Board Detailed Introduction

Popular Analogy

If a chip is compared to a miniature city, its power supply system is exactly the "power grid" of this city. All the residents (cores), shopping malls (SRAM) and external stations (GPIO) in the city require power of different specifications to function. Fortunately, the RP2350A is a "highly integrated" modern city: you only need to connect it to a 3.3V main power supply, and its internal "substation (LDO)" will automatically step down the voltage and distribute it to each component, eliminating the need for you to build a complex external power supply circuit.

The power supply system of the RP2350A has been restructured compared to the RP2040: the separate power pin for the ADC has been removed, and the independence of the core power supply has been enhanced. Its main power supply pins are divided into the following categories:

2.4.8.1 External Main Power Supply Input (VREG_VIN)

This is the "main switch" that supplies power to the entire interior of the chip. You only need to connect a 3.3V DC power supply here, and the voltage regulator inside the chip will start working to generate the required voltage for other modules.

2.4.8.2 Digital IO Power Supplies (VDDIO0 and VDDIO1)

This is the power supply for the chip's "external communication", namely the high-level voltage of the GPIO pins.

2.4.8.3 Core Power Supplies (VCORE0 and VCORE1)

This is a dedicated power supply for the "brain and memory" of the chip (dual-core processor, SRAM, ROM), with an extremely low voltage (usually around 0.8V - 1.1V).

2.4.9 Linear Dropout Regulator (LDO) for Core Power Supply

Simple Analogy

If the external 3.3V supply is the "high-voltage power line", then the on-chip low-dropout regulator (LDO) is the chip's built-in "phone charger (power bank)". It is responsible for precisely stepping down the 3.3V high voltage to around 1.1V that the core can accept, while also keeping the voltage rock-solid so as to prevent the chip from "crashing and rebooting" due to voltage fluctuations.

The RP2350A integrates two independent LDOs (LDO0 and LDO1), which supply power to the two cores (Core 0 and Core 1) of the processor and their associated memory units respectively. Automatic voltage regulation: By default, the LDO outputs 1.1V. However, if you are writing low-power code, you can configure the voltage to a lower level (down to 0.65V minimum) via software; when combined with a reduced main frequency, this enables the chip to achieve ultra-low power consumption when entering sleep mode.

Three operating modes of LDO (controlled via registers):

  1. Normal Mode (Normal): The default state upon power-on, which stably outputs the set voltage and supplies power at full capacity.
  2. High-impedance mode (High-Z): The LDO stops operating, and the output terminal becomes "floating". This mode is typically used when you want to connect an external, more power-efficient switching power supply to replace the internal LDO (an advanced usage scenario).
  3. Shutdown Mode: Complete power-off. If the kernel is still running at this point, it will trigger a reset.

2.4.10 Low Power Mode Adjustment

Popular Analogy

Power consumption of a chip is analogous to running a company, and low-power regulation functions as an "energy-saving management system". When certain departments (peripherals) have no tasks to handle, you either put them on "standby (clock gated)" or directly "lay off staff (power gated)" to cut down the company's operating costs (battery life).

The RP2350A features highly flexible dynamic power management:

For static power consumption (leakage current during standby), the RP2350A provides multiple levels of sleep modes:

  1. WFI (Wait For Interrupt) / Sleep Mode:
    • State: The CPU stops executing instructions, while the contents of the SRAM and registers are fully retained, and all peripherals continue operating.
    • Wake-up: Any interrupt (such as a timer timeout or a key press) can wake up the the CPU instantly.
    • Power consumption: Medium (mainly the static leakage current of SRAM and LDO).
  2. Deep Sleep :
    • Status: The CPU, most peripherals, and even the high-frequency PLL are all shut down. Only the low-speed real-time clock (RTC) and wake-up logic remain operational. The contents of the SRAM are still retained.
    • Wake-up: It can only be triggered by the level change of a specific GPIO pin or the RTC alarm.
    • Power consumption: Extremely low (only at the microampere level), making it ideal for battery-powered IoT devices.

2.4.11 Reset System

Simple Analogy

Reset is the "restart mechanism" of a chip. This mechanism is required in all scenarios, whether it is when power is just plugged in (cold start), when the program runs wild and crashes (watchdog reset), or when you simply want to reset a faulty hardware module (subsystem reset).

2.4.11.1 Chip-Level Reset (Global Reset)

This reset will return the chip to its factory state, clearing all registers and memory (with the exception of special reserved areas).

Trigger Condition:

2.4.11.2 Subsystem Reset (Peripheral Reset)

Only reset the specified peripheral without affecting the CPU and other modules.


2.4.12 Power-On finite-state machine (Power-On State Machine)

Popular Analogy

If we compare chip startup to a rocket launch, the power-on finite-state machine is exactly that "countdown system". It is controlled purely by hardware logic, independent of software, and is responsible for waking up the internal modules of the chip one by one in a strict sequence.

Why is it needed?

If power is supplied to all modules at once, it may generate a huge inrush current that burns out the chip, or cause the kernel to start reading data before the clock stabilizes, leading to a crash.

Boot sequence of the RP2350A:

  1. Power Supply and Reset: When the VREG_VIN voltage is detected to meet the specification, the RUN pin is pulled high to release the global reset.
  2. Start the internal oscillator (ROSC): First, activate a relatively inaccurate internal clock to provide the system with a "heartbeat".
  3. Start the external crystal oscillator (XOSC): Switch to an external high-precision crystal oscillator (e. g., 12MHz) to obtain a stable clock.
  4. Start the phase-locked loop (PLL): multiply the crystal oscillator frequency (e. g., up to 150MHz) to serve as the system clock frequency.
  5. Initialize memory and bus: Wake up the SRAM, initialize the AHB crossbar switch, and open up the data expressway.
  6. Yield control: Finally, jump to the Bootloader code in the ROM to prepare for loading the user program.

The whole process is fully automatic, and developers do not need to write any code, just ensure that the hardware circuit is correct.


2.4.13 Clock System

Popular Analogy

If the heartbeat of a chip is uniform, different components, like organs, require different blood supply rates. The clock system is essentially a "variable-frequency water supply system": it features multiple water inlets (clock sources), which, after going through pressurization (PLL) and flow splitting (frequency dividers), deliver power precisely to every peripheral component.

Clock architecture upgrade points of the RP2350A:

Common clock distribution:


2.4.14 GPIO Interfaces and Peripherals

Popular Analogy

GPIO is the "tentacles" and "eyes" that chips extend to the outside world. The RP2350A features up to 48 GPIO pins (the exact number depends on the package; for example, the QFN-60 package provides 30 user GPIOs), which are extremely flexible and can be configured via software to function as almost any type of Communication Protocol.

2.4.14.1 Function Select

The RP2350A has much more powerful pin multiplexing capabilities. Each pin incorporates an internal multiplexer that can be configured via the FUNCSEL register to assign the pin to one of the following roles at any given time:

(Note: To avoid signal conflicts, only one function can be selected for a single pin at a time; likewise, the input pin of a peripheral cannot be bound to two different GPIOs simultaneously.)

2.4.14.2 Interrupt Control

GPIO can be configured to trigger an interrupt when a level or edge change occurs, eliminating the need for the CPU to constantly perform polling queries.

2.4.14.3 Electrical Characteristics of IO (Pads)

To protect the chip and adapt to different peripherals, the physical interface (Pad) of GPIO supports hardware-level parameter adjustment:


2.4.15 Sysinfo Register (System Information)

Popular Analogy

Just like pressing Win + Pause when a computer starts up to open "System Properties", the Sysinfo module acts as an "ID card reader" reserved by the chip for software to query relevant information.

Its register base address is 0x40000000, which stores several key read-only pieces of information:

RP2350A 0x40000000 0 QFN80 1 QFN60 GITREF_RP2350

2.4.16 Syscfg Register (System Configuration)

Popular Analogy

If Sysinfo serves as the tool for "viewing system properties", then Syscfg is the "BIOS setup interface" for the chip, which governs the most core low-level behavior configurations of the chip.

The address is 0x40008000, and its main functions include:

RP2350A 0x40008000 0x00
RP2350A 0x04 0_31 0x08 32_47 56_57 58_63 0x0c 0x10 0x14

2.4.18 TBMAN (Test Bench Manager)

Popular Explanation

TBMAN is short for Test Bench Manager.

Before a chip leaves the factory, the manufacturer requires an automated mechanism to test whether there are short circuits or open circuits in the logic gates and interconnects inside the chip. TBMAN is a module retained inside the chip for this production test purpose.

Impact on developers:

As an ordinary application developer, you will generally never need to operate on or care about the TBMAN module. It is only used during the self-test performed by Bootrom in the very early stage of chip startup, or in extremely special hardware fault diagnosis scenarios. If you encounter this module in an Errata or during advanced debugging, just know that it serves as an "internal physical checkup for the chip".

References

Version Record

Version Number

Modifier

Time

Content

v1.0.0

Li Zisheng

2025/09/16

Initialize the document, based on MicroPython version V1.23.0.

v1.1.0

Li Zisheng

2025/12/05

Add figure caption

v1.2.0

Li Zisheng

2025/12/17

Added plain-language explanations

v1.3.0

Bright Moon

2026/05/07

Added plain-language explanations