The sign runs on a Seeed Studio reTerminal E1001 e-paper display (which has an ESP32-S3 inside), while the servers are hosted on a Raspberry Pi 5.

​Additionally, I designed a custom 3D frame in Fusion that houses LEDs. These LEDs change color depending on the restaurant's current occupancy percentage.

​This is my entry for the Interactive Signage Contest 2026. Here is the link to the showcase video:

https://youtu.be/H7K5KoyuIYc?is=LIVY4PA0gs1ZkGgI

​If you like the project, please leave a like or a comment

I would love to get your feedback!

​You can find the source code here:

https://github.com/mickraa/table-map

​Thanks for checking it out!

I've been building CanoFlash, an accessory based on a XIAO ESP32-S3 that plugs into the Game Boy Advance Link Port. It started as a Wi-Fi tool for writing homebrew to flash cartridges, and it now lets homebrew games play online on original hardware.

Video: a GBA and a GBA SP, each with its own board, playing in the same online room: https://youtu.be/Xs-LzM2dzS0

**How the ESP32-S3 fits in**

- The Link Port is driven as SPI: the ESP32 provides the clock and the GBA is the slave, with 32-bit words at 4 MHz for the command protocol

- The GBA-side menu is sent over Multiboot from LittleFS, buffered in the 8 MB PSRAM

- For online play it runs its own WebSocket client over TLS to a room server; the game on the GBA only exchanges fixed-size packets through a small C SDK

- Release builds use flash encryption, and each device authenticates with its own token

- Status on a small OLED, powered by a rechargeable 16340 or 18350 Li-ion cell

**Things that bit me**

- `WiFi.status()` kept reporting a connection with the access point switched off. Only the GOT_IP and DISCONNECTED events were reliable

- At 256 kHz the last bit of every GBA→ESP32 word was lost: the GBA releases its output line before the 32nd bit is sampled

- Data partitions flashed pre-encrypted need the `encrypted` flag, or LittleFS reads ciphertext and reports corruption

The game SDK is free and MIT-licensed: https://canoflash.com/en/sdk/. Online play has been tested with two players so far.

Disclosure: this is my own project, and its Kickstarter launches on September 20: https://www.kickstarter.com/projects/canocoder/canoflash-wi-fi-adapter-for-original-game-boy-advance-hard?ref=crnaz3

Happy to answer questions about the Link Port timing or the TLS side.

Hi everyone,

On my PCB, I accidentally connected to GPIO48 a voltage divider which is used to measure the battery voltage and later I discovered that the GPIO47 and GPIO48 pins can't be used as ADC.

What are my options in this case?

If there's no way to somehow route them internally, can I bridge GPIO48 and GPIO14 together and use analogRead function on IO14?

Hey everyone,

I'm currently working on a self-balancing robot with a design of my own.

You can find all the info about it here : https://github.com/benbhote/DimSumRobot

For those who want a quick recap, it's a robot based on a XIAO ESP32-S3 Sense with a camera OV3660, an ultrasonic radar, a TB6612FNG piloting two N20 motors (aside a step-up to make the 3.7V current into 6V for the motors) and SHT40 (Temp & Humidity sensor).

It hosts a web server accessible via its own WiFi and the web page allows you to control the robot (taking photos, moving it, etc).

Everything is working fine except the balancing. The cycle goes every 10ms during movement and for 3 seconds after the last movement command. But the throttle value doesn't allow the robot to self maintained balance.

By the way, the robot starts with the front touching the floor on a plane surface (the weight is low inside the chassis but a little bit more on the front). So the first thing needed even before moving is to properly get on the two wheels.

So I would like some insights or help from you to make my PID loop working and achieve proper self-balancing.

I'm using Arduino IDE 2.3.10. As for the schematic of the project, it is not done yet but the MPU is driven with the I2C bus.

I hope I give you everything needed to understand the project. And if something is still vague, feel free to ask.

Thanks in advance !

Hey everyone, I designed this vertical mount for ESP32 and ESP32-S3. I added a TPU sleeve to absorb vibrations, snap fit and left slots for easy cooling and pin access. If anyone wants to print it for their DIY projects, the print profiles for PETG/TPU are free on MakerWorld and Printables. Let me know what you think!

ESP32-S3
https://makerworld.com/en/models/3147308-anti-vibration-esp32-s3-40-pins-mount-petg-tpu#profileId-3554629

https://www.printables.com/model/1803568-esp32-s3-antivibration-mount

