Firmware - Revision history

Dragon788 at 23:03, 11 November 2020

2020-11-11T23:03:59Z

Dragon788 at 23:03, 11 November 2020

2020-11-11T23:03:39Z

Reynhout: /* GBB Flags */

2020-07-09T18:42:58Z

‎GBB Flags

Reynhout: /* GBB Flags */

2020-07-09T18:42:35Z

‎GBB Flags

Matt Devo at 05:28, 17 January 2020

2020-01-17T05:28:26Z

Matt Devo: /* Availability Options */

2018-08-03T05:43:18Z

‎Availability Options

Matt Devo: /* Availability Options */

2018-06-28T20:24:43Z

‎Availability Options

Matt Devo: /* Availability Options */

2018-02-04T07:49:20Z

‎Availability Options

Matt Devo: /* Availability Options */

2018-02-04T07:48:06Z

‎Availability Options

Reynhout at 21:03, 1 February 2018

2018-02-01T21:03:55Z

Show changes

@@ Line 54: / Line 54: @@
 |-
 | Whiskey Lake
-| style="text-align:center;background-color:#ffe8e8" | RW_LEGACY (all) Tianocore via AltFW
+| style="text-align:center;background-color:#ccffcc" | RW_LEGACY (all) Tianocore via AltFW
 |-
 | AMD Stoney Ridge

@@ Line 54: / Line 54: @@
 |-
 | Whiskey Lake
-| style="text-align:center;background-color:#ffe8e8" | No
+| style="text-align:center;background-color:#ffe8e8" | RW_LEGACY (all) Tianocore via AltFW
 |-
 | AMD Stoney Ridge

← Older revision		Revision as of 18:42, 9 July 2020
Line 144:		Line 144:
	Google Binary Block (GBB) flags are firmware level settings stored directly in the firmware flash chip itself in a read-only (RO) area, and so require the firmware write protect screw to be removed before setting. The GBB flags are used to set the default boot mode (ChromeOS or legacy boot), developer mode boot screen timeout (2s or 30s), prevent exiting developer mode via spacebar, and to enable legacy booting regardless of crossystem setting, among other things.		Google Binary Block (GBB) flags are firmware level settings stored directly in the firmware flash chip itself in a read-only (RO) area, and so require the firmware write protect screw to be removed before setting. The GBB flags are used to set the default boot mode (ChromeOS or legacy boot), developer mode boot screen timeout (2s or 30s), prevent exiting developer mode via spacebar, and to enable legacy booting regardless of crossystem setting, among other things.

