写入官方镜像Buildroot-K1-v2.2.10-20260604175709到emmc启动正常,烧录SD启动异常

Block size 512, name env
[ 2.358] Type U-Boot, bootable 0
[ 2.361] UUID 03c9d1ca-9bcf-4b8d-a765-2273a0ce5dce
[ 2.366]
[ 2.367] Partition 3:
[ 2.369] Start 0MiB, size 0MiB
[ 2.372] Block size 512, name opensbi
[ 2.375] Type U-Boot, bootable 0
[ 2.378] UUID e182a76f-9c4e-4660-b6dc-e6838a297e57
[ 2.383]
[ 2.384] Partition 4:
[ 2.386] Start 0MiB, size 2MiB
[ 2.389] Block size 512, name uboot
[ 2.393] Type U-Boot, bootable 0
[ 2.396] UUID 780420f2-cfd8-40a7-83ba-7537b1c89684
[ 2.401]
[ 2.402] Partition 5:
[ 2.404] Start 4MiB, size 256MiB
[ 2.407] Block size 512, name bootfs
[ 2.411] Type U-Boot, bootable 0
[ 2.414] UUID dffa3ae5-0fba-49f6-ab6b-0fe012a733a3
[ 2.418]
[ 2.419] Partition 6:
[ 2.422] Start 260MiB, size 14933MiB
[ 2.425] Block size 512, name rootfs
[ 2.429] Type U-Boot, bootable 0
[ 2.432] UUID f030c9c2-fb11-4f7e-9bc0-071cb1808e66
[ 2.436]
[ 2.437] success!
[ 2.445] Saving Environment to MMC… Writing to MMC(0)… OK
[ 2.451] Net: RGMII interface
[ 2.452] eth0: ethernet@cac80000
[ 2.456] Autoboot in 0 seconds
[ 2.468] Try to boot from mmc0 …
[ 2.556] product_name: k1-x_MUSE-Pi-Pro
[ 2.557] match dtb by product_name: /k1-x_MUSE-Pi-Pro.dtb
[ 2.562] select /k1-x_MUSE-Pi-Pro.dtb to load
[ 2.566] Loading kernel…
[ 3.001] 36731392 bytes read in 405 ms (86.5 MiB/s)
[ 3.003] Loading dtb…
[ 3.032] 88026 bytes read in 13 ms (6.5 MiB/s)
[ 3.033] Loading ramdisk …
[ 3.123] 5803260 bytes read in 75 ms (73.8 MiB/s)
No FDT memory address configured. Please configure
the FDT address via “fdt addr ” command.
Aborting!
[ 3.145] Moving Image from 0x200000 to 0x600000, end=299d000
[ 3.166] ## Flattened Device Tree blob at 31000000
[ 3.167] Booting using the fdt blob at 0x31000000
[ 3.172] Loading Ramdisk to 7d7f7000, end 7dd7fcfc … OK
[ 3.183] Loading Device Tree to 000000007d7de000, end 000000007d7f67d9 … OK

Starting kernel …

sh: /dev/mmcblk2p6: unknown operand
sh: /dev/mmcblk2p6: unknown operand
sh: /dev/mmcblk2p6: unknown operand
find /dev/mmcblk0p6
/dev/mmcblk2p6: 0
Usage: e2fsck [-panyrcdfktvDFV] [-b superblock] [-B blocksize]
[-l|-L bad_blocks_file] [-C fd] [-j external_journal]
[-E extended-options] [-z undo_file] device

Emergency help:
-p Automatic repair (no questions)
-n Make no changes to the filesystem
-y Assume “yes” to all questions
[ 2.235059] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
-c Check for bad bloc[ 2.246307] CPU: 5 PID: 1 Comm: init Not tainted 6.6.63 #1
ks and add them to the badblock list
-[ 2.255289] Hardware name: spacemit k1-x MUSE-Pi-Pro board (DT)
f Force checking even [ 2.264704] Call Trace:
if filesystem is marked clean
-v [ 2.270628] [] dump_backtrace+0x1c/0x24
Be verbose
-b superblock [ 2.279518] [] show_stack+0x2c/0x38
Use alternative superblock
-B b[ 2.288062] [] dump_stack_lvl+0x3c/0x54
locksize Force blocksize when lo[ 2.296963] [] dump_stack+0x14/0x1c
oking for superblock
-j external_journ[ 2.305511] [] panic+0x100/0x2a0
al Set location of the external journal[ 2.313804] [] do_exit+0x7be/0x7c4

-l bad_blocks_file Add to badblocks[ 2.322264] [] do_group_exit+0x24/0x70
list
-L bad_blocks_file Set badbloc[ 2.331078] [] __wake_up_parent+0x0/0x20
ks list
-z undo_file Create an[ 2.340077] [] do_trap_ecall_u+0x116/0x12a
undo file
resize2fs 1.46.5 (30-Dec-202[ 2.349230] [] ret_from_exception+0x0/0x6e
1)
[ 2.358396] SMP: stopping secondary CPUs
[ 2.362709] —[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100 ]—

Aren’t you confused by the entry:
sh: /dev/mmcblk2p6: unknown operand
sh: /dev/mmcblk2p6: unknown operand
sh: /dev/mmcblk2p6: unknown operand
find /dev/mmcblk0p6
/dev/mmcblk2p6: 0
while when reading data from a memory card it shouldn’t be like this, but something like this:
$ ls /dev/mmcblk0*
/dev/mmcblk0 /dev/mmcblk0p1 /dev/mmcblk0p2 /dev/mmcblk0p3 /dev/mmcblk0p4 /dev/mmcblk0p5 /dev/mmcblk0p6