![]() ![]() |
Jan 10 2005, 07:48 AM
Post
#1
|
|
|
Group: Members Posts: 225 Joined: 9-December 03 Member No.: 1,104 |
Hi,
I've successfully built a new rootfs of OZ GPE 3.5.x for my SL-5600 including matchbox 0.9 and updated gpe packages (I've created a custom distro from openzarurus 3.5.3 and familiar 0.8.1). It's the first time I'm using OE so please don't flame me... :-) I've got the following under "tmp/deploy/images": CODE -rw-r--r-- 1 cedric users 13352960 Jan 10 16:07 gpe-image-poodle-20050110141435.rootfs.jffs2.bin -rw-r--r-- 1 cedric users 984364 Jan 10 15:57 zImage-poodle-20050110141435.bin I've renamed the two files to "zImage" and "initrd.bin" and flash them using the SL-5600 updater.sh from the OZ 3.5.2 release. After a success flash, I'm getting the following during the boot process and that's it... no GPE... :-( CODE RAMDISK: Couldn't find valid RAM disk image starting at 0. Freeing: initrd memory: 4096K VFS: Mounted root (jffs2 filesystem). Freeing init memory: 84K The goal of this custom rom was to test the new updated packages and the SL-5600 kernel without the cache bug errata enabled. Previously this, I've got the OZ GPE 3.5.2 release running perfectly... Ced. |
|
|
|
Jan 10 2005, 12:34 PM
Post
#2
|
|
![]() Group: Members Posts: 2,821 Joined: 13-September 04 From: Wasilla Ak. Member No.: 4,572 |
I can't help, but i amglad you started this thread.
Some directions (maybe they exist, but i have yet to find them) on how to set up oe built images to flash the different zs would be really helpful. I am currently having analagous problems with an opie image i built for my 6000. |
|
|
|
Jan 12 2005, 09:01 AM
Post
#3
|
|
|
Group: Members Posts: 60 Joined: 3-November 04 Member No.: 5,332 |
The only thing I can think of is that maybe you flashed a .jffs2.bz2 file instead of the jffs2 file.
|
|
|
|
Jan 13 2005, 01:45 PM
Post
#4
|
|
![]() Group: Members Posts: 2,821 Joined: 13-September 04 From: Wasilla Ak. Member No.: 4,572 |
maybe try a different updater? the one for the 6k is pretty unique.. i have to use one from nevarrie to try my own stuff ( my earlier problem was that i compiled crap, apparently). I don't remember the 3.5.2 5600 updater being weird, but it is an easy thing to check out.
|
|
|
|
Jan 14 2005, 01:40 AM
Post
#5
|
|
|
Group: Members Posts: 225 Joined: 9-December 03 Member No.: 1,104 |
Finally I've find out my problem... I've setup OE to use the gcc toolchain 3.4.3 and it look like it doesn't produce valid binary. Is it due to the new "visibility" patch? (http://www.nedprod.com/programs/gccvisibility.html)
It's ok with gcc 3.4.2. |
|
|
|
Jan 14 2005, 02:23 AM
Post
#6
|
|
|
Group: Members Posts: 60 Joined: 3-November 04 Member No.: 5,332 |
CODE $ ./arm-linux-gcc --version arm-linux-gcc (GCC) 3.4.3 Copyright (C) 2004 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Checking my gcc binary it seems I'm running 3.4.3 (with the visibility patch), and without any problem. It's my understanding though that the kernel isn't even built with that cross compiler, but a prebuilt 2.95.3 toolchain so it's compatible with the closed source Sharp binaries. If that's right, I can't imaging why 3.4.2 worked or made a difference. I think there's a good chance it was something else that made it successfull. |
|
|
|
Jan 18 2005, 07:36 PM
Post
#7
|
|
|
Group: Members Posts: 102 Joined: 11-October 04 Member No.: 4,962 |
So are you still using GPE on your 5600? How is it working?
|
|
|
|
Feb 22 2005, 12:24 AM
Post
#8
|
|
|
Group: Members Posts: 23 Joined: 17-February 05 Member No.: 6,482 |
Hi,
Any chance of you posting the images up somewhere for others to try? I'm trying to either a) find good instructions on building custom roms, or bye, Victor |
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 17th May 2013 - 09:35 PM |