No power light does not automatically prove a ZimaBoard is dead, but if a known-good power supply produces no network, display, or boot activity, the board needs hardware-level troubleshooting. For a brief red flash followed by a dead-looking board, reseating the RTC battery is a community-verified recovery step; if there is no recovery, support replacement may be the correct outcome.
The original poster tested the power supply and ultimately reported that the board itself was dead and IceWhale provided a replacement. A different user in the same discussion described a similar one-second red flash and recovered by disconnecting and reconnecting the RTC battery. Those are two different outcomes, so this guide keeps the diagnostic boundary explicit.
Step 1: Verify the Power Supply Under Load
Do not rely only on the adapter label. Confirm you are using the correct ZimaBoard power supply and, if possible, test with another known-good compatible adapter.
A supply can show voltage with no load and still collapse when the board starts.
Step 2: Check for Any Sign of Boot
Connect Ethernet and watch link/activity LEDs. Check your router's DHCP client list. If possible, attach a known-good MiniDP display.
A board can boot headlessly even if you do not see the indicator you expected.
Step 3: Disconnect Drives and PCIe Devices
Remove SATA drives, USB devices, PCIe cards, and other peripherals. Test only the board, memory, power, and network/display.
This isolates a shorted peripheral or overloaded supply from a motherboard fault.
Step 4: Reseat RAM
Power off completely, remove the memory module, and reseat it firmly. If you have a known-good compatible module, test it.
Step 5: Try an RTC/CMOS Reset for the Brief-Flash Symptom
A community user with a board that flashed red for less than a second and then appeared dead recovered by opening the bottom, disconnecting the RTC battery, and reconnecting it.
Use ESD precautions and do not short random pins. A CMOS reset can also restore firmware defaults, so review boot settings afterward.
Know When the Board Is Probably Hardware-Failed
If you have:
- a known-good compatible PSU;
- known-good RAM;
- minimal hardware connected;
- no DHCP/network activity;
- no usable display/POST;
- no improvement after a careful RTC reset;
then continued software troubleshooting is unlikely to help.
The Source Case Ultimately Needed Replacement
The original poster later confirmed that their board was dead and was replaced. That is important evidence: the RTC-battery workaround is worth trying, but it should not be presented as a guaranteed resurrection procedure.
The current ZimaBoard getting-started guide provides the normal hardware setup path.
The boot troubleshooting guide provides a wider recovery checklist.
Check Whether the Board Is Drawing Any Power
If you have a suitable inline power meter, compare behavior at plug-in and during attempted boot. Zero draw suggests the power path is not reaching the board; a brief rise followed by collapse can point toward protection, a short, or failed initialization.
Do not probe exposed board power rails unless you are qualified and have the correct schematic. External observation is enough for normal user troubleshooting.
Do Not Reflash the OS Before Proving the Board Boots
A dead-looking board with no network, display, or firmware activity is not fixed by rewriting the ZimaOS image. Confirm that the motherboard reaches POST or at least appears on the network before introducing storage or software recovery steps.
Protect a Working Power Adapter from False Blame
If the same adapter reliably powers another known-good compatible ZimaBoard, that is stronger evidence than simply measuring open-circuit voltage. Conversely, if another compatible adapter restores the board, replace the suspect PSU rather than continuing motherboard diagnosis.
FAQ
Does ZimaBoard have to show a light when powered?
Indicator behavior alone is not enough to prove health. Check Ethernet, DHCP, display, and boot behavior as well.
Can the RTC battery make a ZimaBoard appear dead?
A community user recovered a brief-red-flash case by reseating the RTC battery, so it is a reasonable troubleshooting step for that symptom.
Will an RTC reset erase my SATA data?
No. It resets firmware/clock state, not the contents of attached data drives.
When should I contact support?
When known-good power and RAM plus minimal-hardware and CMOS tests still produce no boot or network activity.
