Angstrom Status On Tosa, Updated March 12, 2008 Options

[undrwater]

Speaking of keymappings; I did an

CODE

ipkg update, ipkg upgrade

which eliminated my ability to get to the Fn generated keys (numbers, punctuation, etc...)

Suspend still has the problem of freezing the prism2_usb module. Can't reload (unload or load) this module after suspend.

I've noticed some other behaviors; but they're specific to Opie or GPE.

Feeling hopeful!

[lumag]

Speaking of keymappings; I did an

CODE

ipkg update, ipkg upgrade

Angstrom 2008 uses opkg. Do you track 2008 (unstable) or 2007 (stable) branch?

which eliminated my ability to get to the Fn generated keys (numbers, punctuation, etc...)

Suspend still has the problem of freezing the prism2_usb module. Can't reload (unload or load) this module after suspend.

The workaround was pushed into 2008 branch. If you do track 2007.1, get apm-tosa-suspendfix package from 2008 feed
and install it.

I've noticed some other behaviors; but they're specific to Opie or GPE.

Tell me more, please
Most probably there should be several problems related to incorrect keymappings,

I did not test GPE at all for a long time. Currently busy with work, RL, providing upgraded kernel via OE (I plan to provide 2.6.27 or 2.6.28-rc soon) and fixing opie issues.

[undrwater]

Angstrom 2008 uses opkg. Do you track 2008 (unstable) or 2007 (stable) branch?

Not sure what you mean by "track", however update specified 2007.

The workaround was pushed into 2008 branch. If you do track 2007.1, get apm-tosa-suspendfix package from 2008 feed
and install it.

Does this mean if I use opkg, I'll be on the right track (so to speak)? Or is it editing the /etc/opkg files?

Tell me more, please
Most probably there should be several problems related to incorrect keymappings,

You jogged my memory.

• Key repeat is still too sensitive. Very easy to do www.goooooogle.commm
• Testing the sketchpad app, I discovered I could not draw a straight line; just jagged ones (even after recalibrating)
• I'd like to be able to install Minimo or Midori, but ran into the "locale not supported" error.
• Installing to SD or CF requires linking to get libs to work.

I'm sure at least a couple of the above are kernel related.

I did not test GPE at all for a long time. Currently busy with work, RL, providing upgraded kernel via OE (I plan to provide 2.6.27 or 2.6.28-rc soon) and fixing opie issues.

Your work is appreciated.

[LeTic]

Not sure what you mean by "track", however update specified 2007.

The workaround was pushed into 2008 branch. If you do track 2007.1, get apm-tosa-suspendfix package from 2008 feed
and install it.

Does this mean if I use opkg, I'll be on the right track (so to speak)? Or is it editing the /etc/opkg files?

Hey undrwater

FYI the 2008 branch is now in the autobuild feeds here : http://www.angstrom-distribution.org/unsta...autobuild/tosa/ so you can test the current development version instead of the "Old" stable. It features lots of improvements (one of them being the use of opkg instead of ipkg) and all the Tosa work from Dmitry.

[undrwater]

OK...I was looking in that directory before, but the images I downloaded still use ipkg.

I do notice the following:

CODE

Angstrom-x11-image-glibc-ipk-2008.1-test-20081127-tosa-installkit.tgz

which I suppose is the "2008" track you speak of. I'll try that out.

[EDIT]
Just tried it out. Show stopper is apparently the keyboard does not work. "new user details" screen is the first...but neither HW or SW keyboard are placing text in the fields. Orange lines are back too. This is with the above installkit and Dmitry's kernel.
[/EDIT]

[undrwater]

I pried my eyes a bit wider and found a few other of the 2008.1 images. None of the x11 images allow me to enter info into the login screens, so I tried the console image and found opkg. Suspend did not work via hardware on this image either. What's the command?

I'm curious to try e-wm...is the one that's in the feed the same as what's showing up on the openmoko devices?

I have to say it's been fun trying new stuff with this device that had been gathering dust!

[lumag]

Just tried it out. Show stopper is apparently the keyboard does not work. "new user details" screen is the first...but neither HW or SW keyboard are placing text in the fields. Orange lines are back too. This is with the above installkit and Dmitry's kernel.

For the keyboard, etc. I'm waiting for general Angstrom decision about future of X11 images (will they contain Kdrive or Xorg and which version).

Suspend did not work via hardware on this image either. What's the command?

