Part Number: AM3352
我现在是将板子的uboot 从sdk 的2017 版本，升级到2026 版本，原本旧的uboot 是可以正常启动fitimage 的，且bootargs 配置为 'earlycon=ns16550a,mmio32,0x44e09000 console=ttyO0,115200n8 loglevel=8 root=/dev/ram0 rw'， 可以正常看到kernel 启动log, 并正常启动，现在换成uboot 2026 版本后，bootargs 没变，还是 'earlycon=ns16550a,mmio32,0x44e09000 console=ttyO0,115200n8 loglevel=8 root=/dev/ram0 rw'，
=> bootm 0x88000000
## Loading kernel (any) from FIT Image at 88000000 ...
Using 'conf-1' configuration
Verifying Hash Integrity ... OK
Trying 'kernel-1' kernel subimage
Description: Linux Kernel
Created: 2011-04-05 23:00:00 UTC
Type: Kernel Image
Compression: uncompressed
Data Start: 0x880113f0
Data Size: 5902848 Bytes = 5.6 MiB
Architecture: ARM
OS: Linux
Load Address: 0x80300000
Entry Point: 0x80300000
Hash algo: sha256
Hash value: dbc1b7373ca439fe70850915362be5991d21580c810c08f430ae67eaa0a65bea
Verifying Hash Integrity ... sha256+ OK
## Loading ramdisk (any) from FIT Image at 88000000 ...
Using 'conf-1' configuration
Verifying Hash Integrity ... OK
Trying 'ramdisk-1' ramdisk subimage
Description: Ramdisk Image
Created: 2011-04-05 23:00:00 UTC
Type: RAMDisk Image
Compression: uncompressed
Data Start: 0x885b26e8
Data Size: 2108265 Bytes = 2 MiB
Architecture: ARM
OS: Linux
Load Address: 0x83000000
Entry Point: 0x83000000
Hash algo: sha256
Hash value: f2adcb28abc8db029d08a70b44922d17181ef12d965b85a1aaa959d4058625e6
Verifying Hash Integrity ... sha256+ OK
Loading ramdisk from 0x885b26e8 to 0x83000000
## Loading fdt (any) from FIT Image at 88000000 ...
Using 'conf-1' configuration
Verifying Hash Integrity ... OK
Trying 'fdt-1' fdt subimage
Description: Flattened Device Tree blob
Created: 2011-04-05 23:00:00 UTC
Type: Flat Device Tree
Compression: uncompressed
Data Start: 0x880000d0
Data Size: 70204 Bytes = 68.6 KiB
Architecture: ARM
Load Address: 0x80200000
Hash algo: sha256
Hash value: 922e664890d89e3e29510ceebcf806157170f2ac0492084f377b4ae4c9d527ac
Verifying Hash Integrity ... sha256+ OK
Loading fdt from 0x880000d0 to 0x80200000
Booting using the fdt blob at 0x80200000
Working FDT set to 80200000
Loading Kernel Image to 80300000
Using Device Tree in place at 80200000, end 8021423b
Working FDT set to 80200000
Starting kernel ...
CCCCCCCC
上面出现Starting kernel ... 后大概等了30s 后出现CCCC, 板子重启，由于kernel 在旧的uboot 可以正常启动，且bootargs 起了作用，我现在怀疑是新的uboot 导致， 为什么新的uboot 下bootargs 没起作用，内核也没看到输出，不知道什么原因，大家有遇到过吗，能帮忙一下！
