[Openembedded-users] H1940 Boot Issues

Khem Raj raj.khem at gmail.com
Thu Dec 23 07:41:41 UTC 2010


On (22/12/10 23:28), openembedded at rkmorris.us wrote:
> Hi,
> 
> I have been strugging with this for quite some now, and really am stuck - so I really would appreciate any thoughts or pointers anyone has! Let me try to explain my problem.
> 
> I have been able to build OpenEmbedded on my machine, with a target of either h1940 or qemuarm - and for the console-image both build just fine. I can use the kernel for both of these (on the appropriate target), but my issue is with the rootfs. If I use the OpenEmbedded built rootfs in qemuarm, targeted for either qemuarm or the h1940 (but always using the qemuarm kernel) everything works just fine.
> 
> My issue arises when trying to use the rootfs on the h1940 - I cannot get my system to boot, and actually INIT is never launched (but the kernel seems fine). If I take an old file system that I was able to find (from Familiar Linux, ~ 2004-2005 vintage), it works fine on my h1940 (with the kernel from OpenEmbedded!) ... so the issue seems to be the rootfs. If I just replace /sbin/init.sysvinit in the Familiar Linux file system with the one from OpenEmbedded - then I get kernel panic (and no init found it says ... :-(). Oddly enough, if I use the Familiar LInux file system with qemuarm - it doesn't work, I have file system errors (and kernel panic), but the OpenEmbedded built file system (even for the h1940) works just great).
> 
> So it seems that I have some sort of filesystem incompatibility ... or am I wrong? BTW, I can load the above mentioned filesystems as ext2 or ext3 in (OpenSUSE) Linux, no issues there.
> 
> Again, any suggestions of how to fix this would be greatly appreciated!

enable USER_DEBUG in kernel .config and set that on bootloader kernel
commandline too if its uboot then pass debug user_debug=-1
this will dump some information on console on the problem. I think the
processor is S3C3210 which has arm920t core which is based on armv4t
architecture. it could be that the compiler is not defaulting to armv4t
in somecases. btw. What version of OE are you using and also tell about
the DISTRO and any customizations you did through local.conf

> 
> Thanks!
> 
> ... Russell
> 
> 
> _______________________________________________
> Openembedded-users mailing list
> Openembedded-users at linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-users




More information about the Openembedded-users mailing list