Board:google/butterfly: Difference between revisions
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
area_offset="0x00600000" area_size="0x00004000" area_name="'''RO_VPD'''" area_flags_raw="0x01" area_flags="static" | area_offset="0x00600000" area_size="0x00004000" area_name="'''RO_VPD'''" area_flags_raw="0x01" area_flags="static" | ||
Extract the RO_VPD section from ROM image. | ==== Extract the RO_VPD section from ROM image. ==== | ||
TODO!!! dd if=original_chrome_image.rom skip=??? bs=??? count=??? of=vpd.bin | TODO!!! dd if=original_chrome_image.rom skip=??? bs=??? count=??? of=vpd.bin | ||
Insert vpd.bin in the custom coreboot image: | ==== Insert vpd.bin in the custom coreboot image: ==== | ||
TODO!!! cbfstool bla bla vpd.bin bla | TODO!!! cbfstool bla bla vpd.bin bla | ||
Revision as of 19:58, 3 December 2013
See Chromebooks for additional details.
Hi. I am the mighty alien dwarf, and I will be talking about the Pavilion Chromebook here.
Building a complete coreboot image (WHIP)
Including the MAC address and keyboard layout
The coreboot that ships with the laptop will read the keyboard layout and MAC address from the flash. Since ChromeOS uses a different layout than CBFS, the region containing these parameters must me included in the CBFS of the custom coreboot. There is a patch to allow coreboot to read this file and configure the hardware accordingly.
Get 'flashmap'
git clone https://chromium.googlesource.com/chromiumos/third_party/flashmap
Find the RO_VPD section
Build flashmap, then run fmap_decode on the extracted chromebook firmware.
fmap_decode original_chrome_image.rom
Locate the RO_VPD section in the output:
area_offset="0x00600000" area_size="0x00004000" area_name="RO_VPD" area_flags_raw="0x01" area_flags="static"
Extract the RO_VPD section from ROM image.
TODO!!! dd if=original_chrome_image.rom skip=??? bs=??? count=??? of=vpd.bin
Insert vpd.bin in the custom coreboot image:
TODO!!! cbfstool bla bla vpd.bin bla