[U-Boot] u-boot: vexpressca9x4: hang(?) with qemu

[U-Boot] u-boot: vexpressca9x4: hang(?) with qemu

[Matwey V. Kornilov]

Hi,

I've build u-boot 2014.04 using

make vexpress_ca9x4_config

Now, I am trying to run it on qemu-system-arm 1.3.1 (as well as 1.7 
gives same result) as the following:

qemu-system-arm -M vexpress-a9 -cpu cortex-a9 -m 1024 -kernel u-boot.bin 
-serial stdio

I want to see u-boot banner and console, but nothing happens, qemu are 
using 100% CPU. How can I dig out what the problem is?

[U-Boot] u-boot: vexpressca9x4: hang(?) with qemu

[Matwey V. Kornilov]

09.06.2014 10:57, Matwey V. Kornilov ?????:
> Hi,
> 
> I've build u-boot 2014.04 using
> 
> make vexpress_ca9x4_config
> 
> Now, I am trying to run it on qemu-system-arm 1.3.1 (as well as 1.7
> gives same result) as the following:
> 
> qemu-system-arm -M vexpress-a9 -cpu cortex-a9 -m 1024 -kernel u-boot.bin
> -serial stdio
> 
> I want to see u-boot banner and console, but nothing happens, qemu are
> using 100% CPU. How can I dig out what the problem is?

So, I've took gdb and found the following:
http://paste.opensuse.org/29548916

If I understand correctly, something is wrong with linking. It is quite
unlikely that get_device_and_partition is the first function to execute.

Any hints?

[U-Boot] u-boot: vexpressca9x4: hang(?) with qemu

[Matwey V. Kornilov]

09.06.2014 21:30, Matwey V. Kornilov ?????:
> 09.06.2014 10:57, Matwey V. Kornilov ?????:
>> Hi,
>>
>> I've build u-boot 2014.04 using
>>
>> make vexpress_ca9x4_config
>>
>> Now, I am trying to run it on qemu-system-arm 1.3.1 (as well as 1.7
>> gives same result) as the following:
>>
>> qemu-system-arm -M vexpress-a9 -cpu cortex-a9 -m 1024 -kernel u-boot.bin
>> -serial stdio
>>
>> I want to see u-boot banner and console, but nothing happens, qemu are
>> using 100% CPU. How can I dig out what the problem is?
> 
> So, I've took gdb and found the following:
> http://paste.opensuse.org/29548916
> 
> If I understand correctly, something is wrong with linking. It is quite
> unlikely that get_device_and_partition is the first function to execute.
> 
> Any hints?

It actually jumps to 0x60010000 where the middle of
get_device_and_partition located.

[U-Boot] u-boot: vexpressca9x4: hang(?) with qemu

[Matwey V. Kornilov]

09.06.2014 21:52, Matwey V. Kornilov ?????:
> 
> It actually jumps to 0x60010000 where the middle of
> get_device_and_partition located.
> 

I've found that it works with qemu 1.7 but I have to provide u-boot in
ELF format, bare-metal u-boot.bin don't work.