Messages

1

6000 - Tosa / Angstrom Status On Tosa

« on: June 05, 2009, 04:44:16 am »

Okay, two more problems have arisen...

1. Building base-image or console-image fails at the wlan-ng packages. Here is the log for wlan-ng modules.

NOTE: make CC=ccache arm-angstrom-linux-gnueabi-gcc -march=armv5te -mtune=xscale -mno-thumb-interwork -mno-thumb LD=arm-angstrom-linux-gnueabi-ld PARALLEL_MAKE= -C src all
make: Entering directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src'
set -e; for d in mkmeta shared p80211 prism2; do make WLAN_SRC=/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/ -C $d ; done
make[1]: Entering directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/mkmeta'
mkdir -p obj
make[1]: Leaving directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/mkmeta'
make[1]: Entering directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/shared'
Nothing to do...
make[1]: Leaving directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/shared'
make[1]: Entering directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/p80211'
make -C /home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/linux-2.6.29-r4/linux-2.6.29 M='/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/p80211' WLAN_SRC=/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/ modules
make: Entering an unknown directory
make: *** /home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/linux-2.6.29-r4/linux-2.6.29: No such file or directory.  Stop.
make: Leaving an unknown directory
make[1]: *** [default] Error 2
make[1]: Leaving directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src/p80211'
make: *** [all] Error 2
make: Leaving directory `/home/fredrick/oe/angstrom-dev/work/tosa-angstrom-linux-gnueabi/wlan-ng-modules-0.2.8+svnr1859-r0/trunk/src'
FATAL: oe_runmake failed

It appears to be a file not found error but I haven't modified the tree at all and I did a "git pull" before building.

2. Two kernels were built (2.6.24-r13 and 2.6.29-r5) as well as updater.sh.tosa. Only 2.6.24-r13 can be flashed using updater.sh.tosa, 2.6.29-r5 gives the error message that the file is too big. This is a problem because as you know, the reason I am trying to get this all up and running is so I can take a shot at installing Android and I believe Android requires a 2.6.25 or higher kernel to work.

2

6000 - Tosa / Angstrom Status On Tosa

« on: June 02, 2009, 03:09:24 am »

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.

3

Android / Android Possible On Sl-6000

« on: May 29, 2009, 04:35:46 am »

Setting up bitbake (Poky or OpenEmbedded) is a good and quick option to get a working build environment. You could tweak one of the provided kernel packages easily to build a kernel for the tosa, even with the latest 2.6.30 sources. The latest kernel should work using stock kernel.org sources without the need for patches.

To get the latest Android version you could rip the file system from the emulator (as I did with the pre-releases) or rebuild it from source (as described here)

Unfortunately, I've run into some problems with openembedded and building tosa images. I've posted the details over here in the tosa forum.

If you or anyone else following this thread can get me back on track I'd appreciate it

4

6000 - Tosa / Angstrom Status On Tosa

« on: May 29, 2009, 04:21:46 am »

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.

5

Android / Android Possible On Sl-6000

« on: May 27, 2009, 11:01:23 am »

Thank you for clarifying the NAND backup procedure.

The version you took from my blog actually is the M5-RC15 release, which was the last "early-look" version before version 1.0 was released. The fact that you see the "oscillating cylon eye" indicates that you've setup everything correctly. The reason Android doesn't boot is because you're kernel doesn't contain the Android Binder device driver.

Add the driver, rebuild and flash the kernel and you're all set. Sounds easy, but I know it's not

It's good to hear that it's setup properly so far

Regarding rebuilding the kernel etc. does this mean I will have to set up bitbake? (I don't think Poky Linux has a build for the tosa).

Also, how do I go about getting the newer version of Android, is it just a matter of downloading the Android SDK and locating the tar.gz file? (getting ahead of myself )

6

Android / Android Possible On Sl-6000

« on: May 27, 2009, 08:16:48 am »

finally, use the D+M boot option to take a rom snapshop and publish

I'm afraid I also don't know how to specify any boot options. I'm not running any kind of boot manager.

7

Android / Android Possible On Sl-6000

« on: May 27, 2009, 08:05:41 am »

Okay, I got it to the oscillating cylon eye but it doesn't go any further.

I first flashed a small Angstrom console image onto the device. Then I copied cortez's SL-C3x00 Android image to an ext2 formatted SD card (the image I used didn't recognize CF cards or ext3 format).

Then booted the Z and untarred the android image onto the card (I recommend using the -v switch with tar as it took about 3 hours).

Then I chrooted to /media/card

There is a shell script here called start. The first thing it does is tar up /dev and untar it to /home/root/android-root/dev. I performed this part of the script manually because I like to include the -v switch (then removed the doit placeholder file - take a look at the script).

I then ran the start script and it booted into the oscillating eye.

The version of Angstrom I'm using is 2007.12-r8 tosa console image. The Android I used was the  SL-C3x00 image from Omegamoon blog (but I don't know what version it is).

If anyone knows of a more functional Angstrom image for the Tosa that would help. The one I'm using has no wireless so I can't even ssh in.

8

Android / Android Possible On Sl-6000

« on: May 22, 2009, 01:48:10 am »

Sorry for not posting this in the Tosa forum but there's like 20 sticky threads in there so I figure it would probably be overlooked (and it is Android related too).

I would like to try getting Android on the 6000 but I'm not really sure how to go about doing it.

Do we have to use the Angstrom distribution kernel and put Android on top of it (like how cortez is doing it on the 3000)? Is there some way we can make an easy to flash distribution?

I'm not really sure where to start, and some things that might be obvious to others are unknown to me (for example, I can't figure out how to turn the tar.gz packages built by the Angstrom auto-builder into an installable image for my 6000) so I need help. But, I'm a pretty quick learner and if anyone's interested in helping me I'd like to give it a shot.

Android with Angstrom could be the modern OS that revives our 6000's and makes them useful again!

9

Personal Java/Jeode/J2ME Personal Profile / Using Netbeans To Build Java Apps

« on: December 28, 2006, 09:48:12 pm »

Below is my original post that someone might find useful...

But right after finagling with this for hours (and starting this thread), I discovered a very simple way to do it without all these plugins.

Basically my problem stemmed from the fact that I couldn't find a template for an AWT Frame in NetBeans so for some reason I assumed it didn't exist.

It's "hidden" in the "New File" dialog. I was only using the right click "New" which only shows JFrames, bah!

Anyway... you still need to set the Source Level to 1.3

Bah humbug, that was my morning

This works for me using Windows running on Parallels and running the resultant app on my SL-6000.

Install NetBeans 5.5

Install NetBeans 5.5 Mobility Pack for CDC

Install Nokia Series 80 Platform SDK for Symbian OS, for Java, Personal Profile (download the Personal Profile version as opposed to the MIDP one).

Be sure to register the Nokia platform in NetBeans from the Java Platform Manager menu.

In NetBeans:

Choose New Project.
Select CDC Application.
Select Nokia S80 CDC S80_DP2.0_PP_SDK as your Platform, CDC S80_DP2.0_PP_SDK as your Device, and PP-1.0 as your Profile (these should be default).
Name your project, leave other options as default.

You can now build your app as desired.

I personally find it helpful to include a "Close" button into the interface so you can end the program without having to close the Nokia emulator which take a while to load (at least in Parallels).

To create a jar runnable on the Zaurus:

Right click your project and select Properties.
Select Sources.
Change Source Level to 1.3 (for some reason this doesn't get saved on restarts) and click OK.
Right click your project again.
Select Build Target Bundle.

The resultant jar file will be placed in the target directory of your NetBeans project directory.

Copy that jar file to the Zaurus and run using the command: evm -jar AppName.jar

10

General Discussion / New Zaurus This Summer?

« on: June 08, 2005, 05:47:58 pm »

Anybody know why Sharp hasnt moved to a faster Xscale processor ?

11

Personal Java/Jeode/J2ME Personal Profile / Swing on SL-6000

« on: May 30, 2005, 07:13:50 pm »

smuelas, you sir, are the man !

it all works now ! I cant believe I never noticed that jeode and personal java were two seperate programs !

Thank you for all your help,

AsLan^

12

Personal Java/Jeode/J2ME Personal Profile / Swing on SL-6000

« on: May 30, 2005, 06:16:13 am »

Thank you for taking the time to post that, unfortunately I still get the same error !

Perhaps its my JVM... evm -showversion displays

java version "J2ME Personal Profile for Zaurus 1.0"
J2ME Personal Profile 1.0 (build 1.0_fcs-b25)
J2ME CDC-HI 1.0_v01

Is this the same as yours ?

13

Personal Java/Jeode/J2ME Personal Profile / Swing on SL-6000

« on: May 26, 2005, 10:43:06 pm »

Hi smuelas,

well I tried removing the WindowDestroyer lines but no dice, I still get the same error. Could you please post your classes.zip and swingZ.jar I would be most grateful.

Also, thanks for the code tidbit

14

User Request for Applications / Zaurus = Ipod?

« on: May 25, 2005, 05:21:20 am »

The easiest thing to do is to use an ftp-client to log into your Zaurus and upload whatever songs you want. Thats pretty much what I do when I want to put music on the zaurus.

Just to be more clear, use iTunes to generate a playlist that you think you'll want to here. Make a temp folder on your desktop, select all the songs in that playlist and drag it to that temp folder, then use a decent ftp-client ot log into the Z and upload that temp folder to a memory card or whatever... if you have DRM'd songs you would of course have to un-DRM them with hymn and use some other utility to make them into mp3s.

EDIT: I actually just re-read your post and saw that you were already doing exactly that... can I suggest using smart playlists to help with your 17,000 songs

15

Personal Java/Jeode/J2ME Personal Profile / Swing on SL-6000

« on: May 23, 2005, 08:53:34 am »

Hi smuelas, I tried a couple of different classes.zip from the blackdown java 1.1.8  jdk, specifically i386 v3, arm v1, and arm v2 and I got the same error each time while trying to compile...

java.lang.NoSuchMethodError: java.lang.Character: method isJavaLetterOrDigit©Z not found

followed by at sun.tools.blah for about ten lines.

Any ideas ? is there a specific version of classes.zip that I should be using ?

Thanks for your help

oh and the program I am trying to compile is very simple... its from a java textbook.

import javax.swing.*;

/**
   A simple demo of a window with swing
*/

public class FirstSwingDemo
{
   public static final int WIDTH = 300;
   
   public static final int HEIGHT = 200;
   
   public static void main(String[] args)
   {
      JFrame myWindow = new JFrame();
      myWindow.setSize(WIDTH, HEIGHT);
      
      JLabel myLabel = new JLabel("Please dont click that button");
      
      myWindow.getContentPane().add(myLabel);
      
      WindowDestroyer myListener = new WindowDestroyer();
      myWindow.addWindowListener(myListener);
      
      myWindow.setVisible(true);
      
   }
   
}