Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Björn Kirchner" <bjoern@am-soft.de>
To: buildroot@busybox.net
Subject: [Buildroot] How transfer what image(s) to target-CF?
Date: Sat, 26 Apr 2014 09:23:14 +0200	[thread overview]
Message-ID: <20140426092314.19527a1b@tux> (raw)
In-Reply-To: <CAEzGmjALnnk=Mqj7pirEnTZ5qvAh_DY7jR6iHnZbQMt+HLL41w@mail.gmail.com>

Am Fri, 25 Apr 2014 23:42:44 +0200
schrieb Lennart Ramberg <ramberg.lennart@gmail.com>:

> >  Ah sorry, grub2 has only been added a couple of weeks ago. But
> > grub-legacy should work fine as well.
> >
> >
> >
> Hm... my mbr on the target CF mentions LILO. Should I for grub-legacy
> do as follows?
> Use dd to copy (part of?) the 512 bytes
> from /media/lennart/5fcblablblabla620/boot/grub/stage1
> to /dev/sdX
> 
> And then copy the e2fs_stage1_5 with destination beginning at 512?
> 
> Or is there a safer trick to install grub here?
> 

I don't know if that is safer, but I used the target grub
build by buildroot to install itself to the CF card.
- Become root on your host system
- Execute </full/path/to/your/cfcard>/sbin/grub
At the grub prompt type:
grub> root (hdx,y)
grub> setup (hdx)
grub> quit
(where x is the "hard disk" and y is the partition in grub notation.
With <TAB> you can get a list of possible values for x and y.
You can search for possible disks with
grub> find /boot/grub/stage1
That lists all partitions which contain the named file. If your host
system does not use grub1, it should only be one partition.

When I build my buildroot system for an x86 based board I ran
into a problem. If grub1 was built with a gcc version newer than,
if I remember correctly, 4.5, the stage2 file was built corrupted.
I don't know if that was fixed in the meantime. I just copied the
stage2 file from a build made with a gcc 4.5 compiler. That worked
fine.


> Thanks and regards.
> Lennart

Hope this helps.

Bj?rn

  reply	other threads:[~2014-04-26  7:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23 13:42 [Buildroot] How transfer what image(s) to target-CF? Lennart Ramberg
2014-04-23 15:33 ` Arnout Vandecappelle
2014-04-24 10:07   ` Lennart Ramberg
2014-04-24 21:44     ` Arnout Vandecappelle
2014-04-25 18:37       ` Lennart Ramberg
2014-04-25 18:53         ` Arnout Vandecappelle
2014-04-25 21:42           ` Lennart Ramberg
2014-04-26  7:23             ` Björn Kirchner [this message]
2014-04-27 16:37               ` Lennart Ramberg
2014-04-27 19:39                 ` Björn Kirchner
2014-04-28 12:33                   ` Lennart Ramberg
2014-04-28 14:25                     ` Jérôme Pouiller
     [not found]                     ` <25917145.tTrImWgKe2@sagittea>
2014-04-28 14:27                       ` Jérôme Pouiller
2014-05-05  9:01                         ` Lennart Ramberg

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=20140426092314.19527a1b@tux \
    --to=bjoern@am-soft.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