Hello all,
I've done more test...
1. remove u-boot.bin in mmc.
2. boot from mmc
3. the serial console will show the x-load prompt and wait for kermit
transfer of u-boot.bin via serial port.
4. fire the command: "ukermit -p /dev/ttyUSB0 -f u-boot.bin"
5. the boot stage goes ahead into u-boot and then the uImage since
there is linux kernel image inside mmc.
So the problem may be in the ROM boot stage,
1. is the transfer really finished?
2. is there any ROM event to load x-load?
I use the omap-u-boot-utils from
http://github.com/nmenon/omap-u-boot-utils.git
I also try to download x-load via usb, the utils download from
http://groups.google.com/group/beagleboard/attach/a124e3b0a2a99d5e/omap3_usb.tar.bz2?part=3
compare the pserial and the usb
I think the uart boot flow is:
1. open the serial/usb port
2. ask the ASIC_ID of the board
3. send command 0xF0030002 to the board
4. transfer the file(x-load.bin) to the board
Since this is a DM3730 board, not a OMAP35xx board, I don't know if
there is any hardware specific parameter should be modified to make
the pserial work?
any hint?
Thanks.