All Activity

Well, it seems that I have a very strange device, as I can boot armbian for devices using Allwinner H3, even tho the SoC shows It self as a RK322BA. I don't know what's happening with my device, and unfortunately, there's no much information about it, just some users trying random armbian builds from devices with the same soc, which works, but features like wi-fi doesn't, probably something that can be fixed making a dtb for this device, which I don't know how to unfortunately.

@Mateus Lima I am not very sure this Is a rockchip board.. i see h3q ...may be an allwinner h3 ?????? Can you check removing the heatsink ? Or check with USB ttl adapter ?

That's my device, I don't if showing it's board will be helpful.

It seems the Ethernet dirver is already in mainline, and oss wifi driver are available: https://github.com/lynxlikenation/aic8800

What is this method about? Hold the button while it is booting with the sdcard inserted? I also tried to boot using a usb drive flashed with multitool flashed, but it still boots into android. As for the bootloader, I'm booting it into bootloader mode, and it gets recognised, but "fastboot oem unlock" just prints three dots "..." and doesn't do nothing. In the guide there's a bootloader file I think, but it's not available anymore.

First of all, I would like to thank you for continuing to maintain this project. I use an RK3228 MXQ running raspotify (another great project) playing music. However, I can't equalize the sound? Is there a way to use a sound equalizer? I tried for ALSA and lost a few days in several things but nothing worked.

Do you try also toothpick (there is a recovery button behind headphone port) methode and SD-Card ? or USB boot , there are some box with lock bootloader

I'm trying to boot multitool, but my device is booting directly into android. I've flashed my sdcard using dd and balena, both works fine apparently, the box recognizes the sdcard (it shows on android file manager), but every time I reboot it, it only boots android... Does anyone have any clue of what should I do?

Those are images from BigTreeTech, not Armbian. Official Armbian images for CB1 are here: https://www.armbian.com/bigtreetech-cb1/ If you want to use vendor images, you should report your issue to BigTreeTech then.

https://www.cnx-software.com/2025/10/25/35-orange-pi-4-pro-an-allwinner-a733-edge-ai-sbc-with-up-to-16gb-lpddr5-wifi-6/ https://www.cnx-software.com/2025/07/07/allwinner-a527-t527-and-a733-datasheets-user-manuals-and-linux-sdk-released/ http://www.orangepi.org/html/hardWare/computerAndMicrocontrollers/details/Orange-Pi-4-Pro.html Another Allwinner board dropped figuring out the wifi chip is always hard, seem to be https://www.taobao.com/list/item/931793873067.htm https://pine64.sfo3.cdn.digitaloceanspaces.com/doc/datasheet/oz64/AIC8800DC Datasheet v1.0.pdf as usual, it is uncertain if drivers and firmware is after all available. Ethernet according to CNX seemed to be YT8531CA Ethernet seemed to be same as that in OrangePi Zero 3 https://www.cnx-software.com/2023/07/03/orange-pi-zero-3-allwinner-h618-sbc-ships-with-up-to-4gb-ram/ WiFi is 'more critical' these days, if it is closed sourced and no firmware, then it is good as just a door stop. Then that thare are other stuff the figure out especially the : - DRAM controller, - and various DRAM timing and configuration aspects - many other low level specific stuff to even have u-boot to boot it up to the linux prompt. - then the other devices e.g. uart etc. - then HDMI - then gpu acceleration (or at least display video, not playing media yet) - then media - and finally NPU, don't seemed documented yet - many more known or unknown unknowns, audio etc

Hi all, I’m trying to get KlipperScreen running directly on the framebuffer on a BigTreeTech CB1 that’s using an Allwinner H616B chip. It’s running Armbian Bookworm (kernel 6.6.66-vendor-sunxi64, Dec 2024 build) on a Manta M8P V2.0 board with a TFT35-SPI display that shows up as fb_st7796s. The goal is to have KlipperScreen render directly to /dev/fb0 without needing a desktop or HDMI. The framebuffer itself seems fine as the screen shows the BigTreeTech logo on boot, and I can write to it manually, so the driver appears to be working correctly. KlipperScreen installs fine, the Python environment and dependencies are all in place, but when I launch it, I always get “Gtk couldn’t be initialized.” If I try running it under Xorg, it throws “xf86OpenConsole: Switching VT failed,” which seems to mean the kernel isn’t allowing virtual terminal switching. I’ve tried both framebuffer and Xorg modes, set SDL_VIDEODRIVER=fbcon and FBDEV=/dev/fb0, and even forced it to use SDL directly, but GTK still won’t start. Everything else works normally, it just refuses to render the GUI. Here’s the kicker: this exact setup worked perfectly on Armbian V2.3.4. KlipperScreen ran out of the box with no special tweaks, so something clearly changed in V3.0 and later builds that broke framebuffer support or GTK initialization. It feels like either framebuffer rendering got dropped, VT switching was removed, or GTK was built without fbdev support. So my main questions are: was framebuffer (fbdev) support intentionally removed from newer Armbian builds for the CB1? Is VT switching disabled by design in the H616 kernel? And is there any known way to run GTK or SDL apps directly on /dev/fb0 under the current Bookworm build? If it’s just a matter of rebuilding GTK or enabling a missing kernel flag, I’m happy to do that I just need to know where the problem actually lies.

