Angstrom and h2200

Angstrom and h2200

[Nicola Ranaldo]

New test images boots over my ipaq h2200, and bug #1677 is now closed, howewer 
i had to disable the S10checkroot.sh startup as it wanted to run fsck over a 
readwrite mounted filesystem, claiming it's very dangerous and asking the 
user for a confirmation. This should be patched in some manner. I tried to 
change the fs to reiserfs, rebuilding the kernel, but i was not lucky. To 
disable the bootsplash i readed the S00psplash script and patched startup.txt 
of haret, but to have a console over the frame buffer i ran make menuconfig 
on the kernel dir, changed the config and after that removed the kernel 
compile stamp, and runned again bitbake amstrong-gpe-image again.
Wath's the official/legacy method to give a different configuration to the 
kernel?
And now some other issues about gpe-image:
* the usb0-eth device is not present, is it normal?
* keyboard, fonts are bigger then rects and sometimes i have to hold down the 
pen to use it, if not the keyboard acts as i pressed the key and a backspace
* i was not able to compile a custom gpe-image (i used the prereleased for 
tests), the build failed on package freetype with:
./configure: line 2943: i686-pc-linux-gnu: command not found
configure: error: native C compiler is not working
* the last, may i use some kind of emulator before deploying the fs image to 
the ipaq?

Hoping i'm not boring you
Best Regards

	Nicola Ranaldo

Re: Angstrom and h2200

[Nicola Ranaldo]

On Sunday 25 February 2007 19:34:30 Paul Sokolovsky wrote:

Hello Paul!

[...]
> Friday, February 23, 2007, 2:26:36 PM, you wrote:
> > Hoping i'm not boring you
>
>   No, but this is OpenEmbedded list. Your report would give more use
> if posted to the proper list - angstrom-distro-users (where I route
> this reply).

Ok!, i will redirect angstrom related questions there.

> > New test images boots over my ipaq h2200, and bug #1677 is now closed,
> > howewer i had to disable the S10checkroot.sh startup as it wanted to run
> > fsck over a readwrite mounted filesystem, claiming it's very dangerous
> > and asking the user for a confirmation. This should be patched in some
> > manner.
>
>   Well, this is one boring problem which is very hard to solve,
> because it is rooted in machine idiosyncrasies. You fix it for one
> machine, and it pops up with another, etc., until it goes thru the
> full circle, something changes outside, and the first machine breaks
> again.
>
>   Someone indeed should break this vicious cycle and make a solution
> which either cuts down mentioned idiosyncrasies or flies above them.

Are there so many differences between machines? i thinked the only difference 
was in the kernel and input devices configuration files.

>   There's an RFC to have consistent (feature-wise) defconfigs for all
> machines. h3900 & h4000 already joined the party. You're welcome to
> work towards h2200 support, please start here:
> http://defconfigman.sourceforge.net/
>
> > And now some other issues about gpe-image:
> > * the usb0-eth device is not present, is it normal?
>
>   No, it is not. See about defconfig consistency above.

I will take a look at it, howewer to customize my kernel configuration is 
there a tool, bitbake config, etc, to submit a .config or to run make 
menuconfig before building the kernel?

[...]
> > * i was not able to compile a custom gpe-image (i used the prereleased
> > for tests), the build failed on package freetype with:
> > ./configure: line 2943: i686-pc-linux-gnu: command not found
> > configure: error: native C compiler is not working
>
>   There's some incompatibility with freetype's configure and your
> gentoo gcc.

Other peoples seems to have the same problem,  with patch in #1906 it seems to 
be fixed, if some one may review the proposed patch and commit to the 
tree.

> > * the last, may i use some kind of emulator before deploying the fs image
> > to the ipaq?
>
>   Yes, QEMU.

fork in a new thread !

Thanks Paul!

	Nicola Ranaldo

testing with qemu, was Re: Angstrom and h2200

[Nicola Ranaldo]

On Sunday 25 February 2007 19:34:30 Paul Sokolovsky wrote:
[...]
> > * the last, may i use some kind of emulator before deploying the fs image
> > to the ipaq?
>
>   Yes, QEMU.

I already use it to emulate x86 machines, but i was not able before to find 
the qemu-system-arm command!!! the poky-runqemu documentation seems to be 
complex, to run the test images at 
http://www.angstrom-distribution.org/unstable/images/20070120/qemuarm/  i 
simply used the following command:

