I've just uploaded a tar file containing a few useful bits and pieces suitable for installing on the empeg-car. This includes the terminfo files necessary to make vi work.

It is accessible from the standard upgrades page at http://www2.empeg.com/upgrades/.

--
Mike Crowe
I may not be speaking on behalf of empeg above :-)

Thanks Mike!

I was able to newfs hda2 and mount. However, maybe I'm missing something, but how does one
mount / as rw? Linking terminfo and other deeds are difficult if you can't write to the / filesystem.

Thanks for any info.

-chris

Something like:

mount -n -o remount rw /

Should work. I didn't have any problems mkfs'ing
/dev/hda2. Now if building the cross compiler was
as easy.... http://www.objsw.com/CrossGCC/

Any of the empeg peeps like to give us a clue to
how exactly they did theirs? I found the gcc cross
compiler faq - but wasn't sure what type the tarfer
system was - arm-aout or arm-coff. Also which lib
did you use glibc or newlib?

Some example code showing how to drive the display would
also be useful.

Ta

Paul

I have done some digging around with HotBot:

Basic details on building the gcc toolchain
More detail on the same
Links to other ARM Linux sites

Hugo has said before that empeg uses glibc 2.1 and I suspect the target type is arm-linux (i.e. elf).
There I go guessing at things I don't know anything about again, I'm sure Hugo or Mike will be along soon to correct me...

__
Unit serial number 47 (was 330 in the queue)...

I built binutlis and arm-linux-gcc without a problem (you can find if here http://members.psi.co.at/weltreise/empeg/) , but compiling glibc2.1 makes troubles:
arm-linux-gcc -nostdlib -nostartfiles -o makedb -Wl,-dynamic-linker=/usr/local/arm-linux/lib/ld-linux.so.2 ../csu/crt1.o ../csu/crti.o `arm-linux-gcc --print-file-name=crtbegin.o` makedb.o libdb.so.3 -Wl,-rpath-link=..:../math:../elf:../nss:../nis:.:../rt:../resolv:../linuxthreads ../libc.so.6 ../libc_nonshared.a -lgcc `arm-linux-gcc --print-file-name=crtend.o` ../csu/crtn.o
libdb.so.3: undefined reference to `__div0'

Why don't you empeg guys publish your tared /usr/local/arm-linux,
so that everyone can use your cross-compile-platform?

I have another wish:
Please code a submenu somewhere in the mpeg player,
which lets us suspend the player and run the programs,
which are configured in a text file (ala WM config).

Given that, I could run pilot-xfer from the player and sync
my palm-pilot with the empeg radio.

Thanks

Raphael Wegmann
[email protected]

Well, ours is configured as arm-empeg-linux :-) but apart from that you're correct.

We're running egcs-1.1.2 with philb's 19990325 patch and binutils 2.9.1.0.19a with philb's 19981230 patch. These are all quite old versions now and I'll probably try and play with gcc-2.95 and the 2.9.5 versions of binutils soon.

We did have trouble building the toolchain the first time but the most important thing to remember is when building gcc don't worry if it dies with an error - you've probably got enough of it compiled to build a libc and that's what you need to build the rest. Once you've built libc you can go back and build the rest of gcc including g++ and even the Fortran compiler I believe.

Also, take a look at http://developer.intel.com/design/strong/applnots/sa1100lx/getstart.htm

--
Mike Crowe
I may not be speaking on behalf of empeg above :-)

There are scripts called rw and ro which mount both the root and music partitions readwrite and readonly respectively.

If, like me, you find the time taken to remount the music partition a pain (and my music partition is only 1.5Gb) then you might like to edit the rw script so it only mounts the root partition readwrite. Leave the ro script mounting both drives just in case.

--
Mike Crowe
I may not be speaking on behalf of empeg above :-)

even the Fortran compiler I believe

Now that is a scary thought, empeg visuals written in Fortran77...

__
Unit serial number 47 (was 330 in the queue)...