chuanzz Posted 7 hours ago Posted 7 hours ago I am using this version "Armbian_community_25.11.0-trunk.334_Kickpik2b_trixie_current_6.12.47_minimal.img". It shows U-Boot SPL 2025.07 (Oct 20 2025 - 18:19:29 +0800) DRAM:This DRAM setup is currently not supported. resetting ... U-Boot SPL 2025.07 (Oct 20 2025 - 18:19:29 +0800) DRAM:This DRAM setup is currently not supported. resetting ... U-Boot SPL 2025.07 (Oct 20 2025 - 18:19:29 +0800) DRAM:This DRAM setup is currently not supported. resetting ... U-Boot SPL 2025.07 (Oct 20 2025 - 18:19:29 +0800) DRAM:This DRAM setup is currently not supported. resetting ... U-Boot SPL 2025.07 (Oct 20 2025 - 18:19:29 +0800) DRAM:This DRAM setup is currently not supported. The system just loops this message and never proceeds. Has anyone encountered this issue before? Any suggestions or solutions would be greatly appreciated. Thanks in advance! 0 Quote
c0rnelius Posted 4 hours ago Posted 4 hours ago @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? 0 Quote
chuanzz Posted 3 hours ago Author Posted 3 hours ago 40 minutes ago, c0rnelius said: Does the PSU have enough juice and is the SD card one of quality? I dont think so. I can boot the official system “kickpi-k2b-ubuntu-jammy-desktop-xfce-linux-5.4.125-20250901.img” using this SD card 0 Quote
c0rnelius Posted 2 hours ago Posted 2 hours ago 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. 0 Quote
chuanzz Posted 1 hour ago Author Posted 1 hour ago 1 hour ago, c0rnelius said: My only other suggestion would be; dd off the u-boot and OS from the eMMC and see if that helps. I dd the armbian.img > emmc. and remove my sd card still the same output 0 Quote
c0rnelius Posted 50 minutes ago Posted 50 minutes ago 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. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.