When a Sunplus chip enters download mode, the Windows USB stack sees a device with:
The operating system does not natively know what to do with this. It needs a custom driver. sunplus loader
Despite its simplicity, the Sunplus Loader is notoriously finicky. Here are the most common failures and solutions. When a Sunplus chip enters download mode, the
| Error Message | Probable Cause | Solution |
| :--- | :--- | :--- |
| "USB Device Not Recognized" | Driver conflict or Windows power management | Uninstall USB Root Hub drivers in Device Manager, disable USB selective suspend in Power Options. |
| "Loader: Write Flash Timeout" | Corrupt firmware file or bad NAND block | Download a different version of the firmware. Use the "Erase Full Flash" option if available (rare). |
| "Invalid Firmware CRC" | Firmware does not match the chipset | Find the exact firmware for your device revision. Do not force-flash. |
| Device flashes for 2 seconds, then disconnects | Insufficient power from USB port | Use a powered USB hub or a rear motherboard USB port (not front panel). |
| Loader tool crashes on Windows 11 | 32-bit vs 64-bit compatibility | Run the loader in Windows 7 Compatibility Mode (Right-click -> Properties -> Compatibility). |
| Driver installs but loader says "Chip ID mismatch" | You have a Sunplus clone or a different die revision | Search for a loader tool with "Auto Detect" or manually edit the .ini config file to bypass chip ID check (advanced). | The operating system does not natively know what
| Symptom | Likely Fix | |---------|-------------| | No response from device | Check boot mode; RX/TX swapped; baud rate mismatch | | Verify fails | Bad serial connection; flash corruption; wrong firmware offset | | Device hangs after download | Missing bootloader; incorrect reset vector; power cycle needed |
The loader implements a barebones USB control transfer protocol:
No mass storage class, no FAT — just raw memory access.