The image in binary format do not contain any debug information. So it can not be debug by gdb. You can try to compile u-boot to elf format.Then if you use SkyEye below 1.0 version, you can type:
skyeye u-boot.elf
if you use skyeye above 1.0 version, you can tyoe:
skyeye -e u-boot.elf
I use a config file to start u-boot with a binary file, it should be the same as skeyeye -e u-boot.elf, but the u-boot get executed when skyeye starts, so I can debug the binary from the first instruction. I use u-boot-1.2
[quote:c1757ee710="imu1234"]I use a config file to start u-boot with a binary file, it should be the same as skeyeye -e u-boot.elf, but the u-boot get executed when skyeye starts, so I can debug the binary from the first instruction. I use u-boot-1.2[/quote]
http://www.skyeye.org/wiki/SkyeyeUboot 中写到
In the interface of skyeye, input: (For Skyeye1.0, this step shoul be ignored and u-boot will start directly.)
target sim
run
At this time , the interface and prompt of u-boot can be saw and then when inputting ?help?, all commands in u-boot can be showed or when inputting ?version?, the current u-boot version can be displayed etc.