Search the Community

Hi folks, I have a Firefly AIO-3399C which boots Armbian fine, but no USB devices besides the root devices are detected. This happens with both the kernel 5.19.170 and 6.0.7 based images, made by @balbes150, which I've downloaded from https://users.armbian.com/balbes150/firefly-rk3399/ Any advice would be appreciated. U-Boot 2022.04-armbian (Nov 03 2022 - 17:26:20 +0300) Linux firefly-rk3399 5.19.17-media #trunk SMP PREEMPT Thu Nov 3 17:40:36 MSK 2022 aarch64 aarch64 aarch64 GNU/Linux In dmesg output, I see the following, which may be relevant: [ 4.616394] hub 7-0:1.0: USB hub found [ 14.296598] fusb30x: module is from the staging directory, the quality is unknown, you have been warned. [ 14.298983] fusb30x: module is from the staging directory, the quality is unknown, you have been warned. [ 14.346438] fusb302 7-0022: Can't get property of role, set role to default DRP [ 14.402787] fusb302 7-0022: Unable to request IRQ for INT_N GPIO! 0 [ 14.555053] fusb302: probe of 7-0022 failed with error -22 [ 14.568604] fusb302 4-0022: Can't get property of role, set role to default DRP [ 14.574971] fusb302 4-0022: Unable to request IRQ for INT_N GPIO! 0 [ 14.576841] fusb302: probe of 4-0022 failed with error -22 [ 14.692030] usbcore: registered new interface driver brcmfmac

Test version with EFI\Grub support (with HDMI output) for rk3399. for station p1 https://disk.yandex.ru/d/HZ34T76zxS9pnw for nanopc t4 https://disk.yandex.ru/d/SjBMYJ37U6699A firefly-rk3399 https://disk.yandex.ru/d/BfrzRRyvdtavIg

Hi folks, This is a bit strange. One core is constantly at 100% on a firefly-rk3399 board. It seems to be because of some emmc issues according to this output. journalctl -f This is htop

Hi, How can I catch the reset button pressed. In other words, how can I change the behavior of the reset button on RK3399?

Anybody have success with panfrost? kernel module and userspace module I have firefly 3399( 5.4.8-rockchip64) board And I don't see panfrost in dmesg or lsmod Any idea?

Recently I've been trying to build Armbian for Firefly RK3399, since I've purchased this board last year, and it has been lacking proper software support for a long time. Here is my fork https://github.com/hjc4869/build/tree/development Basically, It is a copy & paste of what's already done to support Odroid N1, by replacing the Hardkernel's kernel to what Firefly provides (an older 4.4.77 kernel), and replacing the Hardkernel u-boot with rockchip u-boot. I created a new 'firefly' board family for convenience. Also tried to build the image with some other kernel variants (Rockchip 4.4 bsp and mainline 4.17-rc6) without success, still investigating reasons. The image boots and runs flawlessly as a headless OS, but that's far from complete. Remaining work: Kernel 1. Replace mali r13 driver with r14. Since r14 supports fbdev and xf86-video-armsoc while r13 does not. Fbdev performance is terrible, though. 2. (Maybe) Use the latest rockchip 4.4.126 kernel instead of Firefly's old (and buggy) 4.4.77, since this branch seems to be a port-and-forget one, while Rockchip kernel is still been actively developed. Userland 1. Rockchip xserver and libmali This makes the desktop experience much better (glamor, and enables GLES for X11 window programs), but there are some problems related to desktop composition. In Firefly's official Ubuntu release, the desktop composition works just fine, but I haven't figure out how to enable that with my own build. Firefly team never provide any scripts/docs to build a usable rootfs. Even without this, the desktop is definitely usable, including Chromium/Firefox, with mesa llvmpipe properly disabled. 2. Firmware Rockchip's rootfs-build repo contains several firmware required by the board (WiFi/BT/DP/etc). These firmware are currently not packed into the image. 3. Rockchip Gstreamer for hardware video decoding 4. Bluetooth This is troublesome even with Firefly's own Ubuntu image. They put some sort of magic in a `/usr/local/bin/enable_bt` script, and it must be executed right after user logon, or Bluetooth simply won't work. Really terribly documented, never want to mess up with it again. 5. Sound The board uses a rt5640 chip, which needs some tweaks related to ALSA. Most userland tweaks are likely to be the same as other RK3399 boards, given the only difference should be bootloader/kernel related stuff. Will it be possible to merge these into armbian/build as a community supported board in the future when RK3399 board family gets stable? (Of course with cleanup, e.g. use the rk3399 board family instead of a dedicated firefly family)

hi rk3399 is being very popular chip. Firefly 3399 was launched on August last year. Now Orange pi RK 3399 is launching. Pine now are preparing Pine RK3399. the same also is doing HanrdKernel - Odroid N is expected on august this year. Short Question. Are you preparing Armbian for RK3399? Are you interested in this chip. best regards

I have Firefly RK3399 board. I ran armbian from SD card successfully the first time. After full init, I ran nand-sata-flash.sh install script, also successfully. But then I can't boot from the same SD card anymore. I always boot from the eMMC memory. I expected that boot sequence would be set on SD card first, then check eMMC.

When you do gdisk -l /dev/mmcblk1 or fdisk -l you can se that the partition table that armbian is using is MBR (dos). Is any particular reason for this? When you go to the new and improved firefly rk3399 manual page you can see it is making problem when flashing through USB-C cable and upgrade_tool v. 1.24 and v. 1.34 (GBT friendly) http://wiki.t-firefly.com/en/Firefly-RK3399/flashing-notes.html .