Skip to contentSkip to conversation

New: Fail to build for raspberrypi_defconfig with big endian

Buildroot bugzilla at busybox.net 1 participant 2 messages Jan 20, 2016 – Jan 21, 2016

lore
Share & tools
lore
#0 lore raw

https://bugs.busybox.net/show_bug.cgi?id=8616

Bug ID: 8616
Summary: Fail to build for raspberrypi_defconfig with big
endian
Product: buildroot
Version: unspecified
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: paulonunes at mail.com
CC: buildroot at uclibc.org

Created attachment 6286
--> https://bugs.busybox.net/attachment.cgi?id=6286&action=edit
last lines of stdout on the failed execution

On building using raspberrypi_defconfig configuration and changing the endianness to big endian, the buildroot fails to finish the build as attached files describe in detail.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#1 lore raw

[Buildroot] [Bug 8616] Fail to build for raspberrypi_defconfig with big endian

https://bugs.busybox.net/show_bug.cgi?id=8616

Gustavo Zacarias <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #1 from Gustavo Zacarias <[email protected]> --- You can't just change endianness arbitrarily and expect that to work.

For starters the pre-compiled rpi-firmware required for the boot process is only enabled for little-endian, which gives you the error you're seeing because it's not installed for big-endian.

I don't have much technical detail about the broadcom SOCs used in the rpi1/2 and how open they're to changing endianness, some SOCs require hardware changes (pin bootstrap), others can be switched in the bootloader, others use fuses and some can't be changed.
Even if they could be switched in the bootloader for the rpi boards that's a propietary blob in rpi-firmware, so there's not much you can do.

I'm closing this as invalid.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.