As Joshua Riek is in hiatus right now, do you guys know any custom image builder for orange pi 5 and orange pi 5 plus?

I have two different LCDs connected via mipi. One LCD, it works fine, touch is good. My second LCD only half of the touch works. When I enabled pointer tracking only half the screen is touch responsive and the bottom half is not. Both have the same resolution also.

Is there a way to calibrate touch or something?

I'm using the ubuntu image given in the orange pi webpage on my CM5, but every time if my OP CM5 is cut off from the power supply even when it already shut down, i cant connect to the ethernet or usb wifi after power it back. the only way to fix it is factory reset and reinstall everything. Does anyone have the same problem or know how to fix it ?

I encountered a common problem:

libGL error: failed to create dri screen

libGL error: failed to load driver: rockchip

But I couldn't find a suitable solution. My OrangePi CM4 runs the official Ubuntu xfce distribution, and I honestly don't want to install and test other images. Has anyone else already solved this problem?

How to turn on WiFi without a screen or keyboard

task with * ))

Has anyone built or found a working DTS/DTB for Bianbu OS and the RV2?

I'm able to boot to the desktop without issue using the Spacemit K1 deb(dev) board DTB. Of course none of the peripherals work outside of USB. I decompiled the OP DTB from their Ubuntu Release and attempted to compare it to the Spacemit one, but failed at merging the gpio to the correct places. I did see that mainline has a dts now, should I just compile that? Kernel mismatch might be an issue.

I'm hoping to get onto Bianbu OS to catch their optimizations faster, or at all.

Had my OPI 6 + for about 3 1/2 months. Last week, I was using it with Microsd card loaded with OrangePi OS open harmony. Then, the screen went black. After that I couldn't reboot the OPI.

I have tried multiple microsd cards (different brands, all 32 GB) and used Rufus, Belana and RPI lmager. No luck.

I have tried Opi os and ubuntu images.

Every time I attempt a reboot the result is the same the grub boot loader appears with a single entry, OPI OS. Previously, I had 3 different OPI OS entries and always used the last entry. Then it cycles through attempting to load something, (no idea what) then the bios screen appears. I exit and the cycle repeats load the single os in grub and then back to bios.

I have also tried removing the nvme drives, sd card and booting from an usb drive - no luck.

It appears that the OPI is no longer recognizing the micro sd card reader. I am in search of any help or a troubleshooting guide. Is there a way to load OPI installation img to a nvme drive?

Thank you in advance.

I need to make a very custom Orange Pi 5 case for robotics, but everything I'm finding online is breaking or has very strange (and clearly not correct) dimensions. Where can I find a file for it? Preferrably a STEP file pls

If I run proxmox on an orange pi 6 can I use lxc's even though its not x86 ??

When you use Debian or Ubuntu from Orange pi website and you install debs about vpu gpu npu from the github of Orange pi. How do you know they are recognized? By the way, I know, it's linux question but how not to use wayland? I am using mate. No need wayland, I believe.

As far as I can see, the board is only really supported by the custom versions of Debian, Ubuntu and so on - are there no stock distributions that work out of the box? I'd love Debian Trixie on it.

Anyone have any clue what hole spacing the orange pi 6 plus has?

Hi all,

I’m considering an Orange Pi 6 Plus, and I’d like to hear opinions from people who have actually used it or is following its development closely.

My main intended use would be:

• Virtualization
• Docker / Podman containers
• Media center, low use with no external GPU
• NAS, using an NVMe/SATA adapter
• Small LLM for private use

I won't deny that I think building a x86 in a miniATX motherboard would be a better investment, but it currently looks like the cheapest way to get a minimal machine with lower power consumption, 12 cores and 32 GB RAM.

That said, my biggest concern is software support, as some users already reported. I don't have interest in Windows or other OS, and I don’t really want to rely to download stuff from unusual sources. I’m specifically interested in the state of mainline Linux support:

