Cross Compiling for ARM

[Robert Schuster]

Hi Ignacio,

Ignacio Lorenzo Subirá Otal schrieb:
>> Hello Ignacio,
> 
> Hello Paul, 
> I read this documentation and edited the local.conf.sample to fit my needs
>  as a first approach when I sent this e-mail but I got no good results.
> I read it quietly again and again and I could understand better the way
> openembedded works and I could get some results.
> By now, what I can obtain a kernel image and a root-disk image but none
> of them are "true". I mean, I get results in the /work directory and I find
> zImage and the root-disk in jffs2 format but when I load the i.MX21 board
> with this software it hangs. If I try to mount the root-disk image in my
> computer it says it isn't correct.
What says 'file' about the image? Does the endianness fit for your
target system?

For mounting the image on your computer: Have you properly created a
mtdblock device using the mtdram kernel modules? JFFS2 images cannot be
mounted like ext2, vfat etc. See [0].

> I don't know what fails because all the
> logs that openembedded creates are ok and it finishes working without errors
> but the truth is that it isn't working for me....
What does the bootloader say about the rootfs & kernel image? Can it
find it?

Have you tried stepping through the initial kernel startup steps with
GDB and a JTAG probe?

> I don't know what else can I do because I've used both toolchains (the one
> provided by openembedded and the one provided by freescale) and with
> both of them I get the same error.

Regards
Robert

[0] - http://www.linux-mtd.infradead.org/faq/jffs2.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openembedded.org/pipermail/openembedded-users/attachments/20080102/b9a9588e/attachment-0002.sig>