Repository navigation
HowTo Troubleshoot
This guide helps diagnose and resolve common problems with Glitchy.
| Symptom | Jump to Section |
|---|---|
| Device won't power on | Power Issues |
| Can't find WiFi network | WiFi Issues |
| Web interface won't load | Web Interface Issues |
| Glitches never succeed | Glitching Issues |
| No power trace visible | Power Analysis Issues |
| Upload/flash fails | Development Issues |
Symptoms: No LEDs, no WiFi network, no response
Solutions:
-
Check USB cable
- Some cables are charge-only (no data)
- Try a different known-good cable
-
Try different USB port
- Front panel ports may have insufficient power
- Try a port directly on the computer
-
Check power source
- Computer USB: Ensure computer is on and not sleeping
- USB adapter: Ensure it provides 5V/500mA minimum
-
Inspect the board
- Look for visible damage
- Check for loose components
- Smell for burning (disconnect immediately if detected)
Solutions:
-
Reset the device
- Press and hold RST button for 2 seconds
- Wait for complete reboot
-
Check SD card
- Remove, reinsert SD card
- Verify card is formatted FAT32
- Verify GUI files are present
Symptoms: Network doesn't appear in WiFi list
Solutions:
-
Wait a moment
- WiFi starts within a few seconds of power-on
- Refresh your WiFi list
-
Reset the device
- Press RST button
- Wait for WiFi to restart
-
Verify mode
- Device might be in Client mode, not AP mode
- Check if you previously configured Client mode
- Re-flash firmware to restore AP mode
-
Check for interference
- Move closer to the device
- Reduce WiFi congestion (2.4GHz band)
Note: The WiFi AP broadcasts independently of the SD card. If you can see the network but the web interface doesn't load, check the SD card.
This is normal. Glitchy creates a local network without internet access. Dismiss the warning and proceed.
Solutions:
- Reduce distance — Move computer closer to device
- Reduce interference — Turn off other 2.4GHz devices
- Check power supply — Unstable power affects WiFi
Solutions:
-
Verify WiFi connection
- Confirm connected to Glitchy network
- Check IP assignment (should get 192.168.4.x)
-
Check URL
- Use
http://nothttps:// - Use correct IP:
http://192.168.4.1
- Use
-
Try different browser
- Clear cache and cookies
- Disable browser extensions
- Try incognito/private mode
-
Check SD card
- Web files served from SD card
- Verify files exist and are correct version
Solutions:
-
Check version compatibility
- Firmware and Web GUI versions must match
- Update both if mismatched
-
Clear browser cache
- Hard refresh: Ctrl+Shift+R (Cmd+Shift+R on Mac)
- Clear site data in browser settings
-
Check browser console
- Press F12 → Console tab
- Look for JavaScript errors
Solutions:
-
Check WebSocket connection
- If controls are unresponsive, the WebSocket connection may have dropped
- Refresh the page
-
Reset the device
- Press RST button
- Reconnect to WiFi and reload
Symptoms: Sweep completes but no success detected
Solutions:
-
Verify connections
ESP32-S3 Target Pin 15 ─[FET]──── VCC Pin 11 ────────── Trigger input Pin 12 ────────── Success output GND ───────────── GNDNote, while you can connect to the header, it's best to solder directly to the board for a lower resistance connection.
-
Verify target code
- Confirm vulnerable code is uploaded
- Check serial output from target
- Verify trigger mechanism works
-
Widen parameter range
- Decrease shortest_delay_ns (try 100ns)
- Increase longest_delay_ns (try 2000ns)
- Decrease step size (try 5ns)
-
Increase attempts
- Set num_of_attempts to 5 or 10
- Glitching has inherent randomness
-
Check FET circuit
- Verify FET is connected correctly
- Check for proper power supply to target
Symptoms: Target resets during or after every glitch
Solutions:
-
Reduce glitch duration
- Holding the crowbar down too long will cause a reset, lower your max time
-
Check power supply
- Target may need separate power
- USB power may be insufficient
Solutions:
-
Narrow the range
- Note successful parameters
- Set range to success ±50ns
- Increase attempts per step
- Just by the nature of glitching, it may not work every time.
Symptoms: Graph shows flat line or only noise
Solutions:
-
Check analog connections
- The power connections are running through the correct port
- Ground connections solid
-
Adjust bias point
- Signal may be outside ADC range
- Center the signal with bias adjustment
-
Increase gain
- Signal may be too small to see
- Increase analog front-end gain
-
Rsense Adjustment
- You may need to increase rsense
- Increase rsense with dip switches to just under the board not working
- You can optionally install your own resistor value if needed in blank throughhole footprint provided
-
Verify target operation
- Target must be performing operations
- Use key pins to trigger activity
Solutions:
- Reduce gain — Signal is too large
- Adjust bias — Center the signal in range
- Check voltage limits — Don't exceed ADC input range (2.5V)
- Lower Rsense - Rsense may be too high, providing too large of a signal
Solutions:
- Shorten wires — Long wires act as antennas
- Use shielded cable — Reduce EMI pickup
- Separate power sources — Isolate Glitchy from target power
- Increase Rsense - Reduce gain, increase Rsense so you have more signal before amplifying it
"No serial port found"
- Check USB connection
-
Install USB drivers
- CP210x drivers from Silicon Labs (Glitchy uses CP2102N)
-
Linux users: Add user to dialout group
sudo usermod -aG dialout $USER # Log out and back in
"Upload failed, timeout"
-
Enter bootloader mode:
- Hold BOOT button
- Press RST button
- Release RST, then release BOOT
- Upload within 10 seconds
-
Try lower upload speed
- Add to platformio.ini:
upload_speed = 115200
- Add to platformio.ini:
"Permission denied"
-
Linux/macOS:
sudo chmod 666 /dev/ttyUSB0 # or add udev rule for permanent fix
"Library not found"
pio pkg install
pio pkg update -p espressif32"Board not found"
pio pkg install -p espressif32If all else fails, perform a factory reset:
- Re-flash firmware using PlatformIO
- Format SD card as FAT32
- Copy fresh GUI files from release package
- Reset WiFi to AP mode (may require code change)
If these steps don't resolve your issue:
- Search existing issues: GitHub Issues
-
Open new issue with:
- Detailed symptom description
- Steps you've already tried
- Firmware/GUI versions
- Hardware setup details
- Any error messages