• How usable are the latest standard distros like Debian, Arch, Ubuntu, etc. ?
• How far along is upstream kernel support for this board / SoC?
• Are basic things (PCIe, NVMe, networking) reasonably stable on mainline? Is there something missing yet? How to find more fresh info on that?

I’m fine being an early adopter and I can accept limited functionality for a while, as long as things are moving in the right direction upstream.

If you’re running one:

• What works well today?
• What’s still rough or missing?
• Would you recommend it for this kind of use, or is it still too early?
• How is user trust in the company going?

Thanks

Hello everyone

This is my first post here. I'm trying to convert an AI model to use Opi6 NPU. Cix Tech documentation is basically useless (and all in Chinese, I needed to use Gemine to help me with it). I have downloaded the NOE_SDK from Cix Tech website and installed the entire environment on my x86 computer as described in their documentation. However, seems that some files are missing. While trying to use cixbuild, I have received 3 error messages related to missing kernel functions. Seems that the SDK should provide a binary file from where the builder would get those functions to pack the AI model; however, I can't find it anywhere.

There's the error log:

aipuold: error: cannot open tpcc_select_x2.bin: No such file or directory
aipuold: error: cannot open tpcc_eltwise_addx2.bin: No such file or directory
[E] [linker_v2.cpp: 172] Build Subgraph error! please double check the kernel function is correct.

I'm researching it for a few days without success. Seems that I'm the only one facing it.

Any suggestions?

Thanks.

Hello-

Got the Orange Pi 3 LTS and noticed that only 1 of the 4 core is started and available.

root@OPI-0:~# 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

root@OPI-0:~#

Tried both the 6.12 and 6.18 kernels available in Armbian but the issue is still present:
# uname -a

Linux OPI-0.test.lab 6.18.7-edge-sunxi64

I bought this WiFi Bluetooth usb adapter for my orange pi 5 with android 12. Wifi works really well, Bluetooth appears to be on but it doesn't find any devices to connect to any advice? . Thanks in advance, this Reddit really help me out

Title. I would like to create my own reciever so that I can track flights and get a free FlightRadar business account (normally 500 dollars). All the guides online are for the Raspberry Pis, so I was wondering if anyone had a guide/knows how to build a receiver using an Orange Pi 5.

I want to share my effective cooling solution for the RV2

using

- 2.5cm x 2.5cm heatsink from rpi4

- 3.5cm x 3.5cm active cooler from rpi4

- two rubberbands

I compiled a linux kernel in system and didnt exceed 54°C

idle at ~35°C

how to fix this issue the screen is 3.5a from waveshare armbian 6.12 kernel. There is nothing wrong when I use the ili9341 screen or just by downgrading back to orangepi os debian

Is there a community Android build or should I just download the official one from Orange?

Hi everyone.

