All Activity

If you don't need GPIOs, don't take SBCs - they are too expensive, without a case and power supply. For the same money, you can buy a mini X86 PC such as razen5 4600 and you will have no problems with support. If you need an ARM, then buy an H96 Max V56 from two TV boxes. The time of SBCs has come to an end - they are no longer so popular and are mainly needed by developers. Leave these SBCs to the developers!

I was looking for a solution to this for a long time before seeing John's post and figuring it out. Here's a more explicit explanation to hopefully help make this info easier to find. This was tested and does work on both the Orange Pi 5 16GB, and the Orange Pi Zero 3 4GB. I haven't run into this issue on my x86 nodes as it doesn't appear zram exists on them at all on a fresh install. If you go to the /etc/default directory, there should be a file called <distro>-ramlog. If you're on armbian it will be armbian-ramlog, for me on Debian it's called orangepi-ramlog. In this file there will be a line reading "SIZE=50M" Simply edit this line to whatever value you'd like, and then reboot the device. If rebooting the system will cause serious problems, you can use the following command on armbian: service armbian-zram-config restart Again, I'm using the official Orange Pi Debian image, so for me, the command would instead be as follows: service orangepi-zram-config restart Don't panic if you notice that this command results in the creation of a zram2 and zram3, as these duplicates will automatically remove themselves the next time you reboot the machine

I'd say start with the device tree. Maybe it is just not enabled? KDE 6 DE was introduce when it still was beta and I assume this never changed. Feel free to send a PR to make it stable.

Hi @Zaf9670, Are you sure you did the setenv fdt_addr_r 41000000 U-Boot claims DT is still loaded/applied to the original load address: Working FDT set to 41900000 Can you share your armbianEnv.txt and boot.cmd? I'll have a look at the defailt bootscript in the meantime, perhaps some parts of the bootscript is using fdt_addr_r and other parts might still use loadaddr or scriptaddr... Thx, Gr,

Looks like it is still overlapping. => run bootcmd switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 5475 bytes read in 2 ms (2.6 MiB/s) ## Executing script at 41900000 U-boot loaded from SD 176 bytes read in 2 ms (85.9 KiB/s) Load fdt: /boot/dtb/sun8i-s3-pinecube.dtb 12286995 bytes read in 509 ms (23 MiB/s) 11013984 bytes read in 456 ms (23 MiB/s) Found mainline kernel configuration 19691 bytes read in 5 ms (3.8 MiB/s) Working FDT set to 41900000 Kernel image @ 0x41080000 [ 0x000000 - 0xa80f60 ] ## Loading init Ramdisk from Legacy Image at 42080000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 12286931 Bytes = 11.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 41900000 Booting using the fdt blob at 0x41900000 ERROR: FDT image overlaps OS image (OS=0x41080000..0x41b00f60) SCRIPT FAILED: continuing... BootOrder not defined EFI boot manager: Cannot load any image

Hi @Zaf9670, Can you try to reset the U-Boot monitor, press any key to stop the autobooting, then enter the following on the commandline: setenv fdt_addr_r 41000000 setenv kernel_addr_r 41080000 setenv ramdisk_addr_r 42080000 These load addresses are based on the sizes of the DT (438272 bytes) and the kernel image (11013984 bytes). Then to kick off the boot: run bootcmd Do share the results please. Groetjes, p.s. That device tree is huge! 428 KiB??

@laibsch since I cannot boot that doesn't seem to be a command in u-boot I can run. Reformatted the card with latest Bookworm Armbian_community_25.5.0-trunk.444_Pinecube_bookworm_current_6.12.23_minimal.img.gz @djurnyBoot and Outputs requested at the end. Let me know if you need anything else. Thanks! U-Boot 2024.01-armbian-2024.01-S866c-P7738-Ha5c2-V1f00-Bb703-R448a (Mar 16 2025 - 04:03:33 +0000) Allwinner Technology CPU: Allwinner V3s (SUN8I 1681) Model: PineCube IP Camera DRAM: 128 MiB Core: 47 devices, 20 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@1c28800 Out: serial@1c28800 Err: serial@1c28800 Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 5475 bytes read in 2 ms (2.6 MiB/s) ## Executing script at 41900000 U-boot loaded from SD 176 bytes read in 2 ms (85.9 KiB/s) Load fdt: /boot/dtb/sun8i-s3-pinecube.dtb 12286995 bytes read in 509 ms (23 MiB/s) 11013984 bytes read in 457 ms (23 MiB/s) Found mainline kernel configuration 19691 bytes read in 4 ms (4.7 MiB/s) Working FDT set to 41900000 Kernel image @ 0x41000000 [ 0x000000 - 0xa80f60 ] ## Loading init Ramdisk from Legacy Image at 41c00000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 12286931 Bytes = 11.7 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 41900000 Booting using the fdt blob at 0x41900000 ERROR: FDT image overlaps OS image (OS=0x41000000..0x41a80f60) SCRIPT FAILED: continuing... Card did not respond to voltage select! : -110 No EFI system partition No EFI system partition Failed to persist EFI variables BootOrder not defined EFI boot manager: Cannot load any image => echo $fdt_addr_r 0x41900000 => echo $kernel_addr_r 0x41000000 => echo $kernel_addr_r 0x41000000 => echo $kernel_addr_r 0x41000000 => echo $fdt_addr_r 0x41900000 => echo $kernel_addr_r 0x41000000 => echo $ramdisk_addr_r 0x41C00000 => setexpr abc 1 + 1 => echo "abc=x${abc}x" abc=x2x => fdt header magic: 0xd00dfeed totalsize: 0x6b000 (438272) off_dt_struct: 0x38 off_dt_strings: 0x457c off_mem_rsvmap: 0x28 version: 17 last_comp_version: 16 boot_cpuid_phys: 0x0 size_dt_strings: 0x76f size_dt_struct: 0x4544 number mem_rsv: 0x0 => fdt header get def totalsize => echo "def=x${def}x" def=x6b000x

