🌈 ESP32-S3 Rainbow: ZX Spectrum Emulator Board! Get it on Crowd Supply →
View All Posts
read
Want to keep up to date with the latest posts and videos? Subscribe to the newsletter
HELP SUPPORT MY WORK: If you're feeling flush then please stop by Patreon Or you can make a one off donation via ko-fi

I was doing some experiments with a small infrared thermal sensor module — an MLX90640, 32×24 pixel IR camera that talks over I²C.

This was meant to be a quick test before moving on to a larger project.

It did not go to plan.

The Symptom: Nothing on I²C

When I first plugged the module in, it simply didn’t respond at all.

  • No data
  • No errors
  • No sign of life

An I2C scan showed nothing connected. You can easily run an I2C scan in the Arduino IDE - it’s one of the demos for the Wire library.

I2C Scanner Shows Nothing

The Usual I2C Suspects

I went through all the standard checks:

✅ I2C Address Scanning

I ran the I2C scanner to see if the device appeared at any address.

Normally, when nothing shows up, there are three things to check:

  • Pull up resistors - do you need them?
  • Wiring - have you got SDA and SCL swapped over?
  • Power issue - are you actually powering the device? Does it take 3V3 or 5V?

✅ Pull-Up Resistors

I²C needs pull-ups on SDA and SCL, so I checked:

  • Are pull-ups present on the board?
  • Does enabled the built in ESP32 GPIO pull ups make any difference?
  • Does adding external ones help?

Some modules include pull-ups, some don’t. Sometimes you can get away with the internal GPIO pull-ups. Sometimes you need stronger ones.

I tried everything!

✅ 5V vs 3.3V Logic

Originally, Arduinos used 5V logic. A lot of “Arduino Compatible” modules include a 3V3 regulator so they can be powered from 5V.

This can cause some issues if you try and power the modules off 3V3 - the LDO that are used can have a surprisingly high drop out voltage (the classic AMS117 can drop 1.2V!). This can cause the boards not to function, or to behave quite eratically.

I tried both 3V3 and 5V - no joy!

✅ Wiring

The other classic is just incorrect wiring. It’s very easy to get SCL and SDA swapped over, or misread the pins you’ve connected to.

It’s also possible that you may get unlucky and pick some pins that are being used for something else - particularly on dev boards that have a lot of built in peripherals.

I tried everything, different pins, different cables, the works.

My first schoolboy/girl error…

Eventually I noticed something embarrassingly obvious.

This module has a small solder jumper that selects I2C mode.

I’d forgotten to add a blob of solder to it - my module was in UART mode! Problem solved I thought to myself!

…still nothing.

I2C Solder Jumper

The Actual Problem: Bad Soldering

At that point, I stopped assuming the board was electrically sound and put it under the microscope. To be honest, I’d come to the conclusion that my board was DOA and I’d have to ask for a refund.

But, the microscope does reveal all.

Some of the pins on the module’s 3V3 LDO did not look properly soldered.

They looked fine at a distance, but under magnification looked pretty dodgy.

3V3 Regulator

The Fix

I reflowed the joints and everything sprang into life. I2C address scanning found the module and a test program started reading temperatures from it!

Lessons Learned (Again)

This is one of those lessons you know, but still relearn regularly:

🔧 Don’t Trust Factory Soldering

Especially on:

  • Cheap breakout boards
  • Modules from unknown vendors
  • Very fine-pitch ICs

🔍 Look Early, Not Late

If something:

  • Doesn’t respond at all
  • Isn’t visible on I²C
  • Shows zero electrical activity

…get the microscope out sooner rather than later.

🧠 Software Isn’t Always the Problem

If you’ve:

  • Checked wiring
  • Checked voltages
  • Checked pull-ups
  • Checked addresses

It’s probably time to assume hardware.

Coming Up Next

Now that the module is actually working, I can get on with the real project that uses it.

Related Posts

