diff options
Diffstat (limited to 'docs/install')
32 files changed, 4533 insertions, 5724 deletions
diff --git a/docs/install/bbb_setup.html b/docs/install/bbb_setup.html deleted file mode 100644 index fee34c8b..00000000 --- a/docs/install/bbb_setup.html +++ /dev/null @@ -1,478 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>How to program an SPI flash chip with the BeagleBone Black or Teensy 3.1</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">How to program an SPI flash chip with the BeagleBone Black or Teensy 3.1</h1> - <p> - This document exists as a guide for reading from or writing to an SPI flash chip with the BeagleBone Black, - using the <a href="http://flashrom.org/Flashrom">flashrom</a> software. - A BeagleBone Black, rev. C was used when creating this guide, but earlier revisions - may also work. - </p> - - <p> - <strong> - NOTE: this documentation may be outdated, and discusses - configuring SPI flashing on the default Debian system that the BBB - sometimes comes with. If you want an easier time, just use - <a href="https://www.coreboot.org/BBB_screwdriver">BBB ScrewDriver</a> - which comes pre-configured. - </strong> - </p> - <p> - <strong> - This guide is written for Debian Wheezy 7.5, which is what came on - the BBB at the time this guide was written. This one: - <a href="https://debian.beagleboard.org/images/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz">https://debian.beagleboard.org/images/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz</a> - </strong> - </p> - - <p> - There was no justification for a further section for the Teensy. Simply refer to <a href="https://www.flashrom.org/Teensy_3.1_SPI_%2B_LPC/FWH_Flasher#ISP_Usage">this page on flashrom.org</a> for information about how to set it up, and correlate that with the pins on the SPI flash chip as per other guides in the libreboot documentation for each board. At the time of writing, the teensy is tested for flashing on the ThinkPad X200, but it should work for other targets. here is a photo of the setup for the teensy: <a href="http://h5ai.swiftgeek.net/IMG_20160601_120855.jpg">http://h5ai.swiftgeek.net/IMG_20160601_120855.jpg</a></p> - <p> - Onto the Beaglebone black... - </p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section" id="hardware_requirements"> - - <h1>Hardware requirements</h1> - - <p> - Shopping list (pictures of this hardware is shown later): - </p> - <ul> - <li> - A <a href="http://flashrom.org">Flashrom</a>-compatible external SPI programmer: - <strong>BeagleBone Black</strong>, sometimes referred to as 'BBB', (rev. C) is highly recommended. - You can buy one from <a href="https://www.adafruit.com">Adafruit</a> (USA), <a href="http://electrokit.com">ElectroKit</a> (Sweden) - or any of the distributors listed <a href="http://beagleboard.org/black">here</a> (look below 'Purchase'). - We recommend this product because we know that it works well for our purposes and doesn't require any non-free software. - </li> - <li> - Electrical/insulative tape: cover the entire bottom surface of the BBB (the part that rests on a surface). - This is important, when placing the BBB on top of a board so that nothing shorts. - Most hardware/electronics stores have this. Optionally, you can use the bottom half of a - <a href="http://www.hammondmfg.com/1593HAM.htm#BeagleBoneBlack">hammond plastic enclosure</a>. - </li> - <li> - Clip for connecting to the flash chip: if you have a SOIC-16 flash chip (16 pins), you will need the - <strong>Pomona 5252</strong> or equivalent. For SOIC-8 flash chips (8 pins), you will need the <strong>Pomona 5250</strong> - or equivalent. Do check which chip you have, before ordering a clip. Also, you might as well buy two clips or more since they break easily. - <a href="http://farnell.com/">Farnell element 14</a> sells these and ships to many countries. Some people find these clips difficult to - get hold of, especially in South America. If you know of any good suppliers, please contact the libreboot project with the relevant information. - <strong>If you can't get hold of a pomona clip, some other clips might work, e.g. 3M, but they are not always reliable. - You can also directly solder the wires to the chip, if that suits you; the clip is just for convenience, really.</strong> - </li> - <li> - <strong>External 3.3V DC power supply</strong>, for powering the flash chip: an ATX power supply / PSU (common on Intel/AMD desktop - computers) will work for this. A lab PSU (DC) will also work (adjusted to 3.3V). - <ul> - <li>Getting a multimeter might be worthwhile, to verify that it's supplying 3.3V.</li> - </ul> - </li> - <li> - <strong>External 5V DC power supply</strong> (barrel connector), for powering the BBB: - the latter can have power supplied via USB, but a dedicated power supply is recommended. - These should be easy to find in most places that sell electronics. <strong>OPTIONAL. - Only needed if not powering with the USB cable, or if you want to use <a href="../misc/bbb_ehci.html">EHCI debug</a></strong>. - </li> - <li> - <strong>Pin header / jumper cables</strong> (2.54mm / 0.1" headers): you should get male--male, - male--female and female--female cables in 10cm size. Just get a load of them. - Other possible names for these cables/wires/leads are as follows: - <ul> - <li>flying leads</li> - <li>breadboard cables (since they are often used on breadboards).</li> - <li>You might also be able to make these cables yourself.</li> - </ul> - <a href="https://www.adafruit.com">Adafruit</a> sell them, as do many others. - <strong>Some people find them difficult to buy. Please contact the libreboot project if you know of any good sellers.</strong> - You might also be able to make these cables yourself. For PSU connections, using long cables, e.g. 20cm, is fine, and you can extend them longer than that if needed. - </li> - <li> - <b>Mini USB A-B cable</b> (the BeagleBone probably already comes - with one.) - <b>OPTIONAL - only needed for <a href="../misc/bbb_ehci.html">EHCI debug</a> or for serial/ssh access without ethernet cable (g_multi kernel module)</b> - </li> - <li> - <strong>FTDI TTL cable or debug board</strong>: used for accessing the serial console on the BBB. - <a href="http://elinux.org/Beagleboard:BeagleBone_Black_Serial">This page</a> contains a list. - <strong>OPTIONAL---only needed for serial console on the BBB, if not using SSH via ethernet cable.</strong> - </li> - </ul> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section" id="psu33"> - - <h1>Setting up the 3.3V DC PSU</h1> - - <p> - ATX PSU pinouts can be read on <a href="https://en.wikipedia.org/wiki/Power_supply_unit_%28computer%29#Wiring_diagrams">this Wikipedia page</a>. - </p> - <p> - You can use pin 1 or 2 (orange wire) on a 20-pin or 24-pin ATX PSU for 3.3V, and any of the ground/earth sources (black cables) for ground. - Short PS_ON# / Power on (green wire; pin 16 on 24-pin ATX PSU, or pin 14 on a 20-pin ATX PSU) to a ground - (black; there is one right next to it) using a wire/paperclip/jumper, then power on the PSU by grounding PS_ON# - (this is also how an ATX motherboard turns on a PSU). - </p> - <p> - <strong>DO **NOT** use pin 4, 6, do **NOT** use pin 19 or 20 (on a 20-pin ATX PSU), and DO **NOT** use pin - 21, 22 or 23 (on a 24-pin ATX PSU). Those wires (the red ones) are 5V, and they **WILL** kill your flash chip. - ***NEVER*** supply more than 3.3V to your flash chip (that is, if it's a 3.3V flash chip; 5V and 1.8V SPI - flash chips do exist, but they are rare. Always check what voltage your chip takes. Most of them take 3.3V).</strong> - </p> - <p> - You only need one 3.3V supply and one ground for the flash chip, after grounding PS_ON#. - </p> - - <p> - The male end of a 0.1" or 2.54mm header cable is not thick enough to remain permanently - connected to the ATX PSU on its own. - When connecting header cables to the connector on the ATX PSU, use a female end attached to - a thicker piece of wire (you could use a paper clip), or wedge the male end of the jumper cable - into the sides of the hole in the connector, instead of going through the centre. - </p> - - <p> - Here is an example set up:<br/> - <img src="images/x200/psu33.jpg" alt="" title="Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net> see license notice at the end of this document" /> - </p> - - </div> - - <div class="section" id="bbb_access"> - - <h1>Accessing the operating system on the BBB</h1> - <p> - The operating system on your BBB will probably have an SSH daemon - running where the root account has no password. Use SSH to access - the operating system and set a root password. By default, the OS - on your BBB will most likely use DHCP, so it should already have an IP - address. - </p> - <p> - You will also be using the OS on your BBB for programming an SPI flash chip. - </p> - <h2>Alternatives to SSH (in case SSH fails)</h2> - <p> - You can also use a serial FTDI debug board with GNU Screen, to access the serial console.<br/> - # <b>screen /dev/ttyUSB0 115200</b><br/> - Here are some example photos:<br/> - <img src="images/x200/ftdi.jpg" alt="" /> - <img src="images/x200/ftdi_port.jpg" alt="" /><br/> - </p> - <p> - You can also connect the USB cable from the BBB to another computer and a new network interface will appear, - with its own IP address. This is directly accessible from SSH, or screen:<br/> - # <b>screen /dev/ttyACM0 115200</b> - </p> - <p> - You can also access the uboot console, using the serial method - instead of SSH. - </p> - - </div> - - <div class="section" id="spidev"> - - <h1>Setting up spidev on the BBB</h1> - - <p> - Log on as root on the BBB, using either SSH or a serial console as defined in - <a href="#bbb_access">#bbb_access</a>. Make sure that you have internet access - on your BBB. - </p> - - <p> - Follow the instructions at <a href="http://elinux.org/BeagleBone_Black_Enable_SPIDEV#SPI0">http://elinux.org/BeagleBone_Black_Enable_SPIDEV#SPI0</a> - up to (and excluding) the point where it tells you to modify uEnv.txt - </p> - <p> - You need to update the software on the BBB first. If you have an - element14 brand BBB (sold by Premier Farnell plc. stores like - Farnell element14, Newark element14, and Embest), you may need - to <a href="https://groups.google.com/forum/?_escaped_fragment_=msg/beagleboard/LPjCn4LEY2I/alozBGsbTJMJ#!msg/beagleboard/LPjCn4LEY2I/alozBGsbTJMJ">work around a bug</a> - in the LED aging init script before you can update your - software. If you don't have a file named - /etc/init.d/led_aging.sh, you can skip this step and update your - software as described below. Otherwise, replace the contents of - this file with: - </p> -<pre> -#!/bin/sh -e -### BEGIN INIT INFO -# Provides: led_aging.sh -# Required-Start: $local_fs -# Required-Stop: $local_fs -# Default-Start: 2 3 4 5 -# Default-Stop: 0 1 6 -# Short-Description: Start LED aging -# Description: Starts LED aging (whatever that is) -### END INIT INFO - -x=$(/bin/ps -ef | /bin/grep "[l]ed_acc") -if [ ! -n "$x" -a -x /usr/bin/led_acc ]; then - /usr/bin/led_acc & -fi -</pre> - </p> - Run <b>apt-get update</b> and <b>apt-get upgrade</b> then reboot the BBB, before continuing. - </p> - - <p> - Check that the firmware exists:<br/> - # <b>ls /lib/firmware/BB-SPI0-01-00A0.*</b><br/> - Output: - </p> -<pre> -/lib/firmware/BB-SPI0-01-00A0.dtbo -</pre> - <p> - Then:<br/> - # <b>echo BB-SPI0-01 > /sys/devices/bone_capemgr.*/slots</b><br/> - # <b>cat /sys/devices/bone_capemgr.*/slots</b><br/> - Output: - </p> -<pre> - 0: 54:PF--- - 1: 55:PF--- - 2: 56:PF--- - 3: 57:PF--- - 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G - 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI - 7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-SPI0-01 -</pre> - - <p> - Verify that the spidev device now exists:<br/> - # <b>ls -al /dev/spid*</b><br/> - Output: - </p> -<pre> -crw-rw---T 1 root spi 153, 0 Nov 19 21:07 /dev/spidev1.0 -</pre> - <p> - Now the BBB is ready to be used for flashing. Make this persist - across reboots:<br/> - In /etc/default/capemgr add <b>CAPE=BB-SPI0-01</b> at the end - (or change the existing <b>CAPE=</b> entry to say that, if an - entry already exists. - </p> - <p> - Get flashrom from the libreboot_util release archive, or build it from libreboot_src/git if you need to. - An ARM binary (statically compiled) for flashrom exists in libreboot_util releases. Put the flashrom binary - on your BBB. - </p> - <p> - You may also need ich9gen, if you will be flashing an ICH9-M laptop (such as the X200). Get it from libreboot_util, - or build it from libreboot_src, and put the ARM binary for it on your BBB. - </p> - <p> - Finally, get the ROM image that you would like to flash and put that on your BBB. - </p> - - <p> - Now test flashrom:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512</b><br/> - Output: - </p> -<pre> -Calibrating delay loop... OK. -No EEPROM/flash device found. -Note: flashrom can never write if the flash chip isn't found automatically. -</pre> - - <p> - This means that it's working (the clip isn't connected to any flash chip, - so the error is fine). - </p> - - </div> - - <div class="section" id="clip"> - - <h1> - Connecting the Pomona 5250/5252 - </h1> - <p> - Use this image for reference when connecting the pomona to the BBB: - <a href="http://beagleboard.org/Support/bone101#headers">http://beagleboard.org/Support/bone101#headers</a> - (D0 = MISO or connects to MISO). - </p> - - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-16 (clip: Pomona 5252): - </p> -<pre> - NC - - 21 - 1 - - 17 - NC - - NC - NC - - NC - NC - - NC - NC - - NC - 18 - - 3.3V (PSU) - 22 - - NC - this is pin 1 on the flash chip -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> - -You may also need to connect pins 1 and 9 (tie to 3.3V supply). These are HOLD# and WP#. -On some systems they are held high, if the flash chip is attached to the board. -If you're flashing a chip that isn't connected to a board, you'll almost certainly -have to connect them. - -SOIC16 pinout (more info available online, or in the datasheet for your flash chip): -HOLD 1-16 SCK -VDD 2-15 MOSI -N/C 3-14 N/C -N/C 4-13 N/C -N/C 5-12 N/C -N/C 6-11 N/C -SS 7-10 GND -MISO 8-9 WP -</pre> - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): - </p> -<pre> - 18 - - 1 - 22 - - NC - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> - -You may also need to connect pins 3 and 7 (tie to 3.3V supply). These are HOLD# and WP#. -On some systems they are held high, if the flash chip is attached to the board. -If you're flashing a chip that isn't connected to a board, you'll almost certainly -have to connect them. - -SOIC8 pinout (more info available online, or in the datasheet for your flash chip): -SS 1-8 VDD -MISO 2-7 HOLD -WP 3-6 SCK -GND 4-5 MOSI -</pre> - <p> - <b>NC = no connection</b> - </p> - <p> - <b><u>DO NOT</u> connect 3.3V (PSU) yet. ONLY connect this once the pomona is connected to the flash chip.</b> - </p> - <p> - <b>You also need to connect the BLACK wire (ground/earth) from the 3.3V PSU to pin 2 on the BBB (P9 header). - It is safe to install this now - (that is, before you connect the pomona to the flash chip); in fact, you should.</b> - </p> - <p> - if you need to extend the 3.3v psu leads, just use the same colour M-F leads, <b>but</b> keep all other - leads short (10cm or less) - </p> - - <p> - You should now have something that looks like this:<br/> - <img src="images/x200/5252_bbb0.jpg" alt="" /> - <img src="images/x200/5252_bbb1.jpg" alt="" /> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="stability">Notes about stability</h1> - - <p> - <a href="http://flashrom.org/ISP">http://flashrom.org/ISP</a> - is what we typically do in libreboot, though not always. That page - has some notes about using resistors to affect stability. Currently, - we use spispeed=512 (512kHz) but it is possible to use higher speeds while - maintaining stability. - </p> - - <p> - tty0_ in #libreboot was able to get better flashing speeds with the following configuration: - </p> - <ul> - <li>"coax" with 0.1 mm core and aluminum foley (from my kitchen), add 100 Ohm resistors (serial)</li> - <li>put heatshrink above the foley, for: CS, CLK, D0, D1</li> - <li>Twisted pair used as core (in case more capacitors are needed)</li> - <li> - See this image: - <a href="http://i.imgur.com/qHGxKpj.jpg">http://i.imgur.com/qHGxKpj.jpg</a> - </li> - <li>He was able to flash at 50MHz (lower speeds are also fine).</li> - </ul> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net><br/> - Copyright © 2015 Albin Söderqvist<br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/bbb_setup.md b/docs/install/bbb_setup.md new file mode 100644 index 00000000..8471cad9 --- /dev/null +++ b/docs/install/bbb_setup.md @@ -0,0 +1,414 @@ +<div class="section"> + +How to program an SPI flash chip with the BeagleBone Black or Teensy 3.1 {#pagetop} +======================================================================== + +This document exists as a guide for reading from or writing to an SPI +flash chip with the BeagleBone Black, using the +[flashrom](http://flashrom.org/Flashrom) software. A BeagleBone Black, +rev. C was used when creating this guide, but earlier revisions may also +work. + +**NOTE: this documentation may be outdated, and discusses configuring +SPI flashing on the default Debian system that the BBB sometimes comes +with. If you want an easier time, just use [BBB +ScrewDriver](https://www.coreboot.org/BBB_screwdriver) which comes +pre-configured.** + +**This guide is written for Debian Wheezy 7.5, which is what came on the +BBB at the time this guide was written. This one: +<https://debian.beagleboard.org/images/bone-debian-7.8-lxde-4gb-armhf-2015-03-01-4gb.img.xz>** + +There was no justification for a further section for the Teensy. Simply +refer to [this page on +flashrom.org](https://www.flashrom.org/Teensy_3.1_SPI_%2B_LPC/FWH_Flasher#ISP_Usage) +for information about how to set it up, and correlate that with the pins +on the SPI flash chip as per other guides in the libreboot documentation +for each board. At the time of writing, the teensy is tested for +flashing on the ThinkPad X200, but it should work for other targets. +here is a photo of the setup for the teensy: +<http://h5ai.swiftgeek.net/IMG_20160601_120855.jpg> + +Onto the Beaglebone black\... + +[Back to previous index](./) + +</div> + +<div id="hardware_requirements" class="section"> + +Hardware requirements +===================== + +Shopping list (pictures of this hardware is shown later): + +- A [Flashrom](http://flashrom.org)-compatible external SPI + programmer: **BeagleBone Black**, sometimes referred to as \'BBB\', + (rev. C) is highly recommended. You can buy one from + [Adafruit](https://www.adafruit.com) (USA), + [ElectroKit](http://electrokit.com) (Sweden) or any of the + distributors listed [here](http://beagleboard.org/black) (look below + \'Purchase\'). We recommend this product because we know that it + works well for our purposes and doesn\'t require any non-free + software. +- Electrical/insulative tape: cover the entire bottom surface of the + BBB (the part that rests on a surface). This is important, when + placing the BBB on top of a board so that nothing shorts. Most + hardware/electronics stores have this. Optionally, you can use the + bottom half of a [hammond plastic + enclosure](http://www.hammondmfg.com/1593HAM.htm#BeagleBoneBlack). +- Clip for connecting to the flash chip: if you have a SOIC-16 flash + chip (16 pins), you will need the **Pomona 5252** or equivalent. For + SOIC-8 flash chips (8 pins), you will need the **Pomona 5250** or + equivalent. Do check which chip you have, before ordering a clip. + Also, you might as well buy two clips or more since they break + easily. [Farnell element 14](http://farnell.com/) sells these and + ships to many countries. Some people find these clips difficult to + get hold of, especially in South America. If you know of any good + suppliers, please contact the libreboot project with the relevant + information. **If you can\'t get hold of a pomona clip, some other + clips might work, e.g. 3M, but they are not always reliable. You can + also directly solder the wires to the chip, if that suits you; the + clip is just for convenience, really.** +- **External 3.3V DC power supply**, for powering the flash chip: an + ATX power supply / PSU (common on Intel/AMD desktop computers) will + work for this. A lab PSU (DC) will also work (adjusted to 3.3V). + - Getting a multimeter might be worthwhile, to verify that it\'s + supplying 3.3V. +- **External 5V DC power supply** (barrel connector), for powering the + BBB: the latter can have power supplied via USB, but a dedicated + power supply is recommended. These should be easy to find in most + places that sell electronics. **OPTIONAL. Only needed if not + powering with the USB cable, or if you want to use [EHCI + debug](../misc/bbb_ehci.html)**. +- **Pin header / jumper cables** (2.54mm / 0.1\" headers): you should + get male\--male, male\--female and female\--female cables in 10cm + size. Just get a load of them. Other possible names for these + cables/wires/leads are as follows: + - flying leads + - breadboard cables (since they are often used on breadboards). + - You might also be able to make these cables yourself. + + [Adafruit](https://www.adafruit.com) sell them, as do many others. + **Some people find them difficult to buy. Please contact the + libreboot project if you know of any good sellers.** You might also + be able to make these cables yourself. For PSU connections, using + long cables, e.g. 20cm, is fine, and you can extend them longer than + that if needed. +- **Mini USB A-B cable** (the BeagleBone probably already comes with + one.) - **OPTIONAL - only needed for [EHCI + debug](../misc/bbb_ehci.html) or for serial/ssh access without + ethernet cable (g\_multi kernel module)** +- **FTDI TTL cable or debug board**: used for accessing the serial + console on the BBB. [This + page](http://elinux.org/Beagleboard:BeagleBone_Black_Serial) + contains a list. **OPTIONAL\-\--only needed for serial console on + the BBB, if not using SSH via ethernet cable.** + +[Back to top of page.](#pagetop) + +</div> + +<div id="psu33" class="section"> + +Setting up the 3.3V DC PSU +========================== + +ATX PSU pinouts can be read on [this Wikipedia +page](https://en.wikipedia.org/wiki/Power_supply_unit_%28computer%29#Wiring_diagrams). + +You can use pin 1 or 2 (orange wire) on a 20-pin or 24-pin ATX PSU for +3.3V, and any of the ground/earth sources (black cables) for ground. +Short PS\_ON\# / Power on (green wire; pin 16 on 24-pin ATX PSU, or pin +14 on a 20-pin ATX PSU) to a ground (black; there is one right next to +it) using a wire/paperclip/jumper, then power on the PSU by grounding +PS\_ON\# (this is also how an ATX motherboard turns on a PSU). + +**DO \*\*NOT\*\* use pin 4, 6, do \*\*NOT\*\* use pin 19 or 20 (on a +20-pin ATX PSU), and DO \*\*NOT\*\* use pin 21, 22 or 23 (on a 24-pin +ATX PSU). Those wires (the red ones) are 5V, and they \*\*WILL\*\* kill +your flash chip. \*\*\*NEVER\*\*\* supply more than 3.3V to your flash +chip (that is, if it\'s a 3.3V flash chip; 5V and 1.8V SPI flash chips +do exist, but they are rare. Always check what voltage your chip takes. +Most of them take 3.3V).** + +You only need one 3.3V supply and one ground for the flash chip, after +grounding PS\_ON\#. + +The male end of a 0.1\" or 2.54mm header cable is not thick enough to +remain permanently connected to the ATX PSU on its own. When connecting +header cables to the connector on the ATX PSU, use a female end attached +to a thicker piece of wire (you could use a paper clip), or wedge the +male end of the jumper cable into the sides of the hole in the +connector, instead of going through the centre. + +Here is an example set up:\ +![](images/x200/psu33.jpg "Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net> see license notice at the end of this document") + +</div> + +<div id="bbb_access" class="section"> + +Accessing the operating system on the BBB +========================================= + +The operating system on your BBB will probably have an SSH daemon +running where the root account has no password. Use SSH to access the +operating system and set a root password. By default, the OS on your BBB +will most likely use DHCP, so it should already have an IP address. + +You will also be using the OS on your BBB for programming an SPI flash +chip. + +Alternatives to SSH (in case SSH fails) +--------------------------------------- + +You can also use a serial FTDI debug board with GNU Screen, to access +the serial console.\ +\# **screen /dev/ttyUSB0 115200**\ +Here are some example photos:\ + \ + +You can also connect the USB cable from the BBB to another computer and +a new network interface will appear, with its own IP address. This is +directly accessible from SSH, or screen:\ +\# **screen /dev/ttyACM0 115200** + +You can also access the uboot console, using the serial method instead +of SSH. + +</div> + +<div id="spidev" class="section"> + +Setting up spidev on the BBB +============================ + +Log on as root on the BBB, using either SSH or a serial console as +defined in [\#bbb\_access](#bbb_access). Make sure that you have +internet access on your BBB. + +Follow the instructions at +<http://elinux.org/BeagleBone_Black_Enable_SPIDEV#SPI0> up to (and +excluding) the point where it tells you to modify uEnv.txt + +You need to update the software on the BBB first. If you have an +element14 brand BBB (sold by Premier Farnell plc. stores like Farnell +element14, Newark element14, and Embest), you may need to [work around a +bug](https://groups.google.com/forum/?_escaped_fragment_=msg/beagleboard/LPjCn4LEY2I/alozBGsbTJMJ#!msg/beagleboard/LPjCn4LEY2I/alozBGsbTJMJ) +in the LED aging init script before you can update your software. If you +don\'t have a file named /etc/init.d/led\_aging.sh, you can skip this +step and update your software as described below. Otherwise, replace the +contents of this file with: + + #!/bin/sh -e + ### BEGIN INIT INFO + # Provides: led_aging.sh + # Required-Start: $local_fs + # Required-Stop: $local_fs + # Default-Start: 2 3 4 5 + # Default-Stop: 0 1 6 + # Short-Description: Start LED aging + # Description: Starts LED aging (whatever that is) + ### END INIT INFO + + x=$(/bin/ps -ef | /bin/grep "[l]ed_acc") + if [ ! -n "$x" -a -x /usr/bin/led_acc ]; then + /usr/bin/led_acc & + fi + +Run **apt-get update** and **apt-get upgrade** then reboot the BBB, +before continuing. +Check that the firmware exists:\ +\# **ls /lib/firmware/BB-SPI0-01-00A0.\***\ +Output: + + /lib/firmware/BB-SPI0-01-00A0.dtbo + +Then:\ +\# **echo BB-SPI0-01 > /sys/devices/bone\_capemgr.\*/slots**\ +\# **cat /sys/devices/bone\_capemgr.\*/slots**\ +Output: + + 0: 54:PF--- + 1: 55:PF--- + 2: 56:PF--- + 3: 57:PF--- + 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G + 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI + 7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-SPI0-01 + +Verify that the spidev device now exists:\ +\# **ls -al /dev/spid\***\ +Output: + + crw-rw---T 1 root spi 153, 0 Nov 19 21:07 /dev/spidev1.0 + +Now the BBB is ready to be used for flashing. Make this persist across +reboots:\ +In /etc/default/capemgr add **CAPE=BB-SPI0-01** at the end (or change +the existing **CAPE=** entry to say that, if an entry already exists. + +Get flashrom from the libreboot\_util release archive, or build it from +libreboot\_src/git if you need to. An ARM binary (statically compiled) +for flashrom exists in libreboot\_util releases. Put the flashrom binary +on your BBB. + +You may also need ich9gen, if you will be flashing an ICH9-M laptop +(such as the X200). Get it from libreboot\_util, or build it from +libreboot\_src, and put the ARM binary for it on your BBB. + +Finally, get the ROM image that you would like to flash and put that on +your BBB. + +Now test flashrom:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ +Output: + + Calibrating delay loop... OK. + No EEPROM/flash device found. + Note: flashrom can never write if the flash chip isn't found automatically. + +This means that it\'s working (the clip isn\'t connected to any flash +chip, so the error is fine). + +</div> + +<div id="clip" class="section"> + +Connecting the Pomona 5250/5252 +=============================== + +Use this image for reference when connecting the pomona to the BBB: +<http://beagleboard.org/Support/bone101#headers> (D0 = MISO or connects +to MISO). + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-16 (clip: Pomona 5252): + + NC - - 21 + 1 - - 17 + NC - - NC + NC - - NC + NC - - NC + NC - - NC + 18 - - 3.3V (PSU) + 22 - - NC - this is pin 1 on the flash chip + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + + You may also need to connect pins 1 and 9 (tie to 3.3V supply). These are HOLD# and WP#. + On some systems they are held high, if the flash chip is attached to the board. + If you're flashing a chip that isn't connected to a board, you'll almost certainly + have to connect them. + + SOIC16 pinout (more info available online, or in the datasheet for your flash chip): + HOLD 1-16 SCK + VDD 2-15 MOSI + N/C 3-14 N/C + N/C 4-13 N/C + N/C 5-12 N/C + N/C 6-11 N/C + SS 7-10 GND + MISO 8-9 WP + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-8 (clip: Pomona 5250): + + 18 - - 1 + 22 - - NC + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + + You may also need to connect pins 3 and 7 (tie to 3.3V supply). These are HOLD# and WP#. + On some systems they are held high, if the flash chip is attached to the board. + If you're flashing a chip that isn't connected to a board, you'll almost certainly + have to connect them. + + SOIC8 pinout (more info available online, or in the datasheet for your flash chip): + SS 1-8 VDD + MISO 2-7 HOLD + WP 3-6 SCK + GND 4-5 MOSI + +**NC = no connection** + +**DO NOT connect 3.3V (PSU) yet. ONLY connect this once the pomona is +connected to the flash chip.** + +**You also need to connect the BLACK wire (ground/earth) from the 3.3V +PSU to pin 2 on the BBB (P9 header). It is safe to install this now +(that is, before you connect the pomona to the flash chip); in fact, you +should.** + +if you need to extend the 3.3v psu leads, just use the same colour M-F +leads, **but** keep all other leads short (10cm or less) + +You should now have something that looks like this:\ +  + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Notes about stability {#stability} +===================== + +<http://flashrom.org/ISP> is what we typically do in libreboot, though +not always. That page has some notes about using resistors to affect +stability. Currently, we use spispeed=512 (512kHz) but it is possible to +use higher speeds while maintaining stability. + +tty0\_ in \#libreboot was able to get better flashing speeds with the +following configuration: + +- \"coax\" with 0.1 mm core and aluminum foley (from my kitchen), add + 100 Ohm resistors (serial) +- put heatshrink above the foley, for: CS, CLK, D0, D1 +- Twisted pair used as core (in case more capacitors are needed) +- See this image: <http://i.imgur.com/qHGxKpj.jpg> +- He was able to flash at 50MHz (lower speeds are also fine). + +</div> + +<div class="section"> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ +Copyright © 2015 Patrick \"P. J.\" McDermott <pj@pehjota.net>\ +Copyright © 2015 Albin Söderqvist\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/c201.html b/docs/install/c201.html deleted file mode 100644 index b009c6bd..00000000 --- a/docs/install/c201.html +++ /dev/null @@ -1,336 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ASUS Chromebook C201 installation guide</title> -</head> - -<body> - - <div class="section"> - - <h1 id="pagetop">ASUS Chromebook C201 installation guide</h1> - - <p> - These instructions are for installing Libreboot to the ASUS Chromebook C201. - Since the device ships with Coreboot, the installation instructions are the same before and after flashing Libreboot for the first time. - </p> - - <div class="important"> - - <p> - <b>If you are using libreboot_src or git, then make sure that you built the sources first (see <a href="../git/#build">../git/#build</a>).</b> - </p> - - </div> - - <p> - Look at the <a href="#rom">list of ROM images</a> to see which image is compatible with your device. - </p> - - <p> - Libreboot can be installed internally from the device, with sufficient privileges. - The installation process requires using <b>Google's modified version of flashrom</b>, - that has support for reflashing the Chromebook's SPI flash. - Otherwise, flashing externally will work with the upstream flashrom version. - </p> - - <p> - <b>Google's modified version of flashrom</b> is free software and its source code is made available by Google: <a href="https://chromium.googlesource.com/chromiumos/third_party/flashrom/">flashrom</a>.<br /> - It is not distributed along with Libreboot yet. However, it is preinstalled on the device, with ChromeOS. - </p> - - <p> - Installing Libreboot internally requires sufficient privileges on the system installed on the device.<br /> - When the device has ChromeOS installed (as it does initially), it is necessary to gain root privileges in ChromeOS, - to be able to access a root shell. - </p> - - <ul> - <li><a href="#root_chromeos">Gaining root privileges on ChromeOS</a></li> - <li><a href="#preparing_device">Preparing the device for the installation</a> - <ul> - <li><a href="#configuring_verified_boot_parameters">Configuring verified boot parameters</a></li> - <li><a href="#removing_write_protect_screw">Removing the write protect screw</a></li> - </ul> - </li> - <li><a href="">Installing Libreboot to the SPI flash</a> - <ul> - <li><a href="#installing_libreboot_internally">Installing Libreboot internally, from the device</a></li> - <li><a href="#installing_libreboot_externally">Installing Libreboot externally, with a SPI flash programmer</a></li> - </ul> - </li> - <li> - <a href="#debian">Debian GNU+Linux is recommended for this device</a> (TODO: instructions for Devuan) - </i> - </ul> - - <p> - <a href="../">Back to main index</a> - </p> - - </div> - - <div class="section"> - - <h1 id="root_chromeos">Gaining root privileges on ChromeOS</h2> - - <p> - In order to gain root privileges on ChromeOS, developer mode has to be enabled from the recovery mode screen and debugging features have to be enabled in ChromeOS. - </p> - - <div class="important"> - - <p> - Instructions to access the <a href="../depthcharge/#recovery_mode_screen">recovery mode screen</a> and <a href="../depthcharge/#enabling_developer_mode">enabling developer mode</a> are available on the page dedicated to <a href="../depthcharge/">depthcharge</a>. - </p> - - <p> - Once developer mode is enabled, the device will boot to the <a href="../depthcharge/#developer_mode_screen">developer mode screen</a>. ChromeOS can be booted by waiting for 30 seconds (the delay is shortened in Libreboot) or by pressing <b>Ctrl + D</b> - </p> - - <p> - After the system has booted, root access can be enabled by clicking on the <b>Enable debugging features</b> link. A confirmation dialog will ask whether to proceed.<br /> - After confirming by clicking <b>Proceed</b>, the device will reboot and ask for the root password to set. Finally, the operation has to be confirmed by clicking <b>Enable</b>. - </p> - - <p> - After setting the root password, it becomes possible to log-in as root. - A tty prompt can be obtained by pressing <strong>Ctrl + Alt + Next</strong>. - The <strong>Next</strong> key is the one on the top left of the keyboard. - </p> - - </div> - - </div> - - <div class="section"> - - <h1 id="preparing_device">Preparing the device for the installation</h2> - - <p> - Before installing Libreboot on the device, both its software and hardware has to be prepared to allow the installation procedure and to ensure that security features don't get in the way. - </p> - - <div class="subsection"> - - <h2 id="configuring_verified_boot_parameters">Configuring verified boot parameters</h2> - - <p> - It is recommended to have access to the <a href="../depthcharge/#developer_mode_screen">developer mode screen</a> and to <a href="../depthcharge/#configuring_verified_boot_parameters">configure the following verified boot parameters</a>: - <ul> - <li>Kernels signature verification: <i>disabled</i></li> - <li>External media boot: <i>enabled</i></li> - </ul> - Those changes can be reverted later, when the device is known to be in a working state. - </p> - - </div> - - <div class="subsection"> - - <h2 id="removing_write_protect_screw">Removing the write protect screw</h2> - - <p> - Since part of the SPI flash is write-protected by a screw, it is necessary to remove the screw to remove the write protection and allow writing Libreboot to the <i>read-only</i> part of the flash. - </p> - - <p> - To access the screw, the device has to be opened. There are 8 screws to remove from the bottom of the device, as shown on the picture below. Two are hidden under the top pads. After removing the screws, the keyboard plastic part can be carefully detached from the rest. <strong>Beware: there are cables attached to it!</strong> It is advised to flip the keyboard plastic part over, as shown on the picture below. The write protect screw is located next to the SPI flash chip, circled in red in the picture below. It has to be removed. - </p> - - <p> - <a href="images/c201/screws.jpg"><img src="images/c201/screws.jpg" alt="Screws" style="width: 400px;"/></a> - <a href="images/c201/wp-screw.jpg"><img src="images/c201/wp-screw.jpg" alt="WP screw" style="width: 400px;"/></a> - </p> - - <p> - The write protect screw can be put back in place later, when the device is known to be in a working state. - </p> - - </div> - - </div> - - <div class="section"> - - <h1 id="installing_libreboot_spi_flash">Installing Libreboot to the SPI flash</h1> - - <p> - The SPI flash (that holds Libreboot) is divided into various partitions that are used to implement parts of the CrOS security system. - Libreboot is installed in the <i>read-only</i> coreboot partition, that becomes writable after removing the write-protect screw. - </p> - - <div class="subsection"> - - <h2 id="installing_libreboot_internally">Installing Libreboot internally, from the device</h2> - - <p> - Before installing Libreboot to the SPI flash internally, the device has to be reassembled. - </p> - - <p> - All the files from the <b>veyron_speedy</b> release (or build) have to be transferred to the device. - </p> - - <p> - The following operations have to be executed with root privileges on the device (e.g. using the <em>root</em> account). - In addition, the <b>cros-flash-replace</b> script has to be made executable:<br /> - # <b>chmod a+x cros-flash-replace</b><br /> - </p> - - <p> - The SPI flash has to be read first:<br /> - # <b>flashrom -p host -r flash.img</b><br /> - <b>Note: it might be a good idea to copy the produced flash.img file at this point and store it outside of the device for backup purposes.</b> - </p> - - <p> - Then, the <b>cros-flash-replace</b> script has to be executed as such:<br /> - # <b>./cros-flash-replace flash.img coreboot ro-frid</b><br /> - If any error is shown, it is definitely a bad idea to go further than this point. - </p> - - <p> - The resulting flash image can then be flashed back:<br /> - # <b>flashrom -p host -w flash.img</b><br /> - </p> - - <p> - You should also see within the output the following:<br/> - <b>"Verifying flash... VERIFIED."</b> - </p> - - <p> - Shut down. The device will now boot to Libreboot. - </p> - - </div> - - <div class="subsection"> - - <h2 id="installing_libreboot_externally">Installing Libreboot externally, with a SPI flash programmer</h2> - - <p> - Before installing Libreboot to the SPI flash internally, the device has to be opened. - </p> - - <p> - 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 <b>WP#</b> 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 the right and has colorful cables, as shown on the picture below. - </p> - - <p> - <a href="images/c201/spi-flash-layout.jpg"><img src="images/c201/spi-flash-layout.jpg" alt="SPI flash layout" style="width: 400px;"/></a> - <a href="images/c201/battery-connector.jpg"><img src="images/c201/battery-connector.jpg" alt="Battery connector" style="width: 400px;"/></a> - </p> - - <p> - All the files from the <b>veyron_speedy</b> release (or build) have to be transferred to the host. - </p> - - <p> - The following operations have to be executed with root privileges on the host (e.g. using the <em>root</em> account). - In addition, the <b>cros-flash-replace</b> script has to be made executable:<br /> - # <b>chmod a+x cros-flash-replace</b><br /> - </p> - - <p> - The SPI flash has to be read first (using the right spi programmer):<br /> - # <b>flashrom -p <i>programmer</i> -r flash.img</b><br /> - <b>Note: it might be a good idea to copy the produced flash.img file at this point and store it outside of the device for backup purposes.</b> - </p> - - <p> - Then, the <b>cros-flash-replace</b> script has to be executed as such:<br /> - # <b>./cros-flash-replace flash.img coreboot ro-frid</b><br /> - If any error is shown, it is definitely a bad idea to go further than this point. - </p> - - <p> - The resulting flash image can then be flashed back (using the right spi programmer):<br /> - # <b>flashrom -p <i>programmer</i> -w flash.img</b><br /> - </p> - - <p> - You should also see within the output the following:<br/> - <b>"Verifying flash... VERIFIED."</b> - </p> - - <p> - The device will now boot to Libreboot. - </p> - - </div> - - <h2 id="debian"> - Debian GNU+Linux - </h2> - <p> - You might consider replacing ChromeOS with a free distro. - We have a <a href="../distros/">list of recommended distributions</a> - but Debian is recommended for this device (which is on that list). - TODO: Devuan instructions. - </p> - <p> - See <a href="https://wiki.debian.org/InstallingDebianOn/Asus/C201">https://wiki.debian.org/InstallingDebianOn/Asus/C201</a>. - </p> - - <p><a href="#pagetop">Back to top of page.</a></p> - </div> - - <div class="section"> - - <p> - Copyright © 2015 Paul Kocialkowski <contact@paulk.fr><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/c201.md b/docs/install/c201.md new file mode 100644 index 00000000..9774e335 --- /dev/null +++ b/docs/install/c201.md @@ -0,0 +1,290 @@ +<div class="section"> + +ASUS Chromebook C201 installation guide {#pagetop} +======================================= + +These instructions are for installing Libreboot to the ASUS Chromebook +C201. Since the device ships with Coreboot, the installation +instructions are the same before and after flashing Libreboot for the +first time. + +<div class="important"> + +**If you are using libreboot\_src or git, then make sure that you built +the sources first (see [../git/\#build](../git/#build)).** + +</div> + +Look at the [list of ROM images](#rom) to see which image is compatible +with your device. + +Libreboot can be installed internally from the device, with sufficient +privileges. The installation process requires using **Google\'s modified +version of flashrom**, that has support for reflashing the Chromebook\'s +SPI flash. Otherwise, flashing externally will work with the upstream +flashrom version. + +**Google\'s modified version of flashrom** is free software and its +source code is made available by Google: +[flashrom](https://chromium.googlesource.com/chromiumos/third_party/flashrom/).\ +It is not distributed along with Libreboot yet. However, it is +preinstalled on the device, with ChromeOS. + +Installing Libreboot internally requires sufficient privileges on the +system installed on the device.\ +When the device has ChromeOS installed (as it does initially), it is +necessary to gain root privileges in ChromeOS, to be able to access a +root shell. + +- [Gaining root privileges on ChromeOS](#root_chromeos) +- [Preparing the device for the installation](#preparing_device) + - [Configuring verified boot + parameters](#configuring_verified_boot_parameters) + - [Removing the write protect + screw](#removing_write_protect_screw) +- [Installing Libreboot to the SPI flash]() + - [Installing Libreboot internally, from the + device](#installing_libreboot_internally) + - [Installing Libreboot externally, with a SPI flash + programmer](#installing_libreboot_externally) +- [Debian GNU+Linux is recommended for this device](#debian) (TODO: + instructions for Devuan) + +[Back to main index](../) + +</div> + +<div class="section"> + +Gaining root privileges on ChromeOS +In order to gain root privileges on ChromeOS, developer mode has to be +enabled from the recovery mode screen and debugging features have to be +enabled in ChromeOS. + +<div class="important"> + +Instructions to access the [recovery mode +screen](../depthcharge/#recovery_mode_screen) and [enabling developer +mode](../depthcharge/#enabling_developer_mode) are available on the page +dedicated to [depthcharge](../depthcharge/). + +Once developer mode is enabled, the device will boot to the [developer +mode screen](../depthcharge/#developer_mode_screen). ChromeOS can be +booted by waiting for 30 seconds (the delay is shortened in Libreboot) +or by pressing **Ctrl + D** + +After the system has booted, root access can be enabled by clicking on +the **Enable debugging features** link. A confirmation dialog will ask +whether to proceed.\ +After confirming by clicking **Proceed**, the device will reboot and ask +for the root password to set. Finally, the operation has to be confirmed +by clicking **Enable**. + +After setting the root password, it becomes possible to log-in as root. +A tty prompt can be obtained by pressing **Ctrl + Alt + Next**. The +**Next** key is the one on the top left of the keyboard. + +</div> + +</div> + +<div class="section"> + +Preparing the device for the installation +Before installing Libreboot on the device, both its software and +hardware has to be prepared to allow the installation procedure and to +ensure that security features don\'t get in the way. + +<div class="subsection"> + +Configuring verified boot parameters {#configuring_verified_boot_parameters} +------------------------------------ + +It is recommended to have access to the [developer mode +screen](../depthcharge/#developer_mode_screen) and to [configure the +following verified boot +parameters](../depthcharge/#configuring_verified_boot_parameters): + +- Kernels signature verification: *disabled* +- External media boot: *enabled* + +Those changes can be reverted later, when the device is known to be in a +working state. + +</div> + +<div class="subsection"> + +Removing the write protect screw {#removing_write_protect_screw} +-------------------------------- + +Since part of the SPI flash is write-protected by a screw, it is +necessary to remove the screw to remove the write protection and allow +writing Libreboot to the *read-only* part of the flash. + +To access the screw, the device has to be opened. There are 8 screws to +remove from the bottom of the device, as shown on the picture below. Two +are hidden under the top pads. After removing the screws, the keyboard +plastic part can be carefully detached from the rest. **Beware: there +are cables attached to it!** It is advised to flip the keyboard plastic +part over, as shown on the picture below. The write protect screw is +located next to the SPI flash chip, circled in red in the picture below. +It has to be removed. + +[](images/c201/screws.jpg) [](images/c201/wp-screw.jpg) + +The write protect screw can be put back in place later, when the device +is known to be in a working state. + +</div> + +</div> + +<div class="section"> + +Installing Libreboot to the SPI flash {#installing_libreboot_spi_flash} +===================================== + +The SPI flash (that holds Libreboot) is divided into various partitions +that are used to implement parts of the CrOS security system. Libreboot +is installed in the *read-only* coreboot partition, that becomes +writable after removing the write-protect screw. + +<div class="subsection"> + +Installing Libreboot internally, from the device {#installing_libreboot_internally} +------------------------------------------------ + +Before installing Libreboot to the SPI flash internally, the device has +to be reassembled. + +All the files from the **veyron\_speedy** release (or build) have to be +transferred to the device. + +The following operations have to be executed with root privileges on the +device (e.g. using the *root* account). In addition, the +**cros-flash-replace** script has to be made executable:\ +\# **chmod a+x cros-flash-replace**\ + +The SPI flash has to be read first:\ +\# **flashrom -p host -r flash.img**\ +**Note: it might be a good idea to copy the produced flash.img file at +this point and store it outside of the device for backup purposes.** + +Then, the **cros-flash-replace** script has to be executed as such:\ +\# **./cros-flash-replace flash.img coreboot ro-frid**\ +If any error is shown, it is definitely a bad idea to go further than +this point. + +The resulting flash image can then be flashed back:\ +\# **flashrom -p host -w flash.img**\ + +You should also see within the output the following:\ +**\"Verifying flash\... VERIFIED.\"** + +Shut down. The device will now boot to Libreboot. + +</div> + +<div class="subsection"> + +Installing Libreboot externally, with a SPI flash programmer {#installing_libreboot_externally} +------------------------------------------------------------ + +Before installing Libreboot to the SPI flash internally, the device has +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 +the right and has colorful cables, as shown on the picture below. + +[](images/c201/spi-flash-layout.jpg) +[](images/c201/battery-connector.jpg) + +All the files from the **veyron\_speedy** release (or build) have to be +transferred to the host. + +The following operations have to be executed with root privileges on the +host (e.g. using the *root* account). In addition, the +**cros-flash-replace** script has to be made executable:\ +\# **chmod a+x cros-flash-replace**\ + +The SPI flash has to be read first (using the right spi programmer):\ +\# **flashrom -p *programmer* -r flash.img**\ +**Note: it might be a good idea to copy the produced flash.img file at +this point and store it outside of the device for backup purposes.** + +Then, the **cros-flash-replace** script has to be executed as such:\ +\# **./cros-flash-replace flash.img coreboot ro-frid**\ +If any error is shown, it is definitely a bad idea to go further than +this point. + +The resulting flash image can then be flashed back (using the right spi +programmer):\ +\# **flashrom -p *programmer* -w flash.img**\ + +You should also see within the output the following:\ +**\"Verifying flash\... VERIFIED.\"** + +The device will now boot to Libreboot. + +</div> + +Debian GNU+Linux {#debian} +---------------- + +You might consider replacing ChromeOS with a free distro. We have a +[list of recommended distributions](../distros/) but Debian is +recommended for this device (which is on that list). TODO: Devuan +instructions. + +See <https://wiki.debian.org/InstallingDebianOn/Asus/C201>. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Copyright © 2015 Paul Kocialkowski <contact@paulk.fr>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/d510mo.html b/docs/install/d510mo.html deleted file mode 100644 index 54071d01..00000000 --- a/docs/install/d510mo.html +++ /dev/null @@ -1,107 +0,0 @@ - -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>D510MO flashing tutorial</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">D510MO flashing tutorial</h1> - <p> - This guide is for those who want libreboot on their Intel D510MO - motherboard while they still have the original BIOS present. - </p> - <p> - <a href="./">Back to main index</a> - </p> - </div> - - <div class="section"> - - <h1 id="flashchips">Flash chip size</h1> - - <p> - Use this to find out:<br/> - # <b>flashrom -p internal -V</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="clip">Flashing instructions</h1> - - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - set up the BBB for flashing. - </p> - <p> - This is an image of the flash chip, for reference:<br/> - <img src="../images/d510mo/d510mo.jpg" alt="" /> - </p> - </div> - - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/d510mo.md b/docs/install/d510mo.md new file mode 100644 index 00000000..3ef3801c --- /dev/null +++ b/docs/install/d510mo.md @@ -0,0 +1,74 @@ +<div class="section"> + +D510MO flashing tutorial {#pagetop} +======================== + +This guide is for those who want libreboot on their Intel D510MO +motherboard while they still have the original BIOS present. + +[Back to main index](./) + +</div> + +<div class="section"> + +Flash chip size {#flashchips} +=============== + +Use this to find out:\ +\# **flashrom -p internal -V** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Flashing instructions {#clip} +===================== + +Refer to [bbb\_setup.html](bbb_setup.html) for how to set up the BBB for +flashing. + +This is an image of the flash chip, for reference:\ + + +</div> + +<div class="section"> + +Copyright © 2016 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/d945gclf.html b/docs/install/d945gclf.html deleted file mode 100644 index a8874e8e..00000000 --- a/docs/install/d945gclf.html +++ /dev/null @@ -1,88 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Intel D945GCLF flashing tutorial</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Intel D945GCLF flashing tutorial</h1> - <p> - This guide is for those who want libreboot on their Intel D945GCLF - motherboard while they still have the original BIOS present. - </p> - <p> - For information about this board, go to - <a href="../hcl/d945gclf.html">../hcl/d945gclf.html</a> - </p> - <p> - <a href="./">Back to main index</a> - </p> - </div> - - <div class="section"> - <h1 id="clip">Flashing instructions</h1> - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - set up the BBB for external flashing. - </p> - <p> - Here is an image of the flash chip:<br/> - <img alt="" src="../images/d945gclf/d945gclf_spi.jpg" /> - </p> - </div> - - <div class="section"> - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - </div> - -</body> -</html> diff --git a/docs/install/d945gclf.md b/docs/install/d945gclf.md new file mode 100644 index 00000000..d0d02cb9 --- /dev/null +++ b/docs/install/d945gclf.md @@ -0,0 +1,65 @@ +<div class="section"> + +Intel D945GCLF flashing tutorial {#pagetop} +================================ + +This guide is for those who want libreboot on their Intel D945GCLF +motherboard while they still have the original BIOS present. + +For information about this board, go to +[../hcl/d945gclf.html](../hcl/d945gclf.html) + +[Back to main index](./) + +</div> + +<div class="section"> + +Flashing instructions {#clip} +===================== + +Refer to [bbb\_setup.html](bbb_setup.html) for how to set up the BBB for +external flashing. + +Here is an image of the flash chip:\ + + +</div> + +<div class="section"> + +Copyright © 2016 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/ga-g41m-es2l.html b/docs/install/ga-g41m-es2l.html deleted file mode 100644 index 770f453e..00000000 --- a/docs/install/ga-g41m-es2l.html +++ /dev/null @@ -1,139 +0,0 @@ - -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>GA-G41M-ES2L flashing tutorial</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">GA-G41M-ES2L flashing tutorial</h1> - <p> - This guide is for those who want libreboot on their Intel GA-G41M-ES2L - motherboard while they still have the original BIOS present. - </p> - <p> - <a href="./">Back to main index</a> - </p> - </div> - - <div class="section"> - - <h1 id="flashchips">Flash chip size</h1> - - <p> - Use this to find out:<br/> - # <b>flashrom -p internal -V</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="clip">Flashing instructions</h1> - - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - set up the BBB for external flashing. - <strong> - You can only externally reprogram one of the chips at a time, and - you need to disable the chip that you're not flashing, by connecting 3v3 to /CS of that chip, so you will actually need - 2 test clips (you also need to connect GND on the chip that you're disabling). - </strong> - </p> - <p> - Here is an image of the flash chip:<br/> - <img alt="" src="../images/ga-g41m-es2l/ga-g41m-es2l.jpg" /> - </p> - <p> - Internal flashing is possible. Boot with the proprietary BIOS - and GNU+Linux. There are 2 flash chips (one is backup). - </p> - <p> - Flash the first chip: - <br/> - <strong>./flashrom -p internal:dualbiosindex=0 -w libreboot.rom</strong> - </p> - <p> - Flash the second chip: - <br/> - <strong>./flashrom -p internal:dualbiosindex=1 -w libreboot.rom</strong> - </p> - <p> - NOTE: you can still boot the system with just the main flash chip connected, - after desoldering the backup chip. This has been tested while libreboot was - already installed onto the main chip. - </p> - <p> - NOTE: You need the latest flashrom. Just get it on flashrom.org from - their SVN or Git repos. - </p> - <p> - NOTE: due to a bug in the hardware, the MAC address is hardcoded in coreboot-libre. - Therefore, you must set your own MAC address in your operating system. - </p> - </div> - - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/ga-g41m-es2l.md b/docs/install/ga-g41m-es2l.md new file mode 100644 index 00000000..e3218280 --- /dev/null +++ b/docs/install/ga-g41m-es2l.md @@ -0,0 +1,98 @@ +<div class="section"> + +GA-G41M-ES2L flashing tutorial {#pagetop} +============================== + +This guide is for those who want libreboot on their Intel GA-G41M-ES2L +motherboard while they still have the original BIOS present. + +[Back to main index](./) + +</div> + +<div class="section"> + +Flash chip size {#flashchips} +=============== + +Use this to find out:\ +\# **flashrom -p internal -V** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Flashing instructions {#clip} +===================== + +Refer to [bbb\_setup.html](bbb_setup.html) for how to set up the BBB for +external flashing. **You can only externally reprogram one of the chips +at a time, and you need to disable the chip that you\'re not flashing, +by connecting 3v3 to /CS of that chip, so you will actually need 2 test +clips (you also need to connect GND on the chip that you\'re +disabling).** + +Here is an image of the flash chip:\ + + +Internal flashing is possible. Boot with the proprietary BIOS and +GNU+Linux. There are 2 flash chips (one is backup). + +Flash the first chip:\ +**./flashrom -p internal:dualbiosindex=0 -w libreboot.rom** + +Flash the second chip:\ +**./flashrom -p internal:dualbiosindex=1 -w libreboot.rom** + +NOTE: you can still boot the system with just the main flash chip +connected, after desoldering the backup chip. This has been tested while +libreboot was already installed onto the main chip. + +NOTE: You need the latest flashrom. Just get it on flashrom.org from +their SVN or Git repos. + +NOTE: due to a bug in the hardware, the MAC address is hardcoded in +coreboot-libre. Therefore, you must set your own MAC address in your +operating system. + +</div> + +<div class="section"> + +Copyright © 2016 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/index.html b/docs/install/index.html deleted file mode 100644 index f35604c3..00000000 --- a/docs/install/index.html +++ /dev/null @@ -1,566 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>Installing libreboot</title> -</head> - -<body> - - <div class="section"> - - <h1 id="pagetop">Installing libreboot</h1> - <p> - This section relates to installing libreboot on supported targets. - </p> - <p> - NOTE: if running flashrom -p internal for software based flashing, and you - get an error related to /dev/mem access, you should reboot with iomem=relaxed - kernel parameter before running flashrom, or use a kernel that has - CONFIG_STRICT_DEVMEM not enabled. - </p> - <p> - <a href="../">Back to previous index</a> - </p> - - </div> - - <div class="section"> - - <h2>General information</h2> - <ul> - <li><a href="#rom">Information about libreboot ROM images</a></li> - </ul> - <h2>Flashing via software methods, on system:</h2> - <ul> - <li><a href="#flashrom">How to update or install libreboot on all systems</a></li> - <li><a href="#flashrom">ASUS KFSN4-DRE</a></li> - <li><a href="#flashrom_lenovobios">ThinkPad X60/T60 (if running Lenovo BIOS)</a></li> - <li><a href="#flashrom_macbook21">Apple MacBook2,1</a></li> - <li><a href="c201.html">ASUS Chromebook C201</a></li> - </ul> - - <h2>Setting up programmers, for external flashing via hardware method</h2> - <ul> - <li><a href="bbb_setup.html">How to program an SPI flash chip with the BeagleBone Black</a></li> - <li><a href="rpi_setup.html">How to program an SPI flash chip with the Raspberry Pi</a></li> - </ul> - <h2>Flashing via hardware methods, on system:</h2> - <ul> - <li><a href="ga-g41m-es2l.html">Gigabyte GA-G41-ES2L</a></li> - <li><a href="d510mo.html">Intel D510MO</a></li> - <li><a href="d945gclf.html">Intel D945GCLF</a></li> - <li><a href="kgpe-d16.html">ASUS KGPE-D16</a></li> - <li><a href="kcma-d8.html">ASUS KCMA-D8</a></li> - <li><a href="c201.html">ASUS Chromebook C201</a></li> - <li><a href="x60_unbrick.html">ThinkPad X60</a></li> - <li><a href="x60tablet_unbrick.html">ThinkPad X60 Tablet</a></li> - <li><a href="t60_unbrick.html">ThinkPad T60</a></li> - <li><a href="x200_external.html">ThinkPad X200/X200S/X200T</a></li> - <li><a href="r400_external.html">ThinkPad R400</a></li> - <li><a href="t400_external.html">ThinkPad T400</a></li> - <li><a href="t500_external.html">ThinkPad T500</a></li> - </ul> - - </div> - - <div class="section"> - - <h1 id="rom">Information about libreboot ROM images</h1> - - <p> - Libreboot distributes pre-compiled ROM images, built from the libreboot source code. - These images are provided for user convenience, so that they don't have - to build anything from source on their own. - </p> - - <p> - The ROM images in each archive use the following at the end of the file name, - if they are built with the GRUB payload: <b>_<i>keymap</i>_<i>mode</i>.rom</b> - </p> - <p> - Available <i>modes</i>: <b>vesafb</b> or <b>txtmode</b>. The <i>vesafb</i> ROM images are recommended, in most cases; - <i>txtmode</i> ROM images come with MemTest86+, which requires text-mode instead of the usual framebuffer used - by coreboot native graphics initialization. - </p> - <p> - <i>keymap</i> can be one of several keymaps that keyboard supports (there are quite a few), - which affects the keyboard layout configuration that is used in GRUB. It doesn't matter - which ROM image you choose here, as far as the keymap in GNU+Linux is concerned. - </p> - <p> - Keymaps are named appropriately according to each keyboard layout - support in GRUB. To learn how these keymaps are created, see - <a href="../grub/#grub_keyboard">../grub/#grub_keyboard</a> - </p> - - <h2 id="qemu">QEMU</h2> - - <p> - Libreboot comes with ROM images built for QEMU, by default: - </p> - - <p> - Examples of how to use libreboot ROM images in QEMU: - </p> - <ul> - <li>$ <b>qemu-system-i386 -M q35 -m 512 -bios qemu_q35_ich9_keymap_mode.rom</b></li> - <li>$ <b>qemu-system-i386 -M pc -m 512 -bios qemu_i440fx_piix4_keymap_mode.rom</b></li> - </ul> - <p> - You can optionally specify the <b>-serial stdio</b> argument, so that QEMU will emulate - a serial terminal on the standard input/output (most likely your terminal emulator or TTY). - </p> - <p> - Other arguments are available for QEMU. The manual will contain more information. - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="flashrom">How to update or install libreboot (if you are already running libreboot or coreboot)</h1> - - <p> - On all current targets, updating libreboot can be accomplished without disassembly and, - therefore, without having to externally re-flash using any dedicated hardware. In other words, - you can do everything entirely in software, directly from the OS that is running on your libreboot - system. - </p> - - <div class="important"> - <p> - <b>If you are using libreboot_src or git, then make sure that you built the sources first (see <a href="../git/#build">../git/#build</a>).</b> - </p> - </div> - - <p> - Look at the <a href="#rom">list of ROM images</a> to see which image is compatible with your device. - </p> - - <h2>Are you currently running the original, proprietary firmware?</h2> - - <p> - If you are currently running the proprietary firmware (not libreboot or coreboot), - then the flashing instructions for your system are going to be different. - </p> - <p> - X60/T60 users running the proprietary firmware should refer to <a href="#flashrom_lenovobios">#flashrom_lenovobios</a>. - MacBook2,1 users running Apple EFI should refer to <a href="#flashrom_macbook21">#flashrom_macbook21</a> - </p> - <p> - X200 users, refer to <a href="x200_external.html">x200_external.html</a>, - R400 users refer to <a href="r400_external.html">r400_external.html</a>, - T400 users refer to <a href="t400_external.html">t400_external.html</a>, - T500 users refer to <a href="t500_external.html">t500_external.html</a> - </p> - - <h2>ASUS KFSN4-DRE?</h2> - - <p> - Internal flashing should work just fine, even if you are - currently booting the proprietary firmware. - </p> - - <p> - Libreboot currently lacks documentation for externally - re-flashing an LPC flash chip. However, these boards have - the flash chip inside of a PLCC socket, and it is possible - to hot-swap the chips. If you want to back up your - known-working image, simply hot-swap the chip for one that - is the same capacity, after having dumped a copy of the - current firmware (flashrom -p internal -r yourchosenname.rom), - and then flash that chip with the known-working image. - Check whether the system still boots, and if it does, then - it should be safe to flash the new image (because you now - have a backup of the old image). - </p> - - <p> - Keeping at least one spare LPC PLCC chip with working firmware - on it is highly recommended, in case of bricks. - </p> - - <p> - <b> - DO NOT hot-swap the chip with your bare hands. Use a PLCC - chip extractor. These can be found online. - See <a href="http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools">http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools</a> - </b> - </p> - - <p> - Do check the HCL entry: <a href="../hcl/kfsn4-dre.html">../hcl/kfsn4-dre.html</a> - </p> - - <h2>ASUS KGPE-D16?</h2> - - <p> - If you have the proprietary BIOS, you need to flash libreboot externally. - See <a href="kgpe-d16.html">kgpe-d16.html</a>. - </p> - <p> - If you already have coreboot or libreboot installed, without write protection on the flash - chip, then you can do it in software (otherwise, see link above). - </p> - - <p> - <b> - DO NOT hot-swap the chip with your bare hands. Use a PDIP-8 - chip extractor. These can be found online. - See <a href="http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools">http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools</a> - </b> - </p> - - <p> - Do check the HCL entry: <a href="../hcl/kgpe-d16.html">../hcl/kgpe-d16.html</a> - </p> - - <h2>ASUS KCMA-D8?</h2> - - <p> - If you have the proprietary BIOS, you need to flash libreboot externally. - See <a href="kgpe-d8.html">kcma-d8.html</a>. - </p> - <p> - If you already have coreboot or libreboot installed, without write protection on the flash - chip, then you can do it in software (otherwise, see link above). - </p> - - <p> - <b> - DO NOT hot-swap the chip with your bare hands. Use a PDIP-8 - chip extractor. These can be found online. - See <a href="http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools">http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools</a> - </b> - </p> - - <p> - Do check the HCL entry: <a href="../hcl/kcma-d8.html">../hcl/kcma-d8.html</a> - </p> - - <h2>Intel D945GCLF?</h2> - <p> - If you're running the original Intel factory BIOS, then you will need to flash externally. - For instructions on how to do that, refer to <a href="d945gclf.html">d945gclf.html</a>. - </p> - <p> - Otherwise, read the generic instructions below for using the <em>flash</em> script. - </p> - - <h2>Are you currently running libreboot (or coreboot)?</h2> - - <p> - X60/T60 users should be fine with this guide. If you write-protected the flash chip, please refer to - <a href="x60_unbrick.html">x60_unbrick.html</a>, <a href="x60tablet_unbrick.html">x60tablet_unbrick.html</a> - or <a href="t60_unbrick.html">t60_unbrick.html</a>. <i>This probably does not apply to you. Most people - do not write-protect the flash chip, so you probably didn't either.</i> - </p> - <p> - Similarly, it is possible to write-protect the flash chip in coreboot or libreboot on GM45 laptops - (X200/R400/T400/T500). If you did this, then you will need to use the links above for flashing, - treating your laptop as though it currently has the proprietary firmware (because write-protected SPI flash - requires external re-flashing, as is also the case when running the proprietary firmware). - </p> - - <p> - If you did not write-protect the flash chip, or it came to you without any write-protection - (<b><i>libreboot does not write-protect the flash chip by default, so this probably applies to you</i></b>), - read on! - </p> - - <h2>MAC address on GM45 (X200/R400/T400/T500)</h2> - - <p> - <b>Users of the X200/R400/T400/T500 take note:</b> The MAC address for the onboard ethernet chipset - is located inside the flash chip. Libreboot ROM images for these laptops contain a generic MAC - address by default, but this is not what you want. - <i>Make sure to change the MAC address inside the ROM image, before flashing it. - The instructions on <a href="../hcl/gm45_remove_me.html#ich9gen">../hcl/gm45_remove_me.html#ich9gen</a> - show how to do this.</i> - </p> - - <p> - It is important that you change the default MAC address, before flashing. It will be printed on a sticker - at the bottom of the laptop, or it will be printed on a sticker next to or underneath the RAM. Alternatively, - and assuming that your current firmware has the correct MAC address in it, you can get it from your OS. - </p> - <h2>Apple iMac 5,2?</h2> - <p> - Internal flashing works, even when flashing from Apple EFI to libreboot. Continue reading the instructions below. - </p> - <p> - <strong> - NOTE: If you're flashing an older version of Libreboot, - the iMac5,2 motherboard is compatible with the MacBook2,1. - Simply flash a MacBook2,1 ROM image, and it should work. - </strong> - </p> - - <h2>Flash chip size</h2> - - <p> - Use this to find out:<br/> - # <b>flashrom -p internal -V</b> - </p> - - <h2>All good?</h2> - - <p>Excellent! Moving on...</p> - - <p> - Download the <i>libreboot_util.tar.xz</i> archive, and extract it. Inside, you will find - a directory called <i>flashrom</i>. This contains statically compiled executable files of - the <i>flashrom</i> utility, which you will use to re-flash your libreboot system. - </p> - - <p> - Simply use <i>cd</i> on your terminal, to switch to the <i>libreboot_util</i> directory. Inside, - there is a script called <i>flash</i>, which will detect what CPU architecture you have - (e.g. i686, x86_64) and use the appropriate executable. It is also possible for you to - build these executables from the libreboot source code archives. - </p> - - <div class="important"> - <p> - How to update the flash chip contents:<br/> - $ <b>sudo ./flash update <a href="#rom">yourrom.rom</a></b> - </p> - </div> - <div class="important"> - <p> - Ocassionally, coreboot changes the name of a given board. If flashrom complains about a board mismatch, but - you are sure that you chose the correct ROM image, then run this alternative command:<br/> - $ <b>sudo ./flash forceupdate <a href="#rom">yourrom.rom</a></b> - </p> - </div> - - <div class="important"> - - <p> - You should see <b>"Verifying flash... VERIFIED."</b> written at the end of the flashrom output. <b>Shut down</b> - after you see this, and then boot up again after a few seconds. - </p> - - </div> - - <p><a href="#pagetop">Back to top of page</a></p> - - </div> - - <div class="section"> - - <h1 id="flashrom_lenovobios">ThinkPad X60/T60: Initial installation guide (if running the proprietary firmware)</h1> - - <p><b>This is for the ThinkPad X60 and T60 while running Lenovo BIOS. If you already have coreboot or libreboot running, - then go to <a href="#flashrom">#flashrom</a> instead!</b></p> - - <p><b>If you are flashing a Lenovo ThinkPad T60, be sure to read <a href="../hcl/#supported_t60_list">../hcl/#supported_t60_list</a></b></p> - - <div class="important"> - <p> - <b>If you are using libreboot_src or git, then make sure that you built the sources first (see <a href="../git/#build">../git/#build</a>).</b> - </p> - </div> - - <p> - <b> - Warning: this guide will not instruct the user how to backup the original Lenovo BIOS firmware. These backups - are tied to each system, and will not work on any other. - For that, please refer to <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>. - </b> - </p> - - <div class="important"> - - <p> - <b> - If you're using libreboot 20150518, note that there is a mistake in the flashing script. - do this: <em>rm -f patch && wget -O flash https://notabug.org/vimuser/libreboot/raw/9d850543ad90b72e0e333c98075530b31e5d23f1/flash && chmod +x flash</em> - </b> - </p> - - <p> - The first half of the procedure is as follows:<br/> - $ <b>sudo ./flash i945lenovo_firstflash <a href="#rom">yourrom.rom</a>.</b> - </p> - - </div> - - <div class="important"> - - <p> - You should see within the output the following:<br/> - <b>"Updated BUC.TS=1 - 64kb address ranges at 0xFFFE0000 and 0xFFFF0000 are swapped"</b>. - </p> - - <p> - You should also see within the output the following:<br/> - <b>"Your flash chip is in an unknown state"</b>, <b>"FAILED"</b> and <b>"DO NOT REBOOT OR POWEROFF"</b><br/> - Seeing this means that the operation was a <b>resounding</b> success! <b>DON'T PANIC</b>. - </p> - - <p> - See this link for more details: - <a href="http://thread.gmane.org/gmane.linux.bios.flashrom/575">http://thread.gmane.org/gmane.linux.bios.flashrom/575</a>. - </p> - - <p> - If the above is what you see, then <b>SHUT DOWN</b>. Wait a few seconds, and then boot; libreboot is running, but there is a 2nd procedure <b>*needed*</b> (see below). - </p> - - </div> - - <div class="important"> - <p> - When you have booted up again, you must also do this:<br/> - $ <b>sudo ./flash i945lenovo_secondflash <a href="#rom">yourrom.rom</a></b> - </p> - <p> - If flashing fails at this stage, try the following:<br/> - $ <b>sudo ./flashrom/i686/flashrom -p internal:laptop=force_I_want_a_brick -w <a href="#rom">yourrom.rom</a></b> - </p> - </div> - - <div class="important"> - - <p> - You should see within the output the following:<br/> - <b>"Updated BUC.TS=0 - 128kb address range 0xFFFE0000-0xFFFFFFFF is untranslated"</b> - </p> - - <p> - You should also see within the output the following:<br/> - <b>"Verifying flash... VERIFIED."</b> - </p> - - </div> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <h1 id="flashrom_macbook21">MacBook2,1: Initial installation guide (if running the proprietary firmware)</h1> - - <div class="important"> - - <p> - <b>If you have a MacBook1,1, refer to <a href="../hcl/#macbook11">../hcl/#macbook11</a> for flashing instructions.</b> - </p> - - </div> - - <p> - <b> - This is for the MacBook2,1 while running Apple EFI firmware. If you already have - coreboot or libreboot running, then go to <a href="#flashrom">#flashrom</a> instead! - </b> - </p> - - <p> - Be sure to read the information in <a href="../hcl/#macbook21">../hcl/#macbook21</a>. - </p> - - <p> - <b> - Warning: this guide will not instruct the user how to backup the original Apple EFI firmware. - For that, please refer to <a href="http://www.coreboot.org/Board:apple/macbook21">http://www.coreboot.org/Board:apple/macbook21</a>. - </b> - </p> - - <div class="important"> - <p> - <b>If you are using libreboot_src or git, then make sure that you built the sources first (see <a href="../git/#build">../git/#build</a>).</b> - </p> - </div> - - <p> - Look at the <a href="#rom">list of ROM images</a> to see which image is compatible with your device. - </p> - - <div class="important"> - <p> - Use this flashing script, to install libreboot:<br/> - $ <b>sudo ./flash i945apple_firstflash <a href="#rom">yourrom.rom</a></b> - </p> - </div> - - <div class="important"> - - <p> - You should also see within the output the following:<br/> - <b>"Verifying flash... VERIFIED."</b> - </p> - - <p> - Shut down. - </p> - - </div> - - <p><a href="#pagetop">Back to top of page.</a></p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/index.md b/docs/install/index.md new file mode 100644 index 00000000..66e750e7 --- /dev/null +++ b/docs/install/index.md @@ -0,0 +1,484 @@ +<div class="section"> + +Installing libreboot {#pagetop} +==================== + +This section relates to installing libreboot on supported targets. + +NOTE: if running flashrom -p internal for software based flashing, and +you get an error related to /dev/mem access, you should reboot with +iomem=relaxed kernel parameter before running flashrom, or use a kernel +that has CONFIG\_STRICT\_DEVMEM not enabled. + +[Back to previous index](../) + +</div> + +<div class="section"> + +General information +------------------- + +- [Information about libreboot ROM images](#rom) + +Flashing via software methods, on system: +----------------------------------------- + +- [How to update or install libreboot on all systems](#flashrom) +- [ASUS KFSN4-DRE](#flashrom) +- [ThinkPad X60/T60 (if running Lenovo BIOS)](#flashrom_lenovobios) +- [Apple MacBook2,1](#flashrom_macbook21) +- [ASUS Chromebook C201](c201.html) + +Setting up programmers, for external flashing via hardware method +----------------------------------------------------------------- + +- [How to program an SPI flash chip with the BeagleBone + Black](bbb_setup.html) +- [How to program an SPI flash chip with the Raspberry + Pi](rpi_setup.html) + +Flashing via hardware methods, on system: +----------------------------------------- + +- [Gigabyte GA-G41-ES2L](ga-g41m-es2l.html) +- [Intel D510MO](d510mo.html) +- [Intel D945GCLF](d945gclf.html) +- [ASUS KGPE-D16](kgpe-d16.html) +- [ASUS KCMA-D8](kcma-d8.html) +- [ASUS Chromebook C201](c201.html) +- [ThinkPad X60](x60_unbrick.html) +- [ThinkPad X60 Tablet](x60tablet_unbrick.html) +- [ThinkPad T60](t60_unbrick.html) +- [ThinkPad X200/X200S/X200T](x200_external.html) +- [ThinkPad R400](r400_external.html) +- [ThinkPad T400](t400_external.html) +- [ThinkPad T500](t500_external.html) + +</div> + +<div class="section"> + +Information about libreboot ROM images {#rom} +====================================== + +Libreboot distributes pre-compiled ROM images, built from the libreboot +source code. These images are provided for user convenience, so that +they don\'t have to build anything from source on their own. + +The ROM images in each archive use the following at the end of the file +name, if they are built with the GRUB payload: +**\_*keymap*\_*mode*.rom** + +Available *modes*: **vesafb** or **txtmode**. The *vesafb* ROM images +are recommended, in most cases; *txtmode* ROM images come with +MemTest86+, which requires text-mode instead of the usual framebuffer +used by coreboot native graphics initialization. + +*keymap* can be one of several keymaps that keyboard supports (there are +quite a few), which affects the keyboard layout configuration that is +used in GRUB. It doesn\'t matter which ROM image you choose here, as far +as the keymap in GNU+Linux is concerned. + +Keymaps are named appropriately according to each keyboard layout +support in GRUB. To learn how these keymaps are created, see +[../grub/\#grub\_keyboard](../grub/#grub_keyboard) + +QEMU +---- + +Libreboot comes with ROM images built for QEMU, by default: + +Examples of how to use libreboot ROM images in QEMU: + +- \$ **qemu-system-i386 -M q35 -m 512 -bios + qemu\_q35\_ich9\_keymap\_mode.rom** +- \$ **qemu-system-i386 -M pc -m 512 -bios + qemu\_i440fx\_piix4\_keymap\_mode.rom** + +You can optionally specify the **-serial stdio** argument, so that QEMU +will emulate a serial terminal on the standard input/output (most likely +your terminal emulator or TTY). + +Other arguments are available for QEMU. The manual will contain more +information. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +How to update or install libreboot (if you are already running libreboot or coreboot) {#flashrom} +===================================================================================== + +On all current targets, updating libreboot can be accomplished without +disassembly and, therefore, without having to externally re-flash using +any dedicated hardware. In other words, you can do everything entirely +in software, directly from the OS that is running on your libreboot +system. + +<div class="important"> + +**If you are using libreboot\_src or git, then make sure that you built +the sources first (see [../git/\#build](../git/#build)).** + +</div> + +Look at the [list of ROM images](#rom) to see which image is compatible +with your device. + +Are you currently running the original, proprietary firmware? +------------------------------------------------------------- + +If you are currently running the proprietary firmware (not libreboot or +coreboot), then the flashing instructions for your system are going to +be different. + +X60/T60 users running the proprietary firmware should refer to +[\#flashrom\_lenovobios](#flashrom_lenovobios). MacBook2,1 users running +Apple EFI should refer to [\#flashrom\_macbook21](#flashrom_macbook21) + +X200 users, refer to [x200\_external.html](x200_external.html), R400 +users refer to [r400\_external.html](r400_external.html), T400 users +refer to [t400\_external.html](t400_external.html), T500 users refer to +[t500\_external.html](t500_external.html) + +ASUS KFSN4-DRE? +--------------- + +Internal flashing should work just fine, even if you are currently +booting the proprietary firmware. + +Libreboot currently lacks documentation for externally re-flashing an +LPC flash chip. However, these boards have the flash chip inside of a +PLCC socket, and it is possible to hot-swap the chips. If you want to +back up your known-working image, simply hot-swap the chip for one that +is the same capacity, after having dumped a copy of the current firmware +(flashrom -p internal -r yourchosenname.rom), and then flash that chip +with the known-working image. Check whether the system still boots, and +if it does, then it should be safe to flash the new image (because you +now have a backup of the old image). + +Keeping at least one spare LPC PLCC chip with working firmware on it is +highly recommended, in case of bricks. + +**DO NOT hot-swap the chip with your bare hands. Use a PLCC chip +extractor. These can be found online. See +<http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools>** + +Do check the HCL entry: [../hcl/kfsn4-dre.html](../hcl/kfsn4-dre.html) + +ASUS KGPE-D16? +-------------- + +If you have the proprietary BIOS, you need to flash libreboot +externally. See [kgpe-d16.html](kgpe-d16.html). + +If you already have coreboot or libreboot installed, without write +protection on the flash chip, then you can do it in software (otherwise, +see link above). + +**DO NOT hot-swap the chip with your bare hands. Use a PDIP-8 chip +extractor. These can be found online. See +<http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools>** + +Do check the HCL entry: [../hcl/kgpe-d16.html](../hcl/kgpe-d16.html) + +ASUS KCMA-D8? +------------- + +If you have the proprietary BIOS, you need to flash libreboot +externally. See [kcma-d8.html](kgpe-d8.html). + +If you already have coreboot or libreboot installed, without write +protection on the flash chip, then you can do it in software (otherwise, +see link above). + +**DO NOT hot-swap the chip with your bare hands. Use a PDIP-8 chip +extractor. These can be found online. See +<http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools>** + +Do check the HCL entry: [../hcl/kcma-d8.html](../hcl/kcma-d8.html) + +Intel D945GCLF? +--------------- + +If you\'re running the original Intel factory BIOS, then you will need +to flash externally. For instructions on how to do that, refer to +[d945gclf.html](d945gclf.html). + +Otherwise, read the generic instructions below for using the *flash* +script. + +Are you currently running libreboot (or coreboot)? +-------------------------------------------------- + +X60/T60 users should be fine with this guide. If you write-protected the +flash chip, please refer to [x60\_unbrick.html](x60_unbrick.html), +[x60tablet\_unbrick.html](x60tablet_unbrick.html) or +[t60\_unbrick.html](t60_unbrick.html). *This probably does not apply to +you. Most people do not write-protect the flash chip, so you probably +didn\'t either.* + +Similarly, it is possible to write-protect the flash chip in coreboot or +libreboot on GM45 laptops (X200/R400/T400/T500). If you did this, then +you will need to use the links above for flashing, treating your laptop +as though it currently has the proprietary firmware (because +write-protected SPI flash requires external re-flashing, as is also the +case when running the proprietary firmware). + +If you did not write-protect the flash chip, or it came to you without +any write-protection (***libreboot does not write-protect the flash chip +by default, so this probably applies to you***), read on! + +MAC address on GM45 (X200/R400/T400/T500) +----------------------------------------- + +**Users of the X200/R400/T400/T500 take note:** The MAC address for the +onboard ethernet chipset is located inside the flash chip. Libreboot ROM +images for these laptops contain a generic MAC address by default, but +this is not what you want. *Make sure to change the MAC address inside +the ROM image, before flashing it. The instructions on +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +show how to do this.* + +It is important that you change the default MAC address, before +flashing. It will be printed on a sticker at the bottom of the laptop, +or it will be printed on a sticker next to or underneath the RAM. +Alternatively, and assuming that your current firmware has the correct +MAC address in it, you can get it from your OS. + +Apple iMac 5,2? +--------------- + +Internal flashing works, even when flashing from Apple EFI to libreboot. +Continue reading the instructions below. + +**NOTE: If you\'re flashing an older version of Libreboot, the iMac5,2 +motherboard is compatible with the MacBook2,1. Simply flash a MacBook2,1 +ROM image, and it should work.** + +Flash chip size +--------------- + +Use this to find out:\ +\# **flashrom -p internal -V** + +All good? +--------- + +Excellent! Moving on\... + +Download the *libreboot\_util.tar.xz* archive, and extract it. Inside, +you will find a directory called *flashrom*. This contains statically +compiled executable files of the *flashrom* utility, which you will use +to re-flash your libreboot system. + +Simply use *cd* on your terminal, to switch to the *libreboot\_util* +directory. Inside, there is a script called *flash*, which will detect +what CPU architecture you have (e.g. i686, x86\_64) and use the +appropriate executable. It is also possible for you to build these +executables from the libreboot source code archives. + +<div class="important"> + +How to update the flash chip contents:\ +\$ **sudo ./flash update [yourrom.rom](#rom)** + +</div> + +<div class="important"> + +Ocassionally, coreboot changes the name of a given board. If flashrom +complains about a board mismatch, but you are sure that you chose the +correct ROM image, then run this alternative command:\ +\$ **sudo ./flash forceupdate [yourrom.rom](#rom)** + +</div> + +<div class="important"> + +You should see **\"Verifying flash\... VERIFIED.\"** written at the end +of the flashrom output. **Shut down** after you see this, and then boot +up again after a few seconds. + +</div> + +[Back to top of page](#pagetop) + +</div> + +<div class="section"> + +ThinkPad X60/T60: Initial installation guide (if running the proprietary firmware) {#flashrom_lenovobios} +================================================================================== + +**This is for the ThinkPad X60 and T60 while running Lenovo BIOS. If you +already have coreboot or libreboot running, then go to +[\#flashrom](#flashrom) instead!** + +**If you are flashing a Lenovo ThinkPad T60, be sure to read +[../hcl/\#supported\_t60\_list](../hcl/#supported_t60_list)** + +<div class="important"> + +**If you are using libreboot\_src or git, then make sure that you built +the sources first (see [../git/\#build](../git/#build)).** + +</div> + +**Warning: this guide will not instruct the user how to backup the +original Lenovo BIOS firmware. These backups are tied to each system, +and will not work on any other. For that, please refer to +<http://www.coreboot.org/Board:lenovo/x60/Installation>.** + +<div class="important"> + +**If you\'re using libreboot 20150518, note that there is a mistake in +the flashing script. do this: *rm -f patch && wget -O flash +https://notabug.org/vimuser/libreboot/raw/9d850543ad90b72e0e333c98075530b31e5d23f1/flash +&& chmod +x flash*** + +The first half of the procedure is as follows:\ +\$ **sudo ./flash i945lenovo\_firstflash [yourrom.rom](#rom).** + +</div> + +<div class="important"> + +You should see within the output the following:\ +**\"Updated BUC.TS=1 - 64kb address ranges at 0xFFFE0000 and 0xFFFF0000 +are swapped\"**. + +You should also see within the output the following:\ +**\"Your flash chip is in an unknown state\"**, **\"FAILED\"** and +**\"DO NOT REBOOT OR POWEROFF\"**\ +Seeing this means that the operation was a **resounding** success! +**DON\'T PANIC**. + +See this link for more details: +<http://thread.gmane.org/gmane.linux.bios.flashrom/575>. + +If the above is what you see, then **SHUT DOWN**. Wait a few seconds, +and then boot; libreboot is running, but there is a 2nd procedure +**\*needed\*** (see below). + +</div> + +<div class="important"> + +When you have booted up again, you must also do this:\ +\$ **sudo ./flash i945lenovo\_secondflash [yourrom.rom](#rom)** + +If flashing fails at this stage, try the following:\ +\$ **sudo ./flashrom/i686/flashrom -p +internal:laptop=force\_I\_want\_a\_brick -w [yourrom.rom](#rom)** + +</div> + +<div class="important"> + +You should see within the output the following:\ +**\"Updated BUC.TS=0 - 128kb address range 0xFFFE0000-0xFFFFFFFF is +untranslated\"** + +You should also see within the output the following:\ +**\"Verifying flash\... VERIFIED.\"** + +</div> + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +MacBook2,1: Initial installation guide (if running the proprietary firmware) {#flashrom_macbook21} +============================================================================ + +<div class="important"> + +**If you have a MacBook1,1, refer to +[../hcl/\#macbook11](../hcl/#macbook11) for flashing instructions.** + +</div> + +**This is for the MacBook2,1 while running Apple EFI firmware. If you +already have coreboot or libreboot running, then go to +[\#flashrom](#flashrom) instead!** + +Be sure to read the information in +[../hcl/\#macbook21](../hcl/#macbook21). + +**Warning: this guide will not instruct the user how to backup the +original Apple EFI firmware. For that, please refer to +<http://www.coreboot.org/Board:apple/macbook21>.** + +<div class="important"> + +**If you are using libreboot\_src or git, then make sure that you built +the sources first (see [../git/\#build](../git/#build)).** + +</div> + +Look at the [list of ROM images](#rom) to see which image is compatible +with your device. + +<div class="important"> + +Use this flashing script, to install libreboot:\ +\$ **sudo ./flash i945apple\_firstflash [yourrom.rom](#rom)** + +</div> + +<div class="important"> + +You should also see within the output the following:\ +**\"Verifying flash\... VERIFIED.\"** + +Shut down. + +</div> + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Copyright © 2014, 2015, 2016 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/kcma-d8.html b/docs/install/kcma-d8.html deleted file mode 100644 index c4dfbc71..00000000 --- a/docs/install/kcma-d8.html +++ /dev/null @@ -1,109 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>KCMA-D8 external flashing instructions</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">KCMA-D8 external flashing instructions</h1> - <p>Initial flashing instructions for kcma-d8.</p> - <p> - This guide is for those who want libreboot on their ASUS kcma-d8 - motherboard, while they still have the proprietary ASUS BIOS present. - This guide can also be followed (adapted) if you brick you board, to know - how to recover. - </p> - - - <p> - <b>Memory initialization is still problematic, for some modules. We recommend avoiding Kingston modules.</b> - </p> - <p> - For more general information about this board, refer to - <a href="../hcl/kcma-d8.html">../hcl/kcma-d8.html</a>. - </p> - - <p> - TODO: show photos here, and other info. - </p> - - <ul> - <li><a href="#preinstall">kcma-d8 boards (and full systems) with libreboot preinstalled</a></li> - <li><a href="#programmer">External programmer</a></li> - </ul> - - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - <h1 id="programmer">External programmer</h1> - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for a guide on - how to set up an external SPI programmer. - </p> - <p> - The flash chip is in a PDIP 8 socket (SPI flash chip) on the motherboard, - which you take out and then re-flash with libreboot, using the programmer. - <b>DO NOT</b> remove the chip with your hands. Use a chip extractor tool. - </p> - </div> - - <div class="section"> - - <p> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/kcma-d8.md b/docs/install/kcma-d8.md new file mode 100644 index 00000000..ecbb4a17 --- /dev/null +++ b/docs/install/kcma-d8.md @@ -0,0 +1,80 @@ +<div class="section"> + +KCMA-D8 external flashing instructions {#pagetop} +====================================== + +Initial flashing instructions for kcma-d8. + +This guide is for those who want libreboot on their ASUS kcma-d8 +motherboard, while they still have the proprietary ASUS BIOS present. +This guide can also be followed (adapted) if you brick you board, to +know how to recover. + +**Memory initialization is still problematic, for some modules. We +recommend avoiding Kingston modules.** + +For more general information about this board, refer to +[../hcl/kcma-d8.html](../hcl/kcma-d8.html). + +TODO: show photos here, and other info. + +- [kcma-d8 boards (and full systems) with libreboot + preinstalled](#preinstall) +- [External programmer](#programmer) + +[Back to main index](./) + +</div> + +<div class="section"> + +External programmer {#programmer} +=================== + +Refer to [bbb\_setup.html](bbb_setup.html) for a guide on how to set up +an external SPI programmer. + +The flash chip is in a PDIP 8 socket (SPI flash chip) on the +motherboard, which you take out and then re-flash with libreboot, using +the programmer. **DO NOT** remove the chip with your hands. Use a chip +extractor tool. + +</div> + +<div class="section"> + +Copyright © 2016 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/kgpe-d16.html b/docs/install/kgpe-d16.html deleted file mode 100644 index d2e10dd4..00000000 --- a/docs/install/kgpe-d16.html +++ /dev/null @@ -1,124 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>KGPE-D16 external flashing instructions</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">KGPE-D16 external flashing instructions</h1> - <p>Initial flashing instructions for KGPE-D16.</p> - <p> - This guide is for those who want libreboot on their ASUS KGPE-D16 - motherboard, while they still have the proprietary ASUS BIOS present. - This guide can also be followed (adapted) if you brick you board, to know - how to recover. - </p> - - - <p> - <b>Memory initialization is still problematic, for some modules. We recommend avoiding Kingston modules.</b> - </p> - - <p> - For more general information about this board, refer to - <a href="../hcl/kgpe-d16.html">../hcl/kgpe-d16.html</a>. - </p> - - <p> - TODO: show photos here, and other info. - </p> - - <ul> - <li><a href="#preinstall">KGPE-D16 boards (and full systems) with libreboot preinstalled</a></li> - <li><a href="#programmer">External programmer</a></li> - </ul> - - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - - <h1 id="preinstall">KGPE-D16 boards (and full systems) with libreboot preinstalled</h1> - - <p> - If you don't want to install libreboot yourself, companies exist that sell these boards - with libreboot pre-installed, along with a free GNU+Linux distribution. - </p> - <p> - Check the <a href="../../suppliers">suppliers</a> page for more information. - </p> - - </div> - - <div class="section"> - <h1 id="programmer">External programmer</h1> - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for a guide on - how to set up an external SPI programmer. - </p> - <p> - The flash chip is in a PDIP 8 socket (SPI flash chip) on the motherboard, - which you take out and then re-flash with libreboot, using the programmer. - <b>DO NOT</b> remove the chip with your hands. Use a chip extractor tool. - </p> - </div> - - <div class="section"> - - <p> - Copyright © 2015 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/kgpe-d16.md b/docs/install/kgpe-d16.md new file mode 100644 index 00000000..a91af3ff --- /dev/null +++ b/docs/install/kgpe-d16.md @@ -0,0 +1,93 @@ +<div class="section"> + +KGPE-D16 external flashing instructions {#pagetop} +======================================= + +Initial flashing instructions for KGPE-D16. + +This guide is for those who want libreboot on their ASUS KGPE-D16 +motherboard, while they still have the proprietary ASUS BIOS present. +This guide can also be followed (adapted) if you brick you board, to +know how to recover. + +**Memory initialization is still problematic, for some modules. We +recommend avoiding Kingston modules.** + +For more general information about this board, refer to +[../hcl/kgpe-d16.html](../hcl/kgpe-d16.html). + +TODO: show photos here, and other info. + +- [KGPE-D16 boards (and full systems) with libreboot + preinstalled](#preinstall) +- [External programmer](#programmer) + +[Back to main index](./) + +</div> + +<div class="section"> + +KGPE-D16 boards (and full systems) with libreboot preinstalled {#preinstall} +============================================================== + +If you don\'t want to install libreboot yourself, companies exist that +sell these boards with libreboot pre-installed, along with a free +GNU+Linux distribution. + +Check the [suppliers](../../suppliers) page for more information. + +</div> + +<div class="section"> + +External programmer {#programmer} +=================== + +Refer to [bbb\_setup.html](bbb_setup.html) for a guide on how to set up +an external SPI programmer. + +The flash chip is in a PDIP 8 socket (SPI flash chip) on the +motherboard, which you take out and then re-flash with libreboot, using +the programmer. **DO NOT** remove the chip with your hands. Use a chip +extractor tool. + +</div> + +<div class="section"> + +Copyright © 2015 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/r400_external.html b/docs/install/r400_external.html deleted file mode 100644 index 04bb8a98..00000000 --- a/docs/install/r400_external.html +++ /dev/null @@ -1,587 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad R400: flashing tutorial (BeagleBone Black)</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Flashing the R400 with a BeagleBone Black</h1> - <p>Initial flashing instructions for R400.</p> - <p> - This guide is for those who want libreboot on their ThinkPad R400 - while they still have the original Lenovo BIOS present. This guide - can also be followed (adapted) if you brick your R400, to know how - to recover. - </p> - <p> - Before following this section, please make sure to setup your libreboot ROM properly first. - Although ROM images are provided pre-built in libreboot, there are some modifications that - you need to make to the one you chose before flashing. (instructions referenced later in - this guide) - </p> - - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - - <h1 id="t400">Libreboot T400</h1> - <p> - You may also be interested in the smaller, more portable <a href="t400_external.html">Libreboot T400</a>. - </p> - - </div> - - <div class="section"> - - <h2 id="serial_port">Serial port</h2> - - <p> - EHCI debug might not be needed. It has been reported that the docking station - for this laptop has a serial port, so it might be possible to use that instead. - </p> - - </div> - - <div class="section" id="cpu_compatibility"> - - <h1>A note about CPUs</h1> - <p> - <a href="http://www.thinkwiki.org/wiki/Category:R400">ThinkWiki</a> has a list of CPUs - for this system. The Core 2 Duo P8400 and P8600 are believed to work in libreboot. - The Core 2 Duo T9600 was confirmed to work, so the T9400 probably also works. - <b>The Core 2 Duo T5870/5670 and Celeron M 575/585 are untested!</b> - </p> - - <h2>Quad-core CPUs</h2> - - <p> - Incompatible. Do not use. - </p> - - </div> - - <div class="section" id="switchable_graphics"> - - <h1>A note about GPUs</h1> - - <p> - Some models have an Intel GPU, while others have both an ATI and an Intel GPU; this - is referred to as "switchable graphics". In the <i>BIOS setup</i> program - for lenovobios, you can specify that the system will use one or the other (but not both). - </p> - - <p> - Libreboot is known to work on systems with only the Intel GPU, using native graphics initialization. - On systems with switchable graphics, the Intel GPU is used and the ATI GPU is disabled, so - native graphics initialization works all the same. - </p> - - <h1>CPU paste required</h1> - - <p> - See <a href="#paste">#paste</a>. - </p> - - </div> - - <div class="section"> - - <h1 id="flashchips">Flash chip size</h1> - - <p> - Use this to find out:<br> - # <b>flashrom -p internal -V</b><br> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos"> - - <h1 id="macaddress">MAC address</h1> - - <p> - On the R400, the MAC address for the onboard - gigabit ethernet chipset is stored inside the flash chip, - along with other configuration data. - </p> - <p> - Keep a note of the MAC address before disassembly; this is - very important, because you will need to insert this into - the libreboot ROM image before flashing it. - It will be written in one of these locations: - </p> - - <p> - <img src="images/t400/macaddress0.jpg" alt="" /> - <img src="images/t400/macaddress1.jpg" alt="" /> - <img src="images/x200/disassembly/0001.jpg" alt="" /> - </p> - - </div> - - <div class="section photos"> - - <h1>Initial BBB configuration</h1> - - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - setup the BBB for flashing. - </p> - - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-16 (clip: Pomona 5252): - </p> -<pre> -POMONA 5252 (correlate with the BBB guide) -=== ethernet jack and VGA port ==== - NC - - 21 - 1 - - 17 - NC - - NC - NC - - NC - NC - - NC - NC - - NC - 18 - - 3.3V (PSU) - 22 - - NC - this is pin 1 on the flash chip -=== SATA port === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i><br/> -<img src="images/t400/0065.jpg" alt="" /> -</pre> - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): - </p> -<pre> -POMONA 5250 (correlate with the BBB guide) -=== RAM slots ==== - 18 - - 1 - 22 - - NC - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== slot where the AC jack is connected === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i><br/> -<img src="images/r400/0051.jpg" alt="" /> -</pre> - - <h2 id="disassembly">Disassembly</h2> - - <p> - Remove all screws:<br/> - <img src="images/r400/0000.jpg" alt="" /><br/> - Remove the HDD and optical drive:<br/> - <img src="images/r400/0001.jpg" alt="" /><br/> - Remove the hinge screws:<br/> - <img src="images/r400/0002.jpg" alt="" /> - <img src="images/r400/0003.jpg" alt="" /> - </p> - - <p> - Remove the palm rest and keyboard:<br/> - <img src="images/r400/0004.jpg" alt="" /> - <img src="images/r400/0005.jpg" alt="" /> - </p> - - <p> - Remove these screws, and then remove the bezel:<br/> - <img src="images/r400/0006.jpg" alt="" /> - <img src="images/r400/0007.jpg" alt="" /> - </p> - - <p> - Remove the speaker screws, but don't remove the speakers yet - (just set them loose):<br/> - <img src="images/r400/0008.jpg" alt="" /> - <img src="images/r400/0009.jpg" alt="" /> - <img src="images/r400/0010.jpg" alt="" /> - </p> - - <p> - Remove these screws, and then remove the metal plate:<br/> - <img src="images/r400/0011.jpg" alt="" /> - <img src="images/r400/0012.jpg" alt="" /> - <img src="images/r400/0013.jpg" alt="" /> - </p> - - <p> - Remove the antennas from the wifi card, and then - start unrouting them:<br/> - <img src="images/r400/0014.jpg" alt="" /> - <img src="images/r400/0015.jpg" alt="" /> - <img src="images/r400/0016.jpg" alt="" /> - <img src="images/r400/0017.jpg" alt="" /> - <img src="images/r400/0018.jpg" alt="" /> - <img src="images/r400/0019.jpg" alt="" /> - </p> - - <p> - Disconnect the LCD cable from the motherboard:<br/> - <img src="images/r400/0020.jpg" alt="" /> - <img src="images/r400/0021.jpg" alt="" /> - <img src="images/r400/0022.jpg" alt="" /> - <img src="images/r400/0023.jpg" alt="" /> - </p> - - <p> - Remove the hinge screws, and then remove the LCD panel:<br/> - <img src="images/r400/0024.jpg" alt="" /> - <img src="images/r400/0025.jpg" alt="" /> - <img src="images/r400/0026.jpg" alt="" /> - <img src="images/r400/0027.jpg" alt="" /> - </p> - - <p> - Remove this:<br/> - <img src="images/r400/0028.jpg" alt="" /> - <img src="images/r400/0029.jpg" alt="" /> - </p> - - <p> - Remove this long cable (there are 3 connections):<br/> - <img src="images/r400/0030.jpg" alt="" /> - <img src="images/r400/0031.jpg" alt="" /> - <img src="images/r400/0032.jpg" alt="" /> - <img src="images/r400/0033.jpg" alt="" /> - </p> - - <p> - Disconnect the speaker cable, and remove the speakers:<br/> - <img src="images/r400/0034.jpg" alt="" /> - </p> - - <p> - Remove the heatsink screws, remove the fan - and then remove the heatsink/fan:<br/> - <img src="images/r400/0035.jpg" alt="" /> - <img src="images/r400/0036.jpg" alt="" /> - <img src="images/r400/0037.jpg" alt="" /> - <img src="images/r400/0038.jpg" alt="" /> - </p> - - <p> - Remove the NVRAM battery:<br/> - <img src="images/r400/0039.jpg" alt="" /> - <img src="images/r400/0040.jpg" alt="" /> - </p> - - <p> - Remove this screw:<br/> - <img src="images/r400/0041.jpg" alt="" /> - <img src="images/r400/0042.jpg" alt="" /> - </p> - - <p> - Disconnect the AC jack:<br/> - <img src="images/r400/0043.jpg" alt="" /> - <img src="images/r400/0044.jpg" alt="" /> - </p> - - <p> - Remove this screw and then remove what is under it:<br/> - <img src="images/r400/0045.jpg" alt="" /> - </p> - - <p> - Remove this:<br/> - <img src="images/r400/0046.jpg" alt="" /> - </p> - - <p> - Lift the motherboard (which is still inside the cage) - from the side on the right, removing it completely:<br/> - <img src="images/r400/0047.jpg" alt="" /> - <img src="images/r400/0048.jpg" alt="" /> - </p> - - <p> - Remove all screws, marking each hole so that you know - where to re-insert them. You should place the screws in - a layout corresponding to the order that they were in - before removal: - <img src="images/r400/0049.jpg" alt="" /> - <img src="images/r400/0050.jpg" alt="" /> - </p> - - <p> - Remove the motherboard from the cage, and the SPI flash - chip will be next to the memory slots:<br/> - <img src="images/r400/0051.jpg" alt="" /> - <img src="images/r400/0052.jpg" alt="" /> - </p> - - <p> - Connect your programmer, then connect GND and 3.3V<br/> - <img src="images/t400/0065.jpg" alt="" /> - <img src="images/t400/0066.jpg" alt="" /> - <img src="images/t400/0067.jpg" alt="" /> - <img src="images/t400/0069.jpg" alt="" /> - <img src="images/t400/0070.jpg" alt="" /> - <img src="images/t400/0071.jpg" alt="" /> - </p> - <p> - A dedicated 3.3V PSU was used to create this guide, but - at ATX PSU is also fine:<br/> - <img src="images/t400/0072.jpg" alt="" /> - </p> - - <p> - Of course, make sure to turn on your PSU:<br/> - <img src="images/x200/disassembly/0013.jpg" alt="" /> - </p> - - <p> - Now, you should be ready to install libreboot. - </p> - - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - <p> - Log in as root on your BBB, using the instructions in <a href="bbb_setup.html#bbb_access">bbb_setup.html#bbb_access</a>. - </p> - <p> - Test that flashrom works:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512</b><br/> - In this case, the output was: - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. -Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" -Please specify which chip definition to use with the -c <chipname> option. -</pre> - <p> - How to backup factory.rom (change the -c option as neeed, for your flash chip):<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom</b><br/> - Note: the <b>-c</b> option is not required in libreboot's patched flashrom, because - the redundant flash chip definitions in <i>flashchips.c</i> have been removed.<br/> - Now compare the 3 images:<br/> - # <b>sha512sum factory*.rom</b><br/> - If the hashes match, 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 and libreboot. - </p> - <p> - Follow the instructions at <a href="../hcl/gm45_remove_me.html#ich9gen">../hcl/gm45_remove_me.html#ich9gen</a> - to change the MAC address inside the libreboot ROM image, before flashing it. - Although there is a default MAC address inside the ROM image, this is not what you want. <b>Make sure - to always change the MAC address to one that is correct for your system.</b> - </p> - <p> - Now flash it:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V</b> - </p> - <p> - <img src="images/x200/disassembly/0015.jpg" alt="" /> - </p> - <p> - You might see errors, but if it says <b>Verifying flash... VERIFIED</b> at the end, then it's flashed and should boot. - If you see errors, try again (and again, and again); the message <b>Chip content is identical to the requested image</b> - is also an indication of a successful installation. - </p> - <p> - Example output from running the command (see above): - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Reading old flash chip contents... done. -Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 -ERASE FAILED! -Reading current flash chip contents... done. Looking for another erase function. -Erase/write done. -Verifying flash... VERIFIED. -</pre> - - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos" id="paste"> - - <h1>Thermal paste (IMPORTANT)</h1> - - <p> - Because part of this procedure involved removing the heatsink, you will need to apply new paste. - Arctic MX-4 is ok. You will also need isopropyl alcohol and an anti-static cloth to clean with. - </p> - - <p> - When re-installing the heatsink, you must first clean off all old paste with the alcohol/cloth. - Then apply new paste. Arctic MX-4 is also much better than the default paste used on these systems. - </p> - - <p> - <img src="images/t400/paste.jpg" alt="" /> - </p> - - <p> - NOTE: the photo above is for illustration purposes only, and does not show how to properly apply the thermal paste. - Other guides online detail the proper application procedure. - </p> - - </div> - - <div class="section"> - - <h1 id="wifi">Wifi</h1> - - <p> - The R400 typically comes with an Intel wifi chipset, which does not - work without proprietary software. For a list of wifi chipsets that - work without proprietary software, see - <a href="../hcl/#recommended_wifi">../hcl/#recommended_wifi</a>. - </p> - - <p> - Some R400 laptops might come with an Atheros chipset, but this is 802.11g only. - </p> - - <p> - It is recommended that you install a new wifi chipset. This can only - be done after installing libreboot, because the original firmware has - a whitelist of approved chips, and it will refuse to boot if you - use an 'unauthorized' wifi card. - </p> - - <p> - The following photos show an Atheros AR5B95 being installed, to - replace the Intel chip that this R400 came with:<br/> - <img src="images/t400/0012.jpg" alt="" /> - <img src="images/t400/ar5b95.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <h1 id="wwan">WWAN</h1> - <p> - If you have a WWAN/3G card and/or sim card reader, remove them permanently. - The WWAN-3G card has proprietary firmware inside; the technology is - identical to what is used in mobile phones, so it can also track your movements. - </p> - <p> - Not to be confused with wifi (wifi is fine). - </p> - - </div> - - <div class="section photos"> - - <h1 id="memory">Memory</h1> - - <p> - You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs - (speed/size). Non-matching pairs won't work. You can also install a - single module (meaning, one of the slots will be empty) in slot 0. - </p> - - <p> - Make sure that the RAM you buy is the 2Rx8 density. - </p> - - <p> - <a href="http://www.forum.thinkpads.com/viewtopic.php?p=760721">This page</a> might be useful for RAM compatibility info - (note: coreboot raminit is different, so this page might be BS) - </p> - - <p> - The following photo shows 8GiB (2x4GiB) of RAM installed:<br/> - <img src="images/t400/memory.jpg" alt="" /> - </p> - - </div> - - <div class="section photos"> - - <h2> - Boot it! - </h2> - <p> - You should see something like this: - </p> - <p> - <img src="images/t400/boot0.jpg" alt="" /> - <img src="images/t400/boot1.jpg" alt="" /> - </p> - - <p> - Now <a href="../gnulinux/">install GNU+Linux</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/r400_external.md b/docs/install/r400_external.md new file mode 100644 index 00000000..16e96258 --- /dev/null +++ b/docs/install/r400_external.md @@ -0,0 +1,445 @@ +<div class="section"> + +Flashing the R400 with a BeagleBone Black {#pagetop} +========================================= + +Initial flashing instructions for R400. + +This guide is for those who want libreboot on their ThinkPad R400 while +they still have the original Lenovo BIOS present. This guide can also be +followed (adapted) if you brick your R400, to know how to recover. + +Before following this section, please make sure to setup your libreboot +ROM properly first. Although ROM images are provided pre-built in +libreboot, there are some modifications that you need to make to the one +you chose before flashing. (instructions referenced later in this guide) + +[Back to main index](./) + +</div> + +<div class="section"> + +Libreboot T400 {#t400} +============== + +You may also be interested in the smaller, more portable [Libreboot +T400](t400_external.html). + +</div> + +<div class="section"> + +Serial port {#serial_port} +----------- + +EHCI debug might not be needed. It has been reported that the docking +station for this laptop has a serial port, so it might be possible to +use that instead. + +</div> + +<div id="cpu_compatibility" class="section"> + +A note about CPUs +================= + +[ThinkWiki](http://www.thinkwiki.org/wiki/Category:R400) has a list of +CPUs for this system. The Core 2 Duo P8400 and P8600 are believed to +work in libreboot. The Core 2 Duo T9600 was confirmed to work, so the +T9400 probably also works. **The Core 2 Duo T5870/5670 and Celeron M +575/585 are untested!** + +Quad-core CPUs +-------------- + +Incompatible. Do not use. + +</div> + +<div id="switchable_graphics" class="section"> + +A note about GPUs +================= + +Some models have an Intel GPU, while others have both an ATI and an +Intel GPU; this is referred to as \"switchable graphics\". In the *BIOS +setup* program for lenovobios, you can specify that the system will use +one or the other (but not both). + +Libreboot is known to work on systems with only the Intel GPU, using +native graphics initialization. On systems with switchable graphics, the +Intel GPU is used and the ATI GPU is disabled, so native graphics +initialization works all the same. + +CPU paste required +================== + +See [\#paste](#paste). + +</div> + +<div class="section"> + +Flash chip size {#flashchips} +=============== + +Use this to find out:\ +\# **flashrom -p internal -V**\ + +[Back to top of page.](#pagetop) + +</div> + +<div class="section photos"> + +MAC address {#macaddress} +=========== + +On the R400, the MAC address for the onboard gigabit ethernet chipset is +stored inside the flash chip, along with other configuration data. + +Keep a note of the MAC address before disassembly; this is very +important, because you will need to insert this into the libreboot ROM +image before flashing it. It will be written in one of these locations: + +  + + +</div> + +<div class="section photos"> + +Initial BBB configuration +========================= + +Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for +flashing. + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-16 (clip: Pomona 5252): + + POMONA 5252 (correlate with the BBB guide) + === ethernet jack and VGA port ==== + NC - - 21 + 1 - - 17 + NC - - NC + NC - - NC + NC - - NC + NC - - NC + 18 - - 3.3V (PSU) + 22 - - NC - this is pin 1 on the flash chip + === SATA port === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-8 (clip: Pomona 5250): + + POMONA 5250 (correlate with the BBB guide) + === RAM slots ==== + 18 - - 1 + 22 - - NC + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + === slot where the AC jack is connected === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +Disassembly +----------- + +Remove all screws:\ +\ +Remove the HDD and optical drive:\ +\ +Remove the hinge screws:\ +  + +Remove the palm rest and keyboard:\ +  + +Remove these screws, and then remove the bezel:\ +  + +Remove the speaker screws, but don\'t remove the speakers yet (just set +them loose):\ +  + + +Remove these screws, and then remove the metal plate:\ +  + + +Remove the antennas from the wifi card, and then start unrouting them:\ +  +  +  + +Disconnect the LCD cable from the motherboard:\ +  +  + +Remove the hinge screws, and then remove the LCD panel:\ +  +  + +Remove this:\ +  + +Remove this long cable (there are 3 connections):\ +  +  + +Disconnect the speaker cable, and remove the speakers:\ + + +Remove the heatsink screws, remove the fan and then remove the +heatsink/fan:\ +  +  + +Remove the NVRAM battery:\ +  + +Remove this screw:\ +  + +Disconnect the AC jack:\ +  + +Remove this screw and then remove what is under it:\ + + +Remove this:\ + + +Lift the motherboard (which is still inside the cage) from the side on +the right, removing it completely:\ +  + +Remove all screws, marking each hole so that you know where to re-insert +them. You should place the screws in a layout corresponding to the order +that they were in before removal:  + + +Remove the motherboard from the cage, and the SPI flash chip will be +next to the memory slots:\ +  + +Connect your programmer, then connect GND and 3.3V\ +  +  +  + +A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is +also fine:\ + + +Of course, make sure to turn on your PSU:\ + + +Now, you should be ready to install libreboot. + +Flashrom binaries for ARM (tested on a BBB) are distributed in +libreboot\_util. Alternatively, libreboot also distributes flashrom +source code which can be built. + +Log in as root on your BBB, using the instructions in +[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). + +Test that flashrom works:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ +In this case, the output was: + + flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. + Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" + Please specify which chip definition to use with the -c <chipname> option. + +How to backup factory.rom (change the -c option as neeed, for your flash +chip):\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory1.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory2.rom**\ +Note: the **-c** option is not required in libreboot\'s patched +flashrom, because the redundant flash chip definitions in *flashchips.c* +have been removed.\ +Now compare the 3 images:\ +\# **sha512sum factory\*.rom**\ +If the hashes match, 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 +and libreboot. + +Follow the instructions at +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +to change the MAC address inside the libreboot ROM image, before +flashing it. Although there is a default MAC address inside the ROM +image, this is not what you want. **Make sure to always change the MAC +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** + + + +You might see errors, but if it says **Verifying flash\... VERIFIED** at +the end, then it\'s flashed and should boot. If you see errors, try +again (and again, and again); the message **Chip content is identical to +the requested image** is also an indication of a successful +installation. + +Example output from running the command (see above): + + flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Reading old flash chip contents... done. + Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 + ERASE FAILED! + Reading current flash chip contents... done. Looking for another erase function. + Erase/write done. + Verifying flash... VERIFIED. + +[Back to top of page.](#pagetop) + +</div> + +<div id="paste" class="section photos"> + +Thermal paste (IMPORTANT) +========================= + +Because part of this procedure involved removing the heatsink, you will +need to apply new paste. Arctic MX-4 is ok. You will also need isopropyl +alcohol and an anti-static cloth to clean with. + +When re-installing the heatsink, you must first clean off all old paste +with the alcohol/cloth. Then apply new paste. Arctic MX-4 is also much +better than the default paste used on these systems. + + + +NOTE: the photo above is for illustration purposes only, and does not +show how to properly apply the thermal paste. Other guides online detail +the proper application procedure. + +</div> + +<div class="section"> + +Wifi +==== + +The R400 typically comes with an Intel wifi chipset, which does not work +without proprietary software. For a list of wifi chipsets that work +without proprietary software, see +[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). + +Some R400 laptops might come with an Atheros chipset, but this is +802.11g only. + +It is recommended that you install a new wifi chipset. This can only be +done after installing libreboot, because the original firmware has a +whitelist of approved chips, and it will refuse to boot if you use an +\'unauthorized\' wifi card. + +The following photos show an Atheros AR5B95 being installed, to replace +the Intel chip that this R400 came with:\ +  + +</div> + +<div class="section"> + +WWAN +==== + +If you have a WWAN/3G card and/or sim card reader, remove them +permanently. The WWAN-3G card has proprietary firmware inside; the +technology is identical to what is used in mobile phones, so it can also +track your movements. + +Not to be confused with wifi (wifi is fine). + +</div> + +<div class="section photos"> + +Memory +====== + +You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs +(speed/size). Non-matching pairs won\'t work. You can also install a +single module (meaning, one of the slots will be empty) in slot 0. + +Make sure that the RAM you buy is the 2Rx8 density. + +[This page](http://www.forum.thinkpads.com/viewtopic.php?p=760721) might +be useful for RAM compatibility info (note: coreboot raminit is +different, so this page might be BS) + +The following photo shows 8GiB (2x4GiB) of RAM installed:\ + + +</div> + +<div class="section photos"> + +Boot it! +-------- + +You should see something like this: + +  + +Now [install GNU+Linux](../gnulinux/). + +</div> + +<div class="section"> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/rpi_setup.html b/docs/install/rpi_setup.html deleted file mode 100644 index 9c0e1c17..00000000 --- a/docs/install/rpi_setup.html +++ /dev/null @@ -1,702 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>How to program an SPI flash chip with the Raspberry Pi</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">How to program an SPI flash chip with the Raspberry Pi</h1> - <p> - This document exists as a guide for reading from or writing to an SPI flash chip with the Raspberry Pi, - using the <a href="http://flashrom.org/Flashrom">flashrom</a> software. - Most revisions of the RPi should work. - </p> - <p> - This only covers SOIC-8 flash chips, for now. SOIC-16 guide coming later - (for now, it should be easy enough for you to figure this out for SOIC-16). - </p> - <p> - <a href="../">Back to previous index</a> - </p> - </div> - - <div class="section"> - -<h2> -<a id="user-content-raspberry-pi-thinkpad-x60t60-and-macbook-21" class="anchor" href="#raspberry-pi-thinkpad-x60t60-and-macbook-21" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Raspberry Pi (ThinkPad X60/T60 and Macbook 2,1)</h2> - -<p>The Raspberry Pi (a multipurpose $25 GNU+Linux computer) can be used as a BIOS flashing tool, thanks to its GPIO pins and SPI support.</p> - -<blockquote> -<p><strong>Note:</strong> The Raspberry Pi Model A is not supported, since it has no GPIO pins.</p> -</blockquote> - -<h3> -<a id="user-content-disassembling-the-thinkpad" class="anchor" href="#disassembling-the-thinkpad" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Disassembling the ThinkPad</h3> - -<p>Follow the <a href="http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/42x3550_04.pdf">X60 Hardware Maintenance Manual</a> or <a href="http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/42t7844_04.pdf">T60 Hardware Maintenance Manual</a> to disassemble the laptop, until you can access the BIOS chip.</p> - -<p>For photos, follow the <a href="http://libreboot.org/docs/install/t60_unbrick.html">Libreboot T60 Recovery Guide</a>.</p> - -<ul> -<li>On the X60, the BIOS chip is on the bottom of the motherboard, under a layer of protective black tape.</li> -<li>On the T60, the BIOS chip is just under the palmrest, but blocked by a magnesium frame (which you will have to remove).</li> -</ul> - -<h3> -<a id="user-content-pomona-clip-pinout" class="anchor" href="#pomona-clip-pinout" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Pomona Clip Pinout</h3> - -<p>Diagram of the 26 GPIO Pins of the Raspberry Pi Model B (for the Model B+ with 40 pins, start counting from the right and leave 14 pins):</p> - -<p><img src="images/rpi/0012.png" alt="" data-canonical-src="http://i.imgur.com/GjuQaJN.png"> -<img src="images/rpi/0013.png" alt="" data-canonical-src="http://i.imgur.com/WkNvOUy.png"></p> - -<pre><code> 8-pin for X60: - -~~~~ LCD (Front) ~~~~ - 8765 - ---- - | | - ---- - 1234 -~~~ Palmrest (back) ~~ -</code></pre> - -<table> -<thead> -<tr> -<th align="center">Pin #</th> -<th align="center">SPI Pin Name</th> -<th align="center">BP (Seeed)</th> -<th align="center">BP (Spkfun)</th> -<th align="center"><a href="http://beagleboard.org/Support/bone101#headers">Beagleboard Black</a></th> -<th align="center"><a href="images/rpi/0000.jpg">Raspberry Pi</a></th> -</tr> -</thead> -<tbody> -<tr> -<td align="center">1</td> -<td align="center">CS</td> -<td align="center">White</td> -<td align="center">Red</td> -<td align="center">Pin 17</td> -<td align="center">24</td> -</tr> -<tr> -<td align="center">2</td> -<td align="center">MISO</td> -<td align="center">Black</td> -<td align="center">Brown</td> -<td align="center">Pin 21</td> -<td align="center">21</td> -</tr> -<tr> -<td align="center">3</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">4</td> -<td align="center">GND</td> -<td align="center">Brown</td> -<td align="center">Black</td> -<td align="center">Pin 1</td> -<td align="center">25</td> -</tr> -<tr> -<td align="center">5</td> -<td align="center">MOSI</td> -<td align="center">Gray</td> -<td align="center">Orange</td> -<td align="center">Pin 18</td> -<td align="center">19</td> -</tr> -<tr> -<td align="center">6</td> -<td align="center">CLK</td> -<td align="center">Purple</td> -<td align="center">Yellow</td> -<td align="center">Pin 22</td> -<td align="center">23</td> -</tr> -<tr> -<td align="center">7</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">8</td> -<td align="center">3.3V</td> -<td align="center"><em>red</em></td> -<td align="center">White</td> -<td align="center"><a href="http://libreboot.org/docs/install/bbb_setup.html">3.3V PSU RED</a></td> -<td align="center">17</td> -</tr> -</tbody> -</table> - -<p>Make sure the pinouts are correct; otherwise, Flashrom will fail to detect a chip, or it will "detect" a <code>0x0</code> chip. Finally, make sure that the Pomona clip makes contact with the metal wires of the chip. It can be a challenge, but keep trying.</p> - -<h3> -<a id="user-content-how-to-supply-power-to-the-flashchip" class="anchor" href="#how-to-supply-power-to-the-flashchip" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>How to supply power to the flashchip</h3> - -<p>There are two ways to supply power to the chip: plugging in an AC adapter (without turning the laptop on), and using the 8th 3.3v pin.</p> - -<p>I have found that the SST chips work best with the 8th pin, while the Macronix chips require an AC Adapter to power up.</p> - -<p><strong>Never connect both the 8th pin and the AC adapter at the same time.</strong></p> - -<p>Your results may vary.</p> - -<h2> -<a id="user-content-reading-the-flashchip" class="anchor" href="#reading-the-flashchip" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Reading the Flashchip</h2> - -<p>First, visually inspect (with a magnifying glass) the type of flashchip on the motherboard. </p> - -<p>Next, download and compile the latest Flashrom source code on the Raspberry Pi.</p> - -<pre><code>sudo apt-get install build-essential pciutils usbutils libpci-dev libusb-dev libftdi1 libftdi-dev zlib1g-dev subversion -svn co svn://flashrom.org/flashrom/trunk flashrom -cd flashrom -make -sudo modprobe spi_bcm2708 -sudo modprobe spidev -</code></pre> - -<p>If your chip is an SST, run this command:</p> - -<pre><code>sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0 -r test.rom -</code></pre> - -<p>If your chip is a Macronix, run this command:</p> - -<pre><code>sudo ./flashrom -c "MX25L1605" -p linux_spi:dev=/dev/spidev0.0 -r test.rom -</code></pre> - -<p>Next, check the md5sum of the dump:</p> - -<pre><code>md5sum test.rom -</code></pre> - -<p>Run the <code>flashrom</code> command again to make a second dump. Then, check the md5sum of the second dump:</p> - -<pre><code>md5sum test.rom -</code></pre> - -<p>If the md5sums match after three tries, <code>flashrom</code> has managed to read the flashchip precisely (but not always accurately). You may try and flash Libreboot now.</p> - -<h2> -<a id="user-content-flashing-libreboot" class="anchor" href="#flashing-libreboot" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Flashing Libreboot</h2> - -<blockquote> -<p><strong>Note:</strong> replace <code>/path/to/libreboot.rom</code> with the location of your chosen ROM, such as <code>../bin/x60/libreboot_usqwerty.rom</code>):</p> -</blockquote> - -<p>If your chip is an SST, run this command: </p> - -<pre><code>sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0 -w /path/to/libreboot.rom -</code></pre> - -<p>If your chip is a Macronix, run this command:</p> - -<pre><code>sudo ./flashrom -c "MX25L1605" -p linux_spi:dev=/dev/spidev0.0 -w /path/to/libreboot.rom -</code></pre> - -<p>Once that command outputs the following, the flash has completed successfully. If not, just flash again.</p> - -<pre><code>Reading old flash chip contents... done. -Erasing and writing flash chip... Erase/write done. -Verifying flash... VERIFIED. -</code></pre> - -<h3> -<a id="user-content-sources" class="anchor" href="#sources" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Sources</h3> - -<ul> -<li><a href="http://scruss.com/blog/2013/02/02/simple-adc-with-the-raspberry-pi/">Scruss - Simple ADC with the Raspberry Pi</a></li> -<li><a href="https://blogs.fsfe.org/the_unconventional/2015/05/08/flashing-coreboot-on-a-t60-with-a-raspberry-pi/">Flashing coreboot on a T60 with a Raspberry Pi - the_unconventional's blog</a></li> -<li> -<strong>Pomona SOIC Clip flashing</strong> - -<ul> -<li><a href="https://wiki.archlinux.org/index.php/Chromebook">Arch Linux Wiki - Installing Arch Linux on Chromebook</a></li> -<li><a href="https://drive.google.com/folderview?id=0B9f62MH0umbmRTA2Xzd5WHhjWEU&usp=sharing">Google Drive - Raspberry Pi SOIC Clip connection</a></li> -<li><a href="http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf">rPI with Flashrom and SOIC Clip Powerpoint</a></li> -</ul> -</li> -</ul> - -<h3> -<a id="user-content-raspberry-pi-pinout-diagrams" class="anchor" href="#raspberry-pi-pinout-diagrams" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Raspberry Pi Pinout Diagrams</h3> - -<table> -<thead> -<tr> -<th>MCP</th> -<th>3008 Pin</th> -<th>Pi GPIO Pin #</th> -<th>Pi Pin Name</th> -</tr> -</thead> -<tbody> -<tr> -<td>16</td> -<td><code>VDD</code></td> -<td>1</td> -<td><code>3.3 V</code></td> -</tr> -<tr> -<td>15</td> -<td><code>VREF</code></td> -<td>1</td> -<td><code>3.3 V</code></td> -</tr> -<tr> -<td>14</td> -<td><code>AGND</code></td> -<td>6</td> -<td><code>GND</code></td> -</tr> -<tr> -<td>13</td> -<td><code>CLK</code></td> -<td>23</td> -<td><code>GPIO11 SPI0_SCLK</code></td> -</tr> -<tr> -<td>12</td> -<td><code>DOUT</code></td> -<td>21</td> -<td><code>GPIO09 SPI0_MISO</code></td> -</tr> -<tr> -<td>11</td> -<td><code>DIN</code></td> -<td>19</td> -<td><code>GPIO10 SPI0_MOSI</code></td> -</tr> -<tr> -<td>10</td> -<td><code>CS</code></td> -<td>24</td> -<td><code>GPIO08 CE0</code></td> -</tr> -<tr> -<td>9</td> -<td><code>DGND</code></td> -<td>6</td> -<td><code>GND</code></td> -</tr> -</tbody> -</table> - -<ul> -<li>Source: <a href="http://raspberrypi.znix.com/hipidocs/topic_gpiopins.htm">Perl & Raspberry Pi - Raspberry Pi GPIO Pinout</a> -</li> -</ul> - -<h2> -<a id="user-content-raspberry-pi-thinkpad-x200" class="anchor" href="#raspberry-pi-thinkpad-x200" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Raspberry Pi (ThinkPad X200)</h2> - -<h3> -<a id="user-content-requirements" class="anchor" href="#requirements" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Requirements:</h3> - -<ul> -<li>An x86, x86_64, or arm7l (for changing the libreboot.rom image mac address)</li> -<li>Raspberry Pi and peripherals</li> -<li>Relevant SOIC clip</li> -<li>6 female - female jumpers</li> -<li>Internet connection</li> -<li>Screw drivers</li> -</ul> - -<p>Follow the <a href="http://libreboot.org/docs/install/x200_external.html">ThinkPad X200: Initial installation guide</a> to disassemble the laptop, and access the BIOS rom chip.</p> - -<blockquote> -<p><strong>Note:</strong> <code>x86#</code> refers to commands to be run on the x86 computer, and <code>pi#</code> refers to commands to be run on the pi. -A good practice is to make a work directory to keep your libreboot stuff inside.</p> -</blockquote> - -<pre><code>x86# mkdir ~/work -</code></pre> - -<p>Download NOOBS from <a href="https://www.raspberrypi.org/downloads/">The Raspberry Pi Foundation.</a> Torrent download recommended, and remember to seed. :)</p> - -<p> -If you're running Raspian, you can do <strong>sudo raspi-config</strong>, enable SPI under Advanced and then -spidev will be enabled. Simple, eh? -</p> - -<p><a href="http://www.libreboot.org/download/">Download Libreboot from their releases page</a>. For your safety, verify the GPG signature as well. </p> - -<pre><code>x86# gpg --keyserver prefered.keyserver.org --recv-keys 0x656F212E - -x86# for signature in $(ls *.sig); do gpg --verify $signature; done -</code></pre> - -<p>Extract NOOBS and libreboot.</p> - -<pre><code>x86# mkdir ~/work/noobs - -x86# unzip ~/Downloads/NOOBS_v1_4_1.zip -d ~/work/noobs/ - -x86# cd ~/work && tar -xvJf ~/Downloads/libreboot_bin.tar.xz -</code></pre> - -<p>Install Noobs to your fat32 formatted SD card</p> - -<pre><code>x86# cp -R ~/work/noobs/* /path/to/mounted/SDcard/ -</code></pre> - -<h3> -<a id="user-content-set-up-noobs-on-raspberry-pi" class="anchor" href="#set-up-noobs-on-raspberry-pi" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Set up NOOBS on Raspberry Pi</h3> - -<p>Plug in the NOOBs SDCard to your Raspberry Pi, and enable the following under 'Advanced Options':</p> - -<p>SSH server</p> - -<p>SPI</p> - -<p>I2C</p> - -<p>On first boot</p> - -<pre><code>pi# sudo apt-get update && sudo apt-get dist-upgrade && reboot -</code></pre> - -<p>On second boot</p> - -<pre><code>pi# sudo apt-get update && sudo apt-get install libftdi1 libftdi-dev libusb-dev libpci-dev subversion -</code></pre> - -<p>Other dependencies that should already be installed with the noobs base install include:</p> - -<p>pciutils, zlib, libusb, build-essential</p> - -<p>If they are missing then install them.</p> - -<p>Download and build flashrom.</p> - -<pre><code>pi# svn co svn://flashrom.org/flashrom/trunk ~/flashrom - -pi# cd ~/flashrom - -pi# make - -pi# sudo make install -</code></pre> - -<p>On your x86 box change the libreboot.rom mac address</p> - -<pre><code>x86# cd ~/work/libreboot_bin/ -</code></pre> - -<p>Change the mac address on the libreboot images to match yours.</p> - -<pre><code>x86# ./ich9macchange XX:XX:XX:XX:XX:XX -</code></pre> - -<p>Move the libreboot.rom image over to your pi</p> - -<pre><code>x86# scp ~/work/libreboot_bin/<path_to_your_bin> pi@your.pi.address:~/flashrom/libreboot.rom -</code></pre> - -<p>Shutdown your pi, write down your rom chip model, and wire up the clip</p> - -<pre><code>pi# sudo shutdown now -hP -</code></pre> - -<p>Chip model name</p> - -<p><img src="images/rpi/0001.jpg" alt="" data-canonical-src="http://i.imgur.com/GMbcbqS.jpg"></p> - -<p>Pinout. You may want to download the image so you can zoom in on the text.</p> - -<p><img src="images/rpi/0002.jpg" alt="" data-canonical-src="http://i.imgur.com/QkoInwr.jpg"></p> - -<table> -<thead> -<tr> -<th align="center">Pin #</th> -<th align="center">SPI Pin Name</th> -<th align="center">Raspberry Pi Pin #</th> -</tr> -</thead> -<tbody> -<tr> -<td align="center">1</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">2</td> -<td align="center">3.3V</td> -<td align="center">1</td> -</tr> -<tr> -<td align="center">3</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">4</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">5</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">6</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">7</td> -<td align="center">CS#</td> -<td align="center">24</td> -</tr> -<tr> -<td align="center">8</td> -<td align="center">S0/SIO1</td> -<td align="center">21</td> -</tr> -<tr> -<td align="center">9</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">10</td> -<td align="center">GND</td> -<td align="center">25</td> -</tr> -<tr> -<td align="center">11</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">12</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">13</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">14</td> -<td align="center"><em>not used</em></td> -<td align="center"><em>not used</em></td> -</tr> -<tr> -<td align="center">15</td> -<td align="center">S1/SIO0</td> -<td align="center">19</td> -</tr> -<tr> -<td align="center">16</td> -<td align="center">SCLK</td> -<td align="center">23</td> -</tr> -</tbody> -</table> - -<blockquote> -<p><strong>Note:</strong> The raspberry pi 3.3V rail should be sufficient to power the chip during flashing, so no external power supply should be required; however, at the time of writing that has only been tested and confirmed for one chip, the MX25L6405D.</p> -</blockquote> - -<p>Macronix Spec sheet so you can adjust your pinout for 8 pin 4Mb chips as necessary</p> - -<p><img src="images/rpi/0014.gif" alt="" data-canonical-src="http://i.imgur.com/IQI0Shj.gif"></p> - -<p>At this point connect your SOIC clip to the rom chip before powering on your PI.</p> - -<p>Power on your Pi, and run the following. Ensure you swap out "your_chip_name" with the proper name/model of your chip. Check that it can be read successfully. If you cannot read the chip and receive an error similar to "no EEPROM Detected" or "0x0 Chip detected" then you may want to try powering off your PI, and switching the two pins which are connected to the IO ports. I.E. Connect pins (clip)8 to (pi)19 and pins (clip)15 to (pi)21</p> - -<pre><code>pi# cd ~/flashrom - -pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -r romread1.rom - -pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -r romread2.rom - -pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -r romread3.rom - -pi# sha512sum romread*.rom -</code></pre> - -<p>If they are identical sha512 hashes then you can generally assume that it's safe to flash your rom.</p> - -<pre><code>pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -w libreboot.rom -</code></pre> - -<p>It may fail a couple times, but keep at it and when you get the message <code>Verifying flash... Verified</code> or <code>Warning: Chip content is identical to the requested image</code> then you're done. </p> - -<p>Shut down your pi, put your box back together, and install a libre OS for great good!</p> - -<h2> -<a id="user-content-raspberry-pi-c720-chromebook" class="anchor" href="#raspberry-pi-c720-chromebook" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Raspberry Pi (C720 Chromebook)</h2> - -<p>The Raspberry Pi (a multipurpose $25 GNU+Linux computer) can be used as a BIOS flashing tool, thanks to its GPIO pins and SPI support.</p> - -<h3> -<a id="user-content-what-you-need" class="anchor" href="#what-you-need" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>What you need</h3> - -<ul> -<li>$25 - Raspberry Pi Model B (Rev.2 or higher)</li> -<li>$10-20 - SOIC-8 Pomona Clip - -<ul> -<li>Usually comes bundled with nice, color-colored <em>female to female</em> wires</li> -</ul> -</li> -</ul> - -<h3> -<a id="user-content-raspberry-pi-pinouts" class="anchor" href="#raspberry-pi-pinouts" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Raspberry Pi Pinouts</h3> - -<p>GPIO Pinouts:</p> - -<p><img src="images/rpi/0009.png" alt="" data-canonical-src="http://i.imgur.com/GjuQaJN.png"> -<img src="images/rpi/0010.png" alt="" data-canonical-src="http://i.imgur.com/WkNvOUy.png"></p> - -<blockquote> -<p>*Diagram made by <a href="http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html">"Pacman" from Win-Raid Forums*</a></p> -</blockquote> - -<p>SOIC Pinouts:</p> - -<p><img src="docs/rpi/0011.png" alt="" data-canonical-src="http://i.imgur.com/2Z9tveR.png"></p> - -<h3> -<a id="user-content-plugging-in-the-soic-clip" class="anchor" href="#plugging-in-the-soic-clip" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Plugging in the SOIC Clip</h3> - -<p>We have to connect the Raspberry Pi to the SOIC Clip as shown in the below diagram (using the f-f wires usually included with the Pomona clip).</p> - -<p><img src="images/rpi/0003.png" alt="SOIC Pinouts for C720 Chromebook" data-canonical-src="http://i.imgur.com/2Z9tveR.png"></p> - -<p>(C720 Only?) The diagram depicts a "bridged" connection. You will need to fashion one with some copper wire:</p> - -<p><img src="images/rpi/0004.jpg" alt="Bridged wires" data-canonical-src="http://i.imgur.com/iDJQu0x.jpg"></p> - -<p>Plug in the wires to the clip as shown below:</p> - -<p><img src="images/rpi/0005.jpg" alt="Pomona Clip connections" data-canonical-src="http://i.imgur.com/zQjqQCk.jpg"></p> - -<p>Plug in the other end of the wires to the Raspberry Pi as shown below:</p> - -<p><img src="images/rpi/0006.jpg" alt="Raspberry Pi connections" data-canonical-src="http://i.imgur.com/c7CcppU.jpg"></p> - -<p>(C720 only?) Plug in the "bridged" wires as shown below:</p> - -<p><img src="images/rpi/0007.jpg" alt="Bridged wires connected" data-canonical-src="http://i.imgur.com/MCvpyDi.jpg"></p> - -<p>Finally, put the Pomona SOIC clip on the chip:</p> - -<p><img src="images/rpi/0008.jpg" alt="Pomona Clip Connected" data-canonical-src="http://i.imgur.com/BBZlEgh.jpg"></p> - -<h3> -<a id="user-content-flashrom" class="anchor" href="#flashrom" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Flashrom</h3> - -<p><a href="http://www.flashrom.org/RaspberryPi">Once it's all set up, flashrom works out of the box.</a></p> - -<h3> -<a id="user-content-sources-1" class="anchor" href="#sources-1" aria-hidden="true"><svg aria-hidden="true" class="octicon octicon-link" height="16" version="1.1" viewbox="0 0 16 16" width="16"><path d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Sources</h3> - -<ul> -<li> -<strong>Pomona SOIC Clip flashing</strong> - -<ul> -<li><a href="https://wiki.archlinux.org/index.php/Chromebook">Arch Linux Wiki - Installing Arch Linux on Chromebook</a></li> -<li><a href="https://drive.google.com/folderview?id=0B9f62MH0umbmRTA2Xzd5WHhjWEU&usp=sharing">Google Drive - Raspberry Pi SOIC Clip connection</a></li> -<li><a href="http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf">rPI with Flashrom and SOIC Clip Powerpoint</a></li> -<li> -<a href="http://www.tnhh.net/2014/08/25/unbricking-chromebook-with-beaglebone.html">Tnhh - Unbricking Chromebook with Beaglebone</a> </li> -</ul> -</li> -<li> -<strong>Use a DIY DIP System to flash an desoldered BIOS chip</strong> - -<ul> -<li><a href="http://diy.viktak.com/2014/07/how-to-recover-laptop-after-failed-bios.html">Viktak - How to recover laptop after failed BIOS flash</a></li> -<li><a href="http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html">Win-Raid - Recover from Failed BIOS Flashing using Raspberry Pi</a></li> -</ul> -</li> -</ul> - - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Lawrence Wu <sagnessagiel@gmail.com><br/> - Copyright © 2015 snuffeluffegus <><br/> - Copyright © 2015 Kevin Keijzer <><br/> - Copyright © 2016 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/rpi_setup.md b/docs/install/rpi_setup.md new file mode 100644 index 00000000..8b53196e --- /dev/null +++ b/docs/install/rpi_setup.md @@ -0,0 +1,472 @@ +<div class="section"> + +How to program an SPI flash chip with the Raspberry Pi {#pagetop} +====================================================== + +This document exists as a guide for reading from or writing to an SPI +flash chip with the Raspberry Pi, using the +[flashrom](http://flashrom.org/Flashrom) software. Most revisions of the +RPi should work. + +This only covers SOIC-8 flash chips, for now. SOIC-16 guide coming later +(for now, it should be easy enough for you to figure this out for +SOIC-16). + +[Back to previous index](../) + +</div> + +<div class="section"> + +[](#raspberry-pi-thinkpad-x60t60-and-macbook-21){#user-content-raspberry-pi-thinkpad-x60t60-and-macbook-21 .anchor}Raspberry Pi (ThinkPad X60/T60 and Macbook 2,1) +------------------------------------------------------------------------------------------------------------------------------------------------------------------ + +The Raspberry Pi (a multipurpose \$25 GNU+Linux computer) can be used as +a BIOS flashing tool, thanks to its GPIO pins and SPI support. + +> **Note:** The Raspberry Pi Model A is not supported, since it has no +> GPIO pins. + +### [](#disassembling-the-thinkpad){#user-content-disassembling-the-thinkpad .anchor}Disassembling the ThinkPad + +Follow the [X60 Hardware Maintenance +Manual](http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/42x3550_04.pdf) +or [T60 Hardware Maintenance +Manual](http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/42t7844_04.pdf) +to disassemble the laptop, until you can access the BIOS chip. + +For photos, follow the [Libreboot T60 Recovery +Guide](http://libreboot.org/docs/install/t60_unbrick.html). + +- On the X60, the BIOS chip is on the bottom of the motherboard, under + a layer of protective black tape. +- On the T60, the BIOS chip is just under the palmrest, but blocked by + a magnesium frame (which you will have to remove). + +### [](#pomona-clip-pinout){#user-content-pomona-clip-pinout .anchor}Pomona Clip Pinout + +Diagram of the 26 GPIO Pins of the Raspberry Pi Model B (for the Model +B+ with 40 pins, start counting from the right and leave 14 pins): + +  + + 8-pin for X60: + + ~~~~ LCD (Front) ~~~~ + 8765 + ---- + | | + ---- + 1234 + ~~~ Palmrest (back) ~~ + + Pin \# SPI Pin Name BP (Seeed) BP (Spkfun) [Beagleboard Black](http://beagleboard.org/Support/bone101#headers) [Raspberry Pi](images/rpi/0000.jpg) + -------- -------------- ------------ ------------- --------------------------------------------------------------------- ------------------------------------- + 1 CS White Red Pin 17 24 + 2 MISO Black Brown Pin 21 21 + 3 *not used* *not used* *not used* *not used* *not used* + 4 GND Brown Black Pin 1 25 + 5 MOSI Gray Orange Pin 18 19 + 6 CLK Purple Yellow Pin 22 23 + 7 *not used* *not used* *not used* *not used* *not used* + 8 3.3V *red* White [3.3V PSU RED](http://libreboot.org/docs/install/bbb_setup.html) 17 + +Make sure the pinouts are correct; otherwise, Flashrom will fail to +detect a chip, or it will \"detect\" a `0x0` chip. Finally, make sure +that the Pomona clip makes contact with the metal wires of the chip. It +can be a challenge, but keep trying. + +### [](#how-to-supply-power-to-the-flashchip){#user-content-how-to-supply-power-to-the-flashchip .anchor}How to supply power to the flashchip + +There are two ways to supply power to the chip: plugging in an AC +adapter (without turning the laptop on), and using the 8th 3.3v pin. + +I have found that the SST chips work best with the 8th pin, while the +Macronix chips require an AC Adapter to power up. + +**Never connect both the 8th pin and the AC adapter at the same time.** + +Your results may vary. + +[](#reading-the-flashchip){#user-content-reading-the-flashchip .anchor}Reading the Flashchip +-------------------------------------------------------------------------------------------- + +First, visually inspect (with a magnifying glass) the type of flashchip +on the motherboard. + +Next, download and compile the latest Flashrom source code on the +Raspberry Pi. + + sudo apt-get install build-essential pciutils usbutils libpci-dev libusb-dev libftdi1 libftdi-dev zlib1g-dev subversion + svn co svn://flashrom.org/flashrom/trunk flashrom + cd flashrom + make + sudo modprobe spi_bcm2708 + sudo modprobe spidev + +If your chip is an SST, run this command: + + sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0 -r test.rom + +If your chip is a Macronix, run this command: + + sudo ./flashrom -c "MX25L1605" -p linux_spi:dev=/dev/spidev0.0 -r test.rom + +Next, check the md5sum of the dump: + + md5sum test.rom + +Run the `flashrom` command again to make a second dump. Then, check the +md5sum of the second dump: + + md5sum test.rom + +If the md5sums match after three tries, `flashrom` has managed to read +the flashchip precisely (but not always accurately). You may try and +flash Libreboot now. + +[](#flashing-libreboot){#user-content-flashing-libreboot .anchor}Flashing Libreboot +----------------------------------------------------------------------------------- + +> **Note:** replace `/path/to/libreboot.rom` with the location of your +> chosen ROM, such as `../bin/x60/libreboot_usqwerty.rom`): + +If your chip is an SST, run this command: + + sudo ./flashrom -p linux_spi:dev=/dev/spidev0.0 -w /path/to/libreboot.rom + +If your chip is a Macronix, run this command: + + sudo ./flashrom -c "MX25L1605" -p linux_spi:dev=/dev/spidev0.0 -w /path/to/libreboot.rom + +Once that command outputs the following, the flash has completed +successfully. If not, just flash again. + + Reading old flash chip contents... done. + Erasing and writing flash chip... Erase/write done. + Verifying flash... VERIFIED. + +### [](#sources){#user-content-sources .anchor}Sources + +- [Scruss - Simple ADC with the Raspberry + 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/) +- **Pomona SOIC Clip flashing** + - [Arch Linux Wiki - Installing Arch Linux on + Chromebook](https://wiki.archlinux.org/index.php/Chromebook) + - [Google Drive - Raspberry Pi SOIC Clip + connection](https://drive.google.com/folderview?id=0B9f62MH0umbmRTA2Xzd5WHhjWEU&usp=sharing) + - [rPI with Flashrom and SOIC Clip + Powerpoint](http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf) + +### [](#raspberry-pi-pinout-diagrams){#user-content-raspberry-pi-pinout-diagrams .anchor}Raspberry Pi Pinout Diagrams + + MCP 3008 Pin Pi GPIO Pin \# Pi Pin Name + ----- ---------- ---------------- -------------------- + 16 `VDD` 1 `3.3 V` + 15 `VREF` 1 `3.3 V` + 14 `AGND` 6 `GND` + 13 `CLK` 23 `GPIO11 SPI0_SCLK` + 12 `DOUT` 21 `GPIO09 SPI0_MISO` + 11 `DIN` 19 `GPIO10 SPI0_MOSI` + 10 `CS` 24 `GPIO08 CE0` + 9 `DGND` 6 `GND` + +- Source: [Perl & Raspberry Pi - Raspberry Pi GPIO + Pinout](http://raspberrypi.znix.com/hipidocs/topic_gpiopins.htm) + +[](#raspberry-pi-thinkpad-x200){#user-content-raspberry-pi-thinkpad-x200 .anchor}Raspberry Pi (ThinkPad X200) +------------------------------------------------------------------------------------------------------------- + +### [](#requirements){#user-content-requirements .anchor}Requirements: + +- An x86, x86\_64, or arm7l (for changing the libreboot.rom image mac + address) +- Raspberry Pi and peripherals +- Relevant SOIC clip +- 6 female - female jumpers +- Internet connection +- Screw drivers + +Follow the [ThinkPad X200: Initial installation +guide](http://libreboot.org/docs/install/x200_external.html) to +disassemble the laptop, and access the BIOS rom chip. + +> **Note:** `x86#` refers to commands to be run on the x86 computer, and +> `pi#` refers to commands to be run on the pi. A good practice is to +> make a work directory to keep your libreboot stuff inside. + + x86# mkdir ~/work + +Download NOOBS from [The Raspberry Pi +Foundation.](https://www.raspberrypi.org/downloads/) Torrent download +recommended, and remember to seed. :) + +If you\'re running Raspian, you can do **sudo raspi-config**, enable SPI +under Advanced and then spidev will be enabled. Simple, eh? + +[Download Libreboot from their releases +page](http://www.libreboot.org/download/). For your safety, verify the +GPG signature as well. + + x86# gpg --keyserver prefered.keyserver.org --recv-keys 0x656F212E + + x86# for signature in $(ls *.sig); do gpg --verify $signature; done + +Extract NOOBS and libreboot. + + x86# mkdir ~/work/noobs + + x86# unzip ~/Downloads/NOOBS_v1_4_1.zip -d ~/work/noobs/ + + x86# cd ~/work && tar -xvJf ~/Downloads/libreboot_bin.tar.xz + +Install Noobs to your fat32 formatted SD card + + x86# cp -R ~/work/noobs/* /path/to/mounted/SDcard/ + +### [](#set-up-noobs-on-raspberry-pi){#user-content-set-up-noobs-on-raspberry-pi .anchor}Set up NOOBS on Raspberry Pi + +Plug in the NOOBs SDCard to your Raspberry Pi, and enable the following +under \'Advanced Options\': + +SSH server + +SPI + +I2C + +On first boot + + pi# sudo apt-get update && sudo apt-get dist-upgrade && reboot + +On second boot + + pi# sudo apt-get update && sudo apt-get install libftdi1 libftdi-dev libusb-dev libpci-dev subversion + +Other dependencies that should already be installed with the noobs base +install include: + +pciutils, zlib, libusb, build-essential + +If they are missing then install them. + +Download and build flashrom. + + pi# svn co svn://flashrom.org/flashrom/trunk ~/flashrom + + pi# cd ~/flashrom + + pi# make + + pi# sudo make install + +On your x86 box change the libreboot.rom mac address + + x86# cd ~/work/libreboot_bin/ + +Change the mac address on the libreboot images to match yours. + + x86# ./ich9macchange XX:XX:XX:XX:XX:XX + +Move the libreboot.rom image over to your pi + + x86# scp ~/work/libreboot_bin/<path_to_your_bin> pi@your.pi.address:~/flashrom/libreboot.rom + +Shutdown your pi, write down your rom chip model, and wire up the clip + + pi# sudo shutdown now -hP + +Chip model name + + + +Pinout. You may want to download the image so you can zoom in on the +text. + + + + Pin \# SPI Pin Name Raspberry Pi Pin \# + -------- -------------- --------------------- + 1 *not used* *not used* + 2 3.3V 1 + 3 *not used* *not used* + 4 *not used* *not used* + 5 *not used* *not used* + 6 *not used* *not used* + 7 CS\# 24 + 8 S0/SIO1 21 + 9 *not used* *not used* + 10 GND 25 + 11 *not used* *not used* + 12 *not used* *not used* + 13 *not used* *not used* + 14 *not used* *not used* + 15 S1/SIO0 19 + 16 SCLK 23 + +> **Note:** The raspberry pi 3.3V rail should be sufficient to power the +> chip during flashing, so no external power supply should be required; +> however, at the time of writing that has only been tested and +> confirmed for one chip, the MX25L6405D. + +Macronix Spec sheet so you can adjust your pinout for 8 pin 4Mb chips as +necessary + + + +At this point connect your SOIC clip to the rom chip before powering on +your PI. + +Power on your Pi, and run the following. Ensure you swap out +\"your\_chip\_name\" with the proper name/model of your chip. Check that +it can be read successfully. If you cannot read the chip and receive an +error similar to \"no EEPROM Detected\" or \"0x0 Chip detected\" then +you may want to try powering off your PI, and switching the two pins +which are connected to the IO ports. I.E. Connect pins (clip)8 to (pi)19 +and pins (clip)15 to (pi)21 + + pi# cd ~/flashrom + + pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -r romread1.rom + + pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -r romread2.rom + + pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -r romread3.rom + + pi# sha512sum romread*.rom + +If they are identical sha512 hashes then you can generally assume that +it\'s safe to flash your rom. + + pi# ./flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=512 --chip <your_chip_name> -w libreboot.rom + +It may fail a couple times, but keep at it and when you get the message +`Verifying flash... Verified` or +`Warning: Chip content is identical to the requested image` then you\'re +done. + +Shut down your pi, put your box back together, and install a libre OS +for great good! + +[](#raspberry-pi-c720-chromebook){#user-content-raspberry-pi-c720-chromebook .anchor}Raspberry Pi (C720 Chromebook) +------------------------------------------------------------------------------------------------------------------- + +The Raspberry Pi (a multipurpose \$25 GNU+Linux computer) can be used as +a BIOS flashing tool, thanks to its GPIO pins and SPI support. + +### [](#what-you-need){#user-content-what-you-need .anchor}What you need + +- \$25 - Raspberry Pi Model B (Rev.2 or higher) +- \$10-20 - SOIC-8 Pomona Clip + - Usually comes bundled with nice, color-colored *female to + female* wires + +### [](#raspberry-pi-pinouts){#user-content-raspberry-pi-pinouts .anchor}Raspberry Pi Pinouts + +GPIO Pinouts: + +  + +> \*Diagram made by [\"Pacman\" from Win-Raid +> Forums\*](http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html) + +SOIC Pinouts: + + + +### [](#plugging-in-the-soic-clip){#user-content-plugging-in-the-soic-clip .anchor}Plugging in the SOIC Clip + +We have to connect the Raspberry Pi to the SOIC Clip as shown in the +below diagram (using the f-f wires usually included with the Pomona +clip). + + + +(C720 Only?) The diagram depicts a \"bridged\" connection. You will need +to fashion one with some copper wire: + + + +Plug in the wires to the clip as shown below: + + + +Plug in the other end of the wires to the Raspberry Pi as shown below: + + + +(C720 only?) Plug in the \"bridged\" wires as shown below: + + + +Finally, put the Pomona SOIC clip on the chip: + + + +### [](#flashrom){#user-content-flashrom .anchor}Flashrom + +[Once it\'s all set up, flashrom works out of the +box.](http://www.flashrom.org/RaspberryPi) + +### [](#sources-1){#user-content-sources-1 .anchor}Sources + +- **Pomona SOIC Clip flashing** + - [Arch Linux Wiki - Installing Arch Linux on + Chromebook](https://wiki.archlinux.org/index.php/Chromebook) + - [Google Drive - Raspberry Pi SOIC Clip + connection](https://drive.google.com/folderview?id=0B9f62MH0umbmRTA2Xzd5WHhjWEU&usp=sharing) + - [rPI with Flashrom and SOIC Clip + Powerpoint](http://satxhackers.org/wp/hack-content/uploads/2013/04/rPI_flashrom.pdf) + - [Tnhh - Unbricking Chromebook with + Beaglebone](http://www.tnhh.net/2014/08/25/unbricking-chromebook-with-beaglebone.html) +- **Use a DIY DIP System to flash an desoldered BIOS chip** + - [Viktak - How to recover laptop after failed BIOS + flash](http://diy.viktak.com/2014/07/how-to-recover-laptop-after-failed-bios.html) + - [Win-Raid - Recover from Failed BIOS Flashing using Raspberry + Pi](http://www.win-raid.com/t58f16-Guide-Recover-from-failed-BIOS-flash-using-Raspberry-PI.html) + +</div> + +<div class="section"> + +Copyright © 2014, 2015 Lawrence Wu <sagnessagiel@gmail.com>\ +Copyright © 2015 snuffeluffegus <>\ +Copyright © 2015 Kevin Keijzer <>\ +Copyright © 2016 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/t400_external.html b/docs/install/t400_external.html deleted file mode 100644 index 39f9c930..00000000 --- a/docs/install/t400_external.html +++ /dev/null @@ -1,580 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad T400: flashing tutorial (BeagleBone Black)</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Flashing the T400 with a BeagleBone Black</h1> - - <p>Initial flashing instructions for T400.</p> - <p> - This guide is for those who want libreboot on their ThinkPad T400 - while they still have the original Lenovo BIOS present. This guide - can also be followed (adapted) if you brick your T400, to know how - to recover. - </p> - - <p> - An - <a href="https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/43y6629_05.pdf#page=386"> - "HMM"</a> (Hardware Maintenance Manual) detailing the process of - [dis]assembly is available for this model. - Be careful when reassembling the laptop as the screws on page 144 - (with title "1130 Keyboard bezel") are swapped and if you follow the - HMM you will punch a hole through the bezel in the upper right corner. - </p> - - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - - <h1 id="preinstall">T400 laptops with libreboot pre-installed</h1> - - <p> - If you don't want to install libreboot yourself, companies exist that sell these laptops - with libreboot pre-installed, along with a free GNU+Linux distribution. - </p> - <p> - Check the <a href="../../suppliers">suppliers</a> page for more information. - </p> - - </div> - - <div class="section"> - - <h2 id="serial_port">Serial port</h2> - - <p> - EHCI debug might not be needed. It has been reported that the docking station - for this laptop has a serial port, so it might be possible to use that instead. - </p> - - </div> - - <div class="section" id="cpu_compatibility"> - - <h1>A note about CPUs</h1> - <p> - <a href="http://www.thinkwiki.org/wiki/Category:T400">ThinkWiki</a> has a list of CPUs - for this system. The Core 2 Duo P8400, P8600 and P8700 are believed to work in libreboot. - The T9600 was confirmed to work, so the T9500/T9550 probably also work. - </p> - - <h2>Quad-core CPUs</h2> - - <p> - Incompatible. Do not use. - </p> - - </div> - - <div class="section" id="switchable_graphics"> - - <h1>A note about GPUs</h1> - - <p> - Some models have an Intel GPU, while others have both an ATI and an Intel GPU; this - is referred to as "switchable graphics". In the <i>BIOS setup</i> program - for lenovobios, you can specify that the system will use one or the other (but not both). - </p> - - <p> - Libreboot is known to work on systems with only the Intel GPU, using native graphics initialization. - On systems with switchable graphics, the Intel GPU is used and the ATI GPU is disabled, so - native graphics initialization works all the same. - </p> - - <h1>CPU paste required</h1> - - <p> - See <a href="#paste">#paste</a>. - </p> - - </div> - - <div class="section"> - - <h1 id="flashchips">Flash chip size</h1> - - <p> - Use this to find out:<br> - # <b>flashrom -p internal -V</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos"> - - <h1 id="macaddress">MAC address</h1> - - <p> - On the T400, the MAC address for the onboard - gigabit ethernet chipset is stored inside the flash chip, - along with other configuration data. - </p> - <p> - Keep a note of the MAC address before disassembly; this is - very important, because you will need to insert this into - the libreboot ROM image before flashing it. - It will be written in one of these locations: - </p> - - <p> - <img src="images/t400/macaddress0.jpg" alt="" /> - <img src="images/t400/macaddress1.jpg" alt="" /> - <img src="images/x200/disassembly/0001.jpg" alt="" /> - </p> - - </div> - - <div class="section photos"> - - <h1>Initial BBB configuration</h1> - - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - configure the BBB for flashing. - </p> - - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-16 (clip: Pomona 5252): - </p> -<pre> -POMONA 5252 (correlate with the BBB guide) -=== ethernet jack and VGA port ==== - NC - - 21 - 1 - - 17 - NC - - NC - NC - - NC - NC - - NC - NC - - NC - 18 - - 3.3V (PSU) - 22 - - NC - this is pin 1 on the flash chip -=== SATA port === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i><br/> -<img src="images/t400/0065.jpg" alt="" /> -</pre> - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): - </p> -<pre> -POMONA 5250 (correlate with the BBB guide) -=== RAM slots ==== - 18 - - 1 - 22 - - NC - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== slot where the AC jack is connected ===<br/> -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i><br/> -<img src="images/t500/0060.jpg" alt="" /> -</pre> - - <h2> - The procedure - </h2> - - <p> - Remove <i>all</i> screws, placing them in the order that you removed them:<br/> - <img src="images/t400/0001.jpg" alt="" /> - <img src="images/t400/0002.jpg" alt="" /> - </p> - <p> - Remove those three screws then remove the rear bezel:<br/> - <img src="images/t400/0003.jpg" alt="" /> - <img src="images/t400/0004.jpg" alt="" /> - <img src="images/t400/0005.jpg" alt="" /> - <img src="images/t400/0006.jpg" alt="" /> - </p> - <p> - Remove the speakers:<br/> - <img src="images/t400/0007.jpg" alt="" /> - <img src="images/t400/0008.jpg" alt="" /> - <img src="images/t400/0009.jpg" alt="" /> - <img src="images/t400/0010.jpg" alt="" /> - <img src="images/t400/0011.jpg" alt="" /> - </p> - <p> - Remove the wifi:<br/> - <img src="images/t400/0012.jpg" alt="" /> - <img src="images/t400/0013.jpg" alt="" /> - </p> - <p> - Remove this cable:<br/> - <img src="images/t400/0014.jpg" alt="" /> - <img src="images/t400/0015.jpg" alt="" /> - <img src="images/t400/0016.jpg" alt="" /> - <img src="images/t400/0017.jpg" alt="" /> - <img src="images/t400/0018.jpg" alt="" /> - </p> - <p> - Unroute those antenna wires:<br/> - <img src="images/t400/0019.jpg" alt="" /> - <img src="images/t400/0020.jpg" alt="" /> - <img src="images/t400/0021.jpg" alt="" /> - <img src="images/t400/0022.jpg" alt="" /> - <img src="images/t400/0023.jpg" alt="" /> - </p> - <p> - Remove the LCD assembly:<br/> - <img src="images/t400/0024.jpg" alt="" /> - <img src="images/t400/0025.jpg" alt="" /> - <img src="images/t400/0026.jpg" alt="" /> - <img src="images/t400/0027.jpg" alt="" /> - <img src="images/t400/0028.jpg" alt="" /> - <img src="images/t400/0029.jpg" alt="" /> - <img src="images/t400/0030.jpg" alt="" /> - <img src="images/t400/0031.jpg" alt="" /> - </p> - <p> - Disconnect the NVRAM battery:<br/> - <img src="images/t400/0033.jpg" alt="" /> - </p> - <p> - Disconnect the fan:<br/> - <img src="images/t400/0034.jpg" alt="" /> - </p> - <p> - Unscrew these:<br/> - <img src="images/t400/0035.jpg" alt="" /> - <img src="images/t400/0036.jpg" alt="" /> - <img src="images/t400/0037.jpg" alt="" /> - <img src="images/t400/0038.jpg" alt="" /> - </p> - <p> - Unscrew the heatsink, then lift it off:<br/> - <img src="images/t400/0039.jpg" alt="" /> - <img src="images/t400/0040.jpg" alt="" /> - </p> - <p> - Disconnect the power jack:<br/> - <img src="images/t400/0041.jpg" alt="" /> - <img src="images/t400/0042.jpg" alt="" /> - </p> - <p> - Loosen this:<br/> - <img src="images/t400/0043.jpg" alt="" /> - </p> - <p> - Remove this:<br/> - <img src="images/t400/0044.jpg" alt="" /> - <img src="images/t400/0045.jpg" alt="" /> - <img src="images/t400/0046.jpg" alt="" /> - <img src="images/t400/0047.jpg" alt="" /> - <img src="images/t400/0048.jpg" alt="" /> - </p> - <p> - Unscrew these:<br/> - <img src="images/t400/0049.jpg" alt="" /> - <img src="images/t400/0050.jpg" alt="" /> - </p> - <p> - Remove this:<br/> - <img src="images/t400/0051.jpg" alt="" /> - <img src="images/t400/0052.jpg" alt="" /> - </p> - <p> - Unscrew this:<br/> - <img src="images/t400/0053.jpg" alt="" /> - </p> - <p> - Remove the motherboard (the cage is still attached) from - the right hand side, then lift it out:<br/> - <img src="images/t400/0054.jpg" alt="" /> - <img src="images/t400/0055.jpg" alt="" /> - <img src="images/t400/0056.jpg" alt="" /> - </p> - <p> - Remove these screws, placing the screws in the same layout - and marking each screw hole (so that you know what ones - to put the screws back into later): - <img src="images/t400/0057.jpg" alt="" /> - <img src="images/t400/0058.jpg" alt="" /> - <img src="images/t400/0059.jpg" alt="" /> - <img src="images/t400/0060.jpg" alt="" /> - <img src="images/t400/0061.jpg" alt="" /> - <img src="images/t400/0062.jpg" alt="" /> - </p> - <p> - Separate the motherboard:<br/> - <img src="images/t400/0063.jpg" alt="" /> - <img src="images/t400/0064.jpg" alt="" /> - </p> - <p> - Connect your programmer, then connect GND and 3.3V<br/> - <img src="images/t400/0065.jpg" alt="" /> - <img src="images/t400/0066.jpg" alt="" /> - <img src="images/t400/0067.jpg" alt="" /> - <img src="images/t400/0069.jpg" alt="" /> - <img src="images/t400/0070.jpg" alt="" /> - <img src="images/t400/0071.jpg" alt="" /> - </p> - <p> - A dedicated 3.3V PSU was used to create this guide, but - at ATX PSU is also fine:<br/> - <img src="images/t400/0072.jpg" alt="" /> - </p> - - <p> - Of course, make sure to turn on your PSU:<br/> - <img src="images/x200/disassembly/0013.jpg" alt="" /> - </p> - - <p> - Now, you should be ready to install libreboot. - </p> - - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - <p> - Log in as root on your BBB, using the instructions in <a href="bbb_setup.html#bbb_access">bbb_setup.html#bbb_access</a>. - </p> - <p> - Test that flashrom works:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512</b><br/> - In this case, the output was: - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. -Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" -Please specify which chip definition to use with the -c <chipname> option. -</pre> - <p> - How to backup factory.rom (change the -c option as neeed, for your flash chip):<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom</b><br/> - Note: the <b>-c</b> option is not required in libreboot's patched flashrom, because - the redundant flash chip definitions in <i>flashchips.c</i> have been removed.<br/> - Now compare the 3 images:<br/> - # <b>sha512sum factory*.rom</b><br/> - If the hashes match, 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 and libreboot. - </p> - <p> - Follow the instructions at <a href="../hcl/gm45_remove_me.html#ich9gen">../hcl/gm45_remove_me.html#ich9gen</a> - to change the MAC address inside the libreboot ROM image, before flashing it. - Although there is a default MAC address inside the ROM image, this is not what you want. <b>Make sure - to always change the MAC address to one that is correct for your system.</b> - </p> - <p> - Now flash it:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V</b> - </p> - <p> - <img src="images/x200/disassembly/0015.jpg" alt="" /> - </p> - <p> - You might see errors, but if it says <b>Verifying flash... VERIFIED</b> at the end, then it's flashed and should boot. - If you see errors, try again (and again, and again); the message <b>Chip content is identical to the requested image</b> - is also an indication of a successful installation. - </p> - <p> - Example output from running the command (see above): - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Reading old flash chip contents... done. -Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 -ERASE FAILED! -Reading current flash chip contents... done. Looking for another erase function. -Erase/write done. -Verifying flash... VERIFIED. -</pre> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos" id="paste"> - - <h1>Thermal paste (IMPORTANT)</h1> - - <p> - Because part of this procedure involved removing the heatsink, you will need to apply new paste. - Arctic MX-4 is ok. You will also need isopropyl alcohol and an anti-static cloth to clean with. - </p> - - <p> - When re-installing the heatsink, you must first clean off all old paste with the alcohol/cloth. - Then apply new paste. Arctic MX-4 is also much better than the default paste used on these systems. - </p> - - <p> - <img src="images/t400/paste.jpg" alt="" /> - </p> - - <p> - NOTE: the photo above is for illustration purposes only, and does not show how to properly apply the thermal paste. - Other guides online detail the proper application procedure. - </p> - - </div> - - <div class="section"> - - <h1 id="wifi">Wifi</h1> - - <p> - The T400 typically comes with an Intel wifi chipset, which does not - work without proprietary software. For a list of wifi chipsets that - work without proprietary software, see - <a href="../hcl/#recommended_wifi">../hcl/#recommended_wifi</a>. - </p> - - <p> - Some T400 laptops might come with an Atheros chipset, but this is 802.11g only. - </p> - - <p> - It is recommended that you install a new wifi chipset. This can only - be done after installing libreboot, because the original firmware has - a whitelist of approved chips, and it will refuse to boot if you - use an 'unauthorized' wifi card. - </p> - - <p> - The following photos show an Atheros AR5B95 being installed, to - replace the Intel chip that this T400 came with:<br/> - <img src="images/t400/0012.jpg" alt="" /> - <img src="images/t400/ar5b95.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <h1 id="wwan">WWAN</h1> - <p> - If you have a WWAN/3G card and/or sim card reader, remove them permanently. - The WWAN-3G card has proprietary firmware inside; the technology is - identical to what is used in mobile phones, so it can also track your movements. - </p> - <p> - Not to be confused with wifi (wifi is fine). - </p> - - </div> - - <div class="section photos"> - - <h1 id="memory">Memory</h1> - - <p> - You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs - (speed/size). Non-matching pairs won't work. You can also install a - single module (meaning, one of the slots will be empty) in slot 0. - </p> - - <p> - Make sure that the RAM you buy is the 2Rx8 density. - </p> - - <p> - <a href="http://www.forum.thinkpads.com/viewtopic.php?p=760721">This page</a> might be useful for RAM compatibility info - (note: coreboot raminit is different, so this page might be BS) - </p> - - <p> - The following photo shows 8GiB (2x4GiB) of RAM installed:<br/> - <img src="images/t400/memory.jpg" alt="" /> - </p> - - </div> - - <div class="section photos"> - - <h2> - Boot it! - </h2> - <p> - You should see something like this: - </p> - <p> - <img src="images/t400/boot0.jpg" alt="" /> - <img src="images/t400/boot1.jpg" alt="" /> - </p> - - <p> - Now <a href="../gnulinux/">install GNU+Linux</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2015 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/t400_external.md b/docs/install/t400_external.md new file mode 100644 index 00000000..568d5062 --- /dev/null +++ b/docs/install/t400_external.md @@ -0,0 +1,451 @@ +<div class="section"> + +Flashing the T400 with a BeagleBone Black {#pagetop} +========================================= + +Initial flashing instructions for T400. + +This guide is for those who want libreboot on their ThinkPad T400 while +they still have the original Lenovo BIOS present. This guide can also be +followed (adapted) if you brick your T400, to know how to recover. + +An +[\"HMM\"](https://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/43y6629_05.pdf#page=386) +(Hardware Maintenance Manual) detailing the process of \[dis\]assembly +is available for this model. Be careful when reassembling the laptop as +the screws on page 144 (with title \"1130 Keyboard bezel\") are swapped +and if you follow the HMM you will punch a hole through the bezel in the +upper right corner. + +[Back to main index](./) + +</div> + +<div class="section"> + +T400 laptops with libreboot pre-installed {#preinstall} +========================================= + +If you don\'t want to install libreboot yourself, companies exist that +sell these laptops with libreboot pre-installed, along with a free +GNU+Linux distribution. + +Check the [suppliers](../../suppliers) page for more information. + +</div> + +<div class="section"> + +Serial port {#serial_port} +----------- + +EHCI debug might not be needed. It has been reported that the docking +station for this laptop has a serial port, so it might be possible to +use that instead. + +</div> + +<div id="cpu_compatibility" class="section"> + +A note about CPUs +================= + +[ThinkWiki](http://www.thinkwiki.org/wiki/Category:T400) has a list of +CPUs for this system. The Core 2 Duo P8400, P8600 and P8700 are believed +to work in libreboot. The T9600 was confirmed to work, so the +T9500/T9550 probably also work. + +Quad-core CPUs +-------------- + +Incompatible. Do not use. + +</div> + +<div id="switchable_graphics" class="section"> + +A note about GPUs +================= + +Some models have an Intel GPU, while others have both an ATI and an +Intel GPU; this is referred to as \"switchable graphics\". In the *BIOS +setup* program for lenovobios, you can specify that the system will use +one or the other (but not both). + +Libreboot is known to work on systems with only the Intel GPU, using +native graphics initialization. On systems with switchable graphics, the +Intel GPU is used and the ATI GPU is disabled, so native graphics +initialization works all the same. + +CPU paste required +================== + +See [\#paste](#paste). + +</div> + +<div class="section"> + +Flash chip size {#flashchips} +=============== + +Use this to find out:\ +\# **flashrom -p internal -V** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section photos"> + +MAC address {#macaddress} +=========== + +On the T400, the MAC address for the onboard gigabit ethernet chipset is +stored inside the flash chip, along with other configuration data. + +Keep a note of the MAC address before disassembly; this is very +important, because you will need to insert this into the libreboot ROM +image before flashing it. It will be written in one of these locations: + +  + + +</div> + +<div class="section photos"> + +Initial BBB configuration +========================= + +Refer to [bbb\_setup.html](bbb_setup.html) for how to configure the BBB +for flashing. + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-16 (clip: Pomona 5252): + + POMONA 5252 (correlate with the BBB guide) + === ethernet jack and VGA port ==== + NC - - 21 + 1 - - 17 + NC - - NC + NC - - NC + NC - - NC + NC - - NC + 18 - - 3.3V (PSU) + 22 - - NC - this is pin 1 on the flash chip + === SATA port === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-8 (clip: Pomona 5250): + + POMONA 5250 (correlate with the BBB guide) + === RAM slots ==== + 18 - - 1 + 22 - - NC + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + === slot where the AC jack is connected === + + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +The procedure +------------- + +Remove *all* screws, placing them in the order that you removed them:\ +  + +Remove those three screws then remove the rear bezel:\ +  +  + +Remove the speakers:\ +  +  + + +Remove the wifi:\ +  + +Remove this cable:\ +  +  + + +Unroute those antenna wires:\ +  +  + + +Remove the LCD assembly:\ +  +  +  +  + +Disconnect the NVRAM battery:\ + + +Disconnect the fan:\ + + +Unscrew these:\ +  +  + +Unscrew the heatsink, then lift it off:\ +  + +Disconnect the power jack:\ +  + +Loosen this:\ + + +Remove this:\ +  +  + + +Unscrew these:\ +  + +Remove this:\ +  + +Unscrew this:\ + + +Remove the motherboard (the cage is still attached) from the right hand +side, then lift it out:\ +  + + +Remove these screws, placing the screws in the same layout and marking +each screw hole (so that you know what ones to put the screws back into +later):   +  +  + +Separate the motherboard:\ +  + +Connect your programmer, then connect GND and 3.3V\ +  +  +  + +A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is +also fine:\ + + +Of course, make sure to turn on your PSU:\ + + +Now, you should be ready to install libreboot. + +Flashrom binaries for ARM (tested on a BBB) are distributed in +libreboot\_util. Alternatively, libreboot also distributes flashrom +source code which can be built. + +Log in as root on your BBB, using the instructions in +[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). + +Test that flashrom works:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ +In this case, the output was: + + flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. + Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" + Please specify which chip definition to use with the -c <chipname> option. + +How to backup factory.rom (change the -c option as neeed, for your flash +chip):\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory1.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory2.rom**\ +Note: the **-c** option is not required in libreboot\'s patched +flashrom, because the redundant flash chip definitions in *flashchips.c* +have been removed.\ +Now compare the 3 images:\ +\# **sha512sum factory\*.rom**\ +If the hashes match, 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 +and libreboot. + +Follow the instructions at +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +to change the MAC address inside the libreboot ROM image, before +flashing it. Although there is a default MAC address inside the ROM +image, this is not what you want. **Make sure to always change the MAC +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** + + + +You might see errors, but if it says **Verifying flash\... VERIFIED** at +the end, then it\'s flashed and should boot. If you see errors, try +again (and again, and again); the message **Chip content is identical to +the requested image** is also an indication of a successful +installation. + +Example output from running the command (see above): + + flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Reading old flash chip contents... done. + Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 + ERASE FAILED! + Reading current flash chip contents... done. Looking for another erase function. + Erase/write done. + Verifying flash... VERIFIED. + +[Back to top of page.](#pagetop) + +</div> + +<div id="paste" class="section photos"> + +Thermal paste (IMPORTANT) +========================= + +Because part of this procedure involved removing the heatsink, you will +need to apply new paste. Arctic MX-4 is ok. You will also need isopropyl +alcohol and an anti-static cloth to clean with. + +When re-installing the heatsink, you must first clean off all old paste +with the alcohol/cloth. Then apply new paste. Arctic MX-4 is also much +better than the default paste used on these systems. + + + +NOTE: the photo above is for illustration purposes only, and does not +show how to properly apply the thermal paste. Other guides online detail +the proper application procedure. + +</div> + +<div class="section"> + +Wifi +==== + +The T400 typically comes with an Intel wifi chipset, which does not work +without proprietary software. For a list of wifi chipsets that work +without proprietary software, see +[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). + +Some T400 laptops might come with an Atheros chipset, but this is +802.11g only. + +It is recommended that you install a new wifi chipset. This can only be +done after installing libreboot, because the original firmware has a +whitelist of approved chips, and it will refuse to boot if you use an +\'unauthorized\' wifi card. + +The following photos show an Atheros AR5B95 being installed, to replace +the Intel chip that this T400 came with:\ +  + +</div> + +<div class="section"> + +WWAN +==== + +If you have a WWAN/3G card and/or sim card reader, remove them +permanently. The WWAN-3G card has proprietary firmware inside; the +technology is identical to what is used in mobile phones, so it can also +track your movements. + +Not to be confused with wifi (wifi is fine). + +</div> + +<div class="section photos"> + +Memory +====== + +You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs +(speed/size). Non-matching pairs won\'t work. You can also install a +single module (meaning, one of the slots will be empty) in slot 0. + +Make sure that the RAM you buy is the 2Rx8 density. + +[This page](http://www.forum.thinkpads.com/viewtopic.php?p=760721) might +be useful for RAM compatibility info (note: coreboot raminit is +different, so this page might be BS) + +The following photo shows 8GiB (2x4GiB) of RAM installed:\ + + +</div> + +<div class="section photos"> + +Boot it! +-------- + +You should see something like this: + +  + +Now [install GNU+Linux](../gnulinux/). + +</div> + +<div class="section"> + +Copyright © 2015 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/t500_external.html b/docs/install/t500_external.html deleted file mode 100644 index 6d7dedc5..00000000 --- a/docs/install/t500_external.html +++ /dev/null @@ -1,580 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad T500: flashing tutorial (BeagleBone Black)</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Flashing the T500 with a BeagleBone Black</h1> - - <p>Initial flashing instructions for T500.</p> - <p> - This guide is for those who want libreboot on their ThinkPad T500 - while they still have the original Lenovo BIOS present. This guide - can also be followed (adapted) if you brick your T500, to know how - to recover. - </p> - - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - - <h1 id="t400">Libreboot T400</h1> - <p> - You may also be interested in the smaller, more portable <a href="t400_external.html">Libreboot T400</a>. - </p> - - </div> - - <div class="section"> - - <h2 id="serial_port">Serial port</h2> - - <p> - EHCI debug might not be needed. It has been reported that the docking station - for this laptop has a serial port, so it might be possible to use that instead. - </p> - - </div> - - <div class="section" id="cpu_compatibility"> - - <h1>A note about CPUs</h1> - <p> - <a href="http://www.thinkwiki.org/wiki/Category:T500">ThinkWiki</a> has a list of CPUs - for this system. The Core 2 Duo P8400, P8600 and P8700 are believed to work in libreboot. - The T9600 was also tested on the T400 and confirmed working, so the T9400/T9500/T9550 probably - also work, but they are untested. - </p> - - <h2>Quad-core CPUs</h2> - - <p> - Incompatible. Do not use. - </p> - - </div> - - <div class="section" id="switchable_graphics"> - - <h1>A note about GPUs</h1> - - <p> - Some models have an Intel GPU, while others have both an ATI and an Intel GPU; this - is referred to as "switchable graphics". In the <i>BIOS setup</i> program - for lenovobios, you can specify that the system will use one or the other (but not both). - </p> - - <p> - Libreboot is known to work on systems with only the Intel GPU, using native graphics initialization. - On systems with switchable graphics, the Intel GPU is used and the ATI GPU is disabled, so - native graphics initialization works all the same. - </p> - - <h1>CPU paste required</h1> - - <p> - See <a href="#paste">#paste</a>. - </p> - - </div> - - <div class="section"> - - <h1 id="flashchips">Flash chip size</h1> - - <p> - Use this to find out:<br/> - # <b>flashrom -p internal -V</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos"> - - <h1 id="macaddress">MAC address</h1> - - <p> - On the T500, the MAC address for the onboard - gigabit ethernet chipset is stored inside the flash chip, - along with other configuration data. - </p> - <p> - Keep a note of the MAC address before disassembly; this is - very important, because you will need to insert this into - the libreboot ROM image before flashing it. - It will be written in one of these locations: - </p> - - <p> - <img src="images/t400/macaddress0.jpg" alt="" /> - <img src="images/t400/macaddress1.jpg" alt="" /> - <img src="images/x200/disassembly/0001.jpg" alt="" /> - </p> - - </div> - - <div class="section photos"> - - <h1>Initial BBB configuration</h1> - - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - configure the BBB for flashing. - </p> - - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-16 (clip: Pomona 5252): - </p> -<pre> -POMONA 5252 (correlate with the BBB guide) -=== ethernet jack and VGA port ==== - NC - - 21 - 1 - - 17 - NC - - NC - NC - - NC - NC - - NC - NC - - NC - 18 - - 3.3V (PSU) - 22 - - NC - this is pin 1 on the flash chip -=== SATA port === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i><br/> -<img src="images/t400/0065.jpg" alt="" /> -</pre> - <p> - The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): - </p> -<pre> -POMONA 5250 (correlate with the BBB guide) -=== RAM slots ==== - 18 - - 1 - 22 - - NC - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== slot where the AC jack is connected ===<br/> -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i><br/> -<img src="images/t500/0060.jpg" alt="" /> -</pre> - - <h2> - The procedure - </h2> - - <p> - Remove all screws:<br/> - <img src="images/t500/0000.jpg" alt="" /><br/> - It is also advisable to, throughout the disassembly, - place any screws and/or components that you removed in - the same layout or arrangement. The follow photos demonstrate - this:<br/> - <img src="images/t500/0001.jpg" alt="" /> - <img src="images/t500/0002.jpg" alt="" /> - </p> - <p> - Remove the HDD/SSD and optical drive:<br/> - <img src="images/t500/0003.jpg" alt="" /> - <img src="images/t500/0004.jpg" alt="" /> - </p> - <p> - Remove the palm rest:<br/> - <img src="images/t500/0005.jpg" alt="" /> - <img src="images/t500/0006.jpg" alt="" /> - </p> - <p> - Remove the keyboard and rear bezel:<br/> - <img src="images/t500/0007.jpg" alt="" /> - <img src="images/t500/0008.jpg" alt="" /> - <img src="images/t500/0009.jpg" alt="" /> - <img src="images/t500/0010.jpg" alt="" /> - <img src="images/t500/0011.jpg" alt="" /> - <img src="images/t500/0012.jpg" alt="" /> - </p> - <p> - If you have a WWAN/3G card and/or sim card reader, - remove them permanently. The WWAN-3G card has proprietary firmware inside; the technology is identical - to what is used in mobile phones, so it can also track - your movements:<br/> - <img src="images/t500/0013.jpg" alt="" /> - <img src="images/t500/0017.jpg" alt="" /> - <img src="images/t500/0018.jpg" alt="" /> - </p> - <p> - Remove this frame, and then remove the wifi chip:<br/> - <img src="images/t500/0014.jpg" alt="" /> - <img src="images/t500/0015.jpg" alt="" /> - <img src="images/t500/0016.jpg" alt="" /> - </p> - <p> - Remove the speakers:<br/> - <img src="images/t500/0019.jpg" alt="" /> - <img src="images/t500/0020.jpg" alt="" /> - <img src="images/t500/0021.jpg" alt="" /> - <img src="images/t500/0022.jpg" alt="" /> - <img src="images/t500/0023.jpg" alt="" /> - <img src="images/t500/0024.jpg" alt="" /> - <img src="images/t500/0025.jpg" alt="" /> - </p> - <p> - Remove the NVRAM battery (already removed in this photo):<br/> - <img src="images/t500/0026.jpg" alt="" /> - </p> - <p> - When you re-assemble, you will be replacing the wifi chip - with another. These two screws don't hold anything together, - but they are included in your system because the screw - holes for half-height cards are a different size, so - use these if you will be installing a half-height card:<br/> - <img src="images/t500/0027.jpg" alt="" /> - </p> - <p> - Unroute the antenna wires:<br/> - <img src="images/t500/0028.jpg" alt="" /> - <img src="images/t500/0029.jpg" alt="" /> - <img src="images/t500/0030.jpg" alt="" /> - <img src="images/t500/0031.jpg" alt="" /> - </p> - <p> - Disconnect the LCD cable from the motherboard:<br/> - <img src="images/t500/0032.jpg" alt="" /> - <img src="images/t500/0033.jpg" alt="" /> - </p> - <p> - Remove the LCD assembly hinge screws, and then remove the LCD - assembly:<br/> - <img src="images/t500/0034.jpg" alt="" /> - <img src="images/t500/0035.jpg" alt="" /> - <img src="images/t500/0036.jpg" alt="" /> - </p> - <p> - Remove the fan and heatsink:<br/> - <img src="images/t500/0037.jpg" alt="" /> - <img src="images/t500/0038.jpg" alt="" /> - <img src="images/t500/0039.jpg" alt="" /> - </p> - <p> - Remove this screw:<br/> - <img src="images/t500/0040.jpg" alt="" /> - </p> - <p> - Remove these cables, keeping note of how and in what - arrangement they are connected:<br/> - <img src="images/t500/0041.jpg" alt="" /> - <img src="images/t500/0042.jpg" alt="" /> - <img src="images/t500/0043.jpg" alt="" /> - <img src="images/t500/0044.jpg" alt="" /> - <img src="images/t500/0045.jpg" alt="" /> - <img src="images/t500/0046.jpg" alt="" /> - <img src="images/t500/0047.jpg" alt="" /> - <img src="images/t500/0048.jpg" alt="" /> - <img src="images/t500/0049.jpg" alt="" /> - </p> - <p> - Disconnect the power jack:<br/> - <img src="images/t500/0050.jpg" alt="" /> - <img src="images/t500/0051.jpg" alt="" /> - </p> - <p> - Remove the motherboard and cage from the base - (the marked hole is where those cables were routed through):<br/> - <img src="images/t500/0052.jpg" alt="" /> - <img src="images/t500/0053.jpg" alt="" /> - </p> - <p> - Remove all screws, arranging them in the same layout - when placing the screws on a surface and marking each screw - hole (this is to reduce the possibility of putting them - back in the wrong holes):<br/> - <img src="images/t500/0054.jpg" alt="" /> - <img src="images/t500/0055.jpg" alt="" /> - </p> - <p> - Also remove this:<br/> - <img src="images/t500/0056.jpg" alt="" /> - <img src="images/t500/0057.jpg" alt="" /> - </p> - <p> - Separate the motherboard from the cage:<br/> - <img src="images/t500/0058.jpg" alt="" /> - <img src="images/t500/0059.jpg" alt="" /> - </p> - <p> - The flash chip is next to the memory slots. On this - system, it was a SOIC-8 (4MiB or 32Mb) flash chip:<br/> - <img src="images/t500/0060.jpg" alt="" /> - </p> - <p> - Connect your programmer, then connect GND and 3.3V<br/> - <img src="images/t500/0061.jpg" alt="" /><br/> - <img src="images/t400/0067.jpg" alt="" /> - <img src="images/t400/0069.jpg" alt="" /> - <img src="images/t400/0070.jpg" alt="" /> - <img src="images/t400/0071.jpg" alt="" /> - </p> - <p> - A dedicated 3.3V PSU was used to create this guide, but - at ATX PSU is also fine:<br/> - <img src="images/t400/0072.jpg" alt="" /> - </p> - - <p> - Of course, make sure to turn on your PSU:<br/> - <img src="images/x200/disassembly/0013.jpg" alt="" /> - </p> - - <p> - Now, you should be ready to install libreboot. - </p> - - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - <p> - Log in as root on your BBB, using the instructions in <a href="bbb_setup.html#bbb_access">bbb_setup.html#bbb_access</a>. - </p> - <p> - Test that flashrom works:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512</b><br/> - In this case, the output was: - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. -Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" -Please specify which chip definition to use with the -c <chipname> option. -</pre> - <p> - How to backup factory.rom (change the -c option as neeed, for your flash chip):<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom</b><br/> - Note: the <b>-c</b> option is not required in libreboot's patched flashrom, because - the redundant flash chip definitions in <i>flashchips.c</i> have been removed.<br/> - Now compare the 3 images:<br/> - # <b>sha512sum factory*.rom</b><br/> - If the hashes match, 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 and libreboot. - </p> - <p> - Follow the instructions at <a href="../hcl/gm45_remove_me.html#ich9gen">../hcl/gm45_remove_me.html#ich9gen</a> - to change the MAC address inside the libreboot ROM image, before flashing it. - Although there is a default MAC address inside the ROM image, this is not what you want. <b>Make sure - to always change the MAC address to one that is correct for your system.</b> - </p> - <p> - Now flash it:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V</b> - </p> - <p> - <img src="images/x200/disassembly/0015.jpg" alt="" /> - </p> - <p> - You might see errors, but if it says <b>Verifying flash... VERIFIED</b> at the end, then it's flashed and should boot. - If you see errors, try again (and again, and again); the message <b>Chip content is identical to the requested image</b> - is also an indication of a successful installation. - </p> - <p> - Example output from running the command (see above): - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Reading old flash chip contents... done. -Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 -ERASE FAILED! -Reading current flash chip contents... done. Looking for another erase function. -Erase/write done. -Verifying flash... VERIFIED. -</pre> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos" id="paste"> - - <h1>Thermal paste (IMPORTANT)</h1> - - <p> - Because part of this procedure involved removing the heatsink, you will need to apply new paste. - Arctic MX-4 is ok. You will also need isopropyl alcohol and an anti-static cloth to clean with. - </p> - - <p> - When re-installing the heatsink, you must first clean off all old paste with the alcohol/cloth. - Then apply new paste. Arctic MX-4 is also much better than the default paste used on these systems. - </p> - - <p> - <img src="images/t400/paste.jpg" alt="" /> - </p> - - <p> - NOTE: the photo above is for illustration purposes only, and does not show how to properly apply the thermal paste. - Other guides online detail the proper application procedure. - </p> - - </div> - - <div class="section"> - - <h1 id="wifi">Wifi</h1> - - <p> - The T500 typically comes with an Intel wifi chipset, which does not - work without proprietary software. For a list of wifi chipsets that - work without proprietary software, see - <a href="../hcl/#recommended_wifi">../hcl/#recommended_wifi</a>. - </p> - - <p> - Some T500 laptops might come with an Atheros chipset, but this is 802.11g only. - </p> - - <p> - It is recommended that you install a new wifi chipset. This can only - be done after installing libreboot, because the original firmware has - a whitelist of approved chips, and it will refuse to boot if you - use an 'unauthorized' wifi card. - </p> - - <p> - The following photos show an Atheros AR5B95 being installed, to - replace the Intel chip that this T500 came with:<br/> - <img src="images/t400/0012.jpg" alt="" /> - <img src="images/t400/ar5b95.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <h1 id="wwan">WWAN</h1> - <p> - If you have a WWAN/3G card and/or sim card reader, remove them permanently. - The WWAN-3G card has DMA, and proprietary firmware inside; the technology is - identical to what is used in mobile phones, so it can also track your movements. - </p> - <p> - Not to be confused with wifi (wifi is fine). - </p> - - </div> - - <div class="section photos"> - - <h1 id="memory">Memory</h1> - - <p> - You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs - (speed/size). Non-matching pairs won't work. You can also install a - single module (meaning, one of the slots will be empty) in slot 0. - </p> - - <p> - Make sure that the RAM you buy is the 2Rx8 density. - </p> - - <p> - <a href="http://www.forum.thinkpads.com/viewtopic.php?p=760721">This page</a> might be useful for RAM compatibility info - (note: coreboot raminit is different, so this page might be BS) - </p> - - <p> - The following photo shows 8GiB (2x4GiB) of RAM installed:<br/> - <img src="images/t400/memory.jpg" alt="" /> - </p> - - </div> - - <div class="section photos"> - - <h2> - Boot it! - </h2> - <p> - You should see something like this: - </p> - <p> - <img src="images/t500/0062.jpg" alt="" /> - </p> - - <p> - Now <a href="../gnulinux/">install GNU+Linux</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2015 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/t500_external.md b/docs/install/t500_external.md new file mode 100644 index 00000000..b7b60bb7 --- /dev/null +++ b/docs/install/t500_external.md @@ -0,0 +1,456 @@ +<div class="section"> + +Flashing the T500 with a BeagleBone Black {#pagetop} +========================================= + +Initial flashing instructions for T500. + +This guide is for those who want libreboot on their ThinkPad T500 while +they still have the original Lenovo BIOS present. This guide can also be +followed (adapted) if you brick your T500, to know how to recover. + +[Back to main index](./) + +</div> + +<div class="section"> + +Libreboot T400 {#t400} +============== + +You may also be interested in the smaller, more portable [Libreboot +T400](t400_external.html). + +</div> + +<div class="section"> + +Serial port {#serial_port} +----------- + +EHCI debug might not be needed. It has been reported that the docking +station for this laptop has a serial port, so it might be possible to +use that instead. + +</div> + +<div id="cpu_compatibility" class="section"> + +A note about CPUs +================= + +[ThinkWiki](http://www.thinkwiki.org/wiki/Category:T500) has a list of +CPUs for this system. The Core 2 Duo P8400, P8600 and P8700 are believed +to work in libreboot. The T9600 was also tested on the T400 and +confirmed working, so the T9400/T9500/T9550 probably also work, but they +are untested. + +Quad-core CPUs +-------------- + +Incompatible. Do not use. + +</div> + +<div id="switchable_graphics" class="section"> + +A note about GPUs +================= + +Some models have an Intel GPU, while others have both an ATI and an +Intel GPU; this is referred to as \"switchable graphics\". In the *BIOS +setup* program for lenovobios, you can specify that the system will use +one or the other (but not both). + +Libreboot is known to work on systems with only the Intel GPU, using +native graphics initialization. On systems with switchable graphics, the +Intel GPU is used and the ATI GPU is disabled, so native graphics +initialization works all the same. + +CPU paste required +================== + +See [\#paste](#paste). + +</div> + +<div class="section"> + +Flash chip size {#flashchips} +=============== + +Use this to find out:\ +\# **flashrom -p internal -V** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section photos"> + +MAC address {#macaddress} +=========== + +On the T500, the MAC address for the onboard gigabit ethernet chipset is +stored inside the flash chip, along with other configuration data. + +Keep a note of the MAC address before disassembly; this is very +important, because you will need to insert this into the libreboot ROM +image before flashing it. It will be written in one of these locations: + +  + + +</div> + +<div class="section photos"> + +Initial BBB configuration +========================= + +Refer to [bbb\_setup.html](bbb_setup.html) for how to configure the BBB +for flashing. + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-16 (clip: Pomona 5252): + + POMONA 5252 (correlate with the BBB guide) + === ethernet jack and VGA port ==== + NC - - 21 + 1 - - 17 + NC - - NC + NC - - NC + NC - - NC + NC - - NC + 18 - - 3.3V (PSU) + 22 - - NC - this is pin 1 on the flash chip + === SATA port === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +The following shows how to connect clip to the BBB (on the P9 header), +for SOIC-8 (clip: Pomona 5250): + + POMONA 5250 (correlate with the BBB guide) + === RAM slots ==== + 18 - - 1 + 22 - - NC + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + === slot where the AC jack is connected === + + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +The procedure +------------- + +Remove all screws:\ +\ +It is also advisable to, throughout the disassembly, place any screws +and/or components that you removed in the same layout or arrangement. +The follow photos demonstrate this:\ +  + +Remove the HDD/SSD and optical drive:\ +  + +Remove the palm rest:\ +  + +Remove the keyboard and rear bezel:\ +  +  +  + +If you have a WWAN/3G card and/or sim card reader, remove them +permanently. The WWAN-3G card has proprietary firmware inside; the +technology is identical to what is used in mobile phones, so it can also +track your movements:\ +  + + +Remove this frame, and then remove the wifi chip:\ +  + + +Remove the speakers:\ +  +  +  + + +Remove the NVRAM battery (already removed in this photo):\ + + +When you re-assemble, you will be replacing the wifi chip with another. +These two screws don\'t hold anything together, but they are included in +your system because the screw holes for half-height cards are a +different size, so use these if you will be installing a half-height +card:\ + + +Unroute the antenna wires:\ +  +  + +Disconnect the LCD cable from the motherboard:\ +  + +Remove the LCD assembly hinge screws, and then remove the LCD assembly:\ +  + + +Remove the fan and heatsink:\ +  + + +Remove this screw:\ + + +Remove these cables, keeping note of how and in what arrangement they +are connected:\ +  +  +  +  + + +Disconnect the power jack:\ +  + +Remove the motherboard and cage from the base (the marked hole is where +those cables were routed through):\ +  + +Remove all screws, arranging them in the same layout when placing the +screws on a surface and marking each screw hole (this is to reduce the +possibility of putting them back in the wrong holes):\ +  + +Also remove this:\ +  + +Separate the motherboard from the cage:\ +  + +The flash chip is next to the memory slots. On this system, it was a +SOIC-8 (4MiB or 32Mb) flash chip:\ + + +Connect your programmer, then connect GND and 3.3V\ +\ +  +  + +A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is +also fine:\ + + +Of course, make sure to turn on your PSU:\ + + +Now, you should be ready to install libreboot. + +Flashrom binaries for ARM (tested on a BBB) are distributed in +libreboot\_util. Alternatively, libreboot also distributes flashrom +source code which can be built. + +Log in as root on your BBB, using the instructions in +[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). + +Test that flashrom works:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ +In this case, the output was: + + flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. + Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" + Please specify which chip definition to use with the -c <chipname> option. + +How to backup factory.rom (change the -c option as neeed, for your flash +chip):\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory1.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory2.rom**\ +Note: the **-c** option is not required in libreboot\'s patched +flashrom, because the redundant flash chip definitions in *flashchips.c* +have been removed.\ +Now compare the 3 images:\ +\# **sha512sum factory\*.rom**\ +If the hashes match, 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 +and libreboot. + +Follow the instructions at +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +to change the MAC address inside the libreboot ROM image, before +flashing it. Although there is a default MAC address inside the ROM +image, this is not what you want. **Make sure to always change the MAC +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** + + + +You might see errors, but if it says **Verifying flash\... VERIFIED** at +the end, then it\'s flashed and should boot. If you see errors, try +again (and again, and again); the message **Chip content is identical to +the requested image** is also an indication of a successful +installation. + +Example output from running the command (see above): + + flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Reading old flash chip contents... done. + Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 + ERASE FAILED! + Reading current flash chip contents... done. Looking for another erase function. + Erase/write done. + Verifying flash... VERIFIED. + +[Back to top of page.](#pagetop) + +</div> + +<div id="paste" class="section photos"> + +Thermal paste (IMPORTANT) +========================= + +Because part of this procedure involved removing the heatsink, you will +need to apply new paste. Arctic MX-4 is ok. You will also need isopropyl +alcohol and an anti-static cloth to clean with. + +When re-installing the heatsink, you must first clean off all old paste +with the alcohol/cloth. Then apply new paste. Arctic MX-4 is also much +better than the default paste used on these systems. + + + +NOTE: the photo above is for illustration purposes only, and does not +show how to properly apply the thermal paste. Other guides online detail +the proper application procedure. + +</div> + +<div class="section"> + +Wifi +==== + +The T500 typically comes with an Intel wifi chipset, which does not work +without proprietary software. For a list of wifi chipsets that work +without proprietary software, see +[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). + +Some T500 laptops might come with an Atheros chipset, but this is +802.11g only. + +It is recommended that you install a new wifi chipset. This can only be +done after installing libreboot, because the original firmware has a +whitelist of approved chips, and it will refuse to boot if you use an +\'unauthorized\' wifi card. + +The following photos show an Atheros AR5B95 being installed, to replace +the Intel chip that this T500 came with:\ +  + +</div> + +<div class="section"> + +WWAN +==== + +If you have a WWAN/3G card and/or sim card reader, remove them +permanently. The WWAN-3G card has DMA, and proprietary firmware inside; +the technology is identical to what is used in mobile phones, so it can +also track your movements. + +Not to be confused with wifi (wifi is fine). + +</div> + +<div class="section photos"> + +Memory +====== + +You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs +(speed/size). Non-matching pairs won\'t work. You can also install a +single module (meaning, one of the slots will be empty) in slot 0. + +Make sure that the RAM you buy is the 2Rx8 density. + +[This page](http://www.forum.thinkpads.com/viewtopic.php?p=760721) might +be useful for RAM compatibility info (note: coreboot raminit is +different, so this page might be BS) + +The following photo shows 8GiB (2x4GiB) of RAM installed:\ + + +</div> + +<div class="section photos"> + +Boot it! +-------- + +You should see something like this: + + + +Now [install GNU+Linux](../gnulinux/). + +</div> + +<div class="section"> + +Copyright © 2015 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/t60_unbrick.html b/docs/install/t60_unbrick.html deleted file mode 100644 index 40cb3a1e..00000000 --- a/docs/install/t60_unbrick.html +++ /dev/null @@ -1,322 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad T60: Recovery guide</title> -</head> - -<body> - - <div class="section"> - <h1>ThinkPad T60: Recovery guide</h1> - <p>This section documents how to recover from a bad flash that prevents your ThinkPad T60 from booting.</p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - <h2>Table of Contents</h2> - <ul> - <li> - Types of brick: - <ul> - <li><a href="#bucts_brick">Brick type 1: bucts not reset</a></li> - <li><a href="#recovery">Brick type 2: bad rom (or user error), system won't boot</a></li> - </ul> - </li> - </ul> - </div> - - <div class="section"> - <h1 id="bucts_brick">Brick type 1: bucts not reset.</h1> - <p> - You still have Lenovo BIOS, or you had libreboot running and you flashed another ROM; and you had bucts 1 set and - the ROM wasn't dd'd.* or if Lenovo BIOS was present and libreboot wasn't flashed.<br/><br/> - - In this case, unbricking is easy: reset BUC.TS to 0 by removing that yellow cmos coin (it's a battery) and putting it back after a minute or two:<br/> - <img src="../images/t60_dev/0006.JPG" alt="" /><br/><br/> - - *Those dd commands should be applied to all newly compiled T60 ROM images (the ROM images in libreboot binary archives already have this applied!):<br/> - dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k<br/> - dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump<br/> - dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc<br/> - (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, - using those instructions: <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>. - (it says x60, but instructions for t60 are identical) - </p> - </div> - - <div class="section"> - - <h1 id="recovery">bad rom (or user error), system won't boot</h1> - - <p> - In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your system from - booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your system is bricked and will not boot at all. - </p> - <p> - "Unbricking" means flashing a known-good (working) ROM. The problem: you can't boot the system, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides). - </p> - - <p> - Remove those screws and remove the HDD:<br/> - <img src="../images/t60_dev/0001.JPG" alt="" /> <img src="../images/t60_dev/0002.JPG" alt="" /> - </p> - - <p> - Lift off the palm rest:<br/> - <img src="../images/t60_dev/0003.JPG" alt="" /> - </p> - - <p> - Lift up the keyboard, pull it back a bit, flip it over like that and then disconnect it from the board:<br/> - <img src="../images/t60_dev/0004.JPG" alt="" /> <img src="../images/t60_dev/0005.JPG" alt="" /> <img src="../images/t60_dev/0006.JPG" alt="" /> - </p> - - <p> - Gently wedge both sides loose:<br/> - <img src="../images/t60_dev/0007.JPG" alt="" /> <img src="../images/t60_dev/0008.JPG" alt="" /> - </p> - - <p> - Remove that cable from the position:<br/> - <img src="../images/t60_dev/0009.JPG" alt="" /> <img src="../images/t60_dev/0010.JPG" alt="" /> - </p> - - <p> - Now remove that bezel. Remove wifi, nvram battery and speaker connector (also remove 56k modem, on the left of wifi):<br/> - <img src="../images/t60_dev/0011.JPG" alt="" /> - </p> - - <p> - Remove those screws:<br/> - <img src="../images/t60_dev/0012.JPG" alt="" /> - </p> - - <p> - Disconnect the power jack:<br/> - <img src="../images/t60_dev/0013.JPG" alt="" /> - </p> - - <p> - Remove nvram battery:<br/> - <img src="../images/t60_dev/0014.JPG" alt="" /> - </p> - - <p> - Disconnect cable (for 56k modem) and disconnect the other cable:<br/> - <img src="../images/t60_dev/0015.JPG" alt="" /> <img src="../images/t60_dev/0016.JPG" alt="" /> - </p> - - <p> - Disconnect speaker cable:<br/> - <img src="../images/t60_dev/0017.JPG" alt="" /> - </p> - - <p> - Disconnect the other end of the 56k modem cable:<br/> - <img src="../images/t60_dev/0018.JPG" alt="" /> - </p> - - <p> - Make sure you removed it:<br/> - <img src="../images/t60_dev/0019.JPG" alt="" /> - </p> - - <p> - Unscrew those:<br/> - <img src="../images/t60_dev/0020.JPG" alt="" /> - </p> - - <p> - Make sure you removed those:<br/> - <img src="../images/t60_dev/0021.JPG" alt="" /> - </p> - - <p> - Disconnect LCD cable from board:<br/> - <img src="../images/t60_dev/0022.JPG" alt="" /> - </p> - - <p> - Remove those screws then remove the LCD assembly:<br/> - <img src="../images/t60_dev/0023.JPG" alt="" /> <img src="../images/t60_dev/0024.JPG" alt="" /> <img src="../images/t60_dev/0025.JPG" alt="" /> - </p> - - <p> - Once again, make sure you removed those:<br/> - <img src="../images/t60_dev/0026.JPG" alt="" /> - </p> - - <p> - Remove the shielding containing the motherboard, then flip it over. Remove these screws, placing them on a steady - surface in the same layout as they were in before you removed them. Also, you should mark each screw hole after removing the - screw (a permanent marker pen will do), this is so that you have a point of reference when re-assembling the system:<br/> - <img src="../images/t60_dev/0027.JPG" alt="" /> <img src="../images/t60_dev/0028.JPG" alt="" /> <img src="../images/t60_dev/0029.JPG" alt="" /> - <img src="../images/t60_dev/0031.JPG" alt="" /> <img src="../images/t60_dev/0032.JPG" alt="" /> <img src="../images/t60_dev/0033.JPG" alt="" /> - </p> - - <p> - Now wire up the BBB and the Pomona with your PSU.<br/> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to setup - the BBB for flashing.<br/> - <b>Note, the guide mentions a 3.3v DC PSU but you don't need this on the T60: - if you don't have or don't want to use an external PSU, then make - sure not to connect the 3.3v leads mentioned in the guide; - instead, connect the AC adapter (the one that normally charges your - battery) so that the board has power (but don't boot it up)</b><br/> - <img src="../images/t60_dev/0030.JPG" alt="" /><br/> - Correlate the following with the BBB guide linked above: - </p> -<pre> -POMONA 5250: -=== DVD drive ==== - 18 - - 1 - 22 - - NC ---- RAM is on this end - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== audio jacks === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> -</pre> - - <p> - Connect the pomona from the BBB to the flash chip. No pics unfortunately. (use the text diagram above). - </p> - - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - - <p> - SSH'd into the BBB:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom</b> - </p> - <p> - It should be <b>Verifying flash... VERIFIED</b> at the end. If flashrom complains about multiple flash chip - definitions detected, then choose one of them following the instructions in the output. - </p> - - <p> - Put those screws back:<br/> - <img src="../images/t60_dev/0047.JPG" alt="" /> - </p> - - <p> - Put it back into lower chassis:<br/> - <img src="../images/t60_dev/0048.JPG" alt="" /> - </p> - - <p> - Attach LCD and insert screws (also, attach the lcd cable to the board):<br/> - <img src="../images/t60_dev/0049.JPG" alt="" /> - </p> - - <p> - Insert those screws:<br/> - <img src="../images/t60_dev/0050.JPG" alt="" /> - </p> - - <p> - On the CPU (and there is another chip south-east to it, sorry forgot to take pic) - clean off the old thermal paste (with the alcohol) and apply new (Artic Silver 5 is good, others are good too) - you should also clean the heatsink the same way<br/> - <img src="../images/t60_dev/0051.JPG" alt="" /> - </p> - - <p> - Attach the heatsink and install the screws (also, make sure to install the AC jack as highlighted):<br/> - <img src="../images/t60_dev/0052.JPG" alt="" /> - </p> - - <p> - Reinstall that upper bezel:<br/> - <img src="../images/t60_dev/0053.JPG" alt="" /> - </p> - - <p> - Do that:<br/> - <img src="../images/t60_dev/0054.JPG" alt="" /> <img src="../images/t60_dev/0055.JPG" alt="" /> - </p> - - <p> - Re-attach modem, wifi, (wwan?), and all necessary cables. Sorry, forgot to take pics. Look at previous removal steps to see where they go back to. - </p> - - <p> - Attach keyboard and install nvram battery:<br/> - <img src="../images/t60_dev/0056.JPG" alt="" /> <img src="../images/t60_dev/0057.JPG" alt="" /> - </p> - - <p> - Place keyboard and (sorry, forgot to take pics) reinstall the palmrest and insert screws on the underside:<br/> - <img src="../images/t60_dev/0058.JPG" alt="" /> - </p> - - <p> - It lives!<br/> - <img src="../images/t60_dev/0071.JPG" alt="" /> <img src="../images/t60_dev/0072.JPG" alt="" /> <img src="../images/t60_dev/0073.JPG" alt="" /> - </p> - - <p> - Always stress test ('stress -c 2' and xsensors. below 90C is ok) when replacing cpu paste/heatsink:<br/> - <img src="../images/t60_dev/0074.JPG" alt="" /> - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/t60_unbrick.md b/docs/install/t60_unbrick.md new file mode 100644 index 00000000..c86fd294 --- /dev/null +++ b/docs/install/t60_unbrick.md @@ -0,0 +1,259 @@ +<div class="section"> + +ThinkPad T60: Recovery guide +============================ + +This section documents how to recover from a bad flash that prevents +your ThinkPad T60 from booting. + +[Back to previous index](./) + +</div> + +<div class="section"> + +Table of Contents +----------------- + +- Types of brick: + - [Brick type 1: bucts not reset](#bucts_brick) + - [Brick type 2: bad rom (or user error), system won\'t + boot](#recovery) + +</div> + +<div class="section"> + +Brick type 1: bucts not reset. {#bucts_brick} +============================== + +You still have Lenovo BIOS, or you had libreboot running and you flashed +another ROM; and you had bucts 1 set and the ROM wasn\'t dd\'d.\* or if +Lenovo BIOS was present and libreboot wasn\'t flashed.\ +\ +In this case, unbricking is easy: reset BUC.TS to 0 by removing that +yellow cmos coin (it\'s a battery) and putting it back after a minute or +two:\ +\ +\ +\*Those dd commands should be applied to all newly compiled T60 ROM +images (the ROM images in libreboot binary archives already have this +applied!):\ +dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s +coreboot.rom) - 0x10000\] count=64k\ +dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] +count=64k | hexdump\ +dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s +coreboot.rom) - 0x20000\] count=64k conv=notrunc\ +(doing this makes the ROM suitable for use when flashing a system that +still has Lenovo BIOS running, using those instructions: +<http://www.coreboot.org/Board:lenovo/x60/Installation>. (it says x60, +but instructions for t60 are identical) + +</div> + +<div class="section"> + +bad rom (or user error), system won\'t boot {#recovery} +=========================================== + +In this scenario, you compiled a ROM that had an incorrect +configuration, or there is an actual bug preventing your system from +booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash +while Lenovo BIOS was running. In any case, your system is bricked and +will not boot at all. + +\"Unbricking\" means flashing a known-good (working) ROM. The problem: +you can\'t boot the system, making this difficult. In this situation, +external hardware (see hardware requirements above) is needed which can +flash the SPI chip (where libreboot resides). + +Remove those screws and remove the HDD:\ +  + +Lift off the palm rest:\ + + +Lift up the keyboard, pull it back a bit, flip it over like that and +then disconnect it from the board:\ +  + + +Gently wedge both sides loose:\ +  + +Remove that cable from the position:\ +  + +Now remove that bezel. Remove wifi, nvram battery and speaker connector +(also remove 56k modem, on the left of wifi):\ + + +Remove those screws:\ + + +Disconnect the power jack:\ + + +Remove nvram battery:\ + + +Disconnect cable (for 56k modem) and disconnect the other cable:\ +  + +Disconnect speaker cable:\ + + +Disconnect the other end of the 56k modem cable:\ + + +Make sure you removed it:\ + + +Unscrew those:\ + + +Make sure you removed those:\ + + +Disconnect LCD cable from board:\ + + +Remove those screws then remove the LCD assembly:\ +  + + +Once again, make sure you removed those:\ + + +Remove the shielding containing the motherboard, then flip it over. +Remove these screws, placing them on a steady surface in the same layout +as they were in before you removed them. Also, you should mark each +screw hole after removing the screw (a permanent marker pen will do), +this is so that you have a point of reference when re-assembling the +system:\ +  +  +  + +Now wire up the BBB and the Pomona with your PSU.\ +Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for +flashing.\ +**Note, the guide mentions a 3.3v DC PSU but you don\'t need this on the +T60: if you don\'t have or don\'t want to use an external PSU, then make +sure not to connect the 3.3v leads mentioned in the guide; instead, +connect the AC adapter (the one that normally charges your battery) so +that the board has power (but don\'t boot it up)**\ +\ +Correlate the following with the BBB guide linked above: + + POMONA 5250: + === DVD drive ==== + 18 - - 1 + 22 - - NC ---- RAM is on this end + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + === audio jacks === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +Connect the pomona from the BBB to the flash chip. No pics +unfortunately. (use the text diagram above). + +Flashrom binaries for ARM (tested on a BBB) are distributed in +libreboot\_util. Alternatively, libreboot also distributes flashrom +source code which can be built. + +SSH\'d into the BBB:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +yourrom.rom** + +It should be **Verifying flash\... VERIFIED** at the end. If flashrom +complains about multiple flash chip definitions detected, then choose +one of them following the instructions in the output. + +Put those screws back:\ + + +Put it back into lower chassis:\ + + +Attach LCD and insert screws (also, attach the lcd cable to the board):\ + + +Insert those screws:\ + + +On the CPU (and there is another chip south-east to it, sorry forgot to +take pic) clean off the old thermal paste (with the alcohol) and apply +new (Artic Silver 5 is good, others are good too) you should also clean +the heatsink the same way\ + + +Attach the heatsink and install the screws (also, make sure to install +the AC jack as highlighted):\ + + +Reinstall that upper bezel:\ + + +Do that:\ +  + +Re-attach modem, wifi, (wwan?), and all necessary cables. Sorry, forgot +to take pics. Look at previous removal steps to see where they go back +to. + +Attach keyboard and install nvram battery:\ +  + +Place keyboard and (sorry, forgot to take pics) reinstall the palmrest +and insert screws on the underside:\ + + +It lives!\ +  + + +Always stress test (\'stress -c 2\' and xsensors. below 90C is ok) when +replacing cpu paste/heatsink:\ + + +</div> + +<div class="section"> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/x200_external.html b/docs/install/x200_external.html deleted file mode 100644 index 0d820355..00000000 --- a/docs/install/x200_external.html +++ /dev/null @@ -1,477 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad X200: flashing tutorial (BeagleBone Black)</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Flashing the X200 with a BeagleBone Black</h1> - <p>Initial flashing instructions for X200.</p> - <p> - This guide is for those who want libreboot on their ThinkPad X200 - while they still have the original Lenovo BIOS present. This guide - can also be followed (adapted) if you brick your X200, to know how - to recover. - </p> - - <ul> - <li><a href="#preinstall">X200 laptops with libreboot pre-installed</a></li> - <li><a href="#flashchips">Flash chips</a></li> - <li><a href="#macaddress">MAC address</a></li> - <li><a href="#clip">Initial BBB configuration and installation procedure</a></li> - <li><a href="#boot">Boot it!</a></li> - <li><a href="#wifi">Wifi</a></li> - <li><a href="#wwan">wwan</a></li> - <li><a href="#memory">Memory</a></li> - <li><a href="#gpio33">X200S and X200 Tablet users: GPIO33 trick will not work.</a></li> - </ul> - - <p><a href="./">Back to main index</a></p> - </div> - - <div class="section"> - - <h1 id="preinstall">X200 laptops with libreboot pre-installed</h1> - - <p> - If you don't want to install libreboot yourself, companies exist that sell these laptops - with libreboot pre-installed, along with a free GNU+Linux distribution. - </p> - <p> - Check the <a href="../../suppliers">suppliers</a> page for more information. - </p> - - </div> - - <div class="section"> - - <h1 id="flashchips">Flash chip size</h1> - - <p> - Use this to find out:<br/> - # <b>flashrom -p internal -V</b> - </p> - - <p> - The X200S and X200 Tablet will use a WSON-8 flash chip, on the - bottom of the motherboard (this requires removal of the - motherboard). <b>Not all X200S/X200T are supported; - see <a href="../hcl/x200.html#x200s">../hcl/x200.html#x200s</a>.</b> - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="macaddress">MAC address</h1> - - <p> - On the X200/X200S/X200T, the MAC address for the onboard - gigabit ethernet chipset is stored inside the flash chip, - along with other configuration data. - </p> - <p> - Keep a note of the MAC address before disassembly; this is - very important, because you will need to insert this into - the libreboot ROM image before flashing it. - It will be written in one of these locations: - </p> - - <p> - <img src="images/x200/disassembly/0002.jpg" alt="" /> - <img src="images/x200/disassembly/0001.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <h1 id="clip">Initial BBB configuration</h1> - - <p> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to - set up the BBB for flashing. - </p> - - <p> - The following shows how to connect the clip to the BBB (on the P9 header), for SOIC-16 (clip: Pomona 5252): - </p> -<pre> -POMONA 5252 (correlate with the BBB guide) -=== front (display) on your X200 ==== - NC - - 21 - 1 - - 17 - NC - - NC - NC - - NC - NC - - NC - NC - - NC - 18 - - 3.3V (PSU) - 22 - - NC - this is pin 1 on the flash chip -=== back (palmrest) on your X200 === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> -Here is a photo of the SOIC-16 flash chip. Pins are labelled:<br/> -<img src="images/x200/x200_pomona.jpg" alt="" /> -</pre> - <p> - The following shows how to connect the clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): - </p> -<pre> -POMONA 5250 (correlate with the BBB guide) -=== left side of the X200 (where the VGA port is) ==== - 18 - - 1 - 22 - - NC - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip. in front of it is the screen. -=== right side of the X200 (where the audio jacks are) === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> -Here is a photo of the SOIC-8 flash chip. The pins are labelled:<br/> -<img title="Copyright 2015 Patrick "P. J." McDermott <pj@pehjota.net>, see license notice at the end of this document" src="images/x200/soic8.jpg" /> - -Look at the pads in that photo, on the left and right. Those are for SOIC-16. Would it be possible to remove the SOIC-8 and solder a SOIC-16 -chip on those pins? -</pre> - <p> - <b>On the X200S and X200 Tablet the flash chip is underneath the board, in a WSON package. - The pinout is very much the same as a SOIC-8, except you need to solder (there are no clips available).<br/> - The following image shows how this is done:</b><br/> - <img src="images/x200/wson_soldered.jpg" title="Copyright 2014 Steve Shenton <sgsit@libreboot.org> see license notice at the end of this document" alt="" /> - <br/> - In this image, a pin header was soldered onto the WSON. Another solution might be to de-solder the WSON-8 chip and put a SOIC-8 there instead. - Check the list of SOIC-8 flash chips at <a href="../hcl/gm45_remove_me.html#flashchips">../hcl/gm45_remove_me.html#flashchips</a> but - do note that these are only 4MiB (32Mb) chips. The only X200 SPI chips with 8MiB capacity are SOIC-16. For 8MiB capacity in this case, - the X201 SOIC-8 flash chip (Macronix 25L6445E) might work. - </p> - - <h2> - The procedure - </h2> - <p> - This section is for the X200. This does not apply to the X200S or X200 Tablet - (for those systems, you have to remove the motherboard completely, since - the flash chip is on the other side of the board). - </p> - <p> - Remove these screws:<br/> - <img src="images/x200/disassembly/0003.jpg" alt="" /> - </p> - <p> - Push the keyboard forward, gently, then lift it off and - disconnect it from the board:<br/> - <img src="images/x200/disassembly/0004.jpg" alt="" /> - <img src="images/x200/disassembly/0005.jpg" alt="" /> - </p> - <p> - Pull the palm rest off, lifting from the left and right side at the back of the - palm rest:<br/> - <img src="images/x200/disassembly/0006.jpg" alt="" /> - </p> - <p> - Lift back the tape that covers a part of the flash chip, and - then connect the clip:<br/> - <img src="images/x200/disassembly/0007.jpg" alt="" /> - <img src="images/x200/disassembly/0008.jpg" alt="" /> - </p> - <p> - On pin 2 of the BBB, where you have the ground (GND), connect the - ground to your PSU:<br/> - <img src="images/x200/disassembly/0009.jpg" alt="" /> - <img src="images/x200/disassembly/0010.jpg" alt="" /> - </p> - <p> - Connect the 3.3V supply from your PSU to the flash chip (via - the clip):<br/> - <img src="images/x200/disassembly/0011.jpg" alt="" /> - <img src="images/x200/disassembly/0012.jpg" alt="" /> - </p> - <p> - Of course, make sure that your PSU is also plugged in and - turn on:<br/> - <img src="images/x200/disassembly/0013.jpg" alt="" /> - </p> - <p> - This tutorial tells you to use an ATX PSU, for the 3.3V DC - supply. The PSU used when taking these photos is actually - not an ATX PSU, but a PSU that is designed specifically - for providing 3.3V DC (an ATX PSU will also work):<br/> - <img src="images/x200/disassembly/0014.jpg" alt="" /> - </p> - <p> - Now, you should be ready to install libreboot. - </p> - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - <p> - Log in as root on your BBB, using the instructions in - <a href="bbb_setup.html#bbb_access">bbb_setup.html#bbb_access</a>. - </p> - - <p> - Test that flashrom works:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512</b><br/> - In this case, the output was: - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. -Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. -Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" -Please specify which chip definition to use with the -c <chipname> option. -</pre> - <p> - How to backup factory.rom (change the -c option as neeed, for your flash chip):<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom</b><br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom</b><br/> - Note: the <b>-c</b> option is not required in libreboot's patched flashrom, because - the redundant flash chip definitions in <i>flashchips.c</i> have been removed.<br/> - Now compare the 3 images:<br/> - # <b>sha512sum factory*.rom</b><br/> - If the hashes match, 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 and libreboot. - </p> - <p> - Follow the instructions at <a href="../hcl/gm45_remove_me.html#ich9gen">../hcl/gm45_remove_me.html#ich9gen</a> - to change the MAC address inside the libreboot ROM image, before flashing it. - Although there is a default MAC address inside the ROM image, this is not what you want. <b>Make sure - to always change the MAC address to one that is correct for your system.</b> - </p> - <p> - Now flash it:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V</b> - </p> - <p> - <img src="images/x200/disassembly/0015.jpg" alt="" /> - </p> - <p> - You might see errors, but if it says <b>Verifying flash... VERIFIED</b> at the end, then it's flashed and should boot. - If you see errors, try again (and again, and again); the message <b>Chip content is identical to the requested image</b> - is also an indication of a successful installation. - </p> - <p> - Example output from running the command (see above): - </p> -<pre> -flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) -flashrom is free software, get the source code at http://www.flashrom.org -Calibrating delay loop... OK. -Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. -Reading old flash chip contents... done. -Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 -ERASE FAILED! -Reading current flash chip contents... done. Looking for another erase function. -Erase/write done. -Verifying flash... VERIFIED. -</pre> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section"> - - <h1 id="wifi">Wifi</h1> - - <p> - The X200 typically comes with an Intel wifi chipset, which does not - work without proprietary software. For a list of wifi chipsets that - work without proprietary software, see - <a href="../hcl/#recommended_wifi">../hcl/#recommended_wifi</a>. - </p> - - <p> - Some X200 laptops come with an Atheros chipset, but this is 802.11g only. - </p> - - <p> - It is recommended that you install a new wifi chipset. This can only - be done after installing libreboot, because the original firmware has - a whitelist of approved chips, and it will refuse to boot if you - use an 'unauthorized' wifi card. - </p> - - <p> - The following photos show an Atheros AR5B95 being installed, to - replace the Intel chip that this X200 came with:<br/> - <img src="images/x200/disassembly/0016.jpg" alt="" /> - <img src="images/x200/disassembly/0017.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <h1 id="wwan">WWAN</h1> - <p> - If you have a WWAN/3G card and/or sim card reader, remove them permanently. - The WWAN-3G card has proprietary firmware inside; the technology is - identical to what is used in mobile phones, so it can also track your movements. - </p> - <p> - Not to be confused with wifi (wifi is fine). - </p> - - </div> - - <div class="section"> - - <h1 id="memory">Memory</h1> - - <p> - You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs - (speed/size). Non-matching pairs won't work. You can also install a - single module (meaning, one of the slots will be empty) in slot 0. - </p> - <p> - NOTE: according to users repors, non matching pairs (e.g. 1+2 GiB) might work in some cases. - </p> - <p> - Make sure that the RAM you buy is the 2Rx8 density. - </p> - - <p> - In this photo, 8GiB of RAM (2x4GiB) is installed:<br/> - <img src="images/x200/disassembly/0018.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <h2 id="boot"> - Boot it! - </h2> - <p> - You should see something like this: - </p> - <p> - <img src="images/x200/disassembly/0019.jpg" alt="" /> - </p> - - <p> - Now <a href="../gnulinux/">install GNU+Linux</a>. - </p> - - </div> - - <div class="section"> - <h2 id="gpio33"> - X200S and X200 Tablet users: GPIO33 trick will not work. - </h2> - <p> - sgsit found out about a pin called GPIO33, which can be grounded to disable the flashing protections - by the descriptor and stop the ME from starting (which itself interferes with flashing attempts). - The theory was proven correct; however, it is still useless in practise. - </p> - <p> - Look just above the 7 in TP37 (that's GPIO33):<br/> - <img src="../hcl/images/x200/gpio33_location.jpg" alt="" /> - </p> - <p> - By default we would see this in lenovobios, when trying flashrom -p internal -w rom.rom: - </p> -<pre> -FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only. -FREG2: Warning: Management Engine region (0x00001000-0x005f5fff) is locked. -</pre> - <p> - With GPIO33 grounded during boot, this disabled the flash protections as set - by descriptor, and stopped the ME from starting. The output changed to: - </p> -<pre> -The Flash Descriptor Override Strap-Pin is set. Restrictions implied by -the Master Section of the flash descriptor are NOT in effect. Please note -that <b>Protected Range (PR) restrictions still apply.</b> -</pre> - <p> - The part in bold is what got us. This was still observed: - </p> -<pre> -PR0: Warning: 0x007e0000-0x01ffffff is read-only. -PR4: Warning: 0x005f8000-0x005fffff is locked. -</pre> - - <p> - It is actually possible to disable these protections. Lenovobios does, - when updating the BIOS (proprietary one). One possible way to go about this - would be to debug the BIOS update utility from Lenovo, to find out - how it's disabling these protections. Some more research is available here: - <a href="http://www.coreboot.org/Board:lenovo/x200/internal_flashing_research">http://www.coreboot.org/Board:lenovo/x200/internal_flashing_research</a> - </p> - - <p> - On a related note, libreboot has a utility that could help with investigating this: - <a href="../hcl/gm45_remove_me.html#demefactory">../hcl/gm45_remove_me.html#demefactory</a> - </p> - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/x200_external.md b/docs/install/x200_external.md new file mode 100644 index 00000000..fe936c1f --- /dev/null +++ b/docs/install/x200_external.md @@ -0,0 +1,403 @@ +<div class="section"> + +Flashing the X200 with a BeagleBone Black {#pagetop} +========================================= + +Initial flashing instructions for X200. + +This guide is for those who want libreboot on their ThinkPad X200 while +they still have the original Lenovo BIOS present. This guide can also be +followed (adapted) if you brick your X200, to know how to recover. + +- [X200 laptops with libreboot pre-installed](#preinstall) +- [Flash chips](#flashchips) +- [MAC address](#macaddress) +- [Initial BBB configuration and installation procedure](#clip) +- [Boot it!](#boot) +- [Wifi](#wifi) +- [wwan](#wwan) +- [Memory](#memory) +- [X200S and X200 Tablet users: GPIO33 trick will not work.](#gpio33) + +[Back to main index](./) + +</div> + +<div class="section"> + +X200 laptops with libreboot pre-installed {#preinstall} +========================================= + +If you don\'t want to install libreboot yourself, companies exist that +sell these laptops with libreboot pre-installed, along with a free +GNU+Linux distribution. + +Check the [suppliers](../../suppliers) page for more information. + +</div> + +<div class="section"> + +Flash chip size {#flashchips} +=============== + +Use this to find out:\ +\# **flashrom -p internal -V** + +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 supported; see +[../hcl/x200.html\#x200s](../hcl/x200.html#x200s).** + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +MAC address {#macaddress} +=========== + +On the X200/X200S/X200T, the MAC address for the onboard gigabit +ethernet chipset is stored inside the flash chip, along with other +configuration data. + +Keep a note of the MAC address before disassembly; this is very +important, because you will need to insert this into the libreboot ROM +image before flashing it. It will be written in one of these locations: + + + + +</div> + +<div class="section"> + +Initial BBB configuration {#clip} +========================= + +Refer to [bbb\_setup.html](bbb_setup.html) for how to set up the BBB for +flashing. + +The following shows how to connect the clip to the BBB (on the P9 +header), for SOIC-16 (clip: Pomona 5252): + + POMONA 5252 (correlate with the BBB guide) + === front (display) on your X200 ==== + NC - - 21 + 1 - - 17 + NC - - NC + NC - - NC + NC - - NC + NC - - NC + 18 - - 3.3V (PSU) + 22 - - NC - this is pin 1 on the flash chip + === back (palmrest) on your X200 === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + Here is a photo of the SOIC-16 flash chip. Pins are labelled: + + + +The following shows how to connect the clip to the BBB (on the P9 +header), for SOIC-8 (clip: Pomona 5250): + + POMONA 5250 (correlate with the BBB guide) + === left side of the X200 (where the VGA port is) ==== + 18 - - 1 + 22 - - NC + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip. in front of it is the screen. + === right side of the X200 (where the audio jacks are) === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + Here is a photo of the SOIC-8 flash chip. The pins are labelled: + + + + Look at the pads in that photo, on the left and right. Those are for SOIC-16. Would it be possible to remove the SOIC-8 and solder a SOIC-16 + chip on those pins? + +**On the X200S and X200 Tablet the flash chip is underneath the board, +in a WSON package. The pinout is very much the same as a SOIC-8, except +you need to solder (there are no clips available).\ +The following image shows how this is done:**\ +\ +In this image, a pin header was soldered onto the WSON. Another solution +might be to de-solder the WSON-8 chip and put a SOIC-8 there instead. +Check the list of SOIC-8 flash chips at +[../hcl/gm45\_remove\_me.html\#flashchips](../hcl/gm45_remove_me.html#flashchips) +but do note that these are only 4MiB (32Mb) chips. The only X200 SPI +chips with 8MiB capacity are SOIC-16. For 8MiB capacity in this case, +the X201 SOIC-8 flash chip (Macronix 25L6445E) might work. + +The procedure +------------- + +This section is for the X200. This does not apply to the X200S or X200 +Tablet (for those systems, you have to remove the motherboard +completely, since the flash chip is on the other side of the board). + +Remove these screws:\ + + +Push the keyboard forward, gently, then lift it off and disconnect it +from the board:\ + + + +Pull the palm rest off, lifting from the left and right side at the back +of the palm rest:\ + + +Lift back the tape that covers a part of the flash chip, and then +connect the clip:\ + + + +On pin 2 of the BBB, where you have the ground (GND), connect the ground +to your PSU:\ + + + +Connect the 3.3V supply from your PSU to the flash chip (via the clip):\ + + + +Of course, make sure that your PSU is also plugged in and turn on:\ + + +This tutorial tells you to use an ATX PSU, for the 3.3V DC supply. The +PSU used when taking these photos is actually not an ATX PSU, but a PSU +that is designed specifically for providing 3.3V DC (an ATX PSU will +also work):\ + + +Now, you should be ready to install libreboot. + +Flashrom binaries for ARM (tested on a BBB) are distributed in +libreboot\_util. Alternatively, libreboot also distributes flashrom +source code which can be built. + +Log in as root on your BBB, using the instructions in +[bbb\_setup.html\#bbb\_access](bbb_setup.html#bbb_access). + +Test that flashrom works:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512**\ +In this case, the output was: + + flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6406E/MX25L6436E" (8192 kB, SPI) on linux_spi. + Found Macronix flash chip "MX25L6445E/MX25L6473E" (8192 kB, SPI) on linux_spi. + Multiple flash chip definitions match the detected chip(s): "MX25L6405(D)", "MX25L6406E/MX25L6436E", "MX25L6445E/MX25L6473E" + Please specify which chip definition to use with the -c <chipname> option. + +How to backup factory.rom (change the -c option as neeed, for your flash +chip):\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory1.rom**\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -r +factory2.rom**\ +Note: the **-c** option is not required in libreboot\'s patched +flashrom, because the redundant flash chip definitions in *flashchips.c* +have been removed.\ +Now compare the 3 images:\ +\# **sha512sum factory\*.rom**\ +If the hashes match, 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 +and libreboot. + +Follow the instructions at +[../hcl/gm45\_remove\_me.html\#ich9gen](../hcl/gm45_remove_me.html#ich9gen) +to change the MAC address inside the libreboot ROM image, before +flashing it. Although there is a default MAC address inside the ROM +image, this is not what you want. **Make sure to always change the MAC +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** + + + +You might see errors, but if it says **Verifying flash\... VERIFIED** at +the end, then it\'s flashed and should boot. If you see errors, try +again (and again, and again); the message **Chip content is identical to +the requested image** is also an indication of a successful +installation. + +Example output from running the command (see above): + + flashrom v0.9.7-r1854 on Linux 3.8.13-bone47 (armv7l) + flashrom is free software, get the source code at http://www.flashrom.org + Calibrating delay loop... OK. + Found Macronix flash chip "MX25L6405(D)" (8192 kB, SPI) on linux_spi. + Reading old flash chip contents... done. + Erasing and writing flash chip... FAILED at 0x00001000! Expected=0xff, Found=0x00, failed byte count from 0x00000000-0x0000ffff: 0xd716 + ERASE FAILED! + Reading current flash chip contents... done. Looking for another erase function. + Erase/write done. + Verifying flash... VERIFIED. + +[Back to top of page.](#pagetop) + +</div> + +<div class="section"> + +Wifi +==== + +The X200 typically comes with an Intel wifi chipset, which does not work +without proprietary software. For a list of wifi chipsets that work +without proprietary software, see +[../hcl/\#recommended\_wifi](../hcl/#recommended_wifi). + +Some X200 laptops come with an Atheros chipset, but this is 802.11g +only. + +It is recommended that you install a new wifi chipset. This can only be +done after installing libreboot, because the original firmware has a +whitelist of approved chips, and it will refuse to boot if you use an +\'unauthorized\' wifi card. + +The following photos show an Atheros AR5B95 being installed, to replace +the Intel chip that this X200 came with:\ + + + +</div> + +<div class="section"> + +WWAN +==== + +If you have a WWAN/3G card and/or sim card reader, remove them +permanently. The WWAN-3G card has proprietary firmware inside; the +technology is identical to what is used in mobile phones, so it can also +track your movements. + +Not to be confused with wifi (wifi is fine). + +</div> + +<div class="section"> + +Memory +====== + +You need DDR3 SODIMM PC3-8500 RAM installed, in matching pairs +(speed/size). Non-matching pairs won\'t work. You can also install a +single module (meaning, one of the slots will be empty) in slot 0. + +NOTE: according to users repors, non matching pairs (e.g. 1+2 GiB) might +work in some cases. + +Make sure that the RAM you buy is the 2Rx8 density. + +In this photo, 8GiB of RAM (2x4GiB) is installed:\ + + +</div> + +<div class="section"> + +Boot it! {#boot} +-------- + +You should see something like this: + + + +Now [install GNU+Linux](../gnulinux/). + +</div> + +<div class="section"> + +X200S and X200 Tablet users: GPIO33 trick will not work. {#gpio33} +-------------------------------------------------------- + +sgsit found out about a pin called GPIO33, which can be grounded to +disable the flashing protections by the descriptor and stop the ME from +starting (which itself interferes with flashing attempts). The theory +was proven correct; however, it is still useless in practise. + +Look just above the 7 in TP37 (that\'s GPIO33):\ + + +By default we would see this in lenovobios, when trying flashrom -p +internal -w rom.rom: + + FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only. + FREG2: Warning: Management Engine region (0x00001000-0x005f5fff) is locked. + +With GPIO33 grounded during boot, this disabled the flash protections as +set by descriptor, and stopped the ME from starting. The output changed +to: + + The Flash Descriptor Override Strap-Pin is set. Restrictions implied by + the Master Section of the flash descriptor are NOT in effect. Please note + that Protected Range (PR) restrictions still apply. + +The part in bold is what got us. This was still observed: + + PR0: Warning: 0x007e0000-0x01ffffff is read-only. + PR4: Warning: 0x005f8000-0x005fffff is locked. + +It is actually possible to disable these protections. Lenovobios does, +when updating the BIOS (proprietary one). One possible way to go about +this would be to debug the BIOS update utility from Lenovo, to find out +how it\'s disabling these protections. Some more research is available +here: +<http://www.coreboot.org/Board:lenovo/x200/internal_flashing_research> + +On a related note, libreboot has a utility that could help with +investigating this: +[../hcl/gm45\_remove\_me.html\#demefactory](../hcl/gm45_remove_me.html#demefactory) + +</div> + +<div class="section"> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/x60_unbrick.html b/docs/install/x60_unbrick.html deleted file mode 100644 index 07c048b6..00000000 --- a/docs/install/x60_unbrick.html +++ /dev/null @@ -1,314 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad X60: Recovery guide</title> -</head> - -<body> - - <div class="section"> - <h1>ThinkPad X60: Recovery guide</h1> - <p>This section documents how to recover from a bad flash that prevents your ThinkPad X60 from booting.</p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - <h1>Table of Contents</h1> - <ul> - <li> - Types of brick: - <ul> - <li><a href="#bucts_brick">Brick type 1: bucts not reset</a></li> - <li><a href="#recovery">Brick type 2: bad rom (or user error), system won't boot</a></li> - </ul> - </li> - </ul> - </div> - - <div class="section"> - <h1 id="bucts_brick">Brick type 1: bucts not reset.</h1> - <p> - You still have Lenovo BIOS, or you had libreboot running and you flashed another ROM; and you had bucts 1 set and - the ROM wasn't dd'd.* or if Lenovo BIOS was present and libreboot wasn't flashed.<br/><br/> - - In this case, unbricking is easy: reset BUC.TS to 0 by removing that yellow cmos coin (it's a battery) and putting it back after a minute or two:<br/> - <img src="../images/x60_unbrick/0004.jpg" alt="" /><br/><br/> - - *Those dd commands should be applied to all newly compiled X60 ROM images (the ROM images in libreboot binary archives already have this applied!):<br/> - dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k<br/> - dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump<br/> - dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc<br/> - (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, - using those instructions: <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>. - </p> - </div> - - <div class="section"> - - <h1 id="recovery">bad rom (or user error), system won't boot</h1> - <p> - In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your system from - booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your system is bricked and will not boot at all. - </p> - <p> - "Unbricking" means flashing a known-good (working) ROM. The problem: you can't boot the system, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides). - </p> - <p> - Remove those screws:<br/> - <img src="../images/x60_unbrick/0000.jpg" alt="" /> - </p> - <p> - Push the keyboard forward (carefully):<br/> - <img src="../images/x60_unbrick/0001.jpg" alt="" /> - </p> - <p> - Lift the keyboard up and disconnect it from the board:<br/> - <img src="../images/x60_unbrick/0002.jpg" alt="" /> - </p> - <p> - Grab the right-hand side of the chassis and force it off (gently) and pry up the rest of the chassis:<br/> - <img src="../images/x60_unbrick/0003.jpg" alt="" /> - </p> - <p> - You should now have this:<br/> - <img src="../images/x60_unbrick/0004.jpg" alt="" /> - </p> - <p> - Disconnect the wifi antenna cables, the modem cable and the speaker:<br/> - <img src="../images/x60_unbrick/0005.jpg" alt="" /> - </p> - <p> - Unroute the cables along their path, carefully lifting the tape that holds them in place. Then, disconnect the modem - cable (other end) and power connection and unroute all the cables so that they dangle by the monitor hinge on the right-hand - side:<br/> - <img src="../images/x60_unbrick/0006.jpg" alt="" /> - </p> - <p> - Disconnect the monitor from the motherboard, and unroute the grey antenna cable, carefully lifting the tape - that holds it into place:<br/> - <img src="../images/x60_unbrick/0008.jpg" alt="" /> - </p> - <p> - Carefully lift the remaining tape and unroute the left antenna cable so that it is loose:<br/> - <img src="../images/x60_unbrick/0009.jpg" alt="" /> - </p> - <p> - Remove the screw that is highlighted (do NOT remove the other one; it holds part of the heatsink (other side) into place):<br/> - <img src="../images/x60_unbrick/0011.jpg" alt="" /> - </p> - <p> - Remove those screws:<br/> - <img src="../images/x60_unbrick/0012.jpg" alt="" /> - </p> - <p> - Carefully remove the plate, like so:<br/> - <img src="../images/x60_unbrick/0013.jpg" alt="" /> - </p> - <p> - Remove the SATA connector:<br/> - <img src="../images/x60_unbrick/0014.jpg" alt="" /> - </p> - <p> - Now remove the motherboard (gently) and cast the lcd/chassis aside:<br/> - <img src="../images/x60_unbrick/0015.jpg" alt="" /> - </p> - <p> - Lift back that tape and hold it with something. Highlighted is the SPI flash chip:<br/> - <img src="../images/x60_unbrick/0016.jpg" alt="" /> - </p> - <p> - Now wire up the BBB and the Pomona with your PSU.<br/> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to setup - the BBB for flashing.<br/> - <b>Note, the guide mentions a 3.3v DC PSU but you don't need this on the X60: - if you don't have or don't want to use an external PSU, then make - sure not to connect the 3.3v leads mentioned in the guide; - instead, connect the AC adapter (the one that normally charges your - battery) so that the board has power (but don't boot it up)</b> - <img src="../images/x60_unbrick/0017.jpg" alt="" /><br/> - Correlate the following with the BBB guide linked above: - </p> -<pre> -POMONA 5250: -=== golden finger and wifi switch ==== - 18 - - 1 - 22 - - NC ---------- audio jacks are on this end - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== CPU fan === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> -</pre> - - <p> - Connecting the BBB and pomona (in this image, an external 3.3v DC PSU was used):<br/> - <img src="images/x60/th_bbb_flashing.jpg" alt="" /> - </p> - - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - - <p> - SSH'd into the BBB:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom</b> - </p> - <p> - It should be <b>Verifying flash... VERIFIED</b> at the end. If flashrom complains about multiple flash chip - definitions detected, then choose one of them following the instructions in the output. - </p> - - <p> - Remove the programmer and put it away somewhere. Put back the tape and press firmly over it:<br/> - <img src="../images/x60_unbrick/0026.jpg" alt="" /> - </p> - <p> - Your empty chassis:<br/> - <img src="../images/x60_unbrick/0027.jpg" alt="" /> - </p> - <p> - Put the motherboard back in:<br/> - <img src="../images/x60_unbrick/0028.jpg" alt="" /> - </p> - <p> - Reconnect SATA:<br/> - <img src="../images/x60_unbrick/0029.jpg" alt="" /> - </p> - <p> - Put the plate back and re-insert those screws:<br/> - <img src="../images/x60_unbrick/0030.jpg" alt="" /> - </p> - <p> - Re-route that antenna cable around the fan and apply the tape:<br/> - <img src="../images/x60_unbrick/0031.jpg" alt="" /> - </p> - <p> - Route the cable here and then (not shown, due to error on my part) reconnect the monitor cable to the motherboard - and re-insert the screws:<br/> - <img src="../images/x60_unbrick/0032.jpg" alt="" /> - </p> - <p> - Re-insert that screw:<br/> - <img src="../images/x60_unbrick/0033.jpg" alt="" /> - </p> - <p> - Route the black antenna cable like so:<br/> - <img src="../images/x60_unbrick/0034.jpg" alt="" /> - </p> - <p> - Tuck it in neatly like so:<br/> - <img src="../images/x60_unbrick/0035.jpg" alt="" /> - </p> - <p> - Route the modem cable like so:<br/> - <img src="../images/x60_unbrick/0036.jpg" alt="" /> - </p> - <p> - Connect modem cable to board and tuck it in neatly like so:<br/> - <img src="../images/x60_unbrick/0037.jpg" alt="" /> - </p> - <p> - Route the power connection and connect it to the board like so:<br/> - <img src="../images/x60_unbrick/0038.jpg" alt="" /> - </p> - <p> - Route the antenna and modem cables neatly like so:<br/> - <img src="../images/x60_unbrick/0039.jpg" alt="" /> - </p> - <p> - Connect the wifi antenna cables. At the start of the tutorial, this system had an Intel wifi chip. Here you see I've replaced it with an - Atheros AR5B95 (supports 802.11n and can be used without blobs):<br/> - <img src="../images/x60_unbrick/0040.jpg" alt="" /> - </p> - <p> - Connect the modem cable:<br/> - <img src="../images/x60_unbrick/0041.jpg" alt="" /> - </p> - <p> - Connect the speaker:<br/> - <img src="../images/x60_unbrick/0042.jpg" alt="" /> - </p> - <p> - You should now have this:<br/> - <img src="../images/x60_unbrick/0043.jpg" alt="" /> - </p> - <p> - Re-connect the upper chassis:<br/> - <img src="../images/x60_unbrick/0044.jpg" alt="" /> - </p> - <p> - Re-connect the keyboard:<br/> - <img src="../images/x60_unbrick/0045.jpg" alt="" /> - </p> - <p> - Re-insert the screws that you removed earlier:<br/> - <img src="../images/x60_unbrick/0046.jpg" alt="" /> - </p> - <p> - Power on!<br/> - <img src="../images/x60_unbrick/0047.jpg" alt="" /> - </p> - <p> - Operating system:<br/> - <img src="../images/x60_unbrick/0049.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/x60_unbrick.md b/docs/install/x60_unbrick.md new file mode 100644 index 00000000..a38f862b --- /dev/null +++ b/docs/install/x60_unbrick.md @@ -0,0 +1,271 @@ +<div class="section"> + +ThinkPad X60: Recovery guide +============================ + +This section documents how to recover from a bad flash that prevents +your ThinkPad X60 from booting. + +[Back to previous index](./) + +</div> + +<div class="section"> + +Table of Contents +================= + +- Types of brick: + - [Brick type 1: bucts not reset](#bucts_brick) + - [Brick type 2: bad rom (or user error), system won\'t + boot](#recovery) + +</div> + +<div class="section"> + +Brick type 1: bucts not reset. {#bucts_brick} +============================== + +You still have Lenovo BIOS, or you had libreboot running and you flashed +another ROM; and you had bucts 1 set and the ROM wasn\'t dd\'d.\* or if +Lenovo BIOS was present and libreboot wasn\'t flashed.\ +\ +In this case, unbricking is easy: reset BUC.TS to 0 by removing that +yellow cmos coin (it\'s a battery) and putting it back after a minute or +two:\ +\ +\ +\*Those dd commands should be applied to all newly compiled X60 ROM +images (the ROM images in libreboot binary archives already have this +applied!):\ +dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s +coreboot.rom) - 0x10000\] count=64k\ +dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] +count=64k | hexdump\ +dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s +coreboot.rom) - 0x20000\] count=64k conv=notrunc\ +(doing this makes the ROM suitable for use when flashing a system that +still has Lenovo BIOS running, using those instructions: +<http://www.coreboot.org/Board:lenovo/x60/Installation>. + +</div> + +<div class="section"> + +bad rom (or user error), system won\'t boot {#recovery} +=========================================== + +In this scenario, you compiled a ROM that had an incorrect +configuration, or there is an actual bug preventing your system from +booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash +while Lenovo BIOS was running. In any case, your system is bricked and +will not boot at all. + +\"Unbricking\" means flashing a known-good (working) ROM. The problem: +you can\'t boot the system, making this difficult. In this situation, +external hardware (see hardware requirements above) is needed which can +flash the SPI chip (where libreboot resides). + +Remove those screws:\ + + +Push the keyboard forward (carefully):\ + + +Lift the keyboard up and disconnect it from the board:\ + + +Grab the right-hand side of the chassis and force it off (gently) and +pry up the rest of the chassis:\ + + +You should now have this:\ + + +Disconnect the wifi antenna cables, the modem cable and the speaker:\ + + +Unroute the cables along their path, carefully lifting the tape that +holds them in place. Then, disconnect the modem cable (other end) and +power connection and unroute all the cables so that they dangle by the +monitor hinge on the right-hand side:\ + + +Disconnect the monitor from the motherboard, and unroute the grey +antenna cable, carefully lifting the tape that holds it into place:\ + + +Carefully lift the remaining tape and unroute the left antenna cable so +that it is loose:\ + + +Remove the screw that is highlighted (do NOT remove the other one; it +holds part of the heatsink (other side) into place):\ + + +Remove those screws:\ + + +Carefully remove the plate, like so:\ + + +Remove the SATA connector:\ + + +Now remove the motherboard (gently) and cast the lcd/chassis aside:\ + + +Lift back that tape and hold it with something. Highlighted is the SPI +flash chip:\ + + +Now wire up the BBB and the Pomona with your PSU.\ +Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for +flashing.\ +**Note, the guide mentions a 3.3v DC PSU but you don\'t need this on the +X60: if you don\'t have or don\'t want to use an external PSU, then make +sure not to connect the 3.3v leads mentioned in the guide; instead, +connect the AC adapter (the one that normally charges your battery) so +that the board has power (but don\'t boot it up)** +\ +Correlate the following with the BBB guide linked above: + + POMONA 5250: + === golden finger and wifi switch ==== + 18 - - 1 + 22 - - NC ---------- audio jacks are on this end + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + === CPU fan === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +Connecting the BBB and pomona (in this image, an external 3.3v DC PSU +was used):\ + + +Flashrom binaries for ARM (tested on a BBB) are distributed in +libreboot\_util. Alternatively, libreboot also distributes flashrom +source code which can be built. + +SSH\'d into the BBB:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +yourrom.rom** + +It should be **Verifying flash\... VERIFIED** at the end. If flashrom +complains about multiple flash chip definitions detected, then choose +one of them following the instructions in the output. + +Remove the programmer and put it away somewhere. Put back the tape and +press firmly over it:\ + + +Your empty chassis:\ + + +Put the motherboard back in:\ + + +Reconnect SATA:\ + + +Put the plate back and re-insert those screws:\ + + +Re-route that antenna cable around the fan and apply the tape:\ + + +Route the cable here and then (not shown, due to error on my part) +reconnect the monitor cable to the motherboard and re-insert the +screws:\ + + +Re-insert that screw:\ + + +Route the black antenna cable like so:\ + + +Tuck it in neatly like so:\ + + +Route the modem cable like so:\ + + +Connect modem cable to board and tuck it in neatly like so:\ + + +Route the power connection and connect it to the board like so:\ + + +Route the antenna and modem cables neatly like so:\ + + +Connect the wifi antenna cables. At the start of the tutorial, this +system had an Intel wifi chip. Here you see I\'ve replaced it with an +Atheros AR5B95 (supports 802.11n and can be used without blobs):\ + + +Connect the modem cable:\ + + +Connect the speaker:\ + + +You should now have this:\ + + +Re-connect the upper chassis:\ + + +Re-connect the keyboard:\ + + +Re-insert the screws that you removed earlier:\ + + +Power on!\ + + +Operating system:\ + + +</div> + +<div class="section"> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> diff --git a/docs/install/x60tablet_unbrick.html b/docs/install/x60tablet_unbrick.html deleted file mode 100644 index ecc59a9e..00000000 --- a/docs/install/x60tablet_unbrick.html +++ /dev/null @@ -1,215 +0,0 @@ -<!DOCTYPE html> -<html> -<head> - <meta charset="utf-8"> - <meta name="viewport" content="width=device-width, initial-scale=1"> - - <style type="text/css"> - @import url('../css/main.css'); - </style> - - <title>ThinkPad X60 Tablet: Recovery guide</title> -</head> - -<body> - - <div class="section"> - <h1>ThinkPad X60 Tablet: Recovery guide</h1> - <p>This section documents how to recover from a bad flash that prevents your ThinkPad X60 Tablet from booting.</p> - <p><a href="./">Back to previous index</a></p> - </div> - - <div class="section"> - <h2>Table of Contents</h2> - <ul> - <li> - Types of brick: - <ul> - <li><a href="#bucts_brick">Brick type 1: bucts not reset</a></li> - <li><a href="#recovery">Brick type 2: bad rom (or user error), system won't boot</a></li> - </ul> - </li> - </ul> - </div> - - <div class="section"> - <h1 id="bucts_brick">Brick type 1: bucts not reset.</h1> - <p> - You still have Lenovo BIOS, or you had libreboot running and you flashed another ROM; and you had bucts 1 set and - the ROM wasn't dd'd.* or if Lenovo BIOS was present and libreboot wasn't flashed.<br/><br/> - - In this case, unbricking is easy: reset BUC.TS to 0 by removing that yellow cmos coin (it's a battery) and putting it back after a minute or two:<br/> - <img src="../images/x60t_unbrick/0008.JPG" alt="" /><br/><br/> - - *Those dd commands should be applied to all newly compiled X60 ROM images (the ROM images in libreboot binary archives already have this applied!):<br/> - dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k<br/> - dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump<br/> - dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc<br/> - (doing this makes the ROM suitable for use when flashing a system that still has Lenovo BIOS running, - using those instructions: <a href="http://www.coreboot.org/Board:lenovo/x60/Installation">http://www.coreboot.org/Board:lenovo/x60/Installation</a>. - </p> - </div> - - <div class="section"> - - <h1 id="recovery">bad rom (or user error), system won't boot</h1> - <p> - In this scenario, you compiled a ROM that had an incorrect configuration, or there is an actual bug preventing your system from - booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash while Lenovo BIOS was running. In any case, your system is bricked and will not boot at all. - </p> - <p> - "Unbricking" means flashing a known-good (working) ROM. The problem: you can't boot the system, making this difficult. In this situation, external hardware (see hardware requirements above) is needed which can flash the SPI chip (where libreboot resides). - </p> - - <p> - <img src="../images/x60t_unbrick/0000.JPG" alt="" /> - </p> - - <p> - Remove those screws:<br/> - <img src="../images/x60t_unbrick/0001.JPG" alt="" /> - </p> - - <p> - Remove the HDD:<br/> - <img src="../images/x60t_unbrick/0002.JPG" alt="" /> - </p> - - <p> - Push keyboard forward to loosen it:<br/> - <img src="../images/x60t_unbrick/0003.JPG" alt="" /> - </p> - - <p> - Lift:<br/> - <img src="../images/x60t_unbrick/0004.JPG" alt="" /> - </p> - - <p> - Remove those:<br/> - <img src="../images/x60t_unbrick/0005.JPG" alt="" /> - </p> - - <p> - - <img src="../images/x60t_unbrick/0006.JPG" alt="" /> - </p> - - <p> - Also remove that (marked) and unroute the antenna cables:<br/> - <img src="../images/x60t_unbrick/0007.JPG" alt="" /> - </p> - - <p> - For some X60T laptops, you have to unroute those too:<br/> - <img src="../images/x60t_unbrick/0010.JPG" alt="" /> - </p> - - <p> - Remove the LCD extend board screws. Also remove those screws (see blue marks) and remove/unroute the cables and remove the metal plate:<br/> - <img src="../images/x60t_unbrick/0008.JPG" alt="" /> - </p> - - <p> - Remove that screw and then remove the board:<br/> - <img src="../images/x60t_unbrick/0009.JPG" alt="" /> - </p> - - <p> - Now wire up the BBB and the Pomona with your PSU.<br/> - Refer to <a href="bbb_setup.html">bbb_setup.html</a> for how to setup - the BBB for flashing.<br/> - <b>Note, the guide mentions a 3.3v DC PSU but you don't need this on the X60 Tablet: - if you don't have or don't want to use an external PSU, then make - sure not to connect the 3.3v leads mentioned in the guide; - instead, connect the AC adapter (the one that normally charges your - battery) so that the board has power (but don't boot it up)</b> - <img src="../images/x60t_unbrick/0011.JPG" alt="" /><br/> - Correlate the following with the BBB guide linked above: - </p> -<pre> -POMONA 5250: -=== golden finger and wifi switch ==== - 18 - - 1 - 22 - - NC ---------- audio jacks are on this end - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== CPU fan === -<i>This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack.</i> -</pre> - - <p> - Connecting the BBB and pomona (in this image, an external 3.3v DC PSU was used):<br/> - <img src="images/x60/th_bbb_flashing.jpg" alt="" /> - </p> - - <p> - Flashrom binaries for ARM (tested on a BBB) are distributed in libreboot_util. Alternatively, - libreboot also distributes flashrom source code which can be built. - </p> - - <p> - SSH'd into the BBB:<br/> - # <b>./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom</b> - </p> - <p> - It should be <b>Verifying flash... VERIFIED</b> at the end. If flashrom complains about multiple flash chip - definitions detected, then choose one of them following the instructions in the output. - </p> - - <p> - Reverse the steps to re-assemble your system. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Leah Rowe <info@minifree.org><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the Creative Commons Attribution-ShareAlike 4.0 International license - or any later version published by Creative Commons; - - A copy of the license can be found at <a href="../cc-by-sa-4.0.txt">../cc-by-sa-4.0.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode">https://creativecommons.org/licenses/by-sa/4.0/legalcode</a> - </p> - - <p> - UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - </p> - <p> - TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - </p> - <p> - The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - </p> - - </div> - -</body> -</html> diff --git a/docs/install/x60tablet_unbrick.md b/docs/install/x60tablet_unbrick.md new file mode 100644 index 00000000..5d8bea51 --- /dev/null +++ b/docs/install/x60tablet_unbrick.md @@ -0,0 +1,178 @@ +<div class="section"> + +ThinkPad X60 Tablet: Recovery guide +=================================== + +This section documents how to recover from a bad flash that prevents +your ThinkPad X60 Tablet from booting. + +[Back to previous index](./) + +</div> + +<div class="section"> + +Table of Contents +----------------- + +- Types of brick: + - [Brick type 1: bucts not reset](#bucts_brick) + - [Brick type 2: bad rom (or user error), system won\'t + boot](#recovery) + +</div> + +<div class="section"> + +Brick type 1: bucts not reset. {#bucts_brick} +============================== + +You still have Lenovo BIOS, or you had libreboot running and you flashed +another ROM; and you had bucts 1 set and the ROM wasn\'t dd\'d.\* or if +Lenovo BIOS was present and libreboot wasn\'t flashed.\ +\ +In this case, unbricking is easy: reset BUC.TS to 0 by removing that +yellow cmos coin (it\'s a battery) and putting it back after a minute or +two:\ +\ +\ +\*Those dd commands should be applied to all newly compiled X60 ROM +images (the ROM images in libreboot binary archives already have this +applied!):\ +dd if=coreboot.rom of=top64k.bin bs=1 skip=\$\[\$(stat -c %s +coreboot.rom) - 0x10000\] count=64k\ +dd if=coreboot.rom bs=1 skip=\$\[\$(stat -c %s coreboot.rom) - 0x20000\] +count=64k | hexdump\ +dd if=top64k.bin of=coreboot.rom bs=1 seek=\$\[\$(stat -c %s +coreboot.rom) - 0x20000\] count=64k conv=notrunc\ +(doing this makes the ROM suitable for use when flashing a system that +still has Lenovo BIOS running, using those instructions: +<http://www.coreboot.org/Board:lenovo/x60/Installation>. + +</div> + +<div class="section"> + +bad rom (or user error), system won\'t boot {#recovery} +=========================================== + +In this scenario, you compiled a ROM that had an incorrect +configuration, or there is an actual bug preventing your system from +booting. Or, maybe, you set BUC.TS to 0 and shut down after first flash +while Lenovo BIOS was running. In any case, your system is bricked and +will not boot at all. + +\"Unbricking\" means flashing a known-good (working) ROM. The problem: +you can\'t boot the system, making this difficult. In this situation, +external hardware (see hardware requirements above) is needed which can +flash the SPI chip (where libreboot resides). + + + +Remove those screws:\ + + +Remove the HDD:\ + + +Push keyboard forward to loosen it:\ + + +Lift:\ + + +Remove those:\ + + + + +Also remove that (marked) and unroute the antenna cables:\ + + +For some X60T laptops, you have to unroute those too:\ + + +Remove the LCD extend board screws. Also remove those screws (see blue +marks) and remove/unroute the cables and remove the metal plate:\ + + +Remove that screw and then remove the board:\ + + +Now wire up the BBB and the Pomona with your PSU.\ +Refer to [bbb\_setup.html](bbb_setup.html) for how to setup the BBB for +flashing.\ +**Note, the guide mentions a 3.3v DC PSU but you don\'t need this on the +X60 Tablet: if you don\'t have or don\'t want to use an external PSU, +then make sure not to connect the 3.3v leads mentioned in the guide; +instead, connect the AC adapter (the one that normally charges your +battery) so that the board has power (but don\'t boot it up)** +\ +Correlate the following with the BBB guide linked above: + + POMONA 5250: + === golden finger and wifi switch ==== + 18 - - 1 + 22 - - NC ---------- audio jacks are on this end + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip + === CPU fan === + This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. + +Connecting the BBB and pomona (in this image, an external 3.3v DC PSU +was used):\ + + +Flashrom binaries for ARM (tested on a BBB) are distributed in +libreboot\_util. Alternatively, libreboot also distributes flashrom +source code which can be built. + +SSH\'d into the BBB:\ +\# **./flashrom -p linux\_spi:dev=/dev/spidev1.0,spispeed=512 -w +yourrom.rom** + +It should be **Verifying flash\... VERIFIED** at the end. If flashrom +complains about multiple flash chip definitions detected, then choose +one of them following the instructions in the output. + +Reverse the steps to re-assemble your system. + +</div> + +<div class="section"> + +Copyright © 2014, 2015 Leah Rowe <info@minifree.org>\ +Permission is granted to copy, distribute and/or modify this document +under the terms of the Creative Commons Attribution-ShareAlike 4.0 +International license or any later version published by Creative +Commons; A copy of the license can be found at +[../cc-by-sa-4.0.txt](../cc-by-sa-4.0.txt) + +Updated versions of the license (when available) can be found at +<https://creativecommons.org/licenses/by-sa/4.0/legalcode> + +UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE EXTENT +POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS AND +AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND +CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, IMPLIED, STATUTORY, +OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, WARRANTIES OF TITLE, +MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, +ABSENCE OF LATENT OR OTHER DEFECTS, ACCURACY, OR THE PRESENCE OR ABSENCE +OF ERRORS, WHETHER OR NOT KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF +WARRANTIES ARE NOT ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT +APPLY TO YOU. + +TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE TO YOU +ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, NEGLIGENCE) OR +OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, INCIDENTAL, CONSEQUENTIAL, +PUNITIVE, EXEMPLARY, OR OTHER LOSSES, COSTS, EXPENSES, OR DAMAGES +ARISING OUT OF THIS PUBLIC LICENSE OR USE OF THE LICENSED MATERIAL, EVEN +IF THE LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSSES, +COSTS, EXPENSES, OR DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT +ALLOWED IN FULL OR IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + +The disclaimer of warranties and limitation of liability provided above +shall be interpreted in a manner that, to the extent possible, most +closely approximates an absolute disclaimer and waiver of all liability. + +</div> |