Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Rupa X88 Pro 13 - RK3528 board with images

Featured Replies

A question from a beginner: how do I install it to use it for the first time? Should I use a flash drive and Rufus, or is there another way? I didn't quite understand, and I couldn't find any clear information.

I tried installing it to the internal eMMC memory, and now it won't boot. It looks like it'll have to stay on the SD card—or is there a way to install it? 

On 6/29/2026 at 8:40 AM, SuLorde said:

now it won't boot


You are not the 1st to do this:

 

Let me explain the problem first.

 

The CPU itself, without any storage attached, has a built-in U-Boot.
However, this U-Boot does not initialize video output, so you won't be able to see it on an HDMI screen. (The good news is that it usually initializes the serial port.)
This U-Boot reads environmental data from a data blob on the MMC (usually within the first 10 MB of the disk).
This environmental data tells the U-Boot the sequence of commands needed for the MMC/USB U-Boot to boot.
Once the MMC/USB U-Boot boots, you get video output.

The problem is that you deleted the data blob containing the environmental data from the MMC, so the CPU's U-Boot does nothing. It just loops, saying that it found no device to boot.

 

If you have a serial adapter, it is possible to interact with this CPU U-Boot. Pressing Ctrl+C (in a terminal that does not intercept Ctrl+C—my advice is to use PuTTY, even on Linux) should stop whatever it is doing.
By interacting with this CPU U-Boot, you can instruct it how to boot your MMC or USB U-Boot.
However, you will have to do this manually every time you boot.

 

To fix the issue, you need to restore that data blob containing the properties to its specific location on the MMC.
I don't know where it starts or what format it uses, so I was unable to recreate one from scratch.
My way of fixing this was to find a backup of the original MMC and restore the first GB.

 

