[Buildroot] Cannot get build to use start_x.elf and fixup_x.dat Raspberry Pi 3

[Buildroot] Cannot get build to use start_x.elf and fixup_x.dat Raspberry Pi 3

[Vijay]

Hi,

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.

Thanks,
Vijay Dirisala
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200731/c7d92932/attachment.html>

[Buildroot] Cannot get build to use start_x.elf and fixup_x.dat Raspberry Pi 3

[Yann E. MORIN]

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

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.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

[Buildroot] Cannot get build to use start_x.elf and fixup_x.dat Raspberry Pi 3

[Peter Seiderer]

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.
> 

[Buildroot] Cannot get build to use start_x.elf and fixup_x.dat Raspberry Pi 3

[Vijay]

Oh my god, that was it! I just assumed the system would automatically pick
up my changes and rebuild but I should've read the documentation more
closely. Thanks for the responses. I have everything working now as I
wanted.

Regards,
Vijay

On Sat, Aug 1, 2020 at 4:10 AM Peter Seiderer <ps.report@gmx.net> wrote:

> Hello Vijay,
>
> On Sat, 1 Aug 2020 10:06:48 +0200, "Yann E. MORIN" <
> yann.morin.1998 at 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.
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20200801/56347aa4/attachment.html>

[Buildroot] Cannot get build to use start_x.elf and fixup_x.dat Raspberry Pi 3

[Peter Korsgaard]

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > 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

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

Yes it was, in commit d92af490a5 (included in 2020.02.4).

-- 
Bye, Peter Korsgaard