Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] Cannot get build to use start_x.elf and fixup_x.dat Raspberry Pi 3
Date: Sat, 1 Aug 2020 13:09:59 +0200	[thread overview]
Message-ID: <20200801130959.7ca4ac6a@gmx.net> (raw)
In-Reply-To: <20200801080648.GA32736@scaer>

Hello Vijay,

On Sat, 1 Aug 2020 10:06:48 +0200, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:

> Vijay, All,
> 
> On 2020-07-31 18:01 -0700, Vijay spake thusly:
> > I'm fairly new to buildroot and cannot find a solution to this problem
> > I'm having. Everything works well for me and I'm able to create the SD
> > card images to run on my Pi 3. However, I'm trying to get the extended
> > ("x") firmware to boot. In the Target Packages > Hardware Handling >
> > Firmware section, I'm selecting the extended option. Buildroot is
> > building all the different variations of the start.elf (including
> > start_x.elf, start_cd.elf) but only using the start.elf file in the
> > final image instead of the start_x.elf file (same with fixup.dat). So
> > basically whether I select the "default" option on that screen or
> > "extended," the resulting boot image is the same. If I manually copy
> > the start_x.elf and fixup_x.dat files as start.elf and fixup.dat the
> > I get the extended functionality - specifically the camera working.
> > I hope all that?makes sense. Please let me know if you need any
> > further information. Any help is greatly appreciated.  
> 
> The corret files are copied to the unqualified names, and the
> unqualified names are loaded at boot; see the comment in config.txt

And do not forget to re-build the rpi-firmware package (not done automatically
by buildroot, see [1], [2]) after changing the options:

	make rpi-firmware-rebuild
	make

Regards,
Peter

[1] https://buildroot.org/downloads/manual/manual.html#full-rebuild
[2] https://buildroot.org/downloads/manual/manual.html#rebuild-pkg

> 
> Also, see commit 1bdc0334f, which fixed that recently on master. It was
> backported to 2020.05.x, but not to the LTS 2020.02...
> 
> Regards,
> Yann E. MORIN.
> 

  reply	other threads:[~2020-08-01 11:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-01  1:01 [Buildroot] Cannot get build to use start_x.elf and fixup_x.dat Raspberry Pi 3 Vijay
2020-08-01  8:06 ` Yann E. MORIN
2020-08-01 11:09   ` Peter Seiderer [this message]
2020-08-01 20:21     ` Vijay
2020-08-03 11:27   ` Peter Korsgaard

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=20200801130959.7ca4ac6a@gmx.net \
    --to=ps.report@gmx.net \
    --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