So, did you make a backup? If yes, you can restore it with some serial magic.
If you did not make a backup, you can search for one or ask someone who has one. (check that this thread for the other guy's solution)


 

Hi again,

I previously reported here that Wi-Fi was not working on my X88 Pro 13 hardware revision 1.7. Since then, I have successfully tested
transferring Armbian from a microSD card to the internal eMMC. I added the tested x88pro-install-emmc script and installation instructions here:

 

https://github.com/nepnepnep/x88pro/tree/emmc-install

https://github.com/nepnepnep/x88pro/tree/emmc-install/userpatches/overlay/usr/local/sbin

 

The script preserves the factory first-stage bootloader (idbloader), because the generic Armbian RK3528 idbloader caused unstable DDR
initialization and random boot failures on my box.

It writes only Armbian's second-stage u-boot.itb, creates new boot and root filesystems, and copies the running microSD system to eMMC.

After installation, my revision 1.7 box successfully boots Armbian directly from eMMC with the microSD card removed.

If anyone has the same device, especially PCB revision 1.7, please try it and share your results.

 

IMPORTANT: Make as many backups as possible before trying this!

 

Installing to eMMC destroys the existing Android partitions and data. Make a complete dump of the original Android firmware and eMMC
first. Also make sure that you know how to recover the device through Maskrom mode using rkdeveloptool.

The backup automatically created by the script contains only the boot area and partition table. It is not a complete Android backup.

Please run the safe, non-destructive check first:

sudo x88pro-install-emmc --dry-run

Only proceed with the installation if all detected devices and proposed changes are correct:

sudo x88pro-install-emmc

I am also still investigating Wi-Fi on my revision 1.7 board. Unfortunately, I did not back up its original Android firmware before overwriting it.

 

Could someone with the same PCB revision and Wi-Fi hardware please share either:

1. The original Android DTB/device tree from revision 1.7; or, preferably,
2. A complete dump or original factory Android firmware for this exact board revision.

A dump from a device with the same Wi-Fi hardware would be especially useful. It would help me determine the correct Wi-Fi configuration and get Wi-Fi working under Armbian. I would be very grateful for any help. Thank you!

Edited by serovan

@serovan Thank you for contributing. The script now makes it possible to run the operating system from the integrated eMMC.

You can download the latest OTA-Android update for the X88pro13 box at: 

https://boxput.notion.site/X88-Series-Fireware-6f707e5e9b06413aac2df3dc291e67aa

Useing Binwalk  detects and xtract several DTB files; one of them should be the correct one for version 1.7. Is it possible for you to open the device and take a photo of the version 1.7 board? Which Wi-Fi chip is installed?

I might be able to modify the Wi-Fi driver.

Many thanks for this script, everything ok 👍(provided you have binutils installed, which was not the case on my minimal image). I am still struggling to get wifi working on my V1.1 board with the generated rk3528-x88pro.dtb ( works well with hinlink-ht2.dtb)

Hi,

I have X88 Pro 13 hardware revision 1.7. With V0.7 or my compiled trixie minimal 6.1.172 the WiFi doesn't work.

cat /var/log/wifi-init.log :

Unbekannter SDIO Chip oder kein Gerät gefunden: 0x6621

Hardware info:

 Device: X88 Pro 13 (Rev 1.7)

WiFi chip: EA6521 (device ID 0x6621)

I have extracted the dtb from android.

SGCAM_20261105_144112011.jpg

SGCAM_20261105_144543638.jpg

rk3528-x88pro13-v17.dts

HI,

With driver joilg/ea6x21-dkms-6.1 compiled and loaded :

dmesg | grep -E SDIO

mmc2: new ultra high speed SDR104 SDIO card at address 0001

[SKWSDIO INFO] skw_sdio_scan_card: sdio_scan_card

[SKWSDIO ERROR] skw_sdio_scan_card: wait scan card time out

[SKWSDIO INFO] skw_sdio_io_init: OK

dmesg | grep -E "SKW"

[ 20.867835] [SKWSDIO INFO] skw_sdio_scan_card: sdio_scan_card

[ 22.926223] [SKWSDIO ERROR] skw_sdio_scan_card: wait scan card time out

[ 22.926251] [SKWSDIO INFO] skw_sdio_io_init: OK

[ 22.937134] [SKWBOOT]:seekwave_boot_parse_dt, chipen:38 gpio_out:49 gpio_in:50 state = 0 ret=0

[ 22.937162] [SKWBOOT_ERR]:seekwave_boot_probe get bus dev fail, deferring probe

[ 22.960659] [SKWBT_INFO] Seekwave Bluetooth driver ver 0.1

[ 22.984263] [SKWIFI INFO] VERSION: 2.0.240304.e998adb (6.1.115-vendor-rk35xx)

[ 34.235999] [SKWBOOT]:seekwave_boot_parse_dt, chipen:38 gpio_out:49 gpio_in:50 state = 0 ret=0

[ 34.236026] [SKWBOOT_ERR]:seekwave_boot_probe get bus dev fail, deferring probe

[ 34.443123] [SKWBOOT]:seekwave_boot_parse_dt, chipen:38 gpio_out:49 gpio_in:50 state = 0 ret=0

[ 34.443147] [SKWBOOT_ERR]:seekwave_boot_probe get bus dev fail, deferring probe

cat /sys/kernel/debug/devices_deferred

vdd-cpu pwm-regulator: Failed to get PWM

mtd_vendor_storage

vdd-logic pwm-regulator: Failed to get PWM

vdd-gpu pwm-regulator: Failed to get PWM

seekwcn_boot

ff700000.gpu platform: supplier vdd-gpu not ready

Still no wifi, any idea ?

@CD38 Hi,

Unfortunately, the x88pro13 is manufactured by various companies, often featuring different Wi-Fi chips and modified board layouts. I own an older board with an LGX8800 Wi-Fi chip, and have access to a V1.5 board equipped with an EA6521Q chip. Since your image also shows an EA6521Q chip, the driver on https://github.com/joilg/ea6x21-dkms.git should be fine, it is also included in my x88pro image . The PCB layout in the WiFi section differs significantly from that of version 1.5. I assume that the connections for the WiFi control GPIOs have been changed. Due to the modified board layout, it may be necessary to change the GPIO assignments in the dts.

I cannot find any specifically assigned GPIOs for the Seekwave driver in your DTS file. They are likely hardcoded into the Android driver.

First, check whether the chip is responsive.

root@x88pro:~# dmesg | grep SDIO
[    1.726067] mmc2: new UHS-I speed SDR104 SDIO card at address 8800

address 8800 is the Chip ID of the EA6521Q.

this is independent of the wifi driver, and controled from sdio_pwrseq , gpio1 6, which is the same in 1.7 dts.

If you have access to the Android command line, for example, via ADB, the following commands could be helpful to inpect used Pins

adb shell
su
gpioinfo
cat /sys/kernel/debug/gpio
cat /sys/kernel/debug/pinctrl/pinctrl-maps
dmesg | grep skw

you can change the gpios numbers with dts overlays.

Create a DTS overlay file rk3528-skw.dts:

dts-v1/;
/plugin/;

&{/} {
	compatible = "rockchip,rk3528";
	seekwcn_boot {
		gpio_host_wake = <&gpio1 18 1>;
		gpio_chip_wake = <&gpio1 17 1>;	
	};
	sdio_pwrseq {
		reset-gpios = <&gpio1 6 1>;

};

and apply it with:

sudo armbian-add-overlay rk3528-skw.dts
reboot

Play around with the GPIOs pins. <&gpio1 16 1> are used in some other rockchip boards.

view dmesg | grep skw for anny changes on other gpios.

please paste the debug Info to pastebin and show the link here with:

armbianmonitor -u

good luck with the testing

johilg

Thanks, I'll try to look into it further.

So this output

dmesg | grep -E SDIO

mmc2: new ultra high speed SDR104 SDIO card at address 0001

0001 is not he EA6521Q ? should found 8800 instead.

it seems that the chip is not correct powered. sdio_pwrseq reset-gpios is on my board on pin PA_6 = <&gpio1 6 1>; but is the same in dts1.7. android Software do sometimes not comply the dts. Hardware v1.7 could also have a kind of powermanagement or wake on wlan implemented.

Do you have a USB-A to USB-A cable? It is posible to get on the commandline on Android and inspect the log with adb Software.

https://developers.google.com/chromeos/app-development/develop/adb-over-wifi-and-ethernet?hl=de . Maybe it is posible to get into adb over LAN or Wifi. You have to activate the develloper extensions in you android settings.

Edited by johlnx

The log shows the chip id of 0001 vs. 8800 on the 1.5 layout.

This is strange, because the marking on the chip itself bears the exact same name. Maybe it contains an other silicon inside.

Android log and the DTS file shows an other Wifi driver "seekwcn_sv6160lite".

Luckily, retro98boy host a dkms driver , that that might work:

https://github.com/retro98boy/swt6621s

Furthermore, I found two different GPIOs.

PCB v1.7 V1.5

sdio-pwrseq pin gpio1-7 pin gpio1-6

vcc5v0-host-regulator pin gpio4-12 pin gpio4-13

First try if changing the gpio ports and test it with the installed driver:

appply this dts overlay file, reboot and and observe a change in the system log.

dts-v1/;
/plugin/;
&{/} {
	compatible = "rockchip,rk3528";
	sdio_pwrseq {
		reset-gpios = <&gpio1 7 1>;
	vcc5v0_host: vcc5v0-host-regulator {
		gpio = <&gpio4 13 0>;
	};
};

If that does not lead to success, install the new driver on target:

#remove old
dkms remove -m ea6621q -v 1.0

cd /usr/src
git clone https://github.com/retro98boy/swt6621s.git
mv seekwave-swt6621s seekwave-swt6621s-1.1.0
dkms add -mseekwave-swt6621s -v 1.1.0
dkms build -mseekwave-swt6621s -v 1.1.0
dkms install -mseekwave-swt6621s -v 1.1.0

modify file /etc/modprobe.d/seek.conf:

options skw_sdio_lite firmware_dir=seekwave
options swt6621s_wifi firmware_dir=seekwave
options skwbt firmware_dir=seekwave

modyfy file /etc/modules-load.d/seek.conf:

hidp
rfcomm
bnep
skw_sdio_lite
swt6621s_wifi
skwbt

Apply dts overlay;

dts-v1/;
/plugin/;
&{/} {
	seekwcn_sv6160lite {
		compatible = "seekwave,sv6160lite";
		dma_type = <0x01>;
		status = "okay";
		phandle = <0x1ca>;
	};
};

reboot board and check:

 ip link
system log | grep SKW

not testet from my side.

good success

I can't get it to work with ea6621q but Wifi works with dkms build from https://github.com/retro98boy/swt6621s

I attached my working DTD file.

Now, I hope it will remain stable, need more testing...

To sum up :

#remove old

dkms remove -m ea6621q -v 1.0

#compile new

cd /usr/src

git clone https://github.com/retro98boy/swt6621s.git

mv swt6621s swt6621s-1.1.0

dkms add -m swt6621s -v 1.1.0

dkms build -m swt6621s -v 1.1.0

dkms install -m swt6621s -v 1.1.0

mv firmware/ /lib/firmware/seekwave

#modify file /etc/modprobe.d/skw.conf:

options skw_sdio_lite firmware_dir=seekwave

options swt6621s_wifi firmware_dir=seekwave

options skwbt firmware_dir=seekwave

#modyfy file /etc/modules-load.d/skw.conf:

hidp

rfcomm

bnep

skw_sdio_lite

swt6621s_wifi

skwbt

#change dtb in /boot/armbianEnv.txt

Thanks Johlnx !

rk3528-x88pro-seekwave.dtb

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.