Troubleshooting

Troubleshooting

🇷🇺 Русская версия

---

Common issues and solutions.

Connection Issues

"No devices found"

Symptoms: Clicking Scan shows no devices

Solutions:

1. Check USB cable (use data cable, not charge-only)
2. Try different USB port
3. Check if device appears in system:
   • Windows: Device Manager → Ports (COM & LPT)
   • macOS: ls /dev/tty.usb*
   • Linux: ls /dev/ttyACM*
4. Reflash firmware to microcontroller
5. Try Mock mode to verify app works

"Connection failed" after connecting

Symptoms: Device found but ping fails

Solutions:

1. Disconnect and reconnect USB
2. Reset microcontroller (press reset button)
3. Check firmware version matches app version
4. Try different USB cable

Chip Detection Issues

"Unknown chip" or wrong detection

Symptoms: Chip ID shown but not recognized

Solutions:

1. Check wiring - especially CLE, ALE, CE#
2. Verify 3.3V power to chip
3. Add 10kΩ pull-up on R/B# line
4. Check for cold solder joints
5. Try slower timing (if supported)
6. Report chip for database addition

All 0xFF or 0x00 chip ID

Symptoms: ID reads as FF FF FF FF FF or 00 00 00 00 00

Causes:

• No power to chip
• CE# not going low
• Data bus not connected
• Chip is dead

Solutions:

1. Verify VCC and GND connections
2. Check CE# signal with multimeter/scope
3. Verify data bus wiring (D0-D7)
4. Try known-good chip

Dump Issues

Dump contains all 0xFF

Symptoms: Entire dump is empty (0xFF bytes)

Causes:

• Chip is erased/empty
• RE# signal not working
• Data bus issue

Solutions:

1. Check RE# wiring
2. Verify data bus connections
3. Try reading chip ID first (if that works, data bus is OK)
4. Chip may actually be empty

Dump has repeating patterns

Symptoms: Same data repeats every N bytes

Causes:

• Address lines not connected
• Partial address bus failure

Solutions:

1. Check all address-related signals (ALE)
2. Verify column and row address cycles

Corrupted data / bit errors

Symptoms: Data looks mostly correct but has errors

Causes:

• Signal integrity issues
• Timing too fast
• ECC errors in original data

Solutions:

1. Shorten wires
2. Add decoupling capacitors
3. Use ECC correction in analysis
4. Try slower timing

GUI Issues

App won't start

Windows:

• Install WebView2 Runtime
• Run as administrator

macOS:

• Right-click → Open (bypass Gatekeeper)
• Check System Preferences → Security

Linux:

• Make AppImage executable: chmod +x OpenFlash*.AppImage
• Install webkit2gtk: sudo apt install libwebkit2gtk-4.1-0

UI is blank or frozen

Solutions:

1. Check for antivirus blocking
2. Try running from terminal to see errors
3. Delete config: ~/.config/openflash/
4. Reinstall application

Hex viewer is slow

Symptoms: Scrolling is laggy with large dumps

Solutions:

1. Use page navigation instead of scrolling
2. Reduce page size in settings
3. Close other applications
4. Large dumps (>1GB) may be slow

Firmware Issues

Pico not entering bootloader mode

Solutions:

1. Hold BOOTSEL before connecting USB
2. Keep holding until drive appears
3. Try different USB port
4. Check USB cable

Pico 2 (RP2350) bootloader issues

Solutions:

1. Same as Pico - hold BOOTSEL before connecting
2. Ensure using RP2350-specific .uf2 file
3. Check that drive shows as "RP2350" not "RPI-RP2"

STM32 won't flash

Solutions:

1. Set BOOT0 jumper to 1
2. Reset board
3. Flash via ST-Link or serial
4. Set BOOT0 back to 0

Arduino GIGA won't flash

Solutions:

1. Double-tap reset button to enter bootloader
2. Use DFU mode: hold BOOT0, press reset
3. Flash via probe-rs or dfu-util
4. Check USB cable supports data transfer

Firmware crashes / resets

Symptoms: Device disconnects during operation

Causes:

• Power issue
• Firmware bug
• USB enumeration problem

Solutions:

1. Use powered USB hub
2. Update to latest firmware
3. Report issue with steps to reproduce

Performance Issues

Dump is very slow

Expected speeds:

• Arduino GIGA (FMC): ~500KB/s (fastest)
• Raspberry Pi 4/5: ~400KB/s
• STM32F4: ~200KB/s
• Orange Pi: ~150KB/s
• RP2350: ~150KB/s
• RP2040: ~100KB/s
• ESP32: ~80KB/s
• STM32F1: ~50KB/s

If slower:

1. Check USB connection (use USB 2.0+ port)
2. Close other USB-heavy applications
3. Avoid USB hubs if possible
4. For ESP32: use USB instead of UART if available
5. For SBCs: ensure network connection is stable

SBC-Specific Issues (v2.3+)

Raspberry Pi GPIO not working

Symptoms: Permission denied or GPIO errors

Solutions:

1. Run with sudo: sudo openflash-gpio
2. Add user to gpio group: sudo usermod -aG gpio $USER
3. Check /dev/gpiomem permissions
4. For Pi 5: ensure libgpiod is installed

Orange Pi GPIO errors

Symptoms: Failed to map memory or GPIO access denied

Solutions:

1. Run with sudo (required for /dev/mem access)
2. Check SoC compatibility (Allwinner H616/H618 or Rockchip)
3. Verify correct GPIO pin mapping for your board model

Network device won't connect

Symptoms: "Connection refused" or timeout

Solutions:

1. Verify SBC daemon is running: ps aux | grep openflash
2. Check firewall: sudo ufw allow 5000
3. Verify IP address and port
4. Try Unix socket for local connections
5. Check network connectivity: ping <sbc-ip>

SBC daemon crashes

Symptoms: Daemon exits unexpectedly

Solutions:

1. Check logs: journalctl -u openflash-gpio
2. Verify GPIO permissions
3. Ensure no other process is using GPIO pins
4. Update to latest firmware version

Still Having Issues?

1. Check GitHub Issues for similar problems
2. Ask in Discussions
3. Open a bug report with:
   • OS and version
   • Hardware used
   • Steps to reproduce
   • Error messages/logs