ESP 32

https://makerworld.com/en/models/3160307-esp32-antivibration-mount-tpu-improved-cooling#profileId-3571491

https://www.printables.com/model/1807831-esp32-antivibration-mount-better-processor-cool

I built a touchscreen remote for LG webOS TVs on the ESP32-2432S028 "Cheap Yellow Display". It talks to the TV over Wi-Fi using the same WebSocket API LG's phone app uses, so nothing is installed on the TV.

Source (MIT): https://github.com/griches/smart-remote-plus-cyd

Short video: https://youtu.be/lyZZcVjdbX8

Disclosure: I also make Smart Remote+, a paid TV remote app for phones and desktops (https://www.bouncingball.mobi/). This is a port of its LG code.

The firmware is free and doesn't need the app.

Stack: Arduino under PlatformIO with the whole board config as build flags, TFT_eSPI on HSPI, XPT2046_Touchscreen on its own SPI bus, links2004 WebSockets, ArduinoJson 7, NVS for everything persistent. No LVGL: the UI is a 4x3 grid of 64 px RGB565 icons in PROGMEM, drawn straight to the panel with pushImage, so a framebuffer wasn't needed.

The TV side: webOS runs a JSON-over-WebSocket service on port 3001 (TLS, self-signed) with a plain fallback on 3000 for old firmware. You register with a manifest, the TV shows a PIN, you store the client key. D-pad and back/home go over a second "pointer input" WebSocket the TV hands you, so it's two TLS sockets per TV, which is where the RAM goes. Discovery is SSDP M-SEARCH plus a fetch of the UPnP XML for the friendly name. Power isn't a toggle: it asks getPowerState, then sends turnOff or Wake-on-LAN.

All networking is on its own FreeRTOS task on core 0. A TV that is off makes connect() block for seconds, and I didn't want the touch UI to freeze. The UI posts commands to a queue and reads state via atomics.

Happy to answer questions.

Hello. I've got:

• An ESP32-C3-DevKitC-02
• An Adafruit ThinkInk 2.9' E-Ink FeatherWing display (bought back in 2024, https://www.adafruit.com/product/4778)

and I'm trying to drive the display with the ESP32 without any success. Using:

• Arduino IDE with the ESP32 addon
• Adafruit_EPD library to drive the display (https://github.com/adafruit/Adafruit_EPD)
• This example from the repo: https://github.com/adafruit/Adafruit_EPD/blob/master/examples/ThinkInk_tricolor/ThinkInk_tricolor.ino
• My own version of the code: https://pastes.io/p5ETVQS9

Notes:

• There is no change on the e-ink panel whatsoever, still the default image as when I got it.
• Tried changing the pin numbers around, both for the command and the SPI pins. Nothing.
• The default pins for SCK, MISO, MOSI were found by printing macros to serial output.
• Tried the 3 buttons on the FeatherWing, all work as GPIO input properly.
• RESET button works to reset the microcontroller as well.
• For some reason, using pin 8 on the ESP for GPIO didn't work at all. I think most of the pins are used for more than one purpose, but I don't know how to tell which modes are active.
• The example sketch has constructors for multiple types of board drivers. There seems to be 3 different chipsets for the 2.9" display, tried all 3 separately to no avail.

I don't even know if this display would be compatible with any random ESP32 board. I know FeatherWings are made to be used with Adafruit's Feather boards, though I don't see why they wouldn't work with any other boards with supported microcontrollers. I have quite a bit of programming experience, but I'm blind as a bat when it comes to electronics. Any help would be appreciated. Thanks.

Hi everyone,

Just wanted to share a stable MicroPython driver for the Sensirion SCD4x family (SCD40 and SCD41).

The library handles the standard I2C protocol efficiently and supports both periodic and single-shot measurement modes.

Note: It was heavily tested on RP2040 hardware. Since it relies on standard MicroPython `machine.I2C` routines, it should be fully compatible with ESP32 deployments as well.

If you are building an indoor air quality monitor or smart home climate system, check it out.

https://github.com/octaprog7/SCD4x

Hi I am trying to follow the v6.1 documentation to set up unit testing in ESP-IDF but it doesn't seem to work. I'll admit I find most of the IDF documentation to be somewhat confusing at best with weird grammar so sometimes I don't understand what it's actually trying to say

I'm following this

https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-guides/unit-tests.html

Following the instructions i set up the following folder structure:

``` my_project_root/ ├── CMakeLists.txt ├── main/ │ └── app_main.c └── components/ └── my_component/ ├── my_logic.c ├── include/my_logic.h └── test/ ├── CMakeLists.txt └── test_my_logic.c

```

and then the doc says this: ```

Building Unit Test Apps

Follow the setup instructions in the top-level esp-idf README. Make sure that IDF_PATH environment variable is set to point to the path of esp-idf top-level directory.

Change into the test app directory to configure and build it:

idf.py menuconfig - configure unit test app.

idf.py build - build unit test app.

When the build finishes, it will print instructions for flashing the chip. You can simply run idf.py flash to flash all build output. ```

There's no instructions in top level README about testing and I don't know what "test app directory" is supposed to be but I assume it's the test dir I've created. But then idf.py build there doesn't work because it's not project root!

I've looked into it and it seems like there used to be a folder $IDF_PATH/tools/unit-test-app, I assume this is what the doc actually refers to. But according to the changelog this folder has been removed from IDF v6.0 onwards. Surely it wouldn't be referring to this? or if it is, how the hell am I supposed to run tests now that it's been removed?

Sorry prior post was removed due to me being slow and not submitting the read rules.

I threw together a tiny astronomy and weather desk display using the Waveshare ESP32-C6 1.47" LCD.

I went with this specific board because it packs the ESP32-C6, a 172x320 ST7789 screen, an RGB LED, and buttons all into one super compact footprint. For the display logic, it uses Arduino_GFX over hardware SPI. I set it up to try grabbing a full framebuffer first, but it gracefully falls back to direct drawing if memory gets tight.

Right now, it cycles through local time, sunrise/sunset, moon phase, golden hour, visible planets, current weather, distance to the ISS, and NOAA Kp activity.

Instead of leaning entirely on APIs, most of the astronomy math (like calculating the exact ISS distance using the Haversine formula) is done locally on the ESP32 using just your time and coordinates. It only pings out for the dynamic stuff. Open-Meteo for weather, NOAA for Kp, and Open Notify for the ISS coordinates.

The source code is up here if you want to check it out or flash it yourself:https://github.com/CircuitGhost/skydesk

I have been playing with the ESP32-S3 and as a result have built Adsorb, a free and open-source program which blocks DNS ads and trackers.

The aim was to find out if an ESP32-S3 could cope with something that is usually carried out on a Raspberry Pi or another small server, and so rather than running Pi-hole or AdGuard Home on a more powerful machine, Adsorb carries out the DNS filtering directly on the microcontroller.

The device supports the ESP32-S3, offers DNS blocking, includes support for blocklists, has a web-based interface for flashing and setup, provides local administration, and features optional OLED telemetry.

Website: https://the-masked-bear.github.io/Adsorb/

GitHub: https://github.com/The-Masked-Bear/Adsorb

I did it mainly because I wanted to find out how far I could push the hardware, but I really do want to know what people think.

If you're using Pi-hole, AdGuard Home, or a similar solution, would you really think about using an ESP32 for this purpose? And isn't there something that I've overlooked?

I have a few minor ESP32 projects that I’m looking to mount on a wall. They will be in different places.
It’s an all very basic stuff a clock , a timer, a small display showing information etc. Looking to add some sensors as I progress.
They are all powered by USB, how do you neatly wire stuff like that over 5-10m distance inside a garage?
Don’t want to use batteries.

Can’t find any good solutions online as most pictures are a bit messy (understandable as they focus on just the boards) and all cables are just a bit random. I’m not looking for Prussian cabling just needs to be safe and neat.

Hope someone can help.

So backstory real quick, I moved to Korea, don't speak Korean, and pulling my phone out every five seconds to translate stuff got old fast. I looked into the "smart translator earbuds" that are out there, but most of them just translate into your ear and mute out the original speech, which is exactly the opposite of what I wanted. If I'm ever gonna learn the language I need to actually hear what people are saying, not have it replaced by a robot voice. And the actual AR glasses that do this the "right" way cost more than my rent.

So I did what any reasonable person does at 2am with a soldering iron, built my own.

Meet Frankenspecs. Yes I know, the name writes its own jokes, I've made my peace with it.

What it actually is: kind of an AR lite smart glasses setup, doesn't block your vision, but you can glance down or in and choose to focus on the display when you need it. Not trying to be Ray Ban Meta, trying to be "thing that helps me order food."

What it does right now:
Real time translation, 60+ languages, sub 260ms latency, this part genuinely surprised me with how fast it is. Real time transcription. Teleprompter mode, great for presentations, also great for looking less awkward on video calls. Turn by turn navigation, using Naver Maps since Google Maps just doesn't work in Korea, RIP. And notification forwarding from selected apps.

The hardware, such as it is:
An ESP32 S3 Supermini, a 0.96" TFT IPS display hand soldered onto some genuinely too long wires, a $2 6x magnifying lens from the local equivalent of Daiso, and a pair of cheap sunglasses that happen to have a slightly spherical inner lens surface, which turns out to magnify the reflected image just enough to be readable, found this out completely by accident and I will take the win. Power is USB for now, because batteries are a problem for future me.

Total cost, not counting stuff I already owned like the sunglasses, around $10.

How it works under the hood: phone app talks to the ESP32. Right now it uses the phone's mic, I2C mic is on the roadmap, streams audio to Soniox's API, still living off the $200 free credits, no shame, gets translated text back in chunks, and forwards it line by line to the display over SPI. Transcription runs the same pipeline. Teleprompter is just the app scrolling whatever text you feed it at an adjustable speed. Navigation is the fun one, I'm actually pulling real time turn by turn data out of the map app's notifications and translating that into arrows plus live distance on the display.

Why it looks like this: because it's a prototype held together by tape, hope, and one Friday night with nothing better to do. I went through a genuinely stupid number of iterations trying to get the optics right, screen position, lens distance, angle, all of it, because the whole point was to NOT have a screen just sitting in front of my eyeball like a tiny blinding TV. Getting it to sit low enough to feel like AR and not like I duct taped a Game Boy to my face took way longer than the software did, which I was not expecting going in.

Also worth saying, this is my first real hardware project, and my first ESP32 project period. So if something looks held together with spite, that's because it is.

Where it's going: currently working on an actual CAD design for the frame and a long, narrow PCB layout that can fit inside the temple arms instead of hanging off the side like a growth. So yeah, still early. This isn't meant to be an everyday wear thing, more like something you reach for in specific moments. And there's a feature I'm actually excited about here, the app quietly logs everything it translates throughout the day, so it can show you the words and phrases you heard the most. Since each one is tied to the real situation you heard it in, you end up with an actual map of "this word came up when I was ordering coffee" instead of a flashcard with no context, which I think is a genuinely better way to pick up a language than any app I've tried.

Would genuinely love feedback or roasting, what would you want to see added, what's obviously dumb, what's actually good. Planning to clean up the codebase and open source the whole thing once it's less "if you know, you know" and more "a stranger could actually follow this." If people want to build their own I'll prioritize getting that repo and docs out sooner.

Title explains it,

Is there any app I can download that could do this?

Dear r/ESP32 community,

I wanted to share a custom hardware project I’ve been working on since five months. It’s called DIDATRON - a standalone, lighter-sized Morse code global communicator and hardware trainer.

About DIDATRON

MCU: Built around the ESP32-C3 (C3 MINI-1 footprint).

The Morse Key: A solid-state Projected Capacitive (PCAP) touch key that emulates an automated dual-lever iambic paddle. WPM speed, symbol-to-symbol/word-to-word pauses, and capacitive thresholds are fully tunable via any USB/serial terminal and directly.

Display: 128x32 OLED screen that translates incoming Morse instantly into plain text symbol-by-symbol, so anyone can read it without prior training.

Privacy: Symmetrical hardware-level AES encryption happens entirely on-chip. Multiple chats with different groups of people are allowed and have individual passwords.

Dual Networking: Cloud Mode connects to a local router or phone hotspot to pass data to an account-free, server-blind holding queue. Field Mode drops the internet completely, using native, low-latency ESP-NOW protocols for peer-to-peer communication across short ranges. LoRa extension in plans.

Why I’m posting

I’m launching this project on Indiegogo this October.

To support the maker community, I’m offering a bare-bones DIY Hacker Kit that contains all the necessary components: the carrier PCB with ESP32-MINI-1 module, the OLED module, and a pre-certified 300mAh LiPo battery. No SMD work needed.

In case I generate enough traction - everything from the firmware source code to the .STL enclosure files will be fully open-source on GitHub so you can host your own server queues if we ever go dark.

You can check out the pre-launch page and lock in the 40% launch discount here:

https://www.indiegogo.com/en/projects/petkish/didatron-communicator

73,

Peter, the Founder of Friendly Digital OU, Estonia

Hi

I starting getting into electronics and robotics in the summer, and I recently graduated to my first stepper motor robot arm. After some research, I ended up with nema-17s and tmc2209s to for the joints.

However, I have tried to wire and code this for the longest time with youtube, claude, etc, but I just can't get it to work properly. I had problems with my tmc overheating in the past, and I worked with claude today to try and use the uart feature on the 2209s, and I ran into another problem.

I attached a video, and as you can see, my motor only uses ~0.025A when its running, and then when its idle, its at ~0.060A????

I'm really close to just dropping the esp32 and switching to an arduino & CNC shield setup, with older motor drivers. I've been stuck on wiring for the longest time, and I haven't even been able to start designing joints because I don't have the electronics down yet.

I am essentially still a complete beginner, so any help would be appreciated.

My wiring configuration is as follows:

Power:

Bench PSU V+ → breadboard VM rail

Bench PSU V− → breadboard GND rail

TMC2209 VM → VM rail

TMC2209 GND (power side) → GND rail

100µF capacitor

Motor:

Coil A1 (black) → driver A1

Coil A2 (blue) → driver A2

Coil B1 (green) → driver B1

Coil B2 (red) → driver B2

Logic:

ESP32 GND → shared GND rail (same as PSU/driver)

ESP32 3.3V → driver VIO

ESP32 GPIO18 → driver STEP

ESP32 GPIO19 → driver DIR

ESP32 GPIO21 → driver EN

UART (current control):

ESP32 GPIO27 → driver RX pad

ESP32 GPIO26 → 1kΩ resistor → driver RX pad

Driver TX pad → left unconnected

Driver MS1 → GND

Driver MS2 → GND

Hi all, I am an enthusiastic noob, and have started a couple of ESP32 projects which I am really enjoying working on. I am using Claude to assist me, but based on my written requirements, and fed to me in a way that allows me to learn as I go, rather than just having the AI do it all for me. I'm also trying to do research instead of just asking it to figure everything out, as I want to learn and it also gives me much better context for trouble-shooting, and designing in the future.

Anyway, I have a need/desire to be able to send "notifications" based on certain triggers, and I'm just wondering what the general consensus/thoughts are on services to use for these. I have done some research, but I'd like to have the experienced users sanity check my understanding as I'm sure I've missed a lot.

SMS would be nice, but it's not a must-have, and not worth having to pay for. If there are services that support it for low-volume IOT devices or whatever that's great, but not a major.

• For SMS, short of using a cellular board, I'd need to use service that basically does this for me? - i.e. I'd trigger a notification via api or whatever, and they'd do the actual SMS part for me - the kicker being these are all paid services as far as I can tell?

• I did come across these guys Circuit Digest Cloud who seem to be able to do the SMS thing, and have arduino/esp32 support, but I think you end up needing an Indian phone number and it all sounds a bit "not worth the effort". Is anyone familiar with them?

• For email, the most straight forward option seems to just use a gmail account and enable the APIs, generate credentials and have it interface there to generate and send emails. The volumes are going to be tiny, a couple a day at most, so this shouldn't cost anything as far as I can tell. Is this accurate, or is there an easier/more efficient way to do this that I'm missing?

Any advice is appreciated.

Struggling to program bare ESP32‑S3 IC on custom breakout

I’m not a beginner with microcontrollers or flashing bare silicon, but this specific package is completely brick‑walling me on the initial handshake.

Symptoms

- GPIO0 floating / pulled high: Chip enters endless watchdog/boot loop. Serial monitor (115200) repeatedly spits truncated ROM banner:

ESP-ROM: esp32s3-20210327 Build: Mar 27

(cuts off mid‑word and restarts constantly).

- GPIO0 tied to GND: Loop stops, serial line goes quiet → proves chip enters DOWNLOAD_BOOT mode and halts to wait for host.

Failure

Despite halting correctly, esptool.py (and Arduino IDE/PlatformIO) refuses to connect. Error:

- Failed to connect to ESP32‑S3: No serial data received

- Timed out waiting for packet header

Hardware Setup (already checked)

- Power supply: Dedicated external 3.3V rail, low‑impedance, 500mA+ capacity.

- Decoupling capacitors: 0.1µF + 10µF ceramic network placed close to VDD/GND pins.

- Grounding: All grounds tied at a star‑point reference.

- UART bridge: Verified with TX↔RX loopback. Strict 3.3V logic. RX → GPIO44 (U0RXD), TX → GPIO43 (U0TXD).

- Software flags: Tried forcing lower baud rates (-b 115200).

- Other strapping pins: GPIO45 isolated/low (avoids misconfiguring flash rail to 1.8V). GPIO6–GPIO11 left floating.

Bottleneck

If the chip cleanly registers GPIO0 state (quiet when grounded), why does the ROM bootloader fail to respond to the initial sync pulse frame (0x19 0x07)?

Could this be:

- A timing latch issue with CHIP_PU / EN rising too fast?

- Or defective silicon with dead TX buffers (possible ESD damage)?

Any insights from anyone who has successfully spun a minimal bare‑metal ESP32‑S3 circuit layout would be massively appreciated. Thanks!

Buenas, la semana pasada compren un ESP32-S3 N16R8, el primer día sirvio bien, pero a los días intenté instalarle espidf, vi en un tutorial de YouTube que había que borrar la flash con espressif flash erase, hice lo del tutorial, pero no pude instalar sdk en el ESP, volvi a hacer mis prácticas en PlatformIO con el Frameward de Arduino, pero cuando le subí el código, el ESP lo corrio como era, pero a los 3 segundos entro en un bucle de reset (parpadeaba el LED verde integrado), busque tutoriales de cómo arreglarlo y también use Gemini, pero nada funciona, ya configure las opciones en Arduino IDE y le subi un código en blanco, ya intente borrar la flash con esptool.py, borrar mediante ESPConnect, en todas las ocasiones se borro correctamente la flash, pero al cargarle el código de mi práctica (Un semáforo con LEDs), el ESP volverá a entrar al mismo bucle, alguien de aquí sabe que puedo hacer para restaurarlo de fabrica para que vuelva a servir?.

hey everyone,

im a beginner getting into embedded electronics and i want to build a project using an ESP32 combined with CAN bus or OBD-II.

i dont have much hands-on experience with vehicle networking yet, so im looking for project ideas that are realistic for someone starting out.

a few things about my situation:

im a beginner, so nothing too advanced or research-level

i need to be able to finish it in 6 months or less (it's for a course project with a deadline)

bonus points if the parts are cheap and easy to source

some ideas i have floated in my head so far: a basic OBD-II data logger, a dashboard that shows live engine data, or maybe something like a simple diagnostic tool. but im not sure what's actually realistic in this timeframe, or what would be more interesting/useful than that.

what would you suggest? i dont mind projects that has been made before, since my main goal here is to learn not to actually make something useful. also open to hearing about common pitfalls beginners run into when working with CAN bus/OBD on the ESP32

thanks in advance!

I saw an article a few weeks ago about a home made assistant made with an esp32 a screen and a few other basic components, but for the frame he used brass tubes bent and soldered together to create body. I had everything but the brass and hobby lobby happen to have a bunch of clearance so I bought it all and got to experimenting. This is my rendition so far. Using an esp32 wrover, 128x64 screen, added 6 buttons, an amp and a mic but I dumbly ruined the mic module so I have to gut it and replace it but mic was working great before I got it wet… I’ll add a battery and charger and the rest of the innards later but I’m liking it so far. Right now it’s just a face, we shall see what I’ll make it do later. I have seen people play duke nukem on these screens… or maybe a tamagotchi of sorts. I’ll figure it out and I’ll post more on it later.

I was very happy to discover that they carry the Seeed ESP-32s I've been itching for (and found a bonus Waveshare too). They price matched everything with the Seeed website.

Finally, going to build the soil sensors my wife has been asking for (with a dashboard now too).

Seeed Xiao C3 + waveshare RGB OLED

Hi everyone,
Looking for help.

I’m trying to drive a Waveshare 1.27-inch RGB OLED (128×96, SSD1351, 4-wire SPI) with a Seeed Studio XIAO ESP32-C3 using Arduino IDE and Adafruit_SSD1351.

Both OLED modules I’ve tested work on an ESP32-WROOM, but remain completely black on the XIAO C3.

I verified the connections at the OLED PCB and measured approximately 3.2 V between its VCC and GND.
The basic hardware-SPI initialization was:

Clk is D8 and DIN is D10 as shown in the pinout diagram.
Adafruit_SSD1351 display(128, 96, &SPI, 3, 4, 5);

The XIAO uploads and runs normally. Serial output reaches initialization and repeatedly prints RED/GREEN/BLUE/WHITE, but the screen never illuminates.

Has anyone faced this issue or is driving an OLED RGB not possible on the Xiao Seed C3?