From: Christophe Aeschlimann <c.aeschlimann@acn-group.ch>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [hawkboard] OE Kernel Not Booting
Date: Tue, 18 May 2010 15:36:45 +0200 [thread overview]
Message-ID: <4BF297ED.9060301@acn-group.ch> (raw)
In-Reply-To: <hstsna$uhr$1@dough.gmane.org>
Le 18.05.2010 13:12, Koen Kooi a écrit :
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 18-05-10 10:10, Christophe Aeschlimann wrote:
>> Le 18.05.2010 09:30, Koen Kooi a écrit :
>> On 18-05-10 09:27, Christophe Aeschlimann wrote:
>>>>> Hi,
>>>>>
>>>>> We are at least three hawkboard owners that have the same issue.
>>>>>
>>>>> Building org.openembedded.dev HEAD with
>>>>>
>>>>> MACHINE= "hawkboard"
>>>>> DISTRO = "angstrom-2008.1"
>>>>>
>>>>> produces a Kernel Image that cannot be booted on our hawkboards.
>>>>>
>>>>> The behaviour is the following with the following kernel bootargs :
>>>>>
>>>>> console=ttyS2,115200n8 root=/dev/nfs
>>>>> nfsroot=172.16.147.10:/srv/nfs/hawkboard ip=172.16.100.100
>>>>> eth=0a:c1:a8:12:fa:c0
>>>>>
>>>>>> U-Boot 2009.01-dirty (Nov 26 2009 - 02:15:00)
>>
>> Try the OE built u-boot.
>>
>>> Hi Koen,
>>
>>> I haven't been able to boot using the OE generated u-boot so far.
>>
>>> But I'm a bit confused about how everything is working together.
>>
>>> Don't you have to generate an AIS image using AISGen and the OE
>>> generated u-boot image before flashing it in the UBL partition
>>> (beginning of the second erase block) ?
>
> Not that I know of. I flashed uboot using tftp and that seemed to work
> fine. That was on a prototype hawkboard which has released it magic
> smoke since then.
Ok then I assume you had a pre-installed working UBL (User Boot Loader)
in NAND @ Block 1 (0-indexed), that would initialize the board HW (EMIFA
timings, SDRAM refresh cycles, etc) load block 2 in memory (U-Boot)and
executes it. Then you could just overwrite the U-Boot NAND partition
using U-Boot tftp and nand erase / write.e commands.
But AFAIU if you don't have an UBL (E.G. because you don't have a CCS
license to modify/rebuild it) you can workaround it by using the AIS
generator that generate a "self-bootable" image. In this case we want
the OMAP-L138 RBL (ROM Bootloader) to read the AIS image from NAND (@
block 1, where the UBL is normally stored) configure the HW and start
executing U-Boot.
Does this tell you anything ?
Regards,
Christophe
>
> regards,
>
> Koen
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
>
> iD8DBQFL8nYpMkyGM64RGpERAqugAJ99oUDfVGTJAbIs8AQwR1HA/9iTdwCffwgQ
> B6yfaXpEm0axylpQQu6q5v0=
> =H6Ac
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> 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:[~2010-05-18 16:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 7:27 [hawkboard] OE Kernel Not Booting Christophe Aeschlimann
2010-05-18 7:30 ` Koen Kooi
2010-05-18 8:10 ` Christophe Aeschlimann
2010-05-18 11:12 ` Koen Kooi
2010-05-18 13:36 ` Christophe Aeschlimann [this message]
2010-05-20 11:41 ` Koen Kooi
2010-05-20 12:01 ` Christophe Aeschlimann
2010-06-24 23:07 ` John (GMail)
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=4BF297ED.9060301@acn-group.ch \
--to=c.aeschlimann@acn-group.ch \
--cc=openembedded-devel@lists.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