diff options
Diffstat (limited to 'docs/install')
| -rw-r--r-- | docs/install/bbb_setup.md | 2 | ||||
| -rw-r--r-- | docs/install/c201.md | 8 | ||||
| -rw-r--r-- | docs/install/index.md | 2 | ||||
| -rw-r--r-- | docs/install/rpi_setup.md | 2 | ||||
| -rw-r--r-- | docs/install/x200_external.md | 8 |
5 files changed, 12 insertions, 10 deletions
diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md index f2bb840b..5d684a7f 100644 --- a/docs/install/bbb_setup.md +++ b/docs/install/bbb_setup.md @@ -236,7 +236,7 @@ Output: Verify that the spidev device now exists: - # ls -al /dev/spid + # ls -al /dev/spid* Output: diff --git a/docs/install/c201.md b/docs/install/c201.md index 238c0734..fb39196a 100644 --- a/docs/install/c201.md +++ b/docs/install/c201.md @@ -155,10 +155,10 @@ to be opened. The SPI flash is located next to the write protect screw. Its layout is indicated in the picture below. Note that it is not necessary to connect -`WP#` since removing the screw already connects it to ground. Before -writing to the chip externally, the battery connector has to be -detached. It is located under the heat spreader, that has to be -unscrewed from the rest of the case. The battery connector is located on +`WP#` since after removing the screw it is pulled up weakly to 3v3. Before +writing to the chip externally, the battery has to be unplugged. +Battery connector is located under the heat spreader, that has to be +unscrewed from the rest of the case. It is located on the right and has colorful cables, as shown on the picture below. [. +externally. See [kcma-d8.md](kcma-d8.md). If you already have coreboot or libreboot installed, without write protection on the flash chip, then you can do it in software (otherwise, diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md index e46191e7..b083aac9 100644 --- a/docs/install/rpi_setup.md +++ b/docs/install/rpi_setup.md @@ -150,7 +150,7 @@ successfully. If not, just flash again. Pi](http://scruss.com/blog/2013/02/02/simple-adc-with-the-raspberry-pi/) - [Flashing coreboot on a T60 with a Raspberry Pi - the\_unconventional's - blog](https://blogs.fsfe.org/the_unconventional/2015/05/08/flashing-coreboot-on-a-t60-with-a-raspberry-pi/) + blog](https://web.archive.org/web/20150709043222/http://blogs.fsfe.org:80/the_unconventional/2015/05/08/coreboot-t60-raspberry-pi/) - *Pomona SOIC Clip flashing* - [Arch Linux Wiki - Installing Arch Linux on Chromebook](https://wiki.archlinux.org/index.php/Chromebook) diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md index 3ff34501..83a5c23f 100644 --- a/docs/install/x200_external.md +++ b/docs/install/x200_external.md @@ -19,7 +19,7 @@ Flash chip size Run this command on x200 to find out flash chip model and its size: - # flashrom -p internal -V + # flashrom -p internal The X200S and X200 Tablet will use a WSON-8 flash chip, on the bottom of the motherboard (this requires removal of the motherboard). Not all X200S/X200T are @@ -163,7 +163,9 @@ Now compare the 3 images: # sha512sum factory*.rom -If the hashes match, then just copy one of them (the factory.rom) to a +If the hashes match and if hex editor (like `dhex`) shows that +they have valid contents (eg. it's not filled entirely with `0x00`/`0xFF`), +then just copy one of them (the factory.rom) to a safe place (on a drive connected to another system, not the BBB). This is useful for reverse engineering work, if there is a desirable behaviour in the original firmware that could be replicated in coreboot @@ -178,7 +180,7 @@ address to one that is correct for your system. Now flash it: - # ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V + # ./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom  |