| OLD | NEW |
|---|
| 1 | 1 |
| 2 This describes how to change the HWID string that's displayed using the | 2 This describes how to change the HWID string that's displayed using the |
| 3 new-style BIOS bitmaps. For a more detailed explanation of what's going on, | 3 new-style BIOS bitmaps. For a more detailed explanation of what's going on, |
| 4 refer to the README file. | 4 refer to the README file. |
| 5 | 5 |
| 6 The HWID is encoded in the GBB in two ways: An ASCII string that userspace | 6 The HWID is encoded in the GBB in two ways: An ASCII string that userspace |
| 7 can read from /sys/devices/platform/chromeos_acpi/HWID, and as a rendered | 7 can read from /sys/devices/platform/chromeos_acpi/HWID, and as a rendered |
| 8 bitmap that shows up on the BIOS screens. | 8 bitmap that shows up on the BIOS screens. |
| 9 | 9 |
| 10 | 10 |
| (...skipping 13 matching lines...) Expand all Loading... |
| 24 | 24 |
| 25 src/platform/vboot_reference/scripts/newbitmaps/images/1280x800 | 25 src/platform/vboot_reference/scripts/newbitmaps/images/1280x800 |
| 26 | 26 |
| 27 5. cd to the bitmap source directory, INSIDE the chroot. | 27 5. cd to the bitmap source directory, INSIDE the chroot. |
| 28 | 28 |
| 29 6. Edit the .yaml file that describes the bitmap blob (if you're in the | 29 6. Edit the .yaml file that describes the bitmap blob (if you're in the |
| 30 1280x800 directory, it's called "unknown.yaml"). Change the line that | 30 1280x800 directory, it's called "unknown.yaml"). Change the line that |
| 31 starts with "hwid:" to refer to your new hwid.bmp file (or replace the | 31 starts with "hwid:" to refer to your new hwid.bmp file (or replace the |
| 32 existing hwid bitmap file with your new one). | 32 existing hwid bitmap file with your new one). |
| 33 | 33 |
| 34 7. Run "bmpblock_utility -c unknown.yaml new_bitmaps.bin", to create the new | 34 7. Run "bmpblk_utility -c unknown.yaml new_bitmaps.bin", to create the new |
| 35 bitmap blob. | 35 bitmap blob. |
| 36 | 36 |
| 37 8. Install the new_bitmaps.bin on your device (see below). | 37 8. Install the new_bitmaps.bin on your device (see below). |
| 38 | 38 |
| 39 | 39 |
| 40 | 40 |
| 41 | 41 |
| 42 The gbb_utility is used to replace both the ASCII string and the bitmap blob | 42 The gbb_utility is used to replace both the ASCII string and the bitmap blob |
| 43 in a BIOS image. The typical proces is to do this as root on the target | 43 in a BIOS image. The typical proces is to do this as root on the target |
| 44 system. This will only work if THE BIOS write-protect is disabled. | 44 system. This will only work if THE BIOS write-protect is disabled. |
| 45 | 45 |
| 46 | 46 |
| 47 A. Read the existing BIOS from ROM (so you don't lose the VPD): | 47 A. Read the existing BIOS from ROM (so you don't lose the VPD): |
| 48 | 48 |
| 49 cd /mnt/stateful_partition | 49 cd /mnt/stateful_partition |
| 50 flashrom -r bios.bin | 50 flashrom -r bios.bin |
| 51 | 51 |
| 52 B. Modify the GBB in the BIOS image to contain the new bits: | 52 B. Modify the GBB in the BIOS image to contain the new bits: |
| 53 | 53 |
| 54 gbb_utility -s 'NEW HWID STRING 1234' -b new_bitmaps.bin bios.bin | 54 gbb_utility -s 'NEW HWID STRING 1234' -b new_bitmaps.bin bios.bin |
| 55 | 55 |
| 56 C. Write the modified BIOS back to ROM: | 56 C. Write the modified BIOS back to ROM: |
| 57 | 57 |
| 58 flashrom -w bios.bin | 58 flashrom -w bios.bin |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 6598091:
Bitmap generator for components files (Closed)
Base URL: ssh://git@gitrw.chromium.org:9222/vboot_reference.git@master