https://forum.armbian.com/topic/18902-s905-failed-to-boot-from-emmc/
这个帖子里有人声称成功将Armbian 20.10 装入了GXBB盒子的EMMC中，你可以参考下，我对uboot不熟悉没重现成功:[color=rgb( var(--theme-brand_primary) )]@hexdump sorry, I didn't realize how much time has passed since we talked, lol. It is about Amologix S905. As you know the ROM in this SOC looks for bootloader at the 1st sector of the eMMC, so it is not possible to create regular partitions since the part. table would overwrite the bootloader. The result is that u-boot commands like 'fatload' won't work. Which prevented me from installing Armbian into eMMC. E.g.: the chainloaded u-boot will report:
U-Boot 2020.07-dirty (Oct 24 2020 - 21:14:30 +0200) hexdump-gxbb...switch to partitions #0, OKmmc2 is current device** No partition table - mmc 2 **
I resolved this by dedicating 2 areas at the end of eMMC: 200MB 'boot', and the rest (~6GB) as 'root'. I exposed these to Linux using kernel command line parameter: 'blkdevparts=mmcblk1:209715200@1463812096(boot),-@1673528320(root)'.
In Linux I copied the root directory tree to /dev/mmcblk1p2. I left /dev/mmcblk1p1 (the boot "partition") without file system, and copied (dd) uboot (the mailine uboot), kernel, ramdisk, and dtb there at the predefined block positions, e.g: 'dd if=zImage of=/dev/mmcblk1p2 bs=512 seek=2859008 count=54841'.
In Amlogic u-boot instead of fatload I used 'mmc read' to load all files, e.g.: to load the kernel: 'mmc read 0x08080000 0x2BA3FC 0xD639'.
In the chainloaded Mainline u-boot I used 'booti 0x08080000 0x13000000 0x08008000' as 'bootcmd' to start the system.
With this setup I can now boot from eMMC. Thanks for you assistance; your comments on the subject in various threads on the forum were very helpful.
我之前尝试过将Armbian装入emmc，结果遇到了如上所示的找不到分区表错误。帖子中的pistar用mmc read代替mmc fatload来规避第一sector的问题，并声称成功实现。不过我对u-boot不熟悉，他也没给出详细步骤所以没复现成功，你可以看下
| 
/1 
IP卡
狗仔卡
发表于 2022-1-8 08:36
显身卡
