Hi Robert!, >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?
[EMAIL PROTECTED]:/OE/build/tmp/angstrom/deploy/glibc/images/mx21ads$ file Angstrom-bootstrap-image-glibc-ipk-2007.9-test-20071221-mx21ads.rootfs.jffs2 Angstrom-bootstrap-image-glibc-ipk-2007.9-test-20071221-mx21ads.rootfs.jffs2: Linux jffs2 filesystem data little endian Seems that, yes, the endianess is correct, and also, if I extract the image from the tar.gz that I order to build too, the image seems to be right but the first directory in the image is . I don't know if this is ok, or it should start with another directory rather than . in order to be a correct image. Maybe that's the problem, I'll try to build an image starting by the directory tree instead of the directory . When doing a file to the zImage... [EMAIL PROTECTED]:/OE/build/tmp/angstrom/deploy/glibc/images/mx21ads$ file zImage-mx21ads-20071220132753.bin zImage-mx21ads-20071220132753.bin: data I don't know if this is correct but it says... nothing about the file so maybe I have a problem with this... Can you give me an advice about what to use, the toolchain provided by OpenEmbedded or the one provided by Freescale?. Thanks for your help, Nacho >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 _______________________________________________ Openembedded-users mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users
