Jump to content

Nasko

Members
  • Posts

    8
  • Joined

  • Last visited

Recent Profile Visitors

1761 profile views
  1. After long break, I have found some free time to test latest updates that can be found in github It seems that pyavitz made a great progress there with his DTS implementation over Debian. https://github.com/pyavitz/debian-image-builder Now i am able to boot Debian out of the reproduced image. No uboot patching: Here is a copy of my work inside above repository: make config make all board=kickpik2b-v2 sudo dd if=output/kickpik2b-v2/image/sun50i-h618-kickpi-k2b-debian-trixie-6.12.84-arm64-ext4-2026-04-29-1923.img of=/dev/mmcblk0 And boom. Flawless boot into Debian Linux U-Boot SPL 2026.01 (Apr 29 2026 - 18:28:52 +0300) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.12.9(debug):lts-v2.12.9 NOTICE: BL31: Built : 18:28:34, Apr 29 2026 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0cd628, 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 2026.01 (Apr 29 2026 - 18:28:52 +0300) 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: 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 /boot/extlinux/extlinux.conf Retrieving file: /boot/extlinux/extlinux.conf KickPi K2B V2 1: Debian Trixie Enter choice: 1: Debian Trixie Retrieving file: /boot/extlinux/../Image Retrieving file: /boot/extlinux/../uInitrd append: earlyprintk console=tty1 console=ttyS0,115200n8 rw root=PARTUUID=e0688e9b-01 rootwait rootfstype=ext4 fsck.repair=yes loglevel=1 net.ifnames=0 video=HDMI-A-1:1920x1080 init=/sbin/init Retrieving file: /boot/extlinux/../allwinner/sun50i-h618-kickpi-k2b.dtb Moving Image from 0x40080000 to 0x40200000, end=0x41930000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: initramfs-6.12.84 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 11668168 Bytes = 11.1 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 494df000, end 49fffac8 ... OK Loading Device Tree to 00000000494d2000, end 00000000494de815 ... OK Working FDT set to 494d2000 Starting kernel ... Loading, please wait... Starting systemd-udevd version 257.9-1~deb13u1 Most important part - communication devices are available: Pyavitz did a great job! kickpik2b-v2root~: dmesg | grep -i "eth0\|wlan0" [ 19.638015] dwmac-sun8i 5020000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 [ 19.784938] dwmac-sun8i 5020000.ethernet eth0: PHY [stmmac-0:00] driver [MAE0621A-Q2C Gigabit Ethernet] (irq=POLL) [ 19.784980] dwmac-sun8i 5020000.ethernet eth0: No Safety Features support found [ 19.784991] dwmac-sun8i 5020000.ethernet eth0: No MAC Management Counters available [ 19.784999] dwmac-sun8i 5020000.ethernet eth0: PTP not supported by HW [ 19.785390] dwmac-sun8i 5020000.ethernet eth0: configuring for phy/rgmii link mode [ 19.826219] [chip1][SKWIFI6621S DBG] skw_ndo_open: dev: wlan0, type: STA [ 19.826262] [chip1][SKWIFI6621S DBG] skw_ndo_set_rx_mode: wlan0, mc: 1, uc: 0 [ 19.826723] [chip1][SKWIFI6621S DBG] skw_ndo_set_rx_mode: wlan0, mc: 2, uc: 0 [ 19.826885] [chip1][SKWIFI6621S DBG] skw_set_power_mgmt: wlan0, enabled: 0, timeout: -1 I haven't tried Armbian yet, but the heavy lifting part is already done. Big kudos to pyavitz @c0rnelius Thanks, Nasko
  2. Thanks @c0rnelius Is there a sustainable way of building working images for kickpi k2b v2?
  3. HI. I had same issue. For all others that might hit same issue bellow are instructions: 1. Supply yourself with known good SD card. 2. Go to KickPi website, download an image supplied by them and write it to the card using dd or balena-etcher. 2.1 Make sure that you are able to boot the image from above. 3. If you are under widows it is good to have a Virtual Machine (I have Debian 13 running inside virtual box). If you are a Linux user, just skip this step 4. Clone Armbian build project git clone https://github.com/armbian/build 4.1. Build an image: cd build ./compile.sh build BOARD=kickpik2b BRANCH=current BUILD_DESKTOP=no BUILD_MINIMAL=yes KERNEL_CONFIGURE=yes RELEASE=trixie 4.2. Write the image to SD card from above. sudo dd if=output/images/Armbian-unofficial_25.11.0-trunk_Kickpik2b_trixie_current_6.12.58_minimal.img of=/dev/mmcblk0 bs=1M status=progress 5. Clone Debian Image builder git clone https://github.com/pyavitz/debian-image-builder cd debian-image-builder 5.1 Follow the instructions from Readme.md: ./install.sh make menu 5.2 In the menu adjust uboot version to 2025.7 5.2 Build the uboot make uboot board=kickpik2b-v2 6. Write Uboot to your sdcard sudo dd if=output/kickpik2b-v2/u-boot-sunxi-with-spl.bin of=/dev/mmcblk0 conv=fsync bs=1024 seek=8 7. Congratulations: Now you would have working board, but now WiFi or Ethernet.
  4. Same Here. I am using Armbian on top of cubietruk as cups print server for years without issue. Now I have decided to see if I can use scanning function of my Samsung SCX-4600 3 in 1 machine. So, I logged in via ssh to my cubietruk running Armbian 23.02.0-trunk Lunar and I just did sudo apt-get update (And got some errors of missing repos), Despite that I have decided to give a try with sudo apt-get install sane Result was 5-6 missing packages Next obvious step was to start armbian-config and I went directly with "Update firmware and packages" Update was success and armbian-config asked for a reboot, which I did. Unfortunately the system was not able to boot. Luckily I have 23" HP Z-series monitor next to my trusty SBC and saw that on the console was lots of errors related to ETHERNET. Second and third reboot was pointles, so I have decided that It is time for fresh install for my cusps print- server. I have downloaded "Debian 12 (Bookworm)Minimal / IOT" from https://www.armbian.com/cubietruck/ and I have flashed it using dd. Next obvious step was to start the system. I saw U-Boot Logo and "Starting Kernel" Then the screen went BLACK. NOTHING. Now there is no way to configure this fresh install. Is there any workarounds?
  5. Successfully installed on cubietruck: Details are: dmesg snip: [ 12.218407] usb 3-1: New USB device found, idVendor=0bda, idProduct=f179, bcdDevice= 0.00 [ 12.218447] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 12.218461] usb 3-1: Product: 802.11n [ 12.218472] usb 3-1: Manufacturer: Realtek [ 12.218483] usb 3-1: SerialNumber: 00e04c000001 lsusb: Bus 003 Device 002: ID 0bda:f179 Realtek Semiconductor Corp. RTL8188FTV 802.11b/g/n 1T1R 2.4G WLAN Adapter
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines