TI中文支持网SDK3.02版本的uboot2016.05版本，默认编译的话好像是使用了devicetree，但是我编译出来的dtb文件放在sd卡的boot分区，依旧提示
U-Boot SPL 2016.05-g1cbbf3f-dirty (Dec 30 2016 – 18:44:29)
Trying to boot from MMC1
reading args
spl_load_image_fat_os: error reading image args, err – -1
reading u-boot.img
reading u-boot.img
reading u-boot.img
No matching DT out of these options:
am335x-evm
Failed to mount ext2 filesystem…
spl_load_image_ext_os: ext4fs mount err – 0
Failed to mount ext2 filesystem…
spl_load_image_ext: ext4fs mount err – 0
看代码No matching DT out of these options:这条提示是因为分区下没有configurtion文件，但是我在SDK里顶层目录编译没有生成configurtion文件，不知道这个文件是怎么生成的。
另外如果用am335x_evm_nodt_defconfig编译uboot的话，则会提示错误，不明白为什么make u-boot-spl编译会去编译armv8下的文件。
{standard input}: Assembler messages:
{standard input}:33: Error: selected processor does not support requested special purpose register — `mrs r0,cntfrq_el0'
{standard input}:62: Error: selected processor does not support requested special purpose register — `mrs r0,cntpct_el0'
{standard input}:93: Error: selected processor does not support requested special purpose register — `mrs r2,cntfrq_el0'
{standard input}:114: Error: selected processor does not support requested special purpose register — `mrs r3,cntfrq_el0'
scripts/Makefile.build:280: recipe for target 'arch/arm/cpu/armv8/generic_timer.o' failed
make[2]: *** [arch/arm/cpu/armv8/generic_timer.o] Error 1
Makefile:1221: recipe for target 'arch/arm/cpu/armv8' failed
make[1]: *** [arch/arm/cpu/armv8] Error 2
Eggsy Pang：
关于你第一个问题，怀疑是你编译出来的dtb文件有问题，不知道你在原本的dts里修改了什么呢以及编译方法？
zizhen hu：
回复 Eggsy Pang:
你好：
你说的dts文件是kernel的arch/arm/boot/dts下面的am335x_evm.dts里面的内容吗？那个里面是修改了pinmux相关的东西，我用SDK08的uboot用来跑SDK3.02的kernel，是可以正常起来的，所以不是很明白你说的dts里面修改了什么是指哪些？
我的编译方法是在根目录下用make u-boot-spl命令编译的，我看生成的文件有MLO,u-boot.img,u-boot-dtb.img，这些文件我都有拷贝到SD卡的boot分区，甚至把u-boot-dtb.img文件更名为u-boot.img，同样拷贝到SD卡boot分区根目录，做过测试，都出现上面的错误。我有看过SDK02关于uboot的相关说明，好像没有提到和devicetree有关的，相关的资料可以给一份参考吗？
下面的log是mkimage -l u-boot-dtb.img。FIT description: Firmware image with one or more FDT blobsCreated: Mon Jan 2 18:26:54 2017 Image 0 (firmware@1) Description: U-Boot 2016.05-00305-g0e1d3c5-dirty for am335x board Created: Mon Jan 2 18:26:54 2017 Type: Firmware Compression: uncompressed Data Size: unavailable Architecture: ARM Load Address: 0x80800000 Image 1 (fdt@1) Description: am335x-evm Created: Mon Jan 2 18:26:54 2017 Type: Firmware Compression: uncompressed Data Size: unavailable Architecture: ARM Load Address: unavailable Image 2 (fdt@2) Description: am335x-bone Created: Mon Jan 2 18:26:54 2017 Type: Firmware Compression: uncompressed Data Size: unavailable Architecture: ARM Load Address: unavailable Image 3 (fdt@3) Description: am335x-boneblack Created: Mon Jan 2 18:26:54 2017 Type: Firmware Compression: uncompressed Data Size: unavailable Architecture: ARM Load Address: unavailable Image 4 (fdt@4) Description: am335x-evmsk Created: Mon Jan 2 18:26:54 2017 Type: Firmware Compression: uncompressed Data Size: unavailable Architecture: ARM Load Address: unavailable Image 5 (fdt@5) Description: am335x-bonegreen Created: Mon Jan 2 18:26:54 2017 Type: Firmware Compression: uncompressed Data Size: unavailable Architecture: ARM Load Address: unavailable Image 6 (fdt@6) Description: am335x-icev2 Created: Mon Jan 2 18:26:54 2017 Type: Firmware Compression: uncompressed Data Size: unavailable Architecture: ARM Load Address: unavailable Default Configuration: 'conf@1' Configuration 0 (conf@1) Description: am335x-evm Kernel: unavailable FDT: fdt@1 Configuration 1 (conf@2) Description: am335x-bone Kernel: unavailable FDT: fdt@2 Configuration 2 (conf@3) Description: am335x-boneblack Kernel: unavailable FDT: fdt@3 Configuration 3 (conf@4) Description: am335x-evmsk Kernel: unavailable FDT: fdt@4 Configuration 4 (conf@5) Description: am335x-bonegreen Kernel: unavailable FDT: fdt@5 Configuration 5 (conf@6) Description: am335x-icev2 Kernel: unavailable FDT: fdt@6
zizhen hu：
回复 zizhen hu:
没有人来回复吗？
求高手回复。
zizhen hu：
回复 zizhen hu:
求高手回复。