Here: https://fi.mirror.armbian.de/oldarchive/helios64/archive/ you can find older images.

I’ve sent the URL and details here, hoping they can take a look

https://paste.armbian.com/raw/hohumivife

I’ve spent way too much time on this, my back is killing me. I’d rather just buy a more common development board. My project didn’t require me to dig into all this u-boot and DTS stuff. So, fuck you KickPi. Here are all the DTS files I extracted from https://github.com/pyavitz/debian-image-builder and the official Linux SDK. Hopefully someone else can finish this job. dts.zip

Here is everything I have been able to piece together from the web. Maybe something in there would be helpful? https://github.com/pyavitz/binary/releases/download/060420/KICKPI.zip

Post a dmesg and sudo gpioinfo https://paste.armbian.com/

I recently noticed my ODroid XU4 was reporting weird temperature readings: cat /sys/class/thermal/thermal_zone0/temp -22000 Is this a software issue or maybe hardware failing? Also, I would like to upgrade, is there another board I could just transfer my EMMC to and be up and running? Thanks

@Jeeva Kandasamy correct

Looks like the same thing REV 1.1 uses. My guess would be the GPIO or PINCTRL may be different on the REV2. The problem is the schematic only shows 1.0 / 1.1 You could try shooting them an email in an attempt to obtain the v2 schematic? Without it, you would just be guessing.

Still no network. I checked the official SDK, it uses the following hardware: Wired network: Allwinner GMAC driver + external PHY; Wireless network: AIC8800 series WiFi module driver; Bluetooth: AIC8800 Bluetooth Low Energy driver; USB network: RTL8152 USB to Ethernet driver. Does this have any impact?

Nice.

The parameters I’m using were extracted from the official Linux SDK using GPT. At least the DRAM parameters are functional. Debian can boot and log in normally, but there’s no wired network or WiFi/Bluetooth. I’m currently investigating why this is happening.

I was just about to post a binary with something similar. So does the above work for you? I was gonna try this: CONFIG_DRAM_SUNXI_DX_ODT=0x03030303 CONFIG_DRAM_SUNXI_DX_DRI=0x0e0e0e0e CONFIG_DRAM_SUNXI_CA_DRI=0x1f12 CONFIG_DRAM_SUNXI_TPR0=0xc0001002 CONFIG_DRAM_SUNXI_TPR10=0x2f1107 CONFIG_DRAM_SUNXI_TPR11=0xddddcccc CONFIG_DRAM_SUNXI_TPR12=0xeddc7665 CONFIG_MACH_SUN50I_H616=y CONFIG_SUNXI_DRAM_H616_DDR3_1333=y CONFIG_DRAM_CLK=648

I used ur project https://github.com/pyavitz/debian-image-builder changed this file "patches\uboot\v2025.07\sun50i-h618\002-Add-board-KickPi-K2B.patch" +CONFIG_OF_UPSTREAM=y +CONFIG_ARM=y +CONFIG_ARCH_SUNXI=y +CONFIG_DEFAULT_DEVICE_TREE="allwinner/sun50i-h618-kickpi-k2b" +CONFIG_SPL=y +CONFIG_DRAM_SUNXI_DX_ODT=0x03030303 +CONFIG_DRAM_SUNXI_DX_DRI=0x0e0e0e0e +CONFIG_DRAM_SUNXI_CA_DRI=0x1f12 +CONFIG_DRAM_SUNXI_ODT_EN=0x0 +CONFIG_DRAM_SUNXI_TPR0=0xc0001002 +CONFIG_DRAM_SUNXI_TPR1=0x30fb +CONFIG_DRAM_SUNXI_TPR2=0x0000 +CONFIG_DRAM_SUNXI_TPR6=0x33808080 +CONFIG_DRAM_SUNXI_TPR10=0x2f1107 +CONFIG_DRAM_SUNXI_TPR11=0xddddcccc +CONFIG_DRAM_SUNXI_TPR12=0xeddc7665 +CONFIG_DRAM_SUNXI_TPR13=0x40 +CONFIG_MACH_SUN50I_H616=y +CONFIG_SUNXI_DRAM_H616_DDR3_1333=y +CONFIG_DRAM_CLK=648 +CONFIG_MMC_SUNXI_SLOT_EXTRA=2 +CONFIG_R_I2C_ENABLE=y +# CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set +CONFIG_SPL_I2C=y +CONFIG_SPL_SYS_I2C_LEGACY=y +CONFIG_SYS_I2C_MVTWSI=y +CONFIG_SYS_I2C_SLAVE=0x7f +CONFIG_SYS_I2C_SPEED=400000 +CONFIG_SUN8I_EMAC=y +CONFIG_SUPPORT_EMMC_BOOT=y +CONFIG_PHY_REALTEK=y +CONFIG_RTL8211F_PHY_FORCE_EEE_RXC_ON=y +CONFIG_RGMII=y +CONFIG_RMII=y +CONFIG_AXP313_POWER=y +CONFIG_USB_EHCI_HCD=y +CONFIG_USB_OHCI_HCD=y +CONFIG_USB_MUSB_GADGET=y and maked a u-boot the debian was starting I was testing it