It blew itself up! - I recently got my hands on a cheap mini handheld game console from AliExpress that gave up the ghost a bit sooner than expected! After some detective work with a multimeter, I found a dead battery and a suspicious burn mark on the PCB. Looks like the culprit was a failed capacitor, with some diodes to blame too. I managed to jump-start the board, though it lost its voice in the process. Replacement parts are on the way; stay tuned for the next round of electronic surgery!
Danger danger high voltage - In this blog post, I explore my experiments with high-voltage circuits, trying to light up LED filaments salvaged from broken light bulbs. Despite some explosive mishaps with capacitors and MOSFETs, I decided to try a proper DC-DC converter. Unfortunately, the one I got turned out to be faulty, highlighting some rough soldering and component failures. I've ordered replacements and hope to successfully light the filaments soon. Follow along on my troubleshooting journey with plenty of learning curves!
Why Won't My Board Reset? - One of my ESP32 dev boards refused to reset, even though the schematic, layout, and solder joints all checked out. Continuity was dead across the reset switch, reflow didn’t help, and under the scope it looked fine—until I realized the switch was packed with flux. A soak in IPA cleaned it out and the reset worked instantly. Moral of the story: sometimes the fix really is more alcohol.
Are my usb cables any good - Building a USB cable tester turned out to be trickier than anticipated! My first attempt with fully shielded USB sockets was foiled by design flaws and hidden solder issues. The second iteration featured more accessible sockets, yet still posed challenges. The improvement allowed us to distinguish between high-speed cables and average ones. I'm now in the midst of creating Version 3, with all connections broken out for easy testing. Stay tuned for what's next in this unexpectedly complex journey!
A Potentially Explosive Error - Just received the new PCBs for the ESP32-TV project and they're looking sharp with only a tiny resistor tweak needed. But I discovered a sneaky, undocumented resistor causing a conflict between the ESP32 and USB2244 over the USB connection. Fixed that, but there's a bigger issue lurking in the design - check the schematic in the video and see if you can spot it before I reveal the explosive mistake!

Related Videos

I Spent Hours Debugging My Software… - Quick bench update: I tried to get a 32×24 pixel IR module talking over I2C and it just would not play ball—pull-ups, library swaps, address scans, nothing. First silly mistake was not bridging the I2C jumper. Even after fixing that, still dead. Under the microscope I spotted the real issue: poorly soldered pins on the IC. A quick reflow and some IPA cleanup later, it sprang to life. Moral of the story: if yours won’t talk, check the underside soldering. Project video coming soon.
$3 AliExpress Heart Rate and Oxygen Sensor Module - You know how it is—you grab one cute little AliExpress module, then another… so I finally put an ESP32-C3 to work. Under the microscope it looks solid (nice 3.3V reg, ceramic antenna I’m not trusting for Wi‑Fi), and I paired it with a MAX30102 heart-rate/SpO2 sensor. Wired up I2C (SCL pin 6, SDA pin 5, INT to pin 2, 5V in), ran a scan, and boom—two devices found. After some finger-fiddling, the readings matched a commercial oximeter. Code’s on GitHub—cheap, fun, and it works.
Not what I was expecting! Why are all my lightbulbs failing? - So, we've been dealing with a little epidemic of light bulb failures in the house. I took apart a couple of dead bulbs to get to the bottom of what's going on. Turns out, one of the bulbs is kind of flickering and faintly working, while another bulb's base gets surprisingly warm. After some poking around, I found the PCB inside the bulb has a bridge rectifier and a LED driver IC, but all components test out fine! The investigation took a turn when I checked the LED filaments with a makeshift power supply, and surprise surprise, some filaments are completely dead. Still not sure what's causing these failures, but it was fun to tinker!
AliExpress Unbagging: ESP32 PCBs, I²C Sensors, COB LED Strips & More - Another massive AliExpress bagging, plus fresh PCBs from PCBWay! I’ve got an ESP32-C3 dev board, an S3 board with a BLDC controller, and matching stencils ready for when the LCSC parts land. Then it’s a pile of fun bits: a laser level, shrimp peeler and kitchen temp probe, a USB boost converter, USB‑to‑UART, I2C current sensor, wood‑penetrating touch sensor, ToF and ultrasonic rangefinders (perfect for a head‑to‑head), I/O expanders, DC motor controller, magnetic stickers, USB sockets, an IR‑controlled RGB plate (tested!), syringes for paste, a sketchy touch dimmer to tear down, a color sensor, and ultra‑thin COB LED strips (lit up nicely). Lots to solder, test, and probably break—in the best possible way.
Why This ESP32 Reset Button Didn’t Work - Had a slightly annoying issue: one ESP32 dev board’s reset button did nothing while the LED kept happily blinking. Schematic and PCB layout were fine, EN net buzzed out, but there was no continuity across the reset switch. Reflowing didn’t help; under the microscope the joints looked good. The culprit? The tactile switch was gunked up with flux. A soak in IPA brought it back to life—continuity restored, reset works, programming mode good. Moral of the story: sometimes it’s not the design—just clean it. Use more alcohol.
HELP SUPPORT MY WORK: If you're feeling flush then please stop by Patreon Or you can make a one off donation via ko-fi
Want to keep up to date with the latest posts and videos? Subscribe to the newsletter
Blog Logo

Chris Greening


Published

> Image

atomic14

A collection of slightly mad projects, instructive/educational videos, and generally interesting stuff. Building projects around the Arduino and ESP32 platforms - we'll be exploring AI, Computer Vision, Audio, 3D Printing - it may get a bit eclectic...

View All Posts