Yes, maybe. There are a way to make a similar patch for kernel instread of u-boot? In Android, the boot logo show some parameters like DRAM_VCC, DRAM_CLK, Chip id, Param1, param2 and tpr113 , it helps? Tanks for your time. [626]HELLO! SBOOT is starting! [629]sboot commit : 4b34f2890a [632]set pll start [634]periph0 has been enabled [637]set pll end [641]unknow PMU [642]unknow PMU [646]PMU: AXP1530 [650]dram return write ok [653]board init ok [655]enable_jtag [656]DRAM BOOT DRIVE INFO: V0.651 [660]the chip id is 0x2000 [662]chip id check OK [684]DRAM_VCC set to 1500 mv [687]DRAM CLK =648 MHZ [689]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [697]Actual DRAM SIZE =4096 M [700]DRAM SIZE =4096 MBytes, para1 = 310b, para2 = 10000000, dram_tpr13 = 6041 [709]DRAM simple test OK. [711]rtc standby flag is 0x0, super standby flag is 0x0 [717]dram size =4096 [719]Use rtc to store dram tuning para [723][mmc]: mmc driver ver 2021-10-12 13:56 [727][mmc]: b mmc 2 bias 4 [735][mmc]: Wrong media type 0x0, but host sdc2, try mmc first [741][mmc]: ***Try MMC card 2*** [770][mmc]: RMCA OK! [773][mmc]: MMC 5.1 [775][mmc]: HSSDR52/SDR25 8 bit [778][mmc]: 50000000 Hz [780][mmc]: 119280 MB [782][mmc]: ***SD/MMC 2 init OK!!!*** [858]read toc1 from emmc 32800 sector [862]OLD version: 0.0 [864]NEW version: 0.0 [870]don't have rotpk, skip check [941]load rotpk hash [1204]load vbmeta_a-key hash [1207]load vbmeta_a hash [1214]load vbmeta_b-key hash [1217]load vbmeta_b hash [1220]monitor entry=0x48000000 [1223]uboot entry=0x4a000000 [1226]optee entry=0x48600000 [1229]opensbi entry=0x0 [1231]no need rotpk flag [1234]tunning data addr:0x4a0003e8 [1239]run out of boot0 NOTICE: BL3-1: v1.0(debug):54937d5 NOTICE: BL3-1: Built : 17:44:59, 2021-12-13 NOTICE: BL3-1 commit: 8 NOTICE: cpuidle init version V2.0 NOTICE: secure os exist MESSAGE: [0x0] TEE-CORE: OP-TEE version: 5c40397e #1 Tue Feb 2 07:45:37 UTC 2021 arm NOTICE: BL3-1: Preparing for EL3 exit to normal world NOTICE: BL3-1: Next image address = 0x4a000000 NOTICE: BL3-1: Next image spsr = 0x1d3 U-Boot 2018.07-gb99798b4 (Apr 04 2023 - 13:23:26 +0000) Allwinner Technology [01.302]CPU: Allwinner Family [01.305]Model: sun50iw9 I2C: ready [01.313]DRAM: 4 GiB [01.322]Relocation Offset is: 70ecd000 [01.358]secure enable bit: 1 [01.360]smc_tee_inform_fdt failed with: ffffffff [01.365]pmu_axp152_probe pmic_bus_read fail [01.369]PMU: AXP1530 FDT ERROR:fdt_get_regulator_name:get property handle twi-supply error:FDT_ERR_INTERNAL [01.383]CPU=1416 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=400Mhz

@rafaeldavid can you show me the output when you type in the command "fdisk -l"

I tried generating some builds, the only one that works (initially) is Armbian-unofficial_25.05.0-trunk_X96q_jammy_current_6.12.23 (versions with or without desktop). I don't understand much, but I believe that the emmc memory is detected. When I start it, it boots, asks the initial questions (root password, create my user, region settings, etc.). After that, I use the armbian-install command and enter the installer, select to install, ask me to confirm (data will be deleted), ask how I want to format the partition and then get stuck. PS: To mount the image I used this command: ./compile.sh build BOARD=x96q BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=no EXPERT=yes KERNEL_CONFIGURE=no RELEASE=jammy (I tried to use the version BOARD=x96q-mate, but don't work! As you can see in the video, the image shakes for a while, then stops. I think that's when the device freezes. VID-20250509-WA0007.mp4

