From: Alex Raimondi <mailinglist@miromico.ch>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: Openembedded for AVR32
Date: Thu, 23 Oct 2008 09:51:36 +0200 [thread overview]
Message-ID: <49002D08.1000905@miromico.ch> (raw)
In-Reply-To: <gdnj0q$ei6$1@ger.gmane.org>
Koen Kooi wrote:
>> Does OE for AVR32 really work?
>
> It does work if you use DISTRO=angstrom-2008.1
>
My local.conf has the following entries:
TARGET_OS = "linux-uclibc"
DISTRO = "angstrom-2008.1"
ANGSTROM_MODE = "uclibc
My minimal-image does not boot. Still segfault at init....
I am suspecting a library problem.
Could you send me a tar of a minimal-image rootfs, please?
The OE kernel does boot if we use a rootfs generated e.g. with atmel
buildroot.
OE rootfs has the same problem with all kernels compiled in all
different ways..
Any other hints?
Alex
>>
>> I had a working version about two month ago from the monotone
>> repository.
>>
>> For about three weeks we try to get it running from the latest
>> monotone repository and after the
>> transition to git from the latest git.
>>
>> Just as of this morning I grabbed a fresh new clone from the git
>> repository.
>>
>> OE does compile (minimal-image). But I can't boot the image.
>>
>> This is what I found out.
>>
>> ** Kernel **
>> OE Kernel does boot. We included a newer version (2.6.25.10) into OE
>> with our own patches. This version does boot as well.
>> Tested on ATNGW100 and our own hardware.
>>
>> ** rootfs **
>> Rootfs is mounted via NFS. From the server logs I can see, that the
>> filesystem actually is mounted. See the last lines from my bootlog:
>>
>> ------
>> at32ap700x_rtc at32ap700x_rtc.0: setting system clock to 1970-01-01
>> 00:00:00 UTC
>> (0)
>> Sending DHCP requests ., OK
>> eth0: link up (10/Half)
>> IP-Config: Got DHCP answer from 192.168.1.1, my address is 192.168.1.151
>> IP-Config: Complete:
>> device=eth0, addr=192.168.1.151, mask=255.255.255.0,
>> gw=192.168.1.1,
>> host=dhcppc1, domain=, nis-domain=(none),
>> bootserver=192.168.1.1, rootserver=192.168.1.150, rootpath=
>> Looking up port of RPC 100003/2 on 192.168.1.150
>> Looking up port of RPC 100005/1 on 192.168.1.150
>> VFS: Mounted root (nfs filesystem).
>> Freeing init memory: 76K (90000000 - 90013000)
>> init[1]: segfault at 00000008 pc 2aaac620 sp 7f931f40 ecr 24
>> init has generated signal 11 but has no handler for it
>> Kernel panic - not syncing: Attempted to kill init!
>> -------
>>
>> There is always a signal 11 in init (seg fault).
>>
>> ** init **
>> We tried different init.
>> - OE default sysvinit => segfault
>> - Busybox init => segfault
>> - No init => kernel tries to load sh => segfault
>> - Our own "hello world" app (compiled outside of OE) => segfault
>>
>> Can anyone confirm that OE for AVR32 does work?
>> How can we debug and fix this problem?
>>
>> Thanks
>>
>> Alex
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2008-10-23 7:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 13:01 Openembedded for AVR32 Alex Raimondi
2008-10-22 16:05 ` Koen Kooi
2008-10-23 7:51 ` Alex Raimondi [this message]
2008-10-23 11:38 ` Robert Wörle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49002D08.1000905@miromico.ch \
--to=mailinglist@miromico.ch \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox