boot-architecture May 2023

boot-architecture@lists.linaro.org

5 participants
5 discussions

by Vincent Stehlé

Hi, We will have an EBBR call[1] today, May 22, at 15h UTC/BST. On the agenda[2] we have two pull requests to review: - Pull request #[105]: Recommend the firmware update protocol - Pull request #[106]: Recommend usage of partition type GUIDs to find firmware (Heinrich) We could also go through the opened issues[3] if time permits. Feel free to add to the agenda, directly on the wiki page or by e-mail. We can use this pad[4] for the meeting notes. Best regards, Vincent Stehlé System Architect - Arm [1]: https://armltd.zoom.us/j/92081365511?pwd=SFZpRitXUEp3Zy9GM0h3UUZ1b1pnUT09 [2]: https://github.com/ARM-software/ebbr/wiki/EBBR-Meetings [3]: https://github.com/ARM-software/ebbr/issues [4]: https://mensuel.framapad.org/p/ebbr-call-of-22-may-a13j [105]: https://github.com/ARM-software/ebbr/pull/105 [106]: https://github.com/ARM-software/ebbr/pull/106

11 months, 1 week

[RFC] Proposed location to host the firmware handoff specification.

by Jose Marinho

Hi, Arm worked to draft a firmware handoff [1] specification, evolving it based on community feedback. This activity followed the request of some members of the Arm ecosystem [2]. The spec (still at ALP – feedback/comments welcome!) standardizes how information is propagated between different firmware components during boot. The spec hopes to remove the reliance on bespoke/platform-specific information handoff mechanisms, thus reducing the code maintenance burden. The concept of entry types is present in the spec – these are data structure layouts that carry a specific type of data. New types are meant to be added, following the needs and use-cases of the different communities. Thus, these communities should be empowered to request new types! To enable community contributions, the specification must be hosted in a location that is friendly to change requests. We propose to host the spec in trustedfirmware.org (tf.org). Tf.org hosts several open-source projects and already has an open governance model. TF-A, and the associated community, rely on tf.org, and thus are already well equipped to maintain this specification and keep it up to date. Tf.org is agnostic of any downstream projects that would adopt this specification (e.g. U-boot, EDK2, etc.). We welcome the views of the communities and want to understand if there are any strong objections to what’s being proposed! If anyone has objections, we are happy to consider alternatives and associated trade-offs. Regards [1] https://developer.arm.com/documentation/den0135/latest [2] Re: [TF-A] Proposal: TF-A to adopt hand-off blocks (HOBs) for information passing between boot stages - TF-A - lists.trustedfirmware.org<https://lists.trustedfirmware.org/archives/list/tf-a@lists.trustedfirmware.…>

11 months, 3 weeks

Re: Recommendation for identifying partition with firmware to be loaded from SD-card

by Heinrich Schuchardt

On 5/4/23 13:39, Michal Simek wrote: > > > On 5/1/23 16:26, Heinrich Schuchardt wrote: >> Linux distributions are interested in providing a single image which >> enables a high number of boards to boot. This is simple if the boot >> firmware (EDK II or U-Boot) is installed on flash. >> >> For boards that expect to load a boot loader like U-Boot from an SD-card >> it is necessary that the firmware locations for different boards >> on the SD-card don't collide. >> >> When loading from SD-card or eMMC the sector at which the binary >> starts has to be identified. The following has been implemented: >> >> - start from hard coded sector number >> - load file from FAT file system >> - load from given partition number >> - load from partition with boot flag set (MBR partioning only) >> - load from partition with specific type GUID >> >> Loading by partition type GUID seems the most appropriate to avoid >> collisions between the firmware for different boards. >> >> Often firmware is separated into multiple parts due to firmware >> restrictions, e.g. U-Boot SPL and main U-Boot (e.g. as .itb file). >> >> Here the same considerations apply. Using a partition type GUID to >> identify further firmware parts to be loaded is best suited to >> avoid collisions. >> >> I would suggest to add a recommendation to the EBBR specification >> to use SoC specific partition type GUIDs to identify firmware to >> be loaded from SD-card. >> >> Please, provide your feedback. > > Isn't this very similar to effort which Andre presented at Fosdem 2019? > > https://archive.fosdem.org/2019/schedule/event/one_image_to_rule_them_all/a… > > Thanks, > Michal Thanks Michal for the pointer. We are talking about the same topic. The question that was not resolved up to now is how we can avoid conflicts between the U-Boot binaries of different SoCs stored on the same medium. This is where I propose to use GUID partition types. Best regards Heinrich

12 months

Recommendation for identifying partition with firmware to be loaded from SD-card

by Heinrich Schuchardt

Linux distributions are interested in providing a single image which enables a high number of boards to boot. This is simple if the boot firmware (EDK II or U-Boot) is installed on flash. For boards that expect to load a boot loader like U-Boot from an SD-card it is necessary that the firmware locations for different boards on the SD-card don't collide. When loading from SD-card or eMMC the sector at which the binary starts has to be identified. The following has been implemented: - start from hard coded sector number - load file from FAT file system - load from given partition number - load from partition with boot flag set (MBR partioning only) - load from partition with specific type GUID Loading by partition type GUID seems the most appropriate to avoid collisions between the firmware for different boards. Often firmware is separated into multiple parts due to firmware restrictions, e.g. U-Boot SPL and main U-Boot (e.g. as .itb file). Here the same considerations apply. Using a partition type GUID to identify further firmware parts to be loaded is best suited to avoid collisions. I would suggest to add a recommendation to the EBBR specification to use SoC specific partition type GUIDs to identify firmware to be loaded from SD-card. Please, provide your feedback. Best regards Heinrich

12 months

Re: [RISC-V][tech-os-a-see] Recommendation for identifying partition with firmware to be loaded from SD-card

by Heinrich Schuchardt

On 5/1/23 16:31, Aaron Durbin wrote: > Hi, > > On Mon, May 1, 2023 at 8:26 AM Heinrich Schuchardt > <heinrich.schuchardt(a)canonical.com > <mailto:heinrich.schuchardt@canonical.com>> wrote: > > Linux distributions are interested in providing a single image which > enables a high number of boards to boot. This is simple if the boot > firmware (EDK II or U-Boot) is installed on flash. > > For boards that expect to load a boot loader like U-Boot from an SD-card > it is necessary that the firmware locations for different boards > on the SD-card don't collide. > > When loading from SD-card or eMMC the sector at which the binary > starts has to be identified. The following has been implemented: > > - start from hard coded sector number > - load file from FAT file system > - load from given partition number > - load from partition with boot flag set (MBR partioning only) > - load from partition with specific type GUID > > Loading by partition type GUID seems the most appropriate to avoid > collisions between the firmware for different boards. > > Often firmware is separated into multiple parts due to firmware > restrictions, e.g. U-Boot SPL and main U-Boot (e.g. as .itb file). > > Here the same considerations apply. Using a partition type GUID to > identify further firmware parts to be loaded is best suited to > avoid collisions. > > I would suggest to add a recommendation to the EBBR specification > to use SoC specific partition type GUIDs to identify firmware to > be loaded from SD-card. > > > Who is loading the firmware that is identified by a GUID? And how does > that tie into Linux distros? I don't see anything wrong w/ the > recommendation, but I didn't completely follow which piece of software > is loading firmware and how the GUID reduces the problems. Also, is this > "SoC specific partition type GUID" unique per SoC? Or is it expected to > be a global GUID? Booting firmware starts at boot ROM which may either directly load a piece of software from SD-card or may load a piece of software from flash which in turn will load the next step boot loader from the SD-card. From the view of a distro it is best if each board uses a separate GUID. This allows to add multiple U-Boot versions (or other boot software) on the same SD-card. Best regards Heinrich

12 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

boot-architecture May 2023