qemu-system-arm -M versatilepb -kernel 
zImage-2.6.18-qemuarm-20070120215313.bin -hda 
Angstrom-gpe-image-test-20070120-qemuarm.rootfs.ext2  -append "root=/dev/sda"
When the system asked to calibrate to touchscreen i pressed ESC and gpe 
appeared!
I did not use the file modules-2.6.18-qemuarm.tgz.... is there a reason it's 
there?

thanks

	Nicola Ranaldo

Re: testing with qemu, was Re: Angstrom and h2200

[Patrick Fischer]

Nicola Ranaldo wrote:
> On Sunday 25 February 2007 19:34:30 Paul Sokolovsky wrote:
> [...]
>   
>>> * the last, may i use some kind of emulator before deploying the fs image
>>> to the ipaq?
>>>       
>>   Yes, QEMU.
>>     
>
> I already use it to emulate x86 machines, but i was not able before to find 
> the qemu-system-arm command!!! the poky-runqemu documentation seems to be 
> complex, to run the test images at 
> http://www.angstrom-distribution.org/unstable/images/20070120/qemuarm/  i 
> simply used the following command:
>
> qemu-system-arm -M versatilepb -kernel 
> zImage-2.6.18-qemuarm-20070120215313.bin -hda 
> Angstrom-gpe-image-test-20070120-qemuarm.rootfs.ext2  -append "root=/dev/sda"
> When the system asked to calibrate to touchscreen i pressed ESC and gpe 
> appeared!
> I did not use the file modules-2.6.18-qemuarm.tgz.... is there a reason it's 
> there?
>
> thanks
>
> 	Nicola Ranaldo
>   
This is my test script for qemu

#!/bin/sh

KERNEL=$1
IMAGE=$2
IP=192.168.1.42
GATEWAY=192.168.1.1 

cp $KERNEL /tmp/kernel.bin
cp $IMAGE /tmp/image.ext2.gz
gzip -d /tmp/image.ext2.gz

/usr/local/bin/qemu -kernel /tmp/kernel.bin -std-vga \
-append "root=/dev/hda rw mem=64M ip=${IP}::${GATEWAY}:255.255.255.0" \
-net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script= \
-hda /tmp/image.ext2 

rm /tmp/image.ext2
rm /tmp/kernel.bin

---
call it like

./testqemu.sh tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/bootstrap-image-qemux86-20070112211142.rootfs.ext2.gz




-- 
Mit freundlichen Grüßen
Best Regards 

Dipl.-Ing. (FH) Patrick Fischer
Software Engineer


Meet 4G Systems at CeBIT 
March 15th - 21st, Hanover 
Hall 13, Stand B86


4G Systems GmbH  
Jarrestrasse 4,
D-22303 Hamburg

Phone: +49 (0)40-70 38 33-327
Fax:   +49 (0)40-70 38 33-700
Mail: Patrick.Fischer@4g-systems.com
www.4g-systems.com

Amtsgericht Hamburg, HRB 85342
Geschäftsführer: Enrico Just, Achim Schaller

Re: testing with qemu, was Re: Angstrom and h2200

[Richard Purdie]

On Mon, 2007-02-26 at 13:03 +0100, Patrick Fischer wrote: 
> Nicola Ranaldo wrote:
> > I already use it to emulate x86 machines, but i was not able before to find 
> > the qemu-system-arm command!!! the poky-runqemu documentation seems to be 
> > complex, to run the test images at 
> > http://www.angstrom-distribution.org/unstable/images/20070120/qemuarm/  i 
> > simply used the following command:
> >
> > qemu-system-arm -M versatilepb -kernel 
> > zImage-2.6.18-qemuarm-20070120215313.bin -hda 
> > Angstrom-gpe-image-test-20070120-qemuarm.rootfs.ext2  -append "root=/dev/sda"
> > When the system asked to calibrate to touchscreen i pressed ESC and gpe 
> > appeared!
> >
> This is my test script for qemu

> ./testqemu.sh tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/bootstrap-image-qemux86-20070112211142.rootfs.ext2.gz

Lets reinvent the wheel too...

This should work just the same as 
poky-runqemu tmp/deploy/images/bzImage-qemux86.bin tmp/deploy/images/bootstrap-image-qemux86-20070112211142.rootfs.ext2

(except the same command works with qemuarm and several zaurus images if
you have the right qemu)

Note you have to use an ext2 image, not a gzipped one but my setup
generates ext2 files, not ext2.gz ones...

> > I did not use the file modules-2.6.18-qemuarm.tgz.... is there a 
> > reason it's there?

Anyone developing a kernel finds it useful, otherwise just ignore it. 

Regards,

Richard