−	Most users should not attempt to set these manually, but instead use MrChromebox's [https://mrchromebox.tech/#fwscript ChromeOS firmware utility script] to set them based on their preferred default boot mode and boot timeout (the script automatically sets the dev mode and legacy boot mode overrides for all options except factory default). For those curious, a full description of all the GBB flags can be [https://chromium.googlesource.com/chromiumos/platform/vboot/+/master/_vboot_reference/firmware/include/gbb_header.h] found in the Google source code here]	+	Most users should not attempt to set these manually, but instead use MrChromebox's [https://mrchromebox.tech/#fwscript ChromeOS firmware utility script] to set them based on their preferred default boot mode and boot timeout (the script automatically sets the dev mode and legacy boot mode overrides for all options except factory default). For those curious, a full description of all the GBB flags can be [https://chromium.googlesource.com/chromiumos/platform/vboot/+/master/_vboot_reference/firmware/include/gbb_header.h found in the Google source code here]

← Older revision		Revision as of 18:42, 9 July 2020
Line 144:		Line 144:
	Google Binary Block (GBB) flags are firmware level settings stored directly in the firmware flash chip itself in a read-only (RO) area, and so require the firmware write protect screw to be removed before setting. The GBB flags are used to set the default boot mode (ChromeOS or legacy boot), developer mode boot screen timeout (2s or 30s), prevent exiting developer mode via spacebar, and to enable legacy booting regardless of crossystem setting, among other things.		Google Binary Block (GBB) flags are firmware level settings stored directly in the firmware flash chip itself in a read-only (RO) area, and so require the firmware write protect screw to be removed before setting. The GBB flags are used to set the default boot mode (ChromeOS or legacy boot), developer mode boot screen timeout (2s or 30s), prevent exiting developer mode via spacebar, and to enable legacy booting regardless of crossystem setting, among other things.

−	Most users should not attempt to set these manually, but instead use MrChromebox's [https://mrchromebox.tech/#fwscript ChromeOS firmware utility script] to set them based on their preferred default boot mode and boot timeout (the script automatically sets the dev mode and legacy boot mode overrides for all options except factory default). For those curious, a full description of all the GBB flags can be [https://chromium.googlesource.com/chromiumos/platform/~~vboot_reference~~/+/master/firmware/include/gbb_header.h found in the Google source code here]	+	Most users should not attempt to set these manually, but instead use MrChromebox's [https://mrchromebox.tech/#fwscript ChromeOS firmware utility script] to set them based on their preferred default boot mode and boot timeout (the script automatically sets the dev mode and legacy boot mode overrides for all options except factory default). For those curious, a full description of all the GBB flags can be [https://chromium.googlesource.com/chromiumos/platform/vboot/+/master/_vboot_reference/firmware/include/gbb_header.h] found in the Google source code here]

@@ Line 19: / Line 19: @@
 ! scope="col"|
 ! scope="col"| [https://mrchromebox.tech MrChromebox]
 |-
 | ARM
 | style="text-align:center;background-color:#ffe8e8" | No
 |-
 | Pineview
 | style="text-align:center;background-color:#ffe8e8" | No
 |-
 | Sandy/Ivy Bridge
-| style="text-align:center;background-color:#ccffcc" | Full Firmware [UEFI] (all)<br>Full Firmware [Legacy] (Stumpy)<br>RW_LEGACY (LINK)
+| style="text-align:center;background-color:#ccffcc" | Full Firmware [UEFI] (all)<br>RW_LEGACY (LINK)
 |-
 | Haswell
 | style="text-align:center;background-color:#ccffcc" | Full Firmware [UEFI] (all)<br>Full Firmware [Legacy] (Chromeboxes)<br>RW_LEGACY (all)
 |-
 | Broadwell
 | style="text-align:center;background-color:#ccffcc" | Full Firmware [UEFI] (all)<br>Full Firmware [Legacy] (Chromeboxes)<br>RW_LEGACY (all)
 |-
 | Bay Trail
-| style="text-align:center;background-color:#ccffcc" | Full Firmware [UEFI] (all)<br>BOOT_STUB (all)<br>RW_LEGACY (all)
+| style="text-align:center;background-color:#ccffcc" | Full Firmware [UEFI] (all)<br>RW_LEGACY (all)
 |-
 | Braswell
 | style="text-align:center;background-color:#ccffcc" | Full Firmware [UEFI] (all)<br>RW_LEGACY (all)
 |-
 | Skylake
 | style="text-align:center;background-color:#ccffcc" | Full Firmware [UEFI] (all)<br>RW_LEGACY (all)
 |-
 | Apollo Lake
 | style="text-align:center;background-color:#ccffcc" | RW_LEGACY (all)
 | style="text-align:center;background-color:#ffe8e8" | No
 |-
-| Kaby Lake
+| Whiskey Lake
 | style="text-align:center;background-color:#ffe8e8" | No
 |-
 | notes
 | • Easy Install via the [https://mrchromebox.tech/#fwscript Firmware Utility Script]<br>• Offers both UEFI and Legacy boot support for many models<br>• Fixes factory firmware bugs<br>• Built using latest upstream sources<br>• Headless boot support for servers<br>• PXE booting support (legacy only)<br>• UEFI firmware fully supports Windows as well as Linux<br>• [https://github.com/MrChromebox/coreboot Firmware source/build scripts] and payload sources ( [https://github.com/MrChromebox/SeaBIOS Legacy], [https://github.com/MrChromebox/edk2 UEFI])<br>
 |-
 ! scope="col"|
 ! scope="col"| [https://mrchromebox.tech/#fwscript Download/Install]
 |}
-Custom firmware builds for some models were previously available from CoolStar and John Lewis.
+Custom firmware builds for some models were previously available from CoolStar and John Lewis. That firmware is no longer recommended nor supported (by us or them).
 If you're running older firmware, you should strongly consider updating to a current build from MrChromebox. [https://mrchromebox.tech Full info], and [https://mrchromebox.tech/#fwscript Install script].
@@ Line 77: / Line 73: @@
 # '''RW_LEGACY'''
-#* Updates/replaces the stock legacy boot payload (SeaBIOS) included on many models; supplements the ChromeOS / secure boot payload (BOOT_STUB)
+#* Updates/replaces the stock legacy boot payload (SeaBIOS) included on many models; supplements the ChromeOS / secure boot payload
 #* Leaves all stock functionality intact, including the developer mode boot (white "OS verification is OFF") screen
 #* Allows device to dual-boot GalliumOS alongside ChromeOS
@@ Line 83: / Line 79: @@
 #* Carries zero risk of bricking the device
 #* On some models, includes bugfixes and enables additional functionality
 # '''Full Firmware / ROM'''
-#* A complete firmware image which replaces the hardware init component (coreboot) and payload components (BOOT_STUB, RW_LEGACY) of the stock firmware with updated and/or customized versions of coreboot and SeaBIOS (legacy) or Tianocore (UEFI)
+#* A complete firmware image which replaces the hardware init component (coreboot) and payload components of the stock firmware with updated and/or customized versions of coreboot and SeaBIOS (legacy) or Tianocore (UEFI)
 #* Removes the developer mode boot (white "OS verification is OFF") screen
 #* Removes the ability to run ChromeOS, creating a small risk of bricking your device
 #* Offers the best support for booting all OSes besides ChromeOS (including Windows).
-#* On many models, adds full hardware support for virtualization (vmx / VT-x)
+#* On all models, enables full hardware support for virtualization (vmx / VT-x)
 #* Fixes many bugs and/or idiosyncrasies associated with the stock firmware (but could potentially add new ones)
 #* Essentially turns your ChromeOS device into a "regular" PC / laptop
@@ Line 104: / Line 92: @@
 Factory firmware capabilities vary by model family. Haswells have good support for booting GalliumOS out of the box. Broadwells ''should'' have good support, but unfortunately the factory firmware has inconvenient video bugs. Bay Trail, Braswell, and Apollo Lake models don't include any support whatsoever. Skylake models also have video bugs in factory firmware. Kaby Lake models have OK support for eMMC devices, but fatal bugs for NVMe devices.
-In all cases, custom firmware is preferred. Custom RW_LEGACY firmware is available for nearly all Intel models, and is very quick, safe, and simple to update.
+In all cases, custom firmware is strongly recommended. Custom RW_LEGACY firmware is available for nearly all Intel models, and is very quick, safe, and simple to update.
 === Factory Bugs ===
-This is an incomplete list, but includes some model-specific notes.
+This is a (very) incomplete list, but includes some model-specific notes.
 * '''Haswell'''
 ** '''PANTHER, ZAKO''' USB ports non-functional in legacy boot mode / SeaBIOS
-*** <span style="background-color:#ccffcc;padding:0.2em">'''fixed'''</span> in custom firmware: MrChromebox (UEFI Full ROM, RW_LEGACY), John Lewis (full, BOOT_STUB, RW_LEGACY)
+*** <span style="background-color:#ccffcc;padding:0.2em">'''fixed'''</span> in custom firmware: MrChromebox (UEFI Full ROM, RW_LEGACY)
 ** '''WOLF''' non-functional legacy boot mode / SeaBIOS
-*** <span style="background-color:#ccffcc;padding:0.2em">'''fixed'''</span> in custom firmware: MrChromebox (UEFI Full ROM, RW_LEGACY), John Lewis (full, BOOT_STUB, RW_LEGACY)
+*** <span style="background-color:#ccffcc;padding:0.2em">'''fixed'''</span> in custom firmware: MrChromebox (UEFI Full ROM, RW_LEGACY)
 * '''Broadwell'''
@@ Line 122: / Line 110: @@
 * '''Bay Trail'''
 ** '''(all models)''' Legacy boot capability (SeaBIOS) not included
-*** <span style="background-color:#ccffcc;padding:0.2em">'''fixed'''</span> in custom firmware: MrChromebox (UEFI Full ROM, BOOT_STUB, RW_LEGACY), John Lewis (BOOT_STUB, RW_LEGACY)
+*** <span style="background-color:#ccffcc;padding:0.2em">'''fixed'''</span> in custom firmware: MrChromebox (UEFI Full ROM, RW_LEGACY)
 * '''Braswell'''
@@ Line 142: / Line 130: @@
 == Firmware and NVRAM Flags ==
-Both the crossystem and GBB flags listed below are only relevant when booting legacy mode via RW_LEGACY (CTRL+L on dev mode boot screen); they do not have any effect when using custom BOOT_STUB or full firmware.
+Both the crossystem and GBB flags listed below are only relevant when booting legacy mode via RW_LEGACY (CTRL+L on dev mode boot screen); they do not have any effect when using custom Full ROM (UEFI or legacy) firmware.
 === crossystem ===

@@ Line 62: / Line 62: @@
 |-
 | notes
-| • Easy Install via the [https://mrchromebox.tech/#fwscript Firmware Utility Script]<br>• Offers both UEFI and Legacy boot support for many models<br>• Fixes factory firmware bugs<br>• Built using latest upstream sources<br>• Headless boot support for servers<br>• PXE booting support (legacy only)<br>• UEFI firmware fully supports Windows as well as Linux<br>• Supports integration of [http://kodi.tv/about/ Kodi Media Center]<br>• [https://github.com/MattDevo/coreboot Firmware source/build scripts] and payload sources ( [https://github.com/MattDevo/SeaBIOS Legacy], [https://github.com/MattDevo/edk2 UEFI])<br>• UEFI firmware a collaborative effort with [https://www.reddit.com/u/coolstarorg coolstar]
+| • Easy Install via the [https://mrchromebox.tech/#fwscript Firmware Utility Script]<br>• Offers both UEFI and Legacy boot support for many models<br>• Fixes factory firmware bugs<br>• Built using latest upstream sources<br>• Headless boot support for servers<br>• PXE booting support (legacy only)<br>• UEFI firmware fully supports Windows as well as Linux<br>• Supports integration of [http://kodi.tv/about/ Kodi Media Center]<br>• [https://github.com/MrChromebox/coreboot Firmware source/build scripts] and payload sources ( [https://github.com/MrChromebox/SeaBIOS Legacy], [https://github.com/MrChromebox/edk2 UEFI])<br>
 | • Fixes factory firmware bugs<br>• Only supports booting Linux<br>• Firmware build scripts not published
 |-