The Zero is a simple and powerful 32-bit extension
of the platform established by the UNO. The Zero
board expands the family by providing increased
performance, enabling a variety of project
opportunities for devices, and acts as a great
educational tool for learning about 32-bit
The Zero applications span from smart IoT devices,
wearable technology, high-tech automation, to crazy
robotics. The board is powered by Atmel’s SAMD21
MCU, which features a 32-bit ARM Cortex® M0+ core.
One of its most important features is Atmel’s
Embedded Debugger (EDBG), which provides a full
debug interface without the need for additional
hardware, significantly increasing the ease-of-use
for software debugging. EDBG also supports a
virtual COM port that can be used for device and
Warning: Unlike most Arduino & Genuino boards,
the Zero runs at 3.3V. The maximum voltage that the
I/O pins can tolerate is 3.3V. Applying voltages
higher than 3.3V to any I/O pin could damage the
The board contains everything needed to support the
microcontroller; simply connect it to a computer
with a micro-USB cable or power it with a AC-to-DC
adapter or battery to get started. The Zero is
compatible with all the shields that work at 3.3V
and are compliant with the 1.0 Arduino pinout.
You can find
your board warranty informations here
Arduino and Genuino boards based on AVR
microcontrollers get a reset and restart sketch
execution each time the Serial Monitor of the
Arduino Software (IDE) is opened. This is also the
mechanism used to upload sketches to these boards.
This board is different: when the Zero is connected
through the Programming Port and you open the
serial monitor, the board does not automatically
reset and the sketch loaded keeps running. To
restart the sketch you need to press the reset
button on the board itself.
In the Getting Started
, you can find all the information you
need to configure your board, use the Arduino Software (IDE)
start to tinker with coding and electronics.
To keep your Zero's Bootloader up to date, the
explains what you should do each time
there is a new Core release.