在使用MYD-AM3358開發(fā)板過程中把BootLoader里面的bootdelay參數(shù)設(shè)置為0后，不能進(jìn)入到uboot的命令里面，不能燒寫內(nèi)核鏡像到開發(fā)板上了……這怎么辦呢？

先來看該啟動(dòng)日志：
U-Boot 2016.05 (Oct 23 2018 - 11:36:24 +0800)
Watchdog enabled
I2C: ready
DRAM: 512 MiB
NAND: 512 MiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Net: Could not get PHY for cpsw: addr 0
cpsw
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
reading boot.scr
** Unable to read file boot.scr **
** Bad device specification 0x82000000 uEnv **
USB is stopped. Please issue 'usb start' first.
starting USB...
USB0: scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
USB device 0: unknown device
switch to partitions #0, OK
mmc0 is current device
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
reading boot.scr
** Unable to read file boot.scr **
reading uEnv.txt
708 bytes read in 4 ms (172.9 KiB/s)
Loaded env from uEnv.txt
Importing environment from mmc ...
3471064 bytes read in 230 ms (14.4 MiB/s)
39405 bytes read in 26 ms (1.4 MiB/s)
Kernel image @ 0x82000000 [ 0x000000 - 0x34f6d8 ]
## Flattened Device Tree blob at 88000000
Booting using the fdt blob at 0x88000000
Loading Device Tree to 8fff3000, end 8ffff9ec ... OK
Fixing up ETH0 & ETH1 to CPSW Ethernet
Starting kernel ..

1. 編寫一個(gè)boot.cmd文本文件，內(nèi)容如下
setenv bootdelay 2
saveenv
2. 制作一個(gè)boot.scr文件
mkimage -C none -A arm -T script -d boot.cmd boot.scr