[okl4-developer] OKL4 on openmoko simulator

[David Mirabito]

Hi Lukas,

It sounds like you're running Qemu in graphical mode? If so, the  
naming example does not display anything to the framebuffer, so you  
wouldn't see it anyway :)

Try adding the --nographic option to get a u-boot prompt and start  
with 'bootelf 0x31000000'
(note that --nographic will forward ctrl-c to the simulation, to quit  
it's ctrl-a, x)

Alternatively, you can pass '-serial stdio' and get both the graphical  
display and the serial console, and ctrl-c to the console will exit  
the simulation.

Please let me know how this goes, or if you need assistance ...
   - David Mirabito


On 19/03/2008, at 12:54 AM, Lukas HANEL wrote:

> Hi
>
> I have no boot loader shell. I can only use space and return.
>
> However, using qemu I switched to the qemu monitor and used memsave to
> dump the portion to memory. Don't know, however, if its the "same"
> memory. E.g memsave seems to operate on virtual memory:
> memsave addr size file -- save to disk virtual memory dump starting at
> 'addr' of size 'size'
> The outcome is, however the same as the image.boot file:
> 0000000 457f 464c 0101 6101 0000 0000 0000 0000
> 0000010 0002 0028 0001 0000 0000 3000 0034 0000
> 0000020 e370 000d 0202 0000 0034 0020 0017 0028
> 0000030 0043 0042 0001 0000 8000 0000 0000 3000
> ...
>
> Using following binaries:
> OpenMoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-20080314-fic- 
> gta01.rootfs.jffs2
> u-boot-gta01bv4-1.3.0+git20071201+svnr3484-r0.bin
> uImage-2.6.24+svnr4184-r4165-r3-neo1973.bin
>
>
> Geoffrey Lee wrote:
>> On Tue, Mar 18, 2008 at 09:54:02AM +0100, Lukas HANEL wrote:
>>
>>> Hi,
>>>
>>> I have a problem with the simulation of OKL4 gta01 platform.
>>> I build the qemu-neo173 simulator following the steps in the  
>>> openmoko
>>> wiki. So my version is founded on the latest versions of the  
>>> tools, as
>>> downloaded by the script.
>>>
>>> When I start the simulation using the following command, qemu  
>>> starts but
>>> there is no output.
>>> ./tools/build.py machine=gta01 project=iguana example=naming  
>>> simulate
>>>
>>> Using the qemu command like for openmoko, displays the boot options.
>>> After selecting Boot, the bootloader complains about missing magic
>>> numbers in the image.
>>>
>>> Listing:
>>> qemu-system-arm -M gta01 -m 130 -mtdblock openmoko/openmoko- 
>>> flash.image
>>> -kernel /home/lukas/okl4_release_1.5.2/build/images/image.boot -usb
>>> -show-cursor
>>>
>>> ## Booting Image at 30100000 ...
>>> Bad Magic Number
>>>
>>
>> Hi
>>
>> Can you dump the memory in u-boot at 0x30100000 and see if there's
>> anything there?  e.g.
>>
>> GTA01Bv4 # md 0x31000000
>> 31000000: 464c457f 61010101 00000000 00000000    .ELF...a........
>> 31000010: 00280002 00000001 30000000 00000034    ..(........04...
>> 31000020: 007e4510 00000202 00200034 00280013    .E~.....4. ...(.
>> 31000030: 00530054 00000001 00008000 30000000    T.S............0
>>
>> (note that my local copy is a bit older so things are at 0x31000000.)
>>
>> 	-gl
>>
>>
>>> Could you give me some hints what version of qemu-neo to use and  
>>> whether
>>> additional adoptions are necessary to run it with the 1.5.2 OKL4  
>>> snapshot.
>>>
>>> Lukas
>>>
>>> PS: the skyeye simulation works.
>>>
>>> _______________________________________________
>>> Developer mailing list
>>> Developer at okl4.org
>>> https://lists.okl4.org/mailman/listinfo/developer
>>>
>
> _______________________________________________
> Developer mailing list
> Developer at okl4.org
> https://lists.okl4.org/mailman/listinfo/developer