From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] Craneborad and Buildroot
Date: Thu, 23 Feb 2012 16:39:12 +0100 [thread overview]
Message-ID: <4F465DA0.7040407@visionsystems.de> (raw)
In-Reply-To: <CABMxt4gbvhDEkY315AVrRqyqQx1gE3=P3PaZ0Wcnj74J=ieJFQ@mail.gmail.com>
Am 23.02.2012 16:36, schrieb Mohamed HAMZAOUI:
> Hi,
>
> I want to use Buildroot for CraneBoard...
>
> My problem is with configuration files : MLO, u-boot.bin and uImage.
> I installed the last RC buildroot and after I started to configure the build by selecting the desired setting because i dont found a defconfig file for Kernel with buildroot ...
>
> In the configuration of the bootloader I checked xloader and uboot. With uboot I found a configuration file to my card "am3517_crane" but, for xloader, I haven't found anything and I cannot generate the correspendant MLO .
>
> I copy MLO, which was provided for Angstrom distrib for my card (compiled whith openembedded) but I cannot load the u-boot. suddenly, I also tried copying uboot that provided with the same distrib of MLO and then I start but I am blocked on: "booting the kernel"!
>
> Could you tell me why i have this freeze ?
> Could you tell me what I do with buildroot to find the xloader configuration file to my card ?
What toolchain are you using? Try ct-ng. I have reported the problems with CodeSourcery and native toolchains recently.
Best regards,
Yegor
next prev parent reply other threads:[~2012-02-23 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 15:36 [Buildroot] Craneborad and Buildroot Mohamed HAMZAOUI
2012-02-23 15:39 ` Yegor Yefremov [this message]
[not found] ` <CABMxt4hvmfTZXjL=b9=W6J-0-DSDjxzzmGTAPx-ghsXgTk8+HA@mail.gmail.com>
2012-02-24 7:33 ` Yegor Yefremov
-- strict thread matches above, loose matches on Subject: below --
2012-02-20 15:20 [Buildroot] craneborad and buildroot Mohamed HAMZAOUI
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=4F465DA0.7040407@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.