I generally use apm -s. However if the "power" button doesn't work, could you please post the result of

CODE

grep Name /proc/bus/input/devices
grep Handlers /proc/bus/input/devices

Also please check the exact version of kernel package in those images.

[undrwater]

could you please post the result of

CODE

# grep Name /proc/bus/input/devices
N: Name="Tosa Keyboard"
N: Name="wm97xx touchscreen"

Also please check the exact version of kernel package in those images.

Not sure what you meant specifically, but here's:

CODE

# uname -a
Linux tosa 2.6.24 #1 PREEMPT Fri Nov 21 16:46:51 MSK 2008 armv5tel unknown

and:

CODE

#opkg list | grep kernel
.
.
.
kernel - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
kernel - 2.6.24-r16.1 -
kernel-2.6.24 - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
kernel-2.6.24 - 2.6.24-r16.1 -
kernel-cmdline-2.6.24 - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
kernel-cmdline-2.6.24 - 2.6.24-r16.1 -
kernel-dev - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
kernel-image-2.6.24 - 2.6.24-r17.1 - 2.6 Linux Development Kernel for Zaurus devices and iPAQ hx2750.
.
.
.

Hope that's what you needed.

BTW: apm -s worked quite nicely. Hardware button brought Tosa back to life. I had to reset my network settings (which brought back wifi), but at least the module wasn't frozen.

[lumag]

could you please post the result of

CODE

# grep Name /proc/bus/input/devices
N: Name="Tosa Keyboard"
N: Name="wm97xx touchscreen"

Also please check the exact version of kernel package in those images.

Not sure what you meant specifically, but here's:

CODE

# uname -a
Linux tosa 2.6.24 #1 PREEMPT Fri Nov 21 16:46:51 MSK 2008 armv5tel unknown

I see... please reflash the kernel with http://www.angstrom-distribution.org/unsta...24-r17-tosa.bin
It should fix the power key problem.

BTW: apm -s worked quite nicely. Hardware button brought Tosa back to life. I had to reset my network settings (which brought back wifi), but at least the module wasn't frozen.

As assumed.

[undrwater]

please reflash the kernel with http://www.angstrom-distribution.org/unsta...24-r17-tosa.bin
It should fix the power key problem.

It does. But are all of the debug options turned on? It's very noisy!

Also, I was playing around a bit and got e-wm installed and running up to the point where locale is asked for...but it doesn't seem to register the touch screen. Is that a kernel thing, or an e thing?

[lumag]

please reflash the kernel with http://www.angstrom-distribution.org/unsta...24-r17-tosa.bin
It should fix the power key problem.

It does. But are all of the debug options turned on? It's very noisy!

Most probably the debug is on as it's unstable release. At least I didn't do anything special for enabling it

Also, I was playing around a bit and got e-wm installed and running up to the point where locale is asked for...but it doesn't seem to register the touch screen. Is that a kernel thing, or an e thing?

As the ts does work in opie, I'd assume that this is the E problem.

[undrwater]

I think everything looks good so fart at this point except key repeat. Once again, if I type www.google.com, I typically get wwwww.gooooogle.com. This behavior showed up in previous kernels and has a bug filed.

Thanks again...and Happy New Year!!

[AsLan^]

I know you don't need the instructions as you are an experienced tosa users but in case somebody needs them :

I'm almost tearing my hair out with the latest Angstrom! Hopefully someone can help me figure all this out.

I installed openembedded and tried building a couple of images, basically, helloworld-image and console-image. And I ended up with an angstrom-dev/deploy/glibc/images/tosa directory that looks like this:

Angstrom-helloworld-image-glibc-ipk-2009.X-test-20090529-tosa-installkit.tgz
Angstrom-helloworld-image-glibc-ipk-2009.X-test-20090529-tosa-installkit.tgz.md5
Angstrom-helloworld-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.jffs2
Angstrom-helloworld-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.tar.bz2
Angstrom-helloworld-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.tar.gz
Angstrom-helloworld-image-glibc-ipk-2009.X-test-20090529-tosa-testlab
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa-installkit.tgz
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa-installkit.tgz.md5
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.cpio.gz
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.jffs2
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.tar.bz2
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa.rootfs.tar.gz
Angstrom-initramfs-kexecboot-image-glibc-ipk-2009.X-test-20090529-tosa-testlab
helloworld-image-tosa.jffs2
helloworld-image-tosa.tar.bz2
helloworld-image-tosa.tar.gz
initramfs-kexecboot-image-tosa.cpio.gz
initramfs-kexecboot-image-tosa.jffs2
initramfs-kexecboot-image-tosa.tar.bz2
initramfs-kexecboot-image-tosa.tar.gz
modules-2.6.29-r0-tosa.tgz
updater.sh.tosa
zImage-2.6.29-r0-tosa.bin
zImage-kexecboot-2.6.24-r0-tosa.bin
zImage-kexecboot-tosa.bin
zImage-tosa.bin

I have no idea what all these do or how to use them. What I did try is various combinations of flashing a zImage.bin and initrd.bin using option 4 of the maintenance menu (as specified per earlier instructions). The flashing usually works alright but then when it boots, it loads a bootloader that cannot find any bootable devices. On a hunch, I tried unpacking one of the tar.gz images to an ext2 formatted SD card and tried booting with that plugged in and it was detected by the bootloader. Booting it sort of worked but it quickly exited back to the bootloader (I assume that was just a problem with the image I unpacked).

My questions are:

What is the correct usage for all of these file types, i.e. should the .jffs2 files be renamed initrd.bin and included in the flashing process? What am I supposed to do with the bz2 and gz files? Are they only for unpacking to external media?

How do I install to the internal flash? It used to work with the stable 2007-12 build and instructions.

Is there a newer version of updater.sh (that one was not built by oe and I added it myself having picked it up from elsewhere)? The reason I ask is that when trying to flash zImage-2.6.29-r0-tosa.bin it fails during the update program with the error that the file is too big. That kernel is approximately 1.3mb while the others are 1.2mb. Is this a constraint of the SL-6000 itself? I thought it has 32mb of internal memory.

* * *

Unfortunately, none of the available documentation that I could find online talks about installing these files. I did find a small entry here Angstrom Manual which talks about what they are but not how to use them as they are all device specific. Unfortunately the tosa documentation only talks about copying the files from an installkit and flashing the device from the maintenance menu.

[ant]

Hi,

sorry for the lack of documentation, kexecboot is still in development...

Here the important bits:

Sharp Zaurus family (new method - WIP)
For every machine an installkit-${MACHINE}.tar.gz is created, containing updater.sh and zImage (the kexecboot-kernel). Unpack the installkit on a formatted card and follow the usual flashing procedure. If you want a rootfs in nand, this mus be in the .jffs2 format. Just rename your-image-rootfs.jffs2 to initrd.bin and copy it on the card whith updater.sh. On removable media, the root filesystem (your-image-rootfs.tar.gz) must be unpacked into the desired partition.

I'm pretty sure you have an outdated git tree. Please delete all the a.m. images, pull and rebuild.

Regards

Ant

[AsLan^]

Hi,

sorry for the lack of documentation, kexecboot is still in development...

Here the important bits:

Sharp Zaurus family (new method - WIP)
For every machine an installkit-${MACHINE}.tar.gz is created, containing updater.sh and zImage (the kexecboot-kernel). Unpack the installkit on a formatted card and follow the usual flashing procedure. If you want a rootfs in nand, this mus be in the .jffs2 format. Just rename your-image-rootfs.jffs2 to initrd.bin and copy it on the card whith updater.sh. On removable media, the root filesystem (your-image-rootfs.tar.gz) must be unpacked into the desired partition.

I'm pretty sure you have an outdated git tree. Please delete all the a.m. images, pull and rebuild.

Regards

Ant

Thank you for the explanation! After I get it all working I promise to update the wiki

I'm not sure what I'm doing wrong with the git tree. I set it up using the Building Angstrom Instructions literally a few days ago. Unfortunately, that didn't build correctly the first time and I made the following changes to get it to build:

I replaced my copies of:

kexec-arm-atags.patch
kexec-tools-static_1.101.bb
initramfs-kexecboot-image.bb

With copies downloaded from http://cgit.openembedded.org/ in the org.openembedded.dev branch. And I added my own copy of updater.sh.tosa after an error message reported that it couldn't find it.

Doing that allowed me to compile and make the images I was asking about above but doing a "git pull" seems to have broken it and I can't figure out how to fix it so...

I've just decided to delete everything start over following the OE Getting Started Instructions the only notable difference appears to be not checking out the stable/2009 branch.