Armbian for Khadas EDGE (RK3399)

Built a new Armbian image 5.77 20190331 with PCIe NVME support (added patch and changed dtb which is used by default to edge+Captain version). Module EVO-970 now can be seen immediately in the system and can work with it as with usual drive. The speed of NVME is impressive. :slight_smile:

All components work (WiFi, BT, wired network, sound, etc.). After installing the media script - any video in full screen with any resolution up to 4K. :slight_smile:


Do you have an idea whether the aforementioned patch (I guess it’s this one) is also needed on other RK3399 devices combined with the EVO 970?

Alas, I am not familiar with other models and can’t say how much it is necessary for them.

Update image ver 5.78 20190412


New image Armbian 5.82 .


New image Armbian ver 5.86 .
For version kernel 5.1 NEXT added support for USB sound and WiFi.


New image Armbian ver 5.88 .


Hi @balbes150, I thought I’d test out your Armbian-next images (i.e. the ones with modern 5.2-rc kernels) on a new Edge board that’s just turned up. I’ve tested all three of

  • Armbian_5.88_Rk3399-tv_Debian_buster_next_5.2.0-rc4-next-20190613.img
  • Armbian_5.88_Rk3399-tv_Ubuntu_bionic_next_5.2.0-rc4-next-20190613.img
  • Armbian_5.88_Rk3399-tv_Ubuntu_disco_next_5.2.0-rc4-next-20190613.img

They work but the wlan interface doesn’t seem to be detected: iw list, ip link, etc. don’t show it, nothing mentioned in dmesg, unlike say the default_4.4.154 image where it does show up. I also checked the previous

  • Armbian_5.86_Rk3399-tv_Ubuntu_bionic_next_5.1.0-next-20190517.img

where you first mentioned -next support for USB sound and WiFi, in case the latest image had a regression.

I haven’t yet done any debugging on this other than a cursory check to see that the device tree in /proc/device-tree does have something vaguely sensible in wireless-wlan.

Before I dive in too much, I just wanted to check if you’ve seen wlan working on your own board with any these images? It might be an Edge vs Edge-V difference that’s biting me here if so.

Whereas if you haven’t yet had it working yourself, I’ll start by building a new kernel from the for-next branch of and take it from there.

I use a computer translator and did not understand what WLAN means. Specify what is meant.
Do you know the kernel options that are responsible for this ?

It is the wifi chip support.(Wireless Local Area Network).
But I heard the Khadas Edge V doesn’t have mainline support for the wifi chip yet.
It sounds like he has the Khadas Edge V but not 100% sure.

That’s right: it’s the wireless networking that appears not to work in in any of the Armbian 5.x images which I’ve tested. I’m testing with a standard Edge, not the Edge V; we’re designing our own carrier board but for the moment this is just a bare module.

The relevant driver is present in the 5.x kernel but the device tree needs to be correct too, and the image also needs to contain the firmware blob for the wireless chipset. I’m happy to debug this myself; I expect it’ll just be a device tree issue and will be easy to fix.

But given @balbes150 comment above (“For version kernel 5.1 NEXT added support for USB sound and WiFi”), I wondered if it already worked for you or if you hadn’t yet tried it?

It seems to be a machine translation problem. It is about supporting “USB sound” and “USB WiFi”. The built-in WiFi 6398 module does not work on the core 5 yet (it needs a new firmware). Maybe Khadas can try to contact AMPAC (wifi chip manufacturer) for support of this module in the main core.

Ah, I understand where the confusion came from, yes.

Looks like there’s ongoing investigation to get this working. In principle it should work on the mainline brcmfmac driver with the same firmware blob as the legacy vendor kernel, but apparently that firmware blob isn’t downloading to the device correctly for some reason:

AP6398S may have been a poor choice of wireless module if mainline support still isn’t there in mid-2019 for a compute board designed in 2018 though. Ho hum.

Tested latest image (5.88) and here is the result of armbianmonitor -u:
The ethernet chip seems well recognized, but I was not able to make it work so I used an wifi usb stick.

Try to run the option with kernel 4.4.

Please check this version with the use of media script on EDGE-V. I am interested in how the full-screen video output on EDGE-V will work with the DTB that is included in the default image. On EDGE+Captain everything works without problems, including WiFi and BT (when you run the BT enable command).

DTS for Khadas EDGE \ EDGE-V appeared in the NEXT kernel sources :slight_smile:

I tried to build a system with NEXT kernel, but while the kernel does not start, maybe not all changes are still included in the kernel sources.

I downloaded your 4.4 5.88 image and here is the output of armbianmonitor -u:
Ethernet works, but the wireless card seems detected but not able to connect to any wireless network. It is not visible in the desktop network widget and
sudo iwlist wlan0 scan returns:
wlan0 Interface doesn't support scanning.

@balbes150 maybe you missed it or it’s a known limitation… but with kernel 5.2 cpufreq support seems to be broken and all CPU cores clock with just 600 MHz: Performance comparison between the Edge-V and VIM3

The “default” “dev” images use the 4.4 kernel (with additional patches).