It is not a bug but my lack of knowledge in the Debian packaging handling. I removed all the relevant packages, deleted the wrong repositories and
installed the packages again and after that the emdebian tools. I could file a bug to highlight that the emdebian repositories should NOT be on
the host machine. Just give me the url and maybe point me to the bug report rules (I suppose you have some requirements, style, necessary information etc.)
Right now I got the emdebian-arm.tgz which has a size of 25 MByte uncompressed which means it will fit into the flash of the XScale PXA270 board.
In the emdebian how to it is mentioned that a debian like system is required to update the romfs. This is not the case for me. We have uboot running together
with this kernel version:
Hit any key to stop autoboot: 0
**** Try to boot from Flash ****
## Booting image at 00040000 ...
Image Name: Linux Kernel Image
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2367256 Bytes = 2.3 MB
Load Address: a0008000
Entry Point: a0008000
Verifying Checksum ... OK
Starting kernel ...
Linux version 126.96.36.199-ELinOS-469 (joye@hrwks7001-l) (gcc version 3.4.4 (ELinO8
CPU: XScale-PXA270  revision 7 (ARMv5TE), cr=0000397f
The flash is partitioned into:
0x00000000-0x00040000 : "Bootloader"
0x00040000-0x00400000 : "Kernel"
0x00400000-0x02000000 : "Filesystem"
I suppose it won't work to replace the data on 0x00400000 with the packed .tgz data. Do you have any hints on how to proceed?
On Tue, 3 Feb 2009 09:15:26 +0100
"Hoefle Marco" <Marco.Hoefle@nanotronic.ch> wrote:
> >> our customer is using uClinux from a linux distributer charging indirectly
> >> licensing fees for things they took from uClinux.org and other community
> >> developed stuff. Furthermore, their drivers are buggy and not well tested.
> >> Thus I thought emdebian might be a good alternative with well tested drivers
> >> and packages. Thus I want to make a emdebian crush demo
> >> on their board they are currently using (based on a Xscale 270PXA, 16 MByte
> >> Flash and 64 MByte RAM). The problem is that I am not familiar with debian
> >> packages (we use Redhat).
Which is where the problems started.
I think I can see where you've gone wrong now.
*There is NO upgrade path from Debian to Emdebian Crush*
i.e. you cannot install Debian onto an ARM board and then expect it to
upgrade to Crush. You must build a root filesystem for Crush and
install it *instead* of Debian.
To build packages for Crush, you need to be running Debian on your
desktop / powerful laptop.
Emdebian Grip is different - you can install Debian and then migrate to
Grip (that is how Grip works with the Debian Installer).
Crush is VERY different - there is currently no support for migrating
from Debian to Crush because the release freeze for Debian Lenny has
prevented any of the fixes being introduced into Debian to allow such a
migration, partially due to an inability to update the version of
busybox used in Debian right now.
> >> What I did for the demo so far:
> >> - I installed debian lenny and the emdebian tools using the repositories
> >> http://build.emdebian.org/emdebian/ unstable main
> >> http://www.emdebian.org/debian/ unstable main
WRONG. I didn't notice this at first, you do NOT use the
emdebian.org/emdebian repositories except AFTER installation onto the
www.emdebian.org and buildd.emdebian.org are the same machine.
emdebian-tools does all this for you, correctly, anyway. I don't
understand why you thought it necessary to tinker with the sources
lists in the first place, let alone why you added the
Please file a bug against buildd.emdebian.org indicating where the
website can be improved to stop this happening again.
> >> And a few other things are not clear to me: I saw that uboot
> >> is referenced on the emdebian website. After the emdebian crush flow is
> >> there a kernel and a file system image which can be loaded with uboot?
You need to provide the kernel (and modules) yourself. There are no
kernels for Emdebian Crush at this time.
> >> Is there a step by step document available on how to install emdebian crush
> >> on a emedded system with little storage resources?
If sections are unclear or misleading, please file bugs against
> >From my point of view, emdebian needs a little work to do all you want to do.
> It is not so much I want, just a little emdebian demo ;-).
Emdebian isn't at that stage right now. The learning curve is steep and
it has to start with knowing how Debian works. Emdebian *is* Debian,
you do need to be familiar with Debian before Emdebian is likely to
make any sense.
That won't change until the next Debian release *after* Lenny.