Sune Posted Wednesday at 05:44 PM Posted Wednesday at 05:44 PM Hello everyone! Saw that some luckfox boards were getting supported and I was like: YES!!! Flashed an sd-card with the community image. Latest I could find is 25.11.0-trunk.413. And plonked in my working Luckfox Lyra Zero W and it failed to boot. From what I gather there seems to be a missing partition called "misc" and I think it is expected about after the current unallocated 16MB(16,777,216 bytes). I tried creating a 4MB partition after the current unallocated space but it complained about something called "Magic" and my limited u-boot/rockchip/embedded linux experience made me get lost there. This is the serial output: Where the "No misc partition" is where I began. My current board has buildroot flashed to the SPI and boots if i don't have any sd-card inserted. DDR 0ac6b06a19 typ 24/11/13-17:22:47,fwver: v1.04 tREFI:4x, sr_idle:93, pd_idle:13 PHY drv:clk:40,ca:48,DQ:40,odt:240 vrefinner:50%, vrefout:50% dram drv:40,odt:120 sr_dq:0, sr_ca:0, sr_clk:0 rg:0xc-0x1-0x2, 0x3d-0x0-0x2,status:a007 rdtrn:0x14-0x30-0x4c(0x38) wrtrn:0x3-0x20-0x3d(0x3a) DDR3, 750MHz BW=16 Col=10 Bk=8 CS0 Row=15 CS=1 Size=512MB out U-Boot SPL board init U-Boot SPL 2017.09-g4d88b0a #hxj (Jul 30 2025 - 20:08:42) sfc cmd=03H(6BH-x4) SPI Nand ID ef aa 22 unrecognized JEDEC id bytes: ff, ef, aa Trying to boot from MMC1 No misc partition spl: partition error Trying fit image at 0x4000 sector ## Verified-boot: 0 ## Checking op-tee 0x00001000 ... sha256(93603ca22c...) + OK ## Checking u-boot 0x00100000 ... sha256(606b868a00...) + OK ## Checking fdt-1 0x0018baf0 ... sha256(6ae9f912c7...) + OK Jumping to U-Boot(0x00001000) I/TC: I/TC: OP-TEE version: 3.13.0-958-g46dcf51e88a #chenjh (gcc version 10.2.1 20201103 (GNU Toolchain for the A-profile Architecture 10.2-2020.11 (arm-10.16))) #2 Thu Mar 6 10:17:27 CST 2025 arm, fwver: v2.10 I/TC: Status: cluster=0xc00, core=0xe100, bootcpu=0 I/TC: Next entry point address: 0x03f011a7 I/TC: OP-TEE memory size: TEEOS 0x5e000 TA 0x1000 SHM 0x1000 I/TC: Primary CPU initializing I/TC: Primary CPU switching to normal world boot 0 Quote
Sune Posted 2 hours ago Author Posted 2 hours ago So I am not a person to give up on this I basically took the partition scheme of a working ubuntu img and inserted the armbian partition and got further along. I changed it to below and got further along! Check the log for more information. Hint it threw some panic stuff, I wasn't expecting much but got further along. Hope someone can see what is wrong and help me troubleshoot. sudo fdisk -l /dev/sdd Disk /dev/sdd: 28.85 GiB, 30979129344 bytes, 60506112 sectors Disk model: Storage Device Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 863CE3B9-B148-45D1-B850-79AC22F0EB72 Device Start End Sectors Size Type /dev/sdd1 8192 16383 8192 4M Linux filesystem /dev/sdd2 16384 40959 24576 12M Linux filesystem /dev/sdd3 65536 60504063 60438528 28.8G Linux filesystem screenlog.log 0 Quote
Sune Posted 2 hours ago Author Posted 2 hours ago I see now with some examination this: [ 1.995057]3 614e0000-0000-4b53-8000-1d2800995194] No filesystem could moun ext4 [ 1.995269] [ 1.9g: VFS: Unable to mount root fs 002577] CPU2: stopping The reason for the missing characters is likely the shitty CH340 I have connected as the serial monitor. Should still be able to see the issue. 0 Quote
Sune Posted 1 hour ago Author Posted 1 hour ago (edited) I fixed the shitty dd stuff i did previously. I got it to boot now. It seems that the partitions need to be included in the image for it to work. From inside the armbian image: mmcblk0 179:0 0 28.9G 0 disk ├─mmcblk0p1 179:1 0 4M 0 part ├─mmcblk0p2 179:2 0 12M 0 part └─mmcblk0p3 179:3 0 28.8G 0 part /var/log.hdd I will build my own img and see if there is anything I can do about the non working usb. I think it might likely be related to dts Edited 1 hour ago by Sune 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.