@Rodrigo Campos The patch is only for uboot and it’s already in my newer builds. I guess there’s an issue with the kernel.

Hi there, Now two pull requests are awaiting review: - https://github.com/armbian/build/pull/8166#issuecomment-2867147049 Update the boot.scr script to calculate load addresses in case `setexpr` is available on the U-Boot monitor. - https://github.com/armbian/build/pull/8170#issuecomment-2867915659 Enable the `setexpr` command on the U-Boot monitor, to unlock load address calculation in combination with the boot.scr update. Both are now tested OK using a built armbian 'minimal' image based on Bookworm. Groetjes,

Hi all, I was quickly able to get the 3.5inch RPi LCD (B) working with an Orange Pi Zero 2W, but the colors are all wrong, it seems that it wants BGR. Any hints where to change color order? I could not find anything for the DTS. Using this driver with following DTS:

Hi catotinha, Can you please share which image you successfully used, and where you downloaded it from, please? Thanks!!

Hi, I recently got my hands on a used unit of those, quite faster than my old SBC! Only issue I currently have is that I can't seem to get audio output on the 3.5mm jack. (Well the other issue is unrelated .. ) Anyone have an idea on what I should be hunting? I did the obvious cable, etc.. checks. There's always the possibility that it's damaged, hell if I know. Armbian 25.2.1 6.1 kernel KDE Neon (Why use a beta version btw? just wondering) Thanks! DW.

Yes, you already teach me how to make a patch to use secure boot and it works fine. Anyway, the ram patch didn't work. I build a new image now and it still shows only 2GB instead of 4GB. Maybe I miss a step to apply this patch?. The strange thing is that u-boot shows 4GB, than kernel shows 2GB in boot log. Even with a half of memory it works very well.

I have solved the issue of installing on a new system. sudo update-alternatives --config iptables Choose -legacy

Hi Pilinha and Werner. My problem was that I misidentified the board and thus installed the wrong software. https://forum.armbian.com/topic/51779-orange-pi-plus-2e-usb-ports-not-working/ Thanks for your help, I learn a few things here.

So here we are. Another problem we can confidently attribute to that thing between the chair and the keyboard. After trying a lot of weird stuff that made little sense and achieved no positive results whatsoever I started noticing and becoming annoyed at some strange details about ports, pictures and procedures piling up. There were always little things here and there not lining up perfectly with the articles, howtos, etc I was reading. After another wasted evening, burning out and angry, I decided to start reconciling facts by finding out if there were more Orange Pi Plus 2e models or revs, because mine almost matched up with the images, but not quite (and you probably already figured this one out, but I am a little denser than most). After not finding any indications that there were any alt models (and a good night's sleep to clear my mind) it finally dawned on me. I asked my brother about it and he confirmed that the model was indeed a +2e, he even sent me me the PDF receipt. From what I can piece from the episode, the hardware he got from the store is very similar and until some version, things worked fine for him even with the wrong version of the software, but at some point (when he was no longer using the board) compatibility broke. TL;DR I was trying to use Opi +2e software on a Opi +2 board. Everything is fine now. Thanks to the nice people who helped me here.

Great find.... this will be useful for me very soon

That fixed it, it's now detected on i2c3 (i2cdetect -y 3) Python also can interact with it root@orangepizero2w:~# i2cdetect -y 3 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- 27 -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- Thank you SteeMan❤️

I think this line is wrong. I don't believe that the overlay_prefix should be included here, try with overlays=i2c1-pi I seem to recall mention of a bug in armbian-config that was doing the wrong thing regarding overlay_prefix when selecting overlays.

Hello, I'm trying to connect an PCF8574 I2C adapter to my Orange Pi, but it doesn't show up in i2cdetect, only something at 0x30 on i2c0 and 0x36 on i2c1 that is labeled UU. I tried to connect it to arduino, and it found it on address 0x27 Connected on pins 3 and 5 root@orangepizero2w:~# sudo i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- root@orangepizero2w:~# sudo i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- root@orangepizero2w:~# ls -a /dev/i2c-* /dev/i2c-0 /dev/i2c-1 /dev/i2c-2 root@orangepizero2w:~# cat /boot/armbianEnv.txt verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun50i-h616 overlays=sun50i-h616-i2c1-pi rootdev=UUID=b9606c1d-3dea-4df8-940f-51cd0698eef4 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

OK .. now i must "cleanup" all voltage regulators

As a developer I always recomend you to go for https://www.banana-pi.org/ if you want do develop your own device drivers: H96 Max v56 since 2024+ came with alternative wifi and lan controllers, you will need to fix if you buy it. a middle point could be the YY3568