c0rnelius

The /boot/firmware/cmdline.txt requires: console=serial0,115200 The /boot/firmware/config.txt requires: enable_uart=1 That's it.

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/

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.

Nice.

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

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

Another problem here is that they don't have a schematic available for the rev2. They may have changed more than the DRAM? So the first u-boot I posted could have been fine, but the kernel DTS may need adjusting. Oh NVM. You did post the schematic EDIT: Not helpful. Its the same schematic I already have, which was incorrect as the variant I purchased is using DDR4. Not sure whats up with this company but they aren't very good at providing proper sources or essential unit information.

Try this one. I unfortunately I haven't been able to find any other timings. Hopefully this simple change makes a diff. u-boot-sunxi-with-spl.bin

There is another DDR3 option. GIve me a bit and I'll post it.

I've got a REV 1.1. Try flashing the binary. I got the timing from the opi zero2 Make sure you flash it to the correct node, be it mmcblk1, sdb, etc. sudo dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblkX conv=fsync bs=1024 seek=8 u-boot-sunxi-with-spl.bin

If it isn't the PSU or SD than I'm not sure. The only REV available in the STATES "which is where I am" is the 2GB. The u-boot patch set is identical to the BPI-M4-Zero "minus the dts and defconfig of course". All my testing has been done with the unit I have available to me. It works with the Armbian, KIckpi and my own personal builds. As an aside the Kickpi web site is down for me STATE side. Not sure what that means? Doesn't look good though. Anyway, I'm out of ideas. Sorry.

Using mainline, which this img does, I have only had issues when the PSU isn't up to snuff. A 5V 2A should be enough, I use a 5V 3A usually. My only other suggestion would be; dd off the u-boot and OS from the eMMC and see if that helps.

@chuanzz 345032 -rw-rw-r-- 1 patrick patrick 353310884 Oct 23 11:00 Armbian_community_25.11.0-trunk.334_Kickpik2b_trixie_current_6.12.47_minimal.img.xz U-Boot SPL 2025.07 (Sep 24 2025 - 18:40:04 -0400) DRAM: 2048 MiB Trying to boot from MMC2 NOTICE: BL31: v2.12.5(debug):lts-v2.12.5 NOTICE: BL31: Built : 11:56:13, Sep 10 2025 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0cd800, model: KickPi K2B INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: Probing for PMIC on I2C: INFO: PMIC: found AXP313 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. U-Boot SPL 2025.07-armbian-2025.07-Se37d-Pe61e-H8869-Vbdbf-Bb703-R448a (Oct 16 2025 - 02:34:23 +0000) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.12.5(debug):armbian NOTICE: BL31: Built : 03:03:57, Oct 1 2025 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0b7550, model: KickPi K2B INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: Probing for PMIC on I2C: INFO: PMIC: found AXP313 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2025.07-armbian-2025.07-Se37d-Pe61e-H8869-Vbdbf-Bb703-R448a (Oct 16 2025 - 02:34:23 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: KickPi K2B DRAM: 2 GiB Core: 74 devices, 23 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0, mmc@4021000: 2, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Allwinner mUSB OTG (Peripheral) Net: eth0: ethernet@5020000using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in MAC de:ad:be:ef:00:01 HOST MAC de:ad:be:ef:00:00 RNDIS ready , eth1: usb_ether starting USB... sun4i_usb_phy phy@5100400: External vbus detected, not enabling our own vbus USB EHCI 1.00 USB OHCI 1.0 USB EHCI 1.00 USB OHCI 1.0 USB EHCI 1.00 USB OHCI 1.0 Bus usb@5101000: 1 USB Device(s) found Bus usb@5101400: 1 USB Device(s) found Bus usb@5200000: 1 USB Device(s) found Bus usb@5200400: 1 USB Device(s) found Bus usb@5310000: 1 USB Device(s) found Bus usb@5310400: 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 4641 bytes read in 2 ms (2.2 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 191 bytes read in 1 ms (186.5 KiB/s) Load fdt: /boot/dtb/allwinner/sun50i-h618-kickpi-k2b.dtb 43768 bytes read in 5 ms (8.3 MiB/s) Working FDT set to 4fa00000 4203 bytes read in 4 ms (1 MiB/s) Applying kernel provided DT fixup script (sun50i-h616-fixup.scr) ## Executing script at 45000000 17093884 bytes read in 707 ms (23.1 MiB/s) 37613576 bytes read in 1554 ms (23.1 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=0x426d0000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17093820 Bytes = 16.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 48fb2000, end 49fff4bc ... OK Loading Device Tree to 0000000048f3e000, end 0000000048fb1fff ... OK Working FDT set to 48f3e000 Starting kernel ... Does the PSU have enough juice and is the SD card one of quality?

@laibsch That first one you posted is one of the ones I boot tested a week ago. It is still in my Download dir. Booted for me.

You should try erasing the eMMC or re-flashing U-Boot to it. I don't see why that would be necessary, as it wasn't for me. But I did read somewhere on their wiki at one point that in some use cases erasing the eMMC is a work around when getting boot fails.

Plus the kernel source is getting pulled from their repo. If they did make a change, you should see it on Armbian.

I don't see anything in the history that would suggest they made any changes? I could submit a RTW88 patch I put together from the lwfinger/rtw88 repo. But seeing as the pi guys haven't appeared to have changed anything on their end, it is probs more trouble than it is worth.

Run a diff on the pi and armbian defconfig. https://github.com/raspberrypi/linux/tree/rpi-6.12.y/arch/arm64/configs

Well apparently it is an issue, as stated above by @JFL. Also, after a RECALL, I'm the one who did the PR to change it from =y to =m. https://github.com/armbian/build/pull/8300/commits/bb71177580b34c1aeaeb601696d603b6dc49d326 As for udev and delay, you could edit the udev system file; /lib/udev/rules.d/50-udev-default.rules The line you want to edit is about 15 lines down. Change from rtc0 to rtc1.

For those without a battery connected wouldn't this be an issue?

@OleksandrK Would changing the symlink suffice? ls -ls /dev/rtc* 0 lrwxrwxrwx 1 root root 4 Aug 25 11:14 /dev/rtc -> rtc1 0 crw------- 1 root root 252, 0 Aug 25 11:14 /dev/rtc0 0 crw------- 1 root root 252, 1 Aug 25 11:14 /dev/rtc1 echo 'SUBSYSTEM=="rtc", KERNEL=="rtc1", SYMLINK+="rtc" OPTIONS+="link_priority=-100"' | sudo tee /etc/udev/rules.d/10-hym8563-rtc.rules This way both get loaded, but /dev/rtc is linked to rtc1 "hym8563".

On other platforms we can usually set an alias in the DTS for the rtc. On RK I'm not seeing that as an option, but what we can do is make it so one module loads before the other. In short, we set `CONFIG_RTC_DRV_HYM8563=y` and leave `CONFIG_RTC_DRV_RK808=m`. Which will force a hierarchy in the way things load. Case in point; patrick@nanopir3s:~$ dmesg | grep rtc [ 4.646223] rtc-hym8563 1-0051: registered as rtc0 [ 4.647295] rtc-hym8563 1-0051: setting system clock to 2025-08-25T01:34:16 UTC (1756085656) [ 5.548534] rk808-rtc rk808-rtc.5.auto: registered as rtc1 [ 5.605731] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 5.605810] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes We may also be able to achieve this with a udev rule? I'll do a PR after further testing.

Before loading the module `sudo modprobe cfg80211`

Try the devel repo: https://github.com/lwfinger/rtw88