All Activity

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

verbosity was 7 already But no more log

Change the loglevel to 7 in the armbianEnv file and if anything comes up after Starting kernel ... post it.

Out of curiosity, does it work if you drop my firmware build in place? dd bs=512 seek=1 conv=notrunc,fsync if=u-boot-meson.bin of=/dev/${entire-device-to-be-used} u-boot-meson.bin.tgz

This is my first time running Armbian on the odroid HC4, For some reason, I can boot without any drives (uSD card), and sometimes with one drive but never with two. Like no display on the monitor or can't ssh into the system. Anyone else getting something like this? I've wiped the 4 onboard memory locations so that it can boot from SD card (which it does without any drives)

Hey @Adrienne, Github thread talks about two to three ways to so solve the issue. Did you apply the one that removes the symlinks ?

A phandle is a magical number assigned during DTB assembly, whose value is irrelevant as long as it references the same node with the phandle property. The magic value can change when the structure changes because it is assigned arbitrarily; for example, by inserting an additional node.

Thanks @Nick A for the details and link shared ! If I understand correctly, I can build kernel only locally and freeze kernel update. other packages can be downloaded from public repository Is that correct?

In an XWindow environment, these are realistically expected numbers. In a Wayland environment, this is somewhat better; see glmark2-wayland-odroid-m1.log as a reference. But it is in no way comparable to a Mali G610; see glmark2-wayland-odroid-m2.log as a reference. Use WebGL Report to be sure.

There is a minor difference in another node: "phandle = <0x2c2>;" in radxa.dts and phandle = <0x2c3>; No clue if that's the culprit or if there is something on software-side to make fan work.

debug boot issues: https://debug.armbian.de This board is community maintained, therefore Armbian core team does not monitor its status. May be broken, may not. We don't know.

Hi - I have a ZeroPi board running 'bookworm' as supplied by the vendor. I woudl like to run 'trixie' and downloaded it from this page https://www.armbian.com/zero-pi/ but had no luck getting it booted. Would anyone have an idea how to get this to work or what the status is of 'trixie' for the ZeroPi boad. Thanks

@Igor - Can you have a look at this please. I have retrieved the devicetree's for the radxa Debian release on which the fan works and my Armbian Ubuntu build using dtc -I fs /sys/firmware/devicetree/base uname -a lsb_release -a https://github.com/AaronNGray/radxa-rock-5b-plus The 'pwm-fan' nodes are the same.

@BipBip1981, can you please share again your feedback on fancontrol running on Trixie ? The site can't display the image.

He works as ili9341 and as ili9486. I use it now as ili9486. I`ll go further to make it work as native device. DRM frambuffer its something what needs to be kernel recompiled... as i know? And if i want to use it natively, i must edit or recompile u-boot.... DRM support for ILI9486 display panels modulename: ili9486.ko configname: CONFIG_TINYDRM_ILI9486 Linux Kernel Configuration └─>Device Drivers └─>Graphics support └─>Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) └─>SPI support └─>DRM support for ILI9486 display panels In linux kernel since version 4.14.326 (release Date: 2023-09-23) DRM driver for the following Ilitek ILI9486 panels: * PISCREEN 3.5" 320x480 TFT (Ozzmaker 3.5") * RPILCD 3.5" 320x480 TFT (Waveshare 3.5") If M is selected the module will be called ili9486. I will use it for KlipperScreen 😆 But as i se how hard is working that orangePi PC,i`ll doubt if i need this... Any way i`ll try )) Yes. But HDMI not connected. On OrangePiOne image its switching. If HDMI is connected its use it with no output to SPI. But if no HDMI present its use SPI as basic overlay On the same board. Because OPiOne had only 1 usb, OPiPC work only 1 usb ))) if whey work all 3, i`ll didnt open up a topic 😑 ili9486.dts