All Activity

Thank you very much. Will attempt to erase the SPI flash memory.

https://docs.armbian.com/Process_Contribute/#adding-a-new-board

@sven-ola Have you tried booting from a microSD card? I downloaded Armbian-unofficial_26.02.0-trunk_Orangepirv2_trixie_current_6.18.18_gnome_desktop.img and flashed it to my microSD card, but it won't boot. log: sys: 0x200 try sd... bm:3 j... U-Boot SPL 2022.10_armbian-2022.10-Sd61c-P155c-H452d-V4161-B61c5-R448a (Mar 17 2026 - 03:52:17 +0000) [ 0.381] DDR type LPDDR4X [ 0.383] set ddr tx odt to 80ohm! [ 0.393] lpddr silicon init consume 11ms [ 0.394] Change DDR data rate to 2400MT/s [ 0.633] Boot from fit configuration x1_orangepi-rv2 [ 0.635] ## Checking hash(es) for config conf_18 ... OK [ 0.641] ## Checking hash(es) for Image uboot ... crc32+ OK [ 0.652] ## Checking hash(es) for Image fdt_18 ... crc32+ OK [ 0.674] ## Checking hash(es) for config config_1 ... OK [ 0.677] ## Checking hash(es) for Image opensbi ... crc32+ OK [ 0.725] U-Boot 2022.10_armbian-2022.10-Sd61c-P155c-H452d-V4161-B61c5-R448a (Mar 17 2026 - 03:52:17 +0000) [ 0.732] CPU: rv64imafdcv [ 0.734] Model: ky x1 orangepi-rv2 board [ 0.738] DRAM: 2 GiB [ 0.830] Core: 414 devices, 29 uclasses, devicetree: board [ 0.843] WDT: Started PMIC_WDT with servicing (60s timeout) [ 0.848] WDT: Started watchdog@D4080000 with servicing (60s timeout) [ 0.857] MMC: [ 0.956] *** Warning - bad CRC, using default environment [ 0.961] initialize_console_log_buffer [ 0.962] Have allocated memory for console log buffer [ 0.967] In: serial [ 0.969] Out: serial [ 0.971] Err: serial [ 1.116] k1x_qspi spi@d420c000: qspi iobase:0x0x00000000d420c000, ahb_addr:0x0x00000000b8000000, max_hz:26500000Hz [ 1.124] k1x_qspi spi@d420c000: rx buf size:128, tx buf size:256, ahb buf size=512 [ 1.131] k1x_qspi spi@d420c000: AHB read enabled [ 1.136] k1x_qspi spi@d420c000: bus clock: 26500000Hz, PMUap reg[0xd4282860]:0x0000075b [ 1.143] k1x_qspi spi@d420c000: AHB buf size: 512 [ 1.148] SF: Detected XM25QU128C with page size 256 Bytes, erase size 64 KiB, total 16 MiB List of MTD devices: [ 1.159] * nor0 [ 1.160] - device: flash@0 [ 1.163] - parent: spi@d420c000 [ 1.166] - driver: jedec_spi_nor [ 1.170] - path: /soc/spi@d420c000/flash@0 [ 1.173] - type: NOR flash [ 1.176] - block size: 0x10000 bytes [ 1.180] - min I/O: 0x1 bytes [ 1.183] - 0x000000000000-0x000001000000 : "nor0" [ 1.188] - 0x000000000000-0x000000010000 : "bootinfo" [ 1.193] - 0x000000010000-0x000000020000 : "private" [ 1.198] - 0x000000020000-0x000000060000 : "fsbl" [ 1.203] - 0x000000060000-0x000000070000 : "env" [ 1.208] - 0x000000070000-0x0000000a0000 : "opensbi" [ 1.213] - 0x0000000a0000-0x000001000000 : "uboot" [ 1.219] Failed to get fastboot key config: -19 [ 1.222] Failed to probe HUSB239: -19 [ 1.227] RGMII interface [ 1.228] eth0: ethernet@cac80000 [ 1.231] MAC mapping file path not set in environment [ 1.236] K1X: :_load_env_from_blk [ 1.247] Can't set block device [ 1.248] Net: eth0: ethernet@cac80000 [ 1.254] Hit any key to stop autoboot: 0 Loading K1-X Environment ... [ 2.260] [ 2.261] Running NVMe Scan ... [ 2.272] pcie_dw_k1x pcie@ca400000: has no power-on-status flag, use default. [ 2.277] Now init Rterm... [ 2.279] pcie prot id = 1, porta_init_done = 0 [ 2.283] Now waiting portA resister tuning done... [ 2.288] porta redonly_reg2: 00005d37 [ 2.292] pcie_rcal = 0x00005d37 [ 2.295] pcie port id = 1, lane num = 2 [ 2.298] Now int init_puphy... [ 2.301] waiting pll lock... [ 2.304] Now finish init_puphy.... [ 2.307] pcie_dw_k1x pcie@ca400000: Unable to get phy0 [ 2.312] pcie_dw_k1x pcie@ca400000: Unable to get phy1 [ 2.317] pcie_dw_k1x pcie@ca400000: PCIe interface power on, set gpio 116 to 1 [ 3.426] PCIE-0: Link down [ 3.438] pcie_dw_k1x pcie@ca800000: has no power on gpio. [ 3.441] pcie_dw_k1x pcie@ca800000: has no power-on-status flag, use default. [ 3.448] Now init Rterm... [ 3.450] pcie prot id = 2, porta_init_done = 0 [ 3.455] Now waiting portA resister tuning done... [ 3.459] porta redonly_reg2: 00005d37 [ 3.463] pcie_rcal = 0x00005d37 [ 3.466] pcie port id = 2, lane num = 2 [ 3.470] Now int init_puphy... [ 3.472] waiting pll lock... [ 3.475] Now finish init_puphy.... [ 3.479] pcie_dw_k1x pcie@ca800000: Unable to get phy0 [ 3.484] pcie_dw_k1x pcie@ca800000: Unable to get phy1 [ 4.590] PCIE-1: Link down [ 4.642] pcie_dw_k1x pcie@ca400000: has no power-on-status flag, use default. [ 4.646] Now init Rterm... [ 4.648] pcie prot id = 1, porta_init_done = 0 [ 4.653] Now waiting portA resister tuning done... [ 4.657] porta redonly_reg2: 00005d37 [ 4.661] pcie_rcal = 0x00005d37 [ 4.664] pcie port id = 1, lane num = 2 [ 4.668] Now int init_puphy... [ 4.671] waiting pll lock... [ 4.673] Now finish init_puphy.... [ 4.677] pcie_dw_k1x pcie@ca400000: Unable to get phy0 [ 4.682] pcie_dw_k1x pcie@ca400000: Unable to get phy1 [ 4.687] pcie_dw_k1x pcie@ca400000: PCIe interface power on, set gpio 116 to 1 [ 5.795] PCIE-0: Link down [ 5.807] pcie_dw_k1x pcie@ca800000: has no power on gpio. [ 5.810] pcie_dw_k1x pcie@ca800000: has no power-on-status flag, use default. [ 5.817] Now init Rterm... [ 5.819] pcie prot id = 2, porta_init_done = 0 [ 5.824] Now waiting portA resister tuning done... [ 5.828] porta redonly_reg2: 00005d37 [ 5.832] pcie_rcal = 0x00005d37 [ 5.835] pcie port id = 2, lane num = 2 [ 5.839] Now int init_puphy... [ 5.841] waiting pll lock... [ 5.844] Now finish init_puphy.... [ 5.848] pcie_dw_k1x pcie@ca800000: Unable to get phy0 [ 5.853] pcie_dw_k1x pcie@ca800000: Unable to get phy1 [ 6.959] PCIE-1: Link down [ 6.963] no nvme partition table available [ 6.964] Couldn't find partition nvme 0:1 [ 6.968] Couldn't find partition nvme 0:1 [ 6.972] Couldn't find partition nvme 0:1 [ 6.976] Couldn't find partition nvme 0:1 [ 6.980] Couldn't find partition nvme 0:1 =>