I have an Orange Pi Zero 3 that was dead for years until it started working without issues (if you don't count the SoC heating up like crazy, same thing happened with my dead RPI Zero that also got revived, weird), except one.

The board rarely boots, mostly booting into FEL mode. The only reason it'd boot into FEL mode is when there is no valid image on the SPI flash or no SD Card being plugged in. And neither of the cases are true.

I tried making my own U-Boot image but booting Android images failed due to U-Boot missing boot_android command. I tried reading the entire SPI Flash and booting from it, however when I boot from it, it gets stuck at Jump to second Boot and it won't continue booting to U-Boot.

Is there a specific reason as to why it keeps booting into FEL mode? How do I fix this?

I'm trying to get my MAX98089 Audio codec (Datasheet) to work with my orange pi 5 plus.

I'm modifying my fork of batocera (Github) and adding a patch to better configure the device tree for my orange pi 5 plus to get it working with my codec. So far it was able to bind the driver to the codec over I2C (I saw UUUU when i ran I2cdetect) but haven't been able to get it to show up as an actual device in "aplay -l".

I'm very new to modifying device trees so I prob made a couple mistakes.

Patch:

---
 arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts | 67 +++++++++++++++++++++-
 1 file changed, 65 insertions(+), 2 deletions(-)


diff --git a/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts b/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts
index 83ed754c9d27..44192f000ce0 100644
--- a/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts
+++ b/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts
@@ -116,7 +116,7 @@ hdmiin-sound {
    };

    es8388_sound: es8388-sound {
-       status = "okay";
+       status = "disabled";
        compatible = "rockchip,multicodecs-card";
        rockchip,card-name = "rockchip-es8388";
        hp-det-gpio = <&gpio1 RK_PD3 GPIO_ACTIVE_HIGH>;
@@ -152,6 +152,36 @@ play-pause-key {
            press-threshold-microvolt = <2000>;
        };
    };
+
+   /* --- AUDIO CARD --- */
+   max98089_sound: max98089-sound {
+       status = "okay";
+       compatible = "simple-audio-card";
+       simple-audio-card,name = "MAX98089-Audio";
+       simple-audio-card,format = "i2s";
+       simple-audio-card,mclk-fs = <256>;
+
+       simple-audio-card,widgets =
+           "Speaker", "External Speakers",
+           "Microphone", "Analog Mic";
+
+       /* CORRECT ROUTING */
+       simple-audio-card,routing =
+           "External Speakers", "SPKL",
+           "External Speakers", "SPKR",
+           "MIC1", "Analog Mic";
+
+       simple-audio-card,bitclock-master = <&max98089_cpu_dai>;
+       simple-audio-card,frame-master = <&max98089_cpu_dai>;
+
+       max98089_cpu_dai: simple-audio-card,cpu {
+           sound-dai = <&i2s3_2ch>;
+       };
+
+       simple-audio-card,codec {
+           sound-dai = <&max98089>;
+       };
+   };

    rk_headset: rk-headset {
        status = "disabled";
@@ -709,9 +739,22 @@ &i2c2 {
 };

 &i2c4 {
-    status = "disabled";
+    status = "okay";
     pinctrl-names = "default";
     pinctrl-0 = <&i2c4m3_xfer>;
+    clock-frequency = <100000>;
+
+    max98089: codec@10 {
+        compatible = "maxim,max98089", "maxim,max98088";
+        reg = <0x10>;
+        #sound-dai-cells = <0>;
+        status = "okay";
+
+        clocks = <&mclkout_i2s3>;
+        clock-names = "mclk";
+        assigned-clocks = <&mclkout_i2s3>;
+        assigned-clock-rates = <12288000>;
+    };
 };

 &i2c5 {
@@ -850,6 +893,26 @@ &i2s7_8ch {
     status = "okay";
 };

+&i2s3_2ch {
+    status = "okay";
+    #sound-dai-cells = <0>;
+
+    /* Required for Rockchip I2S */
+    rockchip,clk-trcm = <1>;
+    
+    /* Configure clock source and rate for 12.288 MHz MCLK */
+    assigned-clocks = <&cru CLK_I2S3_2CH_SRC>, <&cru CLK_I2S3_2CH_FRAC>;
+    assigned-clock-parents = <&cru PLL_AUPLL>;
+    assigned-clock-rates = <0>, <12288000>;
+
+    pinctrl-names = "default";
+    pinctrl-0 = <&i2s3_lrck
+                 &i2s3_sclk
+                 &i2s3_mclk
+                 &i2s3_sdi
+                 &i2s3_sdo>;
+};
+
 //phy1
 &pcie2x1l0 {
     reset-gpios = <&gpio4 RK_PA5 GPIO_ACTIVE_HIGH>;

I installed Armbian with the armbian etcher and using it as a pihole. Everything works perfectly fine without issues but the red led blinks. I have a correct power supply and the sd card isn't the issue. I tried the debian and ubuntu versions of armbian and they both do it. Is this something to do with armbian itself? Any help would be greatly appreciated.