chuanzz Posted yesterday at 11:14 AM Posted yesterday at 11:14 AM 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 yesterday at 03:07 PM Posted yesterday at 03:07 PM @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 yesterday at 03:51 PM Author Posted yesterday at 03:51 PM 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 yesterday at 04:24 PM Posted yesterday at 04:24 PM 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 yesterday at 05:41 PM Author Posted yesterday at 05:41 PM 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 yesterday at 06:21 PM Posted yesterday at 06:21 PM 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
chuanzz Posted 16 hours ago Author Posted 16 hours ago From what I’ve found, the K2B has three revisions; mine is REV 2.2 (it’s printed right on the PCB). Looks like they swapped the RAM from DDR4L to DDR3—mine has DDR3 chips on board—so that might be why it’s acting up. Kickpi’s site barely loads from China; I really dislike that company, the documentation is almost non-existent. I found some here: https://github.com/tan-zhihao1/kickpi-book/tree/master/h618/en Still, I want to crack the problem. With the current sale the 2 GB + 0 GB version is only 78 CNY (about 11 USD), which is hard to pass up. Thanks for getting back to me. K2B.zip 0 Quote
c0rnelius Posted 10 hours ago Posted 10 hours ago 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 0 Quote
chuanzz Posted 6 hours ago Author Posted 6 hours ago U-Boot SPL 2025.07 (Oct 24 2025 - 06:19:19 -0400) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.12.5(debug):lts-v2.12.5 NOTICE: BL31: Built : 06:13:32, Oct 24 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 2025.07 (Oct 24 2025 - 06:19:19 -0400) 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... 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: 2 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 1 ms (4.4 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 181 bytes read in 1 ms (176.8 KiB/s) Load fdt: /boot/dtb/allwinner/sun50iw9-kickpi-k2b.dtb 67673 bytes read in 5 ms (12.9 MiB/s) Working FDT set to 4fa00000 Failed to load '/boot/dtb/allwinner/overlay/h618-fixup.scr' 17096334 bytes read in 704 ms (23.2 MiB/s) 37613576 bytes read in 1549 ms (23.2 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: 17096270 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 49fffe4e ... OK Loading Device Tree to 0000000048f39000, end 0000000048fb1fff ... OK Working FDT set to 48f39000 No RNG device Starting kernel ... and stuck here. It makes differences!! 0 Quote
c0rnelius Posted 6 hours ago Posted 6 hours ago There is another DDR3 option. GIve me a bit and I'll post it. 0 Quote
c0rnelius Posted 5 hours ago Posted 5 hours ago 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 0 Quote
c0rnelius Posted 5 hours ago Posted 5 hours ago 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. 0 Quote
chuanzz Posted 4 hours ago Author Posted 4 hours ago 50 minutes ago, c0rnelius said: Try this one This one failed with "DRAM:This DRAM setup is currently not supported" I found something from kickpi's site:Linux_SDK_Compilation. including building u-boot https://github.com/tan-zhihao1/kickpi-book/blob/master/h618/en/04-SDK_Compilation_Guide/02-Linux_SDK_Compilation.md Its too huge so I deleted the folder "source" and "toolchains". hope it could help I tried to upload here but it shows errors. try this url: https://we.tl/t-t92S5rlCzD 0 Quote
chuanzz Posted 4 hours ago Author Posted 4 hours ago I build a u-boot with it 39 minutes ago, chuanzz said: I found something from kickpi's site:Linux_SDK_Compilation. including building u-boot https://github.com/tan-zhihao1/kickpi-book/blob/master/h618/en/04-SDK_Compilation_Guide/02-Linux_SDK_Compilation.md dd latest armbian.img and this u-boot, it showed: ▒[40]HELLO! BOOT0 is starting!r = 0x1d3 [43]BOOT0 commit : 4b34f2890a [46]set pll start [48]periph0 has been enabled [51]set pll end [54]unknow PMU [56]unknow PMU [59]PMU: AXP1530 [64]vaild para:15 select dram para1 [68]board init ok [69]enable_jtag [71]DRAM BOOT DRIVE INFO: V0.651 [74]the chip id is 0x2000 [77]chip id check OK [80]DRAM_VCC set to 1500 mv [86]read_calibration error [92]read_calibration error [98]read_calibration error [104]read_calibration error [110]read_calibration error [116]read_calibration error [122]read_calibration error [128]read_calibration error [135]read_calibration error [141]read_calibration error [143]retraining final error [152][AUTO DEBUG]32bit,1 ranks training success! [164]DRAM CLK =648 MHZ [166]DRAM Type =3 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [174]Actual DRAM SIZE =2048 M [177]DRAM SIZE =2048 MBytes, para1 = 310a, para2 = 8000000, dram_tpr13 = 6041 [190]DRAM simple test OK. [193]rtc standby flag is 0x0, super standby flag is 0x0 [198]dram size =2048 [201]Use rtc to store dram tuning para [205]card no is 0 [207]sdcard 0 line count 4 [209][mmc]: mmc driver ver 2021-10-12 13:56 [214][mmc]: b mmc 0 bias 4 [222][mmc]: Wrong media type 0x0 [225][mmc]: ***Try SD card 0*** [240][mmc]: HSSDR52/SDR25 4 bit [243][mmc]: 50000000 Hz [245][mmc]: 119850 MB [247][mmc]: ***SD/MMC 0 init OK!!!*** [319]Loading boot-pkg Succeed(index=0). [323][mmc]: b mmc 0 bias 4 [325]Entry_name = u-boot [332]Entry_name = monitor [336]Entry_name = dtbo [339]Entry_name = optee [343]Entry_name = dtb [346]mmc not para [347]Jump to second Boot. NOTICE: BL3-1: v1.0(debug):54937d5 NOTICE: BL3-1: Built : 17:44:59, 2021-12-13 NOTICE: BL3-1 commit: 8 NOTICE: cpuidle init version V2.0 NOTICE: secure os exist MESSAGE: [0x0] TEE-CORE: OP-TEE version: 81ab7a47 #1 2020年 05月 06日 星期三 02:40:04 UTC arm NOTICE: BL3-1: Preparing for EL3 exit to normal world NOTICE: BL3-1: Next image address = 0x4a000000 NOTICE: BL3-1: Next image spsr = 0x1d3 and I found this: [177]DRAM SIZE =2048 MBytes, para1 = 310a, para2 = 8000000, dram_tpr13 = 6041 is this para what we need? 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.