Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(100)

Side by Side Diff: scripts/newbitmaps/HWID.txt

Issue 6588093: Add instructions for modifying the HWID. (Closed) Base URL: http://git.chromium.org/git/vboot_reference.git@master
Patch Set: Created 9 years, 9 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1
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,
4 refer to the README file.
5
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
8 bitmap that shows up on the BIOS screens.
9
10
11 Here's how to generate a new bitmap blob with a modified HWID
12
13 1. OUTSIDE the chroot, cd to
14 src/platform/vboot_reference/scripts/newbitmaps/strings
15
16 2. Edit the file 'hwid.txt' to contain your new string.
17
18 3. Run "./text_to_bmp hwid.txt" to create "hwid.bmp" which contains ONLY the
19 picture of the HWID string.
20
21 4. Copy the hwid.bmp image to the directory where the rest of the bitmap
22 blob comes from (which might not be public yet). If you don't know where
23 that is, just use the example directory:
24
25 src/platform/vboot_reference/scripts/newbitmaps/images/1280x800
26
27 5. cd to the bitmap source directory, INSIDE the chroot.
28
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
31 starts with "hwid:" to refer to your new hwid.bmp file (or replace the
32 existing hwid bitmap file with your new one).
33
34 7. Run "bmpblock_utility -c unknown.yaml new_bitmaps.bin", to create the new
35 bitmap blob.
36
37 8. Install the new_bitmaps.bin on your device (see below).
38
39
40
41
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
44 system. This will only work if THE BIOS write-protect is disabled.
45
46
47 A. Read the existing BIOS from ROM (so you don't lose the VPD):
48
49 cd /mnt/stateful_partition
50 flashrom -r bios.bin
51
52 B. Modify the GBB in the BIOS image to contain the new bits:
53
54 gbb_utility -s 'NEW HWID STRING 1234' -b new_bitmaps.bin bios.bin
55
56 C. Write the modified BIOS back to ROM:
57
58 flashrom -w bios.bin
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698