实验39.4 烧写自制的系统，从emmc启动后卡死在Starting kernel ...

eisscerav

参考正点原子39.4 烧写自制的系统，烧写自己编译的uboot，zImage, zImage-imx6ull-14x14-evk-emmc.dtb, 按教程改名，之后从emmc读取zImage和设备树文件并启动板子，系统卡死

• Environment size: 2733/8188 bytes
• => fatload mmc 1:1 80800000 zImage
• reading zImage
• 5546940 bytes read in 138 ms (38.3 MiB/s)
• => fatload mmc 1:1 83000000 imx6ull-14x14-evk.dtb
• reading imx6ull-14x14-evk.dtb
• 38695 bytes read in 17 ms (2.2 MiB/s)
• => bootz 80800000 - 83000000
• Kernel image @ 0x80800000 [ 0x000000 - 0x5421e0 ]
• ## Flattened Device Tree blob at 83000000
•    Booting using the fdt blob at 0x83000000
•    Using Device Tree in place at 83000000, end 8300c726
• Starting kernel ...
  

[color=rgb(0, 102, 153) !important]复制代码


从tftp服务器下载到内存启动没有问题：

• => tftp 80800000 zImage
• => tftp 83000000 imx6ull-14x14-evk.dtb
• => bootz 80800000 - 83000000
• Kernel image @ 0x80800000 [ 0x000000 - 0x5421e0 ]
• ## Flattened Device Tree blob at 83000000
•    Booting using the fdt blob at 0x83000000
•    Using Device Tree in place at 83000000, end 8300c726
• Starting kernel ...
• Booting Linux on physical CPU 0x0
• Linux version 4.1.15+ (fanxin@VirtualBox-1804) (gcc version 4.9.4 (Linaro GCC 4.9-2017.01) ) #1 SMP PREEMPT Mon Apr 29 11:09:59 CST 2024
• 
  

[color=rgb(0, 102, 153) !important]复制代码

eisscerav

参考教程37.3 在 Linux中添加自己的开发板，编译出来的zImage无法从emmc启动，可以从tftp网络启动。不知道内核中需要修改什么代码。