Re: [Qemu-discuss] qemu -kernel u-boot.bin

[Matwey V. Kornilov]

Only this instructions are executed:

  >│0x60000000 <_start>                     mov    r0, #0
                                                     │
   │0x60000004 <_start+4>                   ldr    r1, [pc, #6397080]
    ; 0x60000010 <_start+16>                         │
   │0x60000008 <_start+8>                   ldr    r2, [pc, #6397080]
    ; 0x60000014 <_start+20>                         │
   │0x6000000c <_start+12>                  ldr    pc, [pc, #6397080]
    ; 0x60000018 <_start+24>                         │

Next stepi brings me to 0x60010000


2014-06-10 17:25 GMT+04:00 Dale R. Worley <address@hidden>:
>> From: "Matwey V. Kornilov" <address@hidden>
>>
>> Could you please explain me what qemu should do in the following case?
>> I have u-boot.bin and I am running following command (both 1.3.1 and 1.7
>> have the same behavior):
>>
>> qemu-system-arm -M vexpress-a9 -cpu cortex-a9 -m 1024 -kernel u-boot.bin
>> -serial stdio
>>
>> Using -s command and remote gdb I see that u-boot.bin is placed to
>> 0x60000000 (which I suppose is the begin of the RAM) and execution is
>> started from 0x60000000, but after 3 asm instructions execution pointer
>> jumps to 0x60010000 (which is in the middle of some random u-boot
>> function). So, nothing works.
>>
>> Could you please point me, how should I find where is my problem?
>
> What are the three instructions that are executed?  It appears that
> the last of the three is a jump to 0x60010000.
>
> Dale



-- 
With best regards,
Matwey V. Kornilov
http://blog.matwey.name
xmpp:address@hidden