Flashmap: Difference between revisions

From coreboot
Jump to navigation Jump to search
m (Clarify that this guide will be referencing the chromiumos master tree)
(Start flash map table)
Line 1: Line 1:
''or...''
''or...''
=Toward a unified representation for the layout of coreboot flash images=
=Toward a unified representation for the layout of coreboot flash images=
 
'''N.B.''' The changes described herein are being made as part of the Chromium OS project; as such, they will initially be committed to the project's own fork of the main coreboot repository, which is available at [https://chromium.googlesource.com/chromiumos/third_party/coreboot https://chromium.googlesource.com/chromiumos/third_party/coreboot]. Unless otherwise noted, the paths and processes described throughout this page are as they exist(ed) in a checkout of the master branch of the Chromium OS sources as they appeared at the beginning of 2015. One of the guiding design principles is to keep the tools general enough that they will be helpful to others, and the resulting work will be upstreamed to the main repository once it has been regression-tested in the context of Chromium OS hardware.
'''N.B.''' The changes described herein are being made as part of the Chromium OS project; as such, they will initially be committed to the project's own fork of the main coreboot repository, which is available at [https://chromium.googlesource.com/chromiumos/third_party/coreboot/]. Unless otherwise noted, the paths and processes described throughout this page are as they exist(ed) in a checkout of the master branch of the Chromium OS sources as they appeared at the beginning of 2015. One of the guiding design principles is to keep the tools general enough that they will be helpful to others, and the resulting work will be upstreamed to the main repository once it has been regression-tested in the context of Chromium OS hardware.


==How it's currently done (how the Chromium OS project presently constructs firmware images)==
==How it's currently done (how the Chromium OS project presently constructs firmware images)==
Most Intel-based Chromium OS devices currently use an 8 MB firmware image that includes---among other things---the Intel ME firmware, a copy of coreboot including the ramstage and bootloader payload, two additional copies of the ramstage and bootloader payload, and a separate SeaBIOS payload. The primary description of this format exists in board-specific flattened device tree files. For instance, the layout of the Panther board's firmware exists at [https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/master/board/panther/fmap.dts https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/master/board/panther/fmap.dts], and results in an image that looks like this:
{| class="wikitable"
! Section
! Offset
! Contents
|-
| rowspan="8" | RO
|-
| 0x700000
| Boot (coreboot image)
|-
| 0x611000
| GBB (Google Binary Block)
|-
| 0x610840
| (Reserved)
|-
| 0x610800
| FWID (Firmware ID)
|-
| 0x610000
| FMAP (Flash MAP)
|-
| 0x604000
| (Reserved)
|-
| 0x600000
| RO-VPD (Vital Product Data)
|-
| rowspan="4" |
|-
| 0x400000
| Legacy (SeaBIOS image)
|-
| 0x3fa000
| (Reserved)
|-
| 0x3f8000
| RW-VPD (Vital Product Data)
|-
| rowspan="3" | RW/Shared
|-
| 0x3f6000
| Vblock-dev (third-party kernel signing keys)
|-
| 0x3f4000
| Shared-data (RW firmware calibration data)
|-
| rowspan="3" |
|-
| 0x3f0000
| ELOG (Event LOG)
|-
| 0x3e0000
| MRC-cache (Memory Reference Code training data)
|}


==What's so bad about that (the pitfalls of this build model that we hope to solve)==
==What's so bad about that (the pitfalls of this build model that we hope to solve)==

Revision as of 19:19, 11 February 2015

or...

Toward a unified representation for the layout of coreboot flash images

N.B. The changes described herein are being made as part of the Chromium OS project; as such, they will initially be committed to the project's own fork of the main coreboot repository, which is available at https://chromium.googlesource.com/chromiumos/third_party/coreboot. Unless otherwise noted, the paths and processes described throughout this page are as they exist(ed) in a checkout of the master branch of the Chromium OS sources as they appeared at the beginning of 2015. One of the guiding design principles is to keep the tools general enough that they will be helpful to others, and the resulting work will be upstreamed to the main repository once it has been regression-tested in the context of Chromium OS hardware.

How it's currently done (how the Chromium OS project presently constructs firmware images)

Most Intel-based Chromium OS devices currently use an 8 MB firmware image that includes---among other things---the Intel ME firmware, a copy of coreboot including the ramstage and bootloader payload, two additional copies of the ramstage and bootloader payload, and a separate SeaBIOS payload. The primary description of this format exists in board-specific flattened device tree files. For instance, the layout of the Panther board's firmware exists at https://chromium.googlesource.com/chromiumos/platform/depthcharge/+/master/board/panther/fmap.dts, and results in an image that looks like this:

Section Offset Contents
RO
0x700000 Boot (coreboot image)
0x611000 GBB (Google Binary Block)
0x610840 (Reserved)
0x610800 FWID (Firmware ID)
0x610000 FMAP (Flash MAP)
0x604000 (Reserved)
0x600000 RO-VPD (Vital Product Data)
0x400000 Legacy (SeaBIOS image)
0x3fa000 (Reserved)
0x3f8000 RW-VPD (Vital Product Data)
RW/Shared
0x3f6000 Vblock-dev (third-party kernel signing keys)
0x3f4000 Shared-data (RW firmware calibration data)
0x3f0000 ELOG (Event LOG)
0x3e0000 MRC-cache (Memory Reference Code training data)

What's so bad about that (the pitfalls of this build model that we hope to solve)

Why you should care (how this pertains to all coreboot users)

How do we fix it (the solution being pursued)

Retrieved from "https://www.coreboot.org/index.php?title=Flashmap&oldid=15583"