Boot Issues
Solutions for boot-related problems.
Board Doesn't Power On
Symptoms
- No power LED
- No serial output
- Board completely unresponsive
Solutions
-
Check Power Supply
- Verify 5V output
- Minimum 3A current
- Try different power supply
-
Check Connections
- Power jack polarity
- Secure connection
- No loose wires
-
Check for Shorts
- Remove all peripherals
- Inspect board for damage
Kernel Panic
Symptoms
- Boot starts but stops
- "Kernel panic" message
- Stack trace on serial console
Solutions
-
Re-image SD Card
# Re-flash with balenaEtcher# orsudo dd if=image.wic of=/dev/sdX bs=4M -
Check SD Card
- Try different card
- Check for errors:
fsck -y /dev/sdX2 -
Verify Firmware
- Re-flash SPI firmware
- See Flashing Failures for recovery mode instructions
U-Boot Not Starting
Symptoms
- Serial shows garbage characters
- No "U-Boot" banner
- Prompt never appears
Solutions
-
Check DIP Switches
- SW1.1 = OFF
- SW1.2 = OFF (normal boot)
-
Check Serial Connection
- Correct baud rate: 115200
- Correct device path
- Try different USB port
-
Re-flash Bootloader
- Recovery mode flashing
- See Flashing Failures for instructions
Filesystem Corruption
Symptoms
- "Read-only filesystem" errors
- I/O errors
- Boot hangs on filesystem check
Solutions
-
Run fsck
# From another Linux systemsudo fsck -y /dev/sdX2 -
Re-image SD Card
- Backup data first
- Flash fresh image
-
Proper Shutdown
- Always use
powerofforreboot - Don't just unplug power
- Always use
Boot Hangs
Symptoms
- Boot starts but stops mid-way
- No error message
- LED stuck in pattern
Solutions
-
Check Boot Files
- /boot directory exists
- Kernel image present
- Device tree blob present
-
Verbose Boot
- Interrupt U-Boot
- Add
debugto bootargs
-
Minimal Boot
- Remove SD card
- Boot from UART recovery
Quick Diagnostic Commands
# Check boot log
dmesg | head -100
# Check filesystem
df -h
# Check partitions
lsblk
# Check boot files
ls /boot
Still Having Issues?
- Flashing Failures
- Network Issues
- Contact support with serial log