Heres what I am seeing on my screen https://drive.google.com/file/d/1SSNnvOy-BjxAzklcAoApjS2zz1HnMn-v/view?usp=sharing Heres me messing with the headphon jack https://drive.google.com/file/d/1Z2Guva-FWYv2mu3VCPujXPoc7r_iqpB6/view?usp=sharing

Sorry for the late reply I got caught up with my new job and forgot my password for my previous account. eselarm you are probably not wrong but as I have continued to use armbian it seems more like armbian can't differentiate between the headphone jack and the internal speakers. It's like they are one and the same this didn't happen with mint or antix although it was still very broken on antix. [Should I move this part to a separate topic] Unrelated to the headphone jack but I also found that when my Chromebook goes to sleep or when I close the lid armbian will just unmount itself, have a blinking _ on the upper left of the screen or a terminal I can't get out of so l and I have to reflash my micro sd card as a temporary fix. also the minimal build always fails to install a new desktop environment. But everytime I reflash the latest build of Gnome it runs a bit better each time, which is great.

I ran into what appears to be the same issue (see my log). I have added the suggested qemu-user-static package, which forced removal of another qemu- family package I had previously installed to work around problems with binfmt. Not only did it compile correctly, it also ran so much faster, as you can see in the number of log lines for this build! Thank you for the assistance and getting me on the right track with the right package selection! Best Regards, Lobosito

@tin harden A7A mainline is still a WIP.

@Thur_Wander For debugging purposes, UART is highly recommended. Use balena Etcher to write the compiled image to your SD card.

@Nick A One last question, if i do this will i still have to use UART and flash the firmware? imma guess it's a yes but i guess it's still worth asking.

@Thur_Wander Here are the steps to create a secure boot image. This example is using the tanix-tx6s-axp313 defconfig. You probably want one of the X96q defconfig's.

@Nick A could you explain this a bit to me? i'm actually quite new to this and i just got this TV box the only thing i managed to do was installing a software version from a guy who debloated and checked it for spyware. also when i use the reset button in the av jack it just ignores everything and recovers from an internal image or something.

