Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] BR 2012 & pandaboard :: BOOT issue
Date: Fri, 24 Feb 2012 08:29:21 +0100	[thread overview]
Message-ID: <4F473C51.2050500@visionsystems.de> (raw)
In-Reply-To: <CAPEB33zmLTp+95wimobRGVi+Ze4t_7ikSc44goGUpbmmqYZ6Bw@mail.gmail.com>


>    with BR 2011.11 I couldn't boot using MLO/u-boot.bin/uImage generated while building a basic system. I then change to BR 2012 and I still have the same problem. When using the one provided with an "Ubuntu" distro it start to boot. 
>    I have tried different options for the "boot.script" file called boot.scr and nothing improve it.
> 
>    I then have 2 questions:
>      i)    Where it is possible to find documentation to write correct boot.script? as the pdf doc. I found doesn't mention anything helpful according to the memory mapping. On the net I have found different value to start the boot process which one is the good one?...
>      ii)   Why even the uImage created doesn't work, How using BR I can generate correct boot files? I have tried to use MLO/u-boot.bin couple from an Ubuntu distro and use the uImage generated by BR then I got an error message telling me that it couldn't find the kernel!
> 
>    I don't know how to solve this problem neither what I could test next to make thing going ahead? If you have any ideaS there are welcome!

What toolchain are you using? See this post: http://lists.busybox.net/pipermail/buildroot/2012-February/050089.html

Best regards,
Yegor

  reply	other threads:[~2012-02-24  7:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 19:45 [Buildroot] BR 2012 & pandaboard :: BOOT issue MERCADIER Johann
2012-02-24  7:29 ` Yegor Yefremov [this message]
2012-02-24  8:43   ` MERCADIER Johann
2012-02-24  9:10     ` Yegor Yefremov

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=4F473C51.2050500@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox