20250512解决NanoPi NEO core开发板在Ubuntu core20.04系统更新boot.img后MMC Device 1174405120 not found Bad devic

【非常奇葩：不能使用eMMC启动的BOOT分区，要使用TF卡/SD卡启动的BOOT分区】

rootroot@rootroot-X99-Turbo:~$ 
rootroot@rootroot-X99-Turbo:~$ git clone https://github.com/friendlyarm/sd-fuse_h3 -b master --single-branch sd-fuse_h3
rootroot@rootroot-X99-Turbo:~$ cd sd-fuse_h3/
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ 
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ ll
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ ll *.sh
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ tar zxvf friendlycore-jammy-images.tgz
【可选编译uboot，确认/熟悉 友善之臂的编译指令】
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ git clone https://github.com/friendlyarm/u-boot -b sunxi-v2017.x --depth 1 uboot
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ UBOOT_SRC=uboot ./build-uboot.sh friendlycore-jammy
【编译生成Z:\sd-fuse_h3\friendlycore-jammy\u-boot-sunxi-with-spl.bin】
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ ll
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ git clone https://github.com/friendlyarm/linux -b sunxi-4.14.y --depth 1 kernel
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ 
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ ll
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ cd kernel
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ 
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ ll
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ touch .scmversion
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ 
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ make ARCH=arm CROSS_COMPILE=arm-linux- menuconfig
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ ll
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ make ARCH=arm CROSS_COMPILE=arm-linux- savedefconfig
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ cp defconfig ./arch/arm/configs/my_defconfig
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ 
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ git add ./arch/arm/configs/my_defconfig
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ 
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ git status
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3/kernel$ cd -
/home/rootroot/sd-fuse_h3
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ 
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ KERNEL_SRC=kernel KCFG=my_defconfig ./build-kernel.sh friendlycore-jammy
【编译异常了，找不到kernel。直接用编译生成的zImage和 SD卡启动的固件的BOOT分区打包成为boot.img】
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ 
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ mkdir BOOT
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ ll *.sh
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ ll
rootroot@rootroot-X99-Turbo:~/sd-fuse_h3$ ./build-boot-img.sh BOOT/ friendlycore-jammy/boot.img

20250512解决NanoPi NEO core开发板在Ubuntu core20.04系统更新boot.img后MMC Device 1174405120 not found  Bad device mmc 0x46000000 
2025/5/13 17:55

请使用以下压缩包/IMG固件写TF卡之后的BOOT分区：
h3-sd-friendlycore-xenial-4.14-armhf-20210618.img.gz
h3-sd-friendlycore-focal-4.14-armhf-20250402.img.gz
h3-sd-friendlycore-jammy-4.14-armhf-20250402.img.gz

一定不能使用：【不用试了，这些固件的BOOT分区会死在uboot启动之后了】
h3-eflasher-friendlycore-xenial-4.14-armhf-20210618.img.gz
h3-eflasher-friendlycore-focal-4.14-armhf-20250402.img.gz
h3-eflasher-friendlycore-jammy-4.14-armhf-20250402.img.gz

U-Boot SPL 2017.11 (Jun 15 2021 - 10:49:36)
DRAM: 512 MiB(408MHz)
CPU Freq: 408MHz
memory test: 1
Pattern 55aa  Writing...Reading...OK
Trying to boot from MMC2
Boot device: emmc

U-Boot 2017.11 (Jun 15 2021 - 10:49:36 +0800) Allwinner Technology

CPU:   Allwinner H3 (SUN8I 1680)
Model: FriendlyElec NanoPi H3
DRAM:  512 MiB
CPU Freq: 1008MHz
MMC:   SUNXI SD/MMC: 1, SUNXI SD/MMC: 0
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
BOARD: nanopi-neo-core
starting USB...
No controllers found
Hit any key to stop autoboot:  0 
reading boot.scr
1204 bytes read in 18 ms (64.5 KiB/s)
## Executing script at 43100000
running eflasher boot.scr
MMC Device 1174405120 not found
** Bad device mmc 0x46000000 **
MMC Device 1191182336 not found
** Bad device mmc 0x47000000 **
MMC Device 1207959552 not found
** Bad device mmc 0x48000000 **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr

" command.
Aborting!
=> 

[END] 2025/5/13 17:55:54