This page will soon be moved to the docs subdomain.
Support for these boards will come in a future version of the WoR imager, rendering most of the steps here unnecessary.
This guide and software presented here are provided "as is", without warranty of any kind. We're not responsible for any damage caused to your devices by following the steps below.
We've recently started working on support for the new RK3588 series of Arm SoCs from Rockchip. It may be the first ever series that provides desktop-class performance and I/O on affordable single-board computers.
This is still in its early stages, with the following platforms being officially supported at the moment:
Other similar boards may work too, but there might be unexpected issues. If you're an SBC maker and would like official support for your board(s) in this project, please Contact us.
Full status can be found at https://github.com/worproject/Rockchip-Windows-Drivers#hardware-support-status
There's no Estimated Time of Arrival (ETA) for anything yet, though we're actively working on improving Rockchip's UEFI and enabling more peripherals with each release.
There's a script that will guide you through the installation: https://github.com/buddyjojo/workli (thanks to @buddyjojo)
We need to flash an UEFI firmware image to our board, so that it will start behaving almost like a regular desktop PC.
Some of the boards (check product specs) include NOR memory which can hold both the firmware and user settings (like boot order).
If your board doesn't come with such memory, the firmware can be flashed with balenaEtcher / RPi imager / dd and booted off an SD card or EMMC module instead.
These steps need to be performed only when the UEFI is not yet installed or there's an update for it on Github.
Select the indicated empty spaces (they're actually open file dialog buttons).
Choose spl_loader .img as the "Loader" and the UEFI .img as the "Image".
SPINOR is selected for the Storage field of the "Image" (double-click and then click on the drop-down arrow to change).
You can also choose
EMMC instead (if your board doesn't have onboard SPI NOR), but then the image will be stored there and not in the onboard memory.
The Write by Address checkbox below Run must also be checked.
Check documentation of your board to see where this button is located. It's usually printed on the board too.
You may need to provide external power to the board if the USB-C data port cannot accept it (as is the case with Orange Pi 5).
The status in RKDevTool should change from
No Devices Found to
Found One MASKROM Device.
If this is not the case, double-check that you've installed the correct drivers, make sure you're pressing the MASKROM button before powering the board, try another USB data cable.
The process is done when the last log is "Download image OK" and the device restarts by itself, thus exiting MASKROM mode.
Since we've made our board act like a PC now by flashing an UEFI, it is very possible to create an installation USB by copying the contents of a regular Windows on Arm ISO to a FAT32 formatted USB drive (or using a tool like Rufus) and perform the installation as usual on a secondary USB drive. TPM, SecureBoot and RAM checks may need to be bypassed with regedit.
However, as we only have 2 or 3 USB ports (without a hub) to work with, it can be impossible to connect two USB drives, mouse and keyboard at the same time. We're going to perform the installation from another computer instead.
See the Getting Windows images guide. The maximum build number limitation for Raspberry Pi does not apply here as RK3588 meets the minimum CPU requirements of Windows 11 Arm.
Ignore the name, we'll change it in the next version. You can get it from the Downloads page.
Select Raspberry Pi 3 as the Device type. It will install some 3rd party drivers and boot files but those don't have any effect on other boards.
Disconnect the USB drive and connect it to the only USB port on the board that supports SuperSpeed as described in Hardware support - What works.
Also connect a keyboard and/or mouse to the other working ports, the HDMI display and you're ready to power on the board for the first time.
Windows should now do the rest of the installation process and take you to the out-of-box-experience (OOBE) setup screen where you can configure the OS as you like.
Latest Windows 11 requires an internet connection in OOBE. To skip that, press Shift + F10, type
oobe\bypassnro and enter.