# GPIO Published articles for GPIO. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## ESP32-C5 Pico board follows Raspberry Pi Pico form factor, ships with on-board or external antenna DevFeed: [ESP32-C5 Pico board follows Raspberry Pi Pico form factor, ships with on-board or external antenna]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-09T07:00:50Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [ESP32-C5](), [Raspberry Pi](), [Espressif](), [cpu](), [RISC-V](), [SOC](), [Bluetooth](), [wifi 6](), [zigbee](), [Matter](), [Embedded Systems](), [ESP-IDF]() Tags: [802-15-4](), [arduino](), [battery](), [ble](), [bluetooth](), [bluetooth-le](), [boot](), [c-c-plus-plus](), [development-board](), [embedded-systems](), [esp-idf](), [esp32](), [esp32-c5](), [espressif](), [gpio](), [hardware](), [iot](), [matter](), [news](), [port](), [raspberry-pi](), [risc-v](), [thread](), [usb](), [waveshare](), [wifi-6](), [zigbee]() ### AI overview The Waveshare ESP32-C5 Pico is a development board in the Raspberry Pi Pico form factor. It uses an ESP32-C5-MINI-1 series module with a RISC-V processor, dual-band WiFi 6, Bluetooth LE, and 802.15.4 support for Zigbee, Thread, and Matter. The board includes GPIO headers, USB-C, buttons, LEDs, and Li-Ion battery support, with variants offering PCB or external antennas. ### Source excerpt Waveshare ESP32-C5 Pico board brings the ESP32-C5 dual-band WiFi 6, Bluetooth LE, and 802.15.4 (Zigbee/Thread) SoC to the Raspberry Pi Pico form factor. The board features an ESP32-C5-MINI-1 Series module with PCB or external antenna, two 20-pin GPIO headers, a USB-C port for power and programming, Reset and Boot buttons, and a few LEDs. It also supports Li-Ion battery charging and discharging. Waveshare ESP32-C5 Pico specifications: Wireless module - ESP32-C5-MINI-1 or ESP32-C5-MINI-1U Wireless MCU - Espressif Systems ESP32-C5HF4 CPU Single-core 32-bit RISC-V processor @ up to 240 MHz Low-power RISC-V core @ 48 MHz acting as the main processor for power-sensitive applications Memory - 384 KB SRAM on-chip Storage - 320 KB ROM, 4MB SPI flash Wireless Dual-band (2.4/5 GHz) 802.11ax WiFi 6, 802.11b/g/n WiFi 4 backward compatibility WiFi modes: Station mode, SoftAP mode, SoftAP + Station mode, and promiscuous mode Bluetooth 5.0 Low Energy (LE) with Mesh support, up [...] The post ESP32-C5 Pico board follows Raspberry Pi Pico form factor, ships with on-board or external antenna appeared first on CNX Software - Embedded Systems News. ## YuzukiNeko - A Linux-capable Allwinner F101 RISC-V SBC with Raspberry Pi Pico form factor DevFeed: [YuzukiNeko - A Linux-capable Allwinner F101 RISC-V SBC with Raspberry Pi Pico form factor]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-07T17:01:57Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Raspberry Pi](), [Linux](), [RISC-V](), [Hardware](), [SOC](), [Embedded Systems](), [Open Source](), [Kernel](), [Software]() Tags: [allwinner](), [allwinner-d-series](), [buildroot](), [cpu](), [embedded-systems](), [gpio](), [hardware](), [linux](), [linux-7-x](), [mipi](), [open-source](), [psram](), [raspberry-pi](), [risc-v](), [single-board-computer](), [specifications](), [spi](), [storage](), [usb](), [zephyr](), [zephyr-os]() ### AI overview YuzukiHD has introduced YuzukiNeko, a Raspberry Pi Pico-sized open-source single-board computer built around the Allwinner F101 RISC-V SoC. It includes a 1.008 GHz C907 core, 8MB or 16MB PSRAM, SPI NOR flash, microSD storage, USB-C, and GPIO expansion, with support for Linux, Buildroot, and Zephyr RTOS. ### Source excerpt YuzukiHD has made another open-source hardware Linux SBC. YuzukiNeko is a Raspberry Pi Pico-sized single board computer powered by a new Allwinner F101 RISC-V SoC. The Allwinner F101 processor features a single 1.008 GHz C907 RISC-V core, 8MB or 16 MB PSRAM, and support for various display interfaces such as MIPI DSI, 24-bit RGB, and LVDS. The YuzukiNeko board itself features the F101 SoC, an SPI NOR flash, a microSD card for storage, a USB-C port, and two 20-pin GPIO headers. YuzukiNeko specifications: SoC - Allwinner F101 CPU - T-head C907 RISC-V core up to 1.008 GHz Memory - 8MB or 16MB PSRAM @ 252 MHz Package - QFN-68 Storage 128 Mbit NOR flash (PY25Q128HA-SUH-IT) MicroSD card slot USB - USB Type-C port for data, power, and programming Expansion 2x 20-pin expansion headers with GPIOs, ADC, 5V, 3.3V, and GND 5x pads with HP out (analog speaker output) and four [...] The post YuzukiNeko - A Linux-capable Allwinner F101 RISC-V SBC with Raspberry Pi Pico form factor appeared first on CNX Software - Embedded Systems News. ## XIAO SAMD21 Plus and RP2040 Plus USB-C boards get additional GPIO pins, integrated Li-ion battery management DevFeed: [XIAO SAMD21 Plus and RP2040 Plus USB-C boards get additional GPIO pins, integrated Li-ion battery management]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-07T01:07:22Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Embedded Systems](), [Microcontroller](), [USB](), [Raspberry Pi]() Tags: [arm](), [atmel-samd](), [battery](), [boot](), [circuitpython](), [development-board](), [embedded-systems](), [gpio](), [hardware](), [i2c](), [led](), [mcu](), [micropython](), [raspberry-pi](), [rust](), [seeed-studio](), [software](), [usb](), [zephyr](), [zephyr-os]() ### AI overview Seeed Studio has expanded its XIAO Plus Series with the XIAO SAMD21 Plus and XIAO RP2040 Plus USB-C boards. The boards retain the existing form factor while adding GPIO pins and integrated Li-ion battery management, and support several embedded development platforms. ### Source excerpt Seeed Studio has expanded its XIAO Plus Series introduced in 2025, with the XIAO SAMD21 Plus and XIAO RP2040 Plus USB-C boards adding several GPIOs and integrated Li-ion battery management to the XIAO (SAMD21) and XIAO RP2040, launched in 2020 and 2021, respectively, while keeping the same form factor. XIAO SAMD21 Plus Specifications: MCU - Microchip SAMD21G18 Arm Cortex-M0+ microcontroller at up to 48MHz with 256KB Flash,32KB SRAM USB - 1x USB Type-C port for power and programming Expansion I/Os 2x 7-pin "legacy" headers with 11x analog inputs, 11x digital I/Os, 1x DAC, SPI, UART, and I2C Castellated holes and pads with 16x digital I/Os, I2C,and I2S 3.3V I/O voltage (not 5V tolerant) Misc Reset and Boot buttons RGB LED Charge LED Power Supply 5V via USB-C port Pads for battery On-board PMIC Dimensions - 23.5x17.5 mm Temperature Range - -40°C ~ 85°C The upgraded variant of the XIAO SAMD21 [...] The post XIAO SAMD21 Plus and RP2040 Plus USB-C boards get additional GPIO pins, integrated Li-ion battery management appeared first on CNX Software - Embedded Systems News. ## TinyGo 0.42 adds support for 87 Puya PY32 MCU variants and two EmbedFire boards DevFeed: [TinyGo 0.42 adds support for 87 Puya PY32 MCU variants and two EmbedFire boards]() Original publisher: [Read original article]() Author: Jean-Luc Aufranc (CNXSoft) Published: 2026-09-04T04:33:53Z Content type: news Language: en Sources: [CNX Software - Embedded Systems News]() Topics: [Go Language](), [Embedded Systems](), [Microcontroller](), [Compiler](), [Arm](), [Internet of things](), [LLVM]() Tags: [arm](), [article](), [code](), [compiler](), [development](), [development-board](), [devices](), [embedded-systems](), [firmware](), [go](), [gpio](), [guest-post](), [hardware](), [iot](), [llvm](), [mcu](), [microcontrollers](), [news](), [programming](), [puya](), [software-management](), [tooling]() ### AI overview TinyGo 0.42 adds support for the Puya PY32 family of 32-bit Arm microcontrollers, covering 87 MCU configurations and two EmbedFire development boards. The port includes startup code, linker scripts, GPIO, UART, and generated device-register definitions. ### Source excerpt CNXSoft: This is a guest post by Pavel Burgr, who recently added Puya PY32 MCU support to TinyGo 0.42, the latest version of the Go compiler for microcontrollers. We first covered TinyGo in 2019, and the project is still going strong with 17.7k stars, 1.1k forks, and 243 contributors. I just made a few edits and added illustrations and a few links to the article. TinyGo 0.42 adds support for the Puya PY32 family of 32-bit Arm microcontrollers. The new port includes startup code, generated device-register definitions, linker scripts, GPIO and UART support, and targets for 87 individual MCU configurations. It also includes board definitions for two inexpensive EmbedFire development boards available from AliExpress. The port was contributed by Pavel Burgr and merged through TinyGo pull request #5106. One motivation was to establish a solid, easy-to-use firmware platform for small IoT devices built around the Registry service and the BleRiot [...] The post TinyGo 0.42 adds support for 87 Puya PY32 MCU variants and two EmbedFire boards appeared first on CNX Software - Embedded Systems News. ## esp32pin.com: Interactive ESP32 Pinout Reference DevFeed: [esp32pin.com: Interactive ESP32 Pinout Reference]() Original publisher: [Read original article]() Author: John Lee Published: 2026-08-06T00:00:00Z Content type: article Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [kicad](), [Espressif]() Tags: [blog](), [community-contribution](), [development-board](), [esp32](), [gpio](), [kicad](), [open-source](), [pinout]() ### AI overview esp32pin.com is a free, open-source interactive pinout reference for the ESP32 family. It identifies pin constraints such as strapping-pin behavior, ADC2 conflicts with Wi-Fi, flash-pin restrictions, input-only pins, and USB or JTAG warnings. ### Source excerpt esp32pin.com is a free interactive pinout reference for the ESP32 family. Every pin carries its real-world constraints, the data is generated from Espressif's official KiCad libraries and cross-validated against the esp-gpio-tool dataset, and new dev boards can be proposed right in the browser. ## Introducing ESP-IDF button component DevFeed: [Introducing ESP-IDF button component]() Original publisher: [Read original article]() Author: John Lee Published: 2026-02-18T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Embedded Systems](), [ESP32](), [Embedded Software Dev](), [Code]() Tags: [adc](), [blog](), [callback](), [community-software](), [embedded](), [embedded-systems](), [esp-idf](), [esp-idf-component](), [esp32](), [examples](), [gpio](), [home-automation](), [how-to](), [iot](), [practitioner](), [tutorial](), [wi-fi]() ### AI overview This tutorial introduces the ESP-IDF button component and shows how to handle physical buttons in ESP32 projects. It covers GPIO buttons, ADC button matrices, event detection, software debouncing, callbacks, thread safety, low-power support, and a basic GPIO example. ### Source excerpt Learn how to use the ESP-IDF button component to handle GPIO buttons with event detection, debouncing, and callbacks. A step-by-step guide with practical code examples. ## ESP-IDF tutorial series: GPIO get started - Part 2 DevFeed: [ESP-IDF tutorial series: GPIO get started - Part 2]() Original publisher: [Read original article]() Author: John Lee Published: 2026-02-13T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Tutorial](), [ESP32](), [Embedded Software Dev](), [event driven]() Tags: [beginner](), [blog](), [esp-idf](), [esp32](), [event-driven](), [firmware](), [gpio](), [how-to](), [interrupt](), [microcontrollers](), [tutorial]() ### AI overview This tutorial explains how to configure GPIO pins as inputs in ESP-IDF, including the use of pull-up and pull-down resistors to define idle voltage. It demonstrates polling and event-driven interrupt approaches for reading GPIO values, using a button on an ESP32-C61-DevKitC as an example. ### Source excerpt In this article, we explore how to configure GPIO pins as inputs in ESP-IDF and discuss the importance of pull-up/pull-down resistors. We will try two approaches for reading GPIO values: polling and event-driven interrupts, showing how to implement each method effectively. ## ESP-IDF tutorial series: GPIO get started - Part 1 DevFeed: [ESP-IDF tutorial series: GPIO get started - Part 1]() Original publisher: [Read original article]() Author: John Lee Published: 2026-02-02T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP-IDF](), [Tutorial](), [Embedded Systems](), [ESP32](), [Library]() Tags: [beginner](), [blog](), [can](), [embedded-systems](), [esp-idf](), [esp32](), [gpio](), [led](), [spi](), [tutorial]() ### AI overview This tutorial introduces GPIO configuration on Espressif SoCs. It explains push-pull and open-drain output modes, drive capability, and the use of GPIO functions to blink an LED on an ESP32-C61-DevKitC. ### Source excerpt This article explains how to configure and control GPIO pins on Espressif SoCs, covering push-pull and open-drain output modes, drive capability, and library usage. It then provides a hands-on example of blinking an LED using gpio_set_direction and gpio_set_level on a ESP32-C61-DevKitC. ## Implementing a Deep-sleep wake stub application on Espressif chips to enable power-efficient IoT devices DevFeed: [Implementing a Deep-sleep wake stub application on Espressif chips to enable power-efficient IoT devices]() Original publisher: [Read original article]() Author: John Lee Published: 2025-09-02T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Internet of things](), [Espressif](), [Boot Process](), [cpu](), [SOC]() Tags: [battery](), [blog](), [boot-process](), [deep-sleep-wake-stub](), [esp-idf](), [esp32-c6](), [espressif](), [gpio](), [how-to](), [i2c](), [iot](), [low-power](), [spi]() ### AI overview This tutorial explains how Deep-sleep wake stubs work on Espressif chips and demonstrates how to build an application using GPIO, UART, I2C, and SPI. Wake stubs can skip most of the boot sequence after deep-sleep reset, enabling faster wake-up and lower power use for short tasks. ### Source excerpt In this article, we first explain the principles behind the Deep-sleep wake stub application and then demonstrate how to implement GPIO, UART, I2C, and SPI within it. ## Using ESP-BSP with DevKits DevFeed: [Using ESP-BSP with DevKits]() Original publisher: [Read original article]() Author: John Lee Published: 2024-09-27T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [Espressif](), [Development](), [m5stack](), [Filesystems]() Tags: [blog](), [bsp](), [development](), [devkit](), [display](), [driver](), [embedded-systems](), [esp32](), [esp32-c2](), [esp32-s2](), [esp32-s3](), [espressif](), [examples](), [gpio](), [how-to](), [i2c](), [lcd](), [led](), [m5stack](), [spi](), [spiffs]() ### AI overview This tutorial explains how to use Espressif's ESP-BSP with DevKits. It describes the Generic and DevKit BSP options, configurable buttons, LEDs, filesystems, displays, touch interfaces, and example projects. ### Source excerpt Introduction# The BSP (Board Support Package) from Espressif is ready to use package for selected boards (usually for Espressif's and M5Stack boards). This package contains main initialization functions for features, which the board contains. For example display and touch initialization, file system initialization, audio if available, LEDs and buttons. This is the easy way, how to start developing with your board. Except initialization functions, there are examples for selected board too. ## Debugging Targets of idf.py DevFeed: [Debugging Targets of idf.py]() Original publisher: [Read original article]() Author: John Lee Published: 2020-06-24T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [debugging](), [ESP-IDF](), [Command-line interface](), [ESP32](), [Tooling]() Tags: [blog](), [command-line](), [debugger](), [debugging](), [embedded](), [esp-idf](), [esp32](), [gdb](), [gpio](), [ide](), [idf-py](), [iot](), [jtag](), [monitor](), [programming]() ### AI overview This article explains how to use the debugging targets added to idf.py in ESP-IDF v4.2. It covers command-line workflows for OpenOCD, GDB, GDB TUI, IDF Monitor, and the gdbgui debug server, including JTAG requirements and configuration overrides. ### Source excerpt This article outlines a quick and easy way to start a debugger from the command line. More specifically, it discusses the debugging targets of idf.py, which have been added to ESP-IDF from v4.2. At the time of writing, IDF v4.2 is not released yet, but you can try out this feature on the master branch. Why Do We (Not) Debug# Debugging is an essential development technique, no less so for embedded platform engineers. ## GPIO port for Raspberry Pi DevFeed: [GPIO port for Raspberry Pi]() Original publisher: [Read original article]() Author: Nenad Rakocevic (noreply@blogger.com) Published: 2019-07-18T16:08:00Z Content type: release Language: en Sources: [Red]() Topics: [Raspberry Pi](), [Hardware](), [API](), [Code](), [Software](), [GTK]() Tags: [3](), [api](), [code](), [dsl](), [gpio](), [hardware](), [led](), [port](), [pwm](), [raspberry-pi](), [raspberrypi]() ### AI overview The article announces a GPIO driver for Raspberry Pi boards implemented as Red's gpio:// scheme. It describes board detection, GPIO state access, hardware PWM, and a command DSL, and demonstrates the functionality with a joypad project running on a Raspberry Pi 3. ### Source excerpt As part of the R&D work on port! datatype in port-type branch, we have implemented a GPIO driver for Raspberry Pi boards, as a gpio:// scheme (no third-party library needed). This work helped define the low-level API for ports written in purely Red/System or a mix of Red and Red/System. The Raspberry Pi is a very popular board with millions of units sold, so this is a market where Red could be potentially helpful to developers. We could run Red on such boards for years but did not have proper GPIO support, so this is now fixed! The current features supported by the GPIO port are: auto-detecting the Raspberry Pi board type uses /dev/mem or/dev/gpiomem for direct and fast access. reading a GPIO pin state. writing to a GPIO pin state. hardware PWM output support (on capable pins). a simple DSL for sending commands. Planned (but not scheduled) future features include: generating events when a pin state changes. software PWM on all GPIO pins. a higher-level reactive object layer for a API-less interface. various drivers for common peripherals. The source code for the gpio:// scheme can be found there. In the short video below, you can find a little pet project meant for testing some of the features. It implements a simple joypad with 4 directions support, a red LED indicating when the pad is active and a green one for notifying when a level is completed. The game is the Red port contributed by Huang Yongzhao of Rebox!, my old clone of BoxWorld written in Rebol. In the video below, it is running on a Raspberry Pi 3 using our work-in-progress red/GTK backend for Red (contributed by Rcqls), locally merged with the red/port-type development branch (EDIT: that branch has been merged into master now). You can find the breadboard layout below made using Fritzing. Sorry for the messy wiring, it is my first try with such kind of tool. If you have the skills to improve it, here is the sketch file. The buttons rely on the internal pull-down resistors. Note that in the video, the bo ## ESP-Jumpstart: A Customizable ESP32 and ESP8266 Firmware Template for IoT Product Development DevFeed: [ESP-Jumpstart: A Customizable ESP32 and ESP8266 Firmware Template for IoT Product Development]() Original publisher: [Read original article]() Author: John Lee Published: 2019-05-12T00:00:00Z Content type: tutorial Language: en Sources: [Blog on Developer Portal]() Topics: [ESP32](), [Template](), [ESP8266](), [Embedded Software Dev](), [Tutorial](), [Development](), [GitHub](), [Android](), [iOS](), [Amazon Web Services](), [Cloud](), [Internet of things]() Tags: [android](), [applications](), [aws](), [blog](), [cloud](), [esp](), [esp32](), [esp8266](), [firmware](), [github](), [gpio](), [iot](), [jumpstart](), [ota](), [product-development](), [tutorial](), [wi-fi]() ### AI overview ESP-Jumpstart is a customizable firmware template for ESP32 and ESP8266 product development. It provides incremental tutorial steps for building a deployable smart power outlet, with phone applications for Wi-Fi configuration, cloud synchronization through AWS IoT, remote control, OTA firmware upgrades, and factory reset functionality. ### Source excerpt ESP-Jumpstart (GitHub repository) is a production-ready, easy-to-customise firmware template that you can use to jumpstart your product development with ESP32 / ESP8266. ESP-Jumpstart builds a fully functional, ready to deploy "Smart Power Outlet" in a sequence of incremental tutorial steps. ## Android Things: first look DevFeed: [Android Things: first look]() Original publisher: [Read original article]() Author: Marc Plano-Lesay Published: 2017-01-06T09:55:08Z Content type: tutorial Language: en Sources: [Marc Plano-Lesay]() Topics: [Android](), [Internet of things](), [Hardware](), [Raspberry Pi](), [intel](), [SDKs](), [API](), [Android Studio]() Tags: [adb](), [android](), [android-studio](), [framework](), [gpio](), [hardware](), [i2c](), [intel](), [iot](), [optional](), [preview](), [pwm](), [raspberry-pi](), [sdk](), [spi](), [ui]() ### AI overview This article introduces Android Things, an Android version for developing embedded IoT devices. It describes supported boards, the Peripheral I/O and User Driver APIs, limitations of the bundled Android system, optional displays, installation on physical hardware, and initial project setup with Android Studio and adb. ### Source excerpt What is Android Things? Android Things is an alternative Android version, announced at Google I/O 2015, and released as a first developer preview in December 2016. Its purpose is to develop embedded IoT devices, with a known and widely documented Android ecosystem basis. It's currently running on three different boards: the Intel Edison, the NXP Pico i.MX6UL, and the Raspberry Pi 3. Some higher-end boards are coming soon. On the SDK side, Android Things comes with a specific support library to ease low-level hardware usage. It consists in two parts: the Peripheral I/O API, which supports GPIO, PWM, I2C, SPI and UART, and the User Driver API, which allows a developer to write a hardware-specific, high-level driver, to ease hardware reusability by injecting events into the Android framework. Other applications can in turn use those events without having to interact with the hardware directly. There's a downside: the bundled Android is not as complete as the one you can find on a phone. Most of the standard applications aren't installed (Calendar, Phone...), and standard content providers are absent too (MediaProvider, Dictionary...). Android Things supports displays, with the default Android UI toolkit. However, the display is a bit different from what you're used to seeing on an Android device: there's no notification bar, navigation bar or anything, the running application will use the full display. That is, if it uses it at all: displays are purely optional.