Search the Community

Showing results for tags 'rk3399'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements & first aid
    • Announcements
    • Board doesn't start
  • Community forums
    • Common issues / peer to peer technical support
    • Reviews, Tutorials, Hardware hacks
    • Help wanted
    • Feature Requests
    • TV boxes
    • General chit chat
  • Bug tracker - supported boards and images only
    • Allwinner A20
    • Allwinner H2 & H3
    • Allwinner A64, H5, H6 and H616
    • Armada A388, A3700
    • Amlogic S905(x), S922X
    • NXP (Freescale)
    • Rockchip 3288 & 3328
    • Rockchip 3399
    • Other supported boards
  • Development
    • Development
  • TV Boxes's General Chat
  • TV Boxes's Reviews/Tutorials
  • TV Boxes's FAQ
  • TV Boxes's TV Boxes running Armbian
  • TV Boxes's Rockchip CPU Boxes
  • TV Boxes's Amlogic CPU Boxes
  • TV Boxes's Allwinner CPU Boxes
  • Android fanboys's Forums
  • Gaming on ARM's Reviews
  • Gaming on ARM's Issues
  • Kobol Forum's Helios4
  • Kobol Forum's Helios64

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Matrix


Mastodon


IRC


Website URL


XMPP


Skype


Github


Location


Interests

Found 8 results

  1. Could anyone launch armbian on ebox r99 (Processor (CPU) – RK3399 Hexa Core 64-bit: Dual Cortex-A72 core + Quad Cortex-A53 core/ ARM Mali-T860 high-performance GPU quad-core 800MHZ)? Which baseline and which dtb might function? Thanks for any kind hint! I have tried this image "Armbian_21.05.0-trunk_Station-p1_buster_current_5.10.26_xfce_desktop.img" with the following dtb file, the android box displayed after 10s-20s the typical android recovery menu : FDT /boot/dtb/rockchip/rk3399-roc-pc-plus.dtb FDT /boot/dtb/rockchip/rk3399-hugsun-x99.dtb FDT /boot/dtb/rockchip/rk3399-firefly.dtb FDT /boot/dtb/rockchip/rk3399-evb.dtb FDT /boot/dtb/rockchip/rk3399-khadas-edge.dtb FDT /boot/dtb/rockchip/rk3399-ficus.dtb FDT /boot/dtb/rockchip/rk3399-gru-bob.dtb FDT /boot/dtb/rockchip/rk3399-gru-kevin.dtb FDT /boot/dtb/rockchip/rk3399-gru-scarlet-inx.dtb FDT /boot/dtb/rockchip/rk3399-rock-pi-4a.dtb FDT /boot/dtb/rockchip/rk3399-kobol-helios64.dtb FDT /boot/dtb/rockchip/rk3399-leez-p710.dtb FDT /boot/dtb/rockchip/rk3399-nanopc-t4.dtb FDT /boot/dtb/rockchip/rk3399-orangepi.dtb
  2. Dear community! Could any one launch armbian or any other linux distro on ebox r99 (Processor (CPU) – RK3399 Hexa Core 64-bit: Dual Cortex-A72 core + Quad Cortex-A53 core/ ARM Mali-T860 high-performance GPU quad-core 800MHZ)? Which baseline and which dtb might function? Thanks for any kind hint!
  3. Hi, I am looking at investing in a RockPro64 NAS setup using the Pine64 Desktop casing and other necessary accessories. I'm hoping to run OpenMediaVault on it and have 2 3.5" HDDs attached. The entire setup would be configured to be a backup of my operational NAS (Helios4) in a different location (i.e. different room of the house). My reading of the forum and the armbian download section has me a bit confused. The download section indicates that the board is supported, but the forum indicates it's a WIP. Just trying to understand the status/stability of the board for what I'm planning on using it for and whether it would be a good investment or a waste of money. Also wondering whether this post regarding updating the CPU governor is related - and will be a benefit - to the RockPro64 as both the NanoPi M4 and RockPro64 share the same SoC RK3399. Thanks
  4. Hello all, I get the message "qemu kvm_arm_vcpu_init failed: Invalid argument" which I refer to the source file code "https://git.qemu.org/?p=qemu.git;a=blob;f=cpus.c;hb=refs/ heads / stable-2.11 # l1122" and "https://github.com/qemu/qemu/blob/master/accel/kvm/kvm-all.c " Row 444. I don't know which vCPU feature is expected ... #cat /proc/cpuinfo processor : 0 BogoMIPS : 48.00 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4 .... is it currently or later even possible to use virtualization? Regards
  5. Hello, using the image provided at https://www.armbian.com/rockpro64/ the board works when booted via uSD card but not via MMC. There appears to be no device mode USB drivers installed. I pulled the kernel sources with `armbian-config` and compiled them myself making sure to select dual-mode support for the DWC2 and DWC3 drivers. The kernel boots after install, but I still see nothing in /sys/class/udc and am unable to see any dwc2/3 drivers (save dwc2_pci and some dwc3 i3c drivers). I'm able to load libcomposite, the configfs driver, but that does not pull in a USB device mode driver. I'm unable to attach armbian monitor status right now but will update my post with it.
  6. Hello Folks, Good day. I hope you're doing great. I'm trying to make the OrangePI 10.1 inch MIPI DSI (product page) work on the most recent (mainline) Armbian build. Building the image using the OrangePI source repositories and following the instructions on OPi4B manual enables the LCD and touch, However, my intention is to make the LCD + Touch work on the most recent Armbian Focal (mainline). I've setup my Armbian build env but I cannot see to find how to enable this MIPI screen on any build options. Here's the instructions from Page #20 of OPi 4B manual: Download the Linux source code and make the following changes in dts --- a/arch/arm64/boot/dts/rockchip/rk3399-orangepi-lcd.dtsi +++ b/arch/arm64/boot/dts/rockchip/rk3399-orangepi-lcd.dtsi @@ -40,12 +40,12 @@ max-x = <800>; max-y = <1280>; tp-size = <101>; // <911> for 8 inch // <101> for 10 inch - status = "disable"; + status = "okay"; }; }; &dsi { - status = "disable"; + status = "okay"; panel@1 { compatible = "simple-panel-dsi"; reg = <0>; That specific file doesn't exist on the Armbian build directory tree. I'm not familiar enough with the dts and dtsi files to be integrating it. I've been searching the forum for answers but, so far, I'm not able to make it work. I'm looking for help on enable it and appreciate any pointers or guidance that can help make the LCD + Touch work on a mainline kernel version. I linked some dts files from the OrangePI source repository that "might" help. I'm thankful for any help. Thank you.
  7. Is there any way/plans to support the FrindlyArm RK3399 SOM in Armbian? Does anyone know the hardware well enough to know if another firmware could be loaded on it? It seems to be a very nice module, and the dev board has just about everything one might want on it. On a side note, possibly derailing my own topic, is there any plans to add any of the VPU patches for the RK3399 and associated software? It seems like support for that is getting pretty close, and it would be great if some of the patches that are floating around could get include in the official distro. I'm about to dive in an try getting at least accelerated ffmpeg working on my M4V2 and/or neo4, but have been hoping that it would get into the standard distro first. :-)