@Octavio Cuatrochio@Thur_Wander Maybe it has secure boot enabled.

Hi, I am here in 2026 with the Amrbian 26.2.1, I've tried the proposed fix from @c0rnelius but it's not working on my OS version. If anyone has any updated solution that'd be amazing. Thank you

I have this exact same model and the device appears to be heavily locked down... Did this method worK? i'm trying to get a linux ARM distribution running but i can't flash a custom ROM

The most current download images for Helios64 are now all provided with linux 6.18.xx. I downloaded a minimal image and checked the dtb: it would not appear to contain the opp-microvolt patch that made Helios64 finally stable. So for the ones who have stability issues again on Helios64, I attached the patched dtb compiled for linux 6.18.xx using the exact same opp-microvolt values as in the previous dtb versions I compiled for linux 6.6 and 6.12. The current linux deb files can be downloaded from beta.armbian.com, the linux 6.18.18 deb files I used can be downloaded from here (to be installed with 'dpkg -i linux*'). In order to install the dtb, simply unzip it, copy it into the proper location, update initramfs and reboot: # install the dtb with the opp-microvolt patch: unzip rk3399-kobol-helios64.dtb-6.18.18-opp.zip cp rk3399-kobol-helios64.dtb-6.18.18-opp /boot/dtb/rockchip/rk3399-kobol-helios64.dtb update-initramfs -u reboot rk3399-kobol-helios64.dtb-6.18.18-opp.zip

Another attempt, again check https://testing.armbian.de/r4s/?C=M&O=D for most recent debs. This time adding an artificial bus scan delay into the r4s dts. Another poke in the dark but perhaps...

See inline comments. Dirty SPI may cause this but without logs from serial console this is just a guess

Is there mainline support for a7a now

I will try downgrading u-boot next once I find the older package somewhere. Kernel does not seem to be the cause given that it has been working fine with both my own build 6.6.122 and 6.6.128 before and rolling back not helping. New device is something I had on my mind for a while. But given the RAM and SSD prices these days, I do not really want to overspend. Not to mention that the SBC landscape has not been that great lately when it comes to compact NAS offerings. HC4 is five years old at this point. Many even recommend N100 but this is a whole different size category.

I would not be surprised if there has always been a HW initialization issue. It is just that now with newer Linux (whole systemd stuff etc) you hit this problem. I always liked this HC1, but it is not even on Odroid WiKi anymore. You might need to focus on version/build of U-Boot in combination with kernel and DTB. I have some examples (Rockchip based SBC's) were it is make-or-break, e.g. if I just take latest U-Boot whole system / use-case is useless / gone. So I need to stick to legacy U-Boot or just buy other HW/platform.

This could be, but something has changed and is now triggering this behaviour. Warm reboots have been working fine for years.

Is the much trouble USB-SATA chip, I have it as 'cable', but unused as it at least fails with RPI4 when SSD. It looks like a sequencing/timing issue. You can treat it like external maybe and/or reset the USB device node. That usually works for various USB connected HW that fails at boot but when Linux/platform fully up and running, a reset then somehow avoids timing issues.

Good day, I have recently purchased an Orange Pi 5 Pro and want to use Armbian on it. Armbian (Debian 13 Trixie) does not boot and gives a initramfs error. I have read on erasing the SPI flash memory, but have a few questions. Will erasing the SPI flash memory affect the booting of other operating systems. Is it safe to erase the SPI flash memory? What is the issue around Armbian not booting because of the SPI flash memory? How exactly would I safely erase the SPI flash memory? Thank You

Other packages upgraded by unattended-upgrades: Start-Date: 2026-03-15 10:51:39 Commandline: apt upgrade Requested-By: julas (1000) Upgrade: linux-base:armhf (4.12~bpo12+1, 4.12.1~bpo12+1) End-Date: 2026-03-15 10:51:51 Start-Date: 2026-03-16 06:20:00 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-image-current-odroidxu4:armhf (25.11.2.3, 26.2.1) End-Date: 2026-03-16 06:21:56 Start-Date: 2026-03-16 06:22:47 Commandline: /usr/bin/unattended-upgrade Upgrade: base-files:armhf (25.11.2-12.4+deb12u12-bookworm, 26.2.1-12.4+deb12u13-bookworm), armbian-bsp-cli-odroidxu4-current:armhf (25.11.2, 26.2.1) End-Date: 2026-03-16 06:23:48 Start-Date: 2026-03-16 06:24:54 Commandline: /usr/bin/unattended-upgrade Upgrade: armbian-firmware:armhf (25.11.2, 26.2.1) End-Date: 2026-03-16 06:26:03 Start-Date: 2026-03-16 06:26:48 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-dtb-current-odroidxu4:armhf (25.11.2.3, 26.2.1) End-Date: 2026-03-16 06:26:52 Start-Date: 2026-03-16 06:27:35 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-u-boot-odroidxu4-current:armhf (25.11.2, 26.2.1) End-Date: 2026-03-16 06:27:37 Unfortunately, the previous versions seem to be gone from the repos. Is there any way of getting these back?

Rolling "back" linux-{dtb,image}-current to my self-built 6.6.128 did not help.