[U-Boot] BUG: hang with an empty flash (due to recent bootm changes) bisected

[Ira Snyder]

On Wed, Aug 27, 2008 at 05:20:17PM -0500, Kumar Gala wrote:
>
> On Aug 27, 2008, at 4:49 PM, Ira Snyder wrote:
>
>> Hello,
>>
>> I'm working with an MPC8349EMDS board, doing testing. I usually just
>> leave the flash blank, and let the autoboot time out, where it sits  
>> with
>> the following message:
>>
>> Hit any key to stop autoboot:  0
>> Wrong Image Format for bootm command
>> ERROR: can't get kernel image!
>> =>
>>
>>
>> Since commit 396f635b8ff3ccbc38d75d5eda98444c6466810a, this is no  
>> longer
>> the case. The board hangs up after the autoboot times out, showing the
>> following:
>>
>> Hit any key to stop autoboot:  0
>> Wrong Image Format for bootm command
>> ERROR: can't get kernel image!
>>   XIP Invalid Image ... OK
>>   OK
>
> What does the boot command look like?
>
> If I can reproduce this I can track down what's going on.
>
> - k
>

Here is what appears to be the relevant parts of the env.

=> printenv bootcmd
bootcmd=run flash_self
=> printenv flash_self
flash_self=run ramargs addip addtty;bootm ${kernel_addr} ${ramdisk_addr}
=> printenv ramargs addip addtty kernel_addr ramdisk_addr
ramargs=setenv bootargs root=/dev/ram rw
addip=setenv bootargs ${bootargs}
ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}:${netdev}:off panic=1
addtty=setenv bootargs ${bootargs} console=ttyS0,${baudrate}
## Error: "kernel_addr" not defined
## Error: "ramdisk_addr" not defined

Is there anything else that would help?
Ira