diff options
Diffstat (limited to 'docs/install')
26 files changed, 3021 insertions, 5516 deletions
diff --git a/docs/install/bbb_ehci.html b/docs/install/bbb_ehci.html deleted file mode 100644 index 3cdda48..0000000 --- a/docs/install/bbb_ehci.html +++ /dev/null @@ -1,514 +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>EHCI debugging on the BeagleBone Black</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">EHCI debugging on the BeagleBone Black</h1> - - <p><a href="index.html">Back to previous index</a></p> - </div> - - <div class="section"> - <h1>EHCI debugging</h1> - <ol class="toc"> - <li><a href="#FindUSBportonthetargetthatsupportsEHCIdebug">Find - USB port on the target that supports EHCI debug</a></li> - <li><a href="#InitialsetupofBBBtoactasEHCIdebugdongle">Initial - setup of BBB to act as EHCI debug dongle</a></li> - <li><a href="#PatchBBBsgdbgpmoduleoptionalbuthighlyrecommended">Patch - BBB's <tt>g_dbgp</tt> module (optional, but highly recommended)</a></li> - <li><a href="#ConfigurelibrebootwithEHCIdebug">Configure - libreboot with EHCI debug</a> - <ol> - <li><a href="#SelectingHCDIndexandUSBDebugport">Selecting - <tt>HCD Index</tt> and <tt>USB Debug port</tt></a></li> - </ol></li> - <li><a href="#Howtogetthedebuglogs">How to get the debug - logs</a></li> - <li><a - href="#EnebleEHCIDebugonthetargetskerneloptionalrecommended">Eneble - EHCI Debug on the target's kernel (optional, recommended)</a></li> - <li><a href="#References">References</a></li> - </ol> - <p>If your computer does not boot after installing libreboot, it is - very useful to get debug logs from it, from the payload (grub) and/or - the kernel (if gets to there). All of them stream debug logs on the - available serial (RS-232) by default. However, most of todays laptops - lack RS-232 port. The other option is to stream the logs to USB EHCI - debug port.</p> - <p>This section explains step-by-step how to setup BBB as a - “USB EHCI debug dongle” and configure libreboot and the - linux kernel to stream logs to it (TODO: grub).</p> - <p>I will refer to three computers:</p> - <ul> - <li><b>host</b> - this is the computer you use, have - tools, compiler, Internet, etc</li> - <li><b>BBB</b> - Beaglebone Black (rev. B or higher, i - use rev. C)</li> - <li><b>target</b> - the computer you are trying to - install liberboot</li> - </ul> - <h3 id="FindUSBportonthetargetthatsupportsEHCIdebug">Find USB port - on the target that supports EHCI debug</h3> - <p> - Not all USB controllers support EHCI debug (see: <a - href="http://www.coreboot.org/EHCI_Debug_Port#Hardware_capability">EHCI - Debug Port</a> ). Even more, if a USB controller supports EHCI debug, it - is available only <b>on a single port</b> that might or might - not be exposed externally. - </p> - <ul> - <li>You need running OS (GNU/Linux) on your target for this step - (If you’ve flashed libreboot and it does not boot, you have to - flush back the stock bios)</li> - <li>You need USB memory stick (the data on it will not be - touched).</li> - <li>The EHCI debugging can not be done through external hub, BBB - must be connected directly to the debug port of the controller (so, no - hubs)</li> - </ul> - <ul> - <li>Download<sup class="footnote"><a href="#___fn1">1</a></sup> <a - href="http://www.coreboot.org/pipermail/coreboot/attachments/20080909/ae11c291/attachment.sh">this</a> - shell script. - </li> - </ul> - <ol> - <li>Plug the usb stick in the first available usb port</li> - <li>Run the script, you will get output similar to following:</li> -<pre>The following PCI devices support a USB debug port (says lspci): 0000:00:1a.0 0000:00:1d.0 -The following PCI devices support a USB debug port (says the kernel): 0000:00:1a.0 0000:00:1d.0 -*PCI device 0000:00:1a.0, USB bus 3, USB physical port 1* -*PCI device 0000:00:1d.0, USB bus 4, USB physical port 2* -Currently connected high-speed devices: -/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M - |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M - |__ Port 7: Dev 14, If 0, Class=Hub, Driver=hub/4p, 480M - |__ Port 1: Dev 15, If 0, Class=Hub, Driver=hub/4p, 480M - |__ Port 3: Dev 17, If 0, Class=Hub, Driver=hub/2p, 480M - |__ Port 4: Dev 18, If 0, Class=Hub, Driver=hub/4p, 480M -/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M - |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M -/: *Bus 01*.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M - |__ *Port 3: Dev 31, If 0, Class=Mass Storage, Driver=usb-storage, 480M* -</pre> - <li>The buses the support debug are Bus 3 (0000:00:1a.0) on Port 1 - and Bus 4 (0000:00:1d.0) on port 2. Your usb stick is plugged on Bus - 1, Port 3</li> - <li>Repeat the steps, plugging the USB stick in the next available - port</li> - <li>Go through all available ports and remember(write down) those - for which bus/port of the usb stick matches one of the bus/port that - support debug (bold).</li> - </ol> - <p>Remember (write down) for each port (external plug) you found - that supports debug: <b>PCI device id, the bus id, the port number, and - the physical location of the usb plug.</b></p> - <p>If you do not find a match, you can not get debug over EHCI. - Sorry.</p> - <p id="___fn1" class="footnote"> - <sup>1</sup> The guys from coreboot were talking about including the - script in coreboot distribution (check the status). - </p> - <h3 id="InitialsetupofBBBtoactasEHCIdebugdongle">Initial setup of - BBB to act as EHCI debug dongle</h3> - <p>BBB must be powered with a barrel power connector since the - mini-B USB plug will be used for the EHCI debug stream. So you will - need:</p> - <ul> - <li>power supply (5V, 2A(10W) is sufficient).</li> - <li>an extra usb cable: A to mini-B</li> - </ul> - <p> - (On BBB) The linux kernel includes module (g_dbgp that enables one of the usb ports on a computer to behave as EHCI - debug dongle. Make sure you have this module available on your BBB - (Debian 7.8 that comes with BBB should have it), if not, you should - compile it yourself (see next section): - </p> -<pre>ls /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget/g_dbgp.ko</pre> - <p> - Unload all other - g_* - modules: - </p> -<pre># lsmod -# rmmod g_multi -... -</pre> - <p> - Then load - g_dbgp - : - </p> -<pre># modprobe g_dbgp -# lsmod # should show that g_dbgp is loaded, and no other g_* -</pre> - <p> - Plug the mini-B side of the USB cable in your BBB and the A side in - your target. Then one of the usb devices on your target (with - lsusb - ) should be: - </p> -<pre>Bus 001 Device 024: ID 0525:c0de Netchip Technology, Inc.</pre> - <p>If you see the device on the target, you are good to continue to - the next step.</p> - <h3 id="PatchBBBsgdbgpmoduleoptionalbuthighlyrecommended"> - Patch BBB’s - g_dbgp - module (optional, but highly recommended) - </h3> - <p> - For the reasons why you need this, see: <a - href="http://www.coreboot.org/EHCI_Gadget_Debug">EHCI Gadget Debug</a>.<br />Make - sure that you have cross compiling environment for - arm-linux-gnueabihf - setup on your <em>host</em>. - </p> - <ul> - <li>On BBB: uname -r - this will give you version - number like 3.8.13-bone70 (I will refer to this as: $mav.$miv-$lv: - where mav=3.8, miv=13, lv=bone70 - </li> - <li>Get the BBB kernel ready on your host for cross-compiling:</li> - </ul> -<pre>$ cd $work_dir -$ git clone https://github.com/beagleboard/kernel.git -$ cd kernel -$ git checkout $mav (see above) -$ ./patch.sh -$ wget http://arago-project.org/git/projects/?p=am33x-cm3.git\;a=blob_plain\;f=bin/am335x-pm-firmware.bin\;hb=HEAD -O kernel/firmware/am335x-pm-firmware.bin -$ cp configs/beaglebone kernel/arch/arm/configs/beaglebone_defconfig -</pre> - <ul> - <li>Download the patch from <a - href="http://www.coreboot.org/images/8/88/Ehci-debug-gadget-patches.tar.gz">here</a></li> - <li>tar -xf Ehci-debug-gadget-patches.tar.gz (will - create dir: usbdebug-gadget)</li> - <li>Note that there are two patches (patch_1 and patch_2) for each - of the two different version of the kernel (3.8 and 3.10). I will use - 3.8. (If using kernel 3.12 patch_1 is not needed)</li> - <li>cd kernel (note that this is one more level: you - should be in $work_dir/kernel/kernel)</li> - <li>Apply the patches:</li> - </ul> -<pre> -git apply ../usbdebug-gadget/v3.8-debug-gadget/0001-usb-dbgp-gadget-Fix-re-connecting-after-USB-disconne.patch -git apply ../usbdebug-gadget/v3.8-debug-gadget/0002-usb-serial-gadget-no-TTY-hangup-on-USB-disconnect-WI.patch -; -make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- beaglebone_defconfig -j4@ -</pre> - <ul> - <li> - You should also apply the linux-libre <i>deblob</i> script to turn it into linux-libre - (deletes all the blobs from the linux kernel). - <a href="http://www.fsfla.org/ikiwiki/selibre/linux-libre/">fsfla website</a> - - see <a href="http://www.fsfla.org/svn/fsfla/software/linux-libre/scripts/">scripts</a>. - </li> - <li>Get your current BBB kernel config (from: /boot/config-<ver>) - and copy it to your host as $work_dir/kernel/kernel/.config</li> -<pre> -make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- oldconfig - all default answers</pre> - <li>Set proper version number: - <ul> - <li>On your host, edit $work_dir/kernel/kernel/.config - (the one you’ve just copied from BBB), find the line CONFIG_LOCALVERSION="<something - or empty>" and change it to CONFIG_LOCALVERSION="-$lv", - so it will look something like: CONFIG_LOCALVERSION="-bone70"</li> - </ul> - </li> - <li>Also, make sure that: CONFIG_USB_G_DBGP=m (If - not, make menuconfig, and set @Device Drivers-> USB - Support -> USB Gadget Support -> EHCI Debug Device Gadget=m</li> - <li>Build the module:</li> - </ul> -<pre> -$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 (is it possoble to build only the gadget modules) -$ mkdir ../tmp && make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=../tmp modules_install -</pre> - <ul> - <li>on BBB, backup /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget - (i.e. mv - /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget $HOME) - </li> - <li>copy the freshly compiled usb/gadget dir to /lib/modules/3.8.13-bone70/kernel/drivers/usb</li> - <li>restart BBB</li> - <li>Remove all g_* modules (rmmod - g_<>) - </li> - <li>modprobpe g_dbgp</li> - </ul> - <h3 id="ConfigurelibrebootwithEHCIdebug">Configure libreboot with - EHCI debug</h3> - <p> - Libreboot(coreboot) should be configured with debug turned on and to - push debug messages to the EHCI debug port.<br />If you’ve - downloaded the binary distribution, you can check if it is properly - configured in the following way: - </p> - <ul> - <li>Go to the libreboot dist root directory cd - $libreboot_bin</li> - <li>Locate the rom image for your target (I will call it: $img_path) - </li> - <li>Running the following command will extract the config in a - file ./my_config: - </li> - </ul> -<pre> -./cbfstool/i686/cbfstool $img_path extract -n config -f ./my_config -</pre> - <ul> - <li>Make sure that the following params in the config are set as - following:</li> - </ul> -<pre> -CONFIG_USBDEBUG=y (Generic Drivers -> USB 2.0 EHCI debug dongle support) -CONFIG_USBDEBUG_IN_ROMSTAGE=y (Generic Drivers -> Enable early (pre-RAM) usbdebug) -CONFIG_USBDEBUG_HCD_INDEX=<HCD Index of usb controller - see below> (Generic Drivers -> Index for EHCI controller to use with usbdebug) -CONFIG_USBDEBUG_DEFAULT_PORT=<USB Debug port - see below> (Generic Drivers -> Default USB port to use as Debug Port) -</pre> - <p> - The following three are behind radio button in the menu. Only the first - one<sup class="footnote"><a href="#___fn2">2</a></sup> should be = y - </p> -<pre> -USBDEBUG_DONGLE_STD=y (Generic Drivers -> Type of dongle (Net20DC or compatible) -> Net20DC or compatible) -CONFIG_USBDEBUG_DONGLE_BEAGLEBONE=n (Generic Drivers -> Type of dongle (Net20DC or compatible) -> BeagleBone) -CONFIG_USBDEBUG_DONGLE_BEAGLEBONE_BLACK=n (Generic Drivers -> Type of dongle (Net20DC or compatible) -> BeagleBone Black) -</pre> - <p id="___fn2" class="footnote"> - <sup>2</sup> The g_dbgp module on BeagleBone Black (Rev. C) reports it self as Net20DC, the - other options are for older BB(B) - ver1. This is documented <a - href="https://johnlewis.ie/coreboot-ehci-debug-gadget-demonstration/">here</a> - (also tested/verified). - </p> - <p> - Then:<br /> -<pre> -CONFIG_CONSOLE_USB=y (Console -> USB dongle console output) -</pre> - </p> - <p> - Also - Debugging ---> Output verbose XYZ - ) (<b>FIXME</b> somebody verify these): - </p> -<pre> -CONFIG_DEBUG_CBFS=y (Output verbose CBFS debug messages ) -CONFIG_HAVE_DEBUG_RAM_SETUP=y (??? What/where is this) -CONFIG_DEBUG_RAM_SETUP=y (Output verbose RAM init debug messages) -CONFIG_DEBUG_SMI=y (Output verbose SMI debug messages) -CONFIG_DEBUG_ACPI=y (Output verbose ACPI debug messages ) -CONFIG_DEBUG_USBDEBUG=y (Output verbose USB 2.0 EHCI debug dongle messages) -</pre> - <p>If some of the above mentioned configuration options are not as - specified, you have to configure and compile libreboot yourself. Please - refer to the doc(<b>FIXME: link</b> about compiling libreboot.</p> - <h4 id="SelectingHCDIndexandUSBDebugport"> - Selecting - HCD Index - and - USB Debug port - </h4> - <p> - This applies (and works) only if the USB controller that supports debug - (found in the first section) is from Intel.<br />If the PCI ID of the - port you found in the first section is - 0000:00:1a.0 - or - 0000:00:1d.0 - , you are ok. Otherwise you have to try without guarantee that will - work. - </p> - <p> - If the externally exposed port is on a bus with - PCI ID == 0000:00:1a.0 - then for - CONFIG_USBDEBUG_HCD_INDEX - choose 2, otherwise choose 0 - . - </p> - <p> - For - CONFIG_USBDEBUG_DEFAULT_PORT - choose the port from the first section that correspond to the - PCI ID - </p> - <p> - Notes:<br />The above is based on the implementation of - coreboot/src/southbridge/intel/common/usb_debug.c : pci_ehci_dbg_dev() - .<br />This is enough as it applies for the supported GM45/G45 - Thinkpads. coreboot support some other contollers too, but they are - irellevent for libreboot (for now). - </p> - <ul> - <li>On T500 (with switchable GPU) the debug ports for both intel - controllers is exposed.</li> - <li>On x200t the debug ports for both intel controllers is - exposed.</li> - </ul> - <h3 id="Howtogetthedebuglogs">How to get the debug logs</h3> - <ul> - <li>Plug the USB cable in the target’s debug port (the one - you found in step 1) and BBB’s mini-B USB</li> - <li>Make sure no other then g_dbgp of the g_* - modules is loaded on your BBB - </li> - <li>On the BBB:</li> - </ul> -<pre> -stty -icrnl -inlcr -F /dev/ttyGS0 -cat /dev/ttyGS0 -</pre> - <ul> - <li>Power on the target with libreboot</li> - <li>You should see debug logs comming on your BBB console</li> - </ul> - <p> - Note that this is not permanent on BBB, if you reboot it, you have to - rmmod g_* - and - modprobe g_dbgp - </p> - <h3 id="EnebleEHCIDebugonthetargetskerneloptionalrecommended">Eneble - EHCI Debug on the target’s kernel (optional, recommended)</h3> - <p>You have to know how to compile kernel for your target.</p> - <ol> - <li>Check if early debugging is already enabled: grep - CONFIG_EARLY_PRINTK_DBGP /boot/config-<ver></li> - <li>If enabled, you do not have to compile the kernel (skip this - step). Otherwise, prepare kernel source for your distribution and - select (Kernel hacking -> Early printk via EHCI debug - port). Compile and install the new kernel. - </li> - <li>Edit your grub configuration and add following to the kenel - parameters<sup class="footnote"><a href="#___fn20">20</a></sup><sup - class="footnote"><a href="#___fn21">21</a></sup>: earlyprintk=dbgp,keep. - Also, try: earlyprintk=dbgp<N>,keep where N - is the debug port id if the first does not work. - </li> - </ol> - <h3 id="References">References</h3> - <p id="___fn10" class="footnote"> - <sup>10</sup> <a href="http://www.coreboot.org/EHCI_Debug_Port">EHCI - Debug Port</a> - </p> - <p id="___fn11" class="footnote"> - <sup>11</sup> <a - href="https://johnlewis.ie/coreboot-ehci-debug-gadget-demonstration/">coreboot - EHCI debug gadget demonstration</a> - </p> - <p id="___fn12" class="footnote"> - <sup>12</sup> <a href="http://www.coreboot.org/EHCI_Gadget_Debug">EHCI - Gadget Debug</a> - </p> - <p id="___fn13" class="footnote"> - <sup>13</sup> <a - href="http://www.coreboot.org/images/8/88/Ehci-debug-gadget-patches.tar.gz">Ehci-debug-gadget-patches.tar.gz</a> - </p> - <p id="___fn14" class="footnote"> - <sup>14</sup> <a - href="http://wiki.beyondlogic.org/index.php/BeagleBoneBlack_Building_Kernel">Compiling - the BeagleBone Black Kernel</a> - </p> - <p id="___fn15" class="footnote"> - <sup>15</sup> - http://dumb-looks-free.blogspot.ca/2014/06/beaglebone-black-bbb-compile-kernel.html - </p> - <p id="___fn16" class="footnote"> - <sup>16</sup> - http://dumb-looks-free.blogspot.fr/2014/06/beaglebone-black-bbb-kernal-headers.html - </p> - <p id="___fn17" class="footnote"> - <sup>17</sup> <a href="http://elinux.org/Building_BBB_Kernel">Building - BBB Kernel</a> - </p> - <p id="___fn18" class="footnote"> - <sup>18</sup> - http://komposter.com.ua/documents/USB-2.0-Debug-Port%28John-Keys%29.pdf - </p> - <p id="___fn19" class="footnote"> - <sup>19</sup> <a href="http://cs.usfca.edu/~cruse/cs698s10/">Exploring - USB at the Hardware/Software Interface</a> - </p> - <p id="___fn20" class="footnote"> - <sup>20</sup> - https://www.kernel.org/doc/Documentation/x86/earlyprintk.txt - </p> - <p id="___fn21" class="footnote"> - <sup>21</sup> https://wiki.ubuntu.com/Kernel/Debugging/USBearlyprintk - </p> - <p> - <b>TODO</b>: - </p> - <ol> - <li>grub does not send messages to EHCI debug. Investigate.</li> - <li>The section “Configure libreboot with EHCI debug” - can be skipped/simplified if a common configuration works for all - relevant targets is selected as defualt</li> - <li>Patch and compule g_dbgp on BBB instead cross-compile</li> - <li>Find a simple way to send debug messages from targets userland</li> - </ol> - </div> - - <div class="section"> - - <p> - Copyright © 2015 Alex David <opdecirkel@gmail.com><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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_ehci.texi b/docs/install/bbb_ehci.texi new file mode 100644 index 0000000..8531b82 --- /dev/null +++ b/docs/install/bbb_ehci.texi @@ -0,0 +1,400 @@ +\input texinfo +@documentencoding UTF-8 + +@macro textsuperscript{text} +@iftex +@textsuperscript{\text\} +@end iftex +@ifnottex +^@{\text\@} +@end ifnottex +@end macro + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title EHCI debugging on the BeagleBone Black +@end titlepage + +@node Top +@top EHCI debugging on the BeagleBone Black + +@menu +* EHCI debugging on the BeagleBone Black:: +* EHCI debugging:: +@end menu + +@node EHCI debugging on the BeagleBone Black +@chapter EHCI debugging on the BeagleBone Black +@anchor{#ehci-debugging-on-the-beaglebone-black} +@uref{index.html,Back to previous index} + +@node EHCI debugging +@chapter EHCI debugging +@anchor{#ehci-debugging} +@enumerate +@item +@ref{#FindUSBportonthetargetthatsupportsEHCIdebug,Find USB port on the target that supports EHCI debug} +@item +@ref{#InitialsetupofBBBtoactasEHCIdebugdongle,Initial setup of BBB to act as EHCI debug dongle} +@item +@ref{#PatchBBBsgdbgpmoduleoptionalbuthighlyrecommended,Patch BBB's @code{g_dbgp} module (optional, but highly recommended)} +@item +@ref{#ConfigurelibrebootwithEHCIdebug,Configure libreboot with EHCI debug} +@enumerate +@item +@ref{#SelectingHCDIndexandUSBDebugport,Selecting @code{HCD Index} and @code{USB Debug port}} +@end enumerate + +@item +@ref{#Howtogetthedebuglogs,How to get the debug logs} +@item +@ref{#EnebleEHCIDebugonthetargetskerneloptionalrecommended,Eneble EHCI Debug on the target's kernel (optional, recommended)} +@item +@ref{#References,References} +@end enumerate + +If your computer does not boot after installing libreboot, it is very useful to get debug logs from it, from the payload (grub) and/or the kernel (if gets to there). All of them stream debug logs on the available serial (RS-232) by default. However, most of todays laptops lack RS-232 port. The other option is to stream the logs to USB EHCI debug port. + +This section explains step-by-step how to setup BBB as a “USB EHCI debug dongle” and configure libreboot and the linux kernel to stream logs to it (TODO: grub). + +I will refer to three computers: + +@itemize +@item +@strong{host} - this is the computer you use, have tools, compiler, Internet, etc +@item +@strong{BBB} - Beaglebone Black (rev. B or higher, i use rev. C) +@item +@strong{target} - the computer you are trying to install liberboot +@end itemize + +@node Find USB port on the target that supports EHCI debug +@subsection Find USB port on the target that supports EHCI debug +@anchor{#find-usb-port-on-the-target-that-supports-ehci-debug} +Not all USB controllers support EHCI debug (see: @uref{http://www.coreboot.org/EHCI_Debug_Port#Hardware_capability,EHCI Debug Port} ). Even more, if a USB controller supports EHCI debug, it is available only @strong{on a single port} that might or might not be exposed externally. + +@itemize +@item +You need running OS (GNU/Linux) on your target for this step (If you've flashed libreboot and it does not boot, you have to flush back the stock bios) +@item +You need USB memory stick (the data on it will not be touched). +@item +The EHCI debugging can not be done through external hub, BBB must be connected directly to the debug port of the controller (so, no hubs) +@end itemize + +@itemize +@item +Download@textsuperscript{@ref{#___fn1,1}} @uref{http://www.coreboot.org/pipermail/coreboot/attachments/20080909/ae11c291/attachment.sh,this} shell script. +@end itemize + +@enumerate +@item +Plug the usb stick in the first available usb port +@item +Run the script, you will get output similar to following: +@item +The buses the support debug are Bus 3 (0000:00:1a.0) on Port 1 and Bus 4 (0000:00:1d.0) on port 2. Your usb stick is plugged on Bus 1, Port 3 +@item +Repeat the steps, plugging the USB stick in the next available port +@item +Go through all available ports and remember(write down) those for which bus/port of the usb stick matches one of the bus/port that support debug (bold). +@end enumerate + +Remember (write down) for each port (external plug) you found that supports debug: @strong{PCI device id, the bus id, the port number, and the physical location of the usb plug.} + +If you do not find a match, you can not get debug over EHCI. Sorry. + +@textsuperscript{1} The guys from coreboot were talking about including the script in coreboot distribution (check the status). + +@node Initial setup of BBB to act as EHCI debug dongle +@subsection Initial setup of BBB to act as EHCI debug dongle +@anchor{#initial-setup-of-bbb-to-act-as-ehci-debug-dongle} +BBB must be powered with a barrel power connector since the mini-B USB plug will be used for the EHCI debug stream. So you will need: + +@itemize +@item +power supply (5V, 2A(10W) is sufficient). +@item +an extra usb cable: A to mini-B +@end itemize + +(On BBB) The linux kernel includes module (g_dbgp that enables one of the usb ports on a computer to behave as EHCI debug dongle. Make sure you have this module available on your BBB (Debian 7.8 that comes with BBB should have it), if not, you should compile it yourself (see next section): + +@verbatim +ls /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget/g_dbgp.ko +@end verbatim + +Unload all other g_* modules: + +@verbatim +# lsmod +# rmmod g_multi +... +@end verbatim + +Then load g_dbgp : + +@verbatim +# modprobe g_dbgp +# lsmod # should show that g_dbgp is loaded, and no other g_* +@end verbatim + +Plug the mini-B side of the USB cable in your BBB and the A side in your target. Then one of the usb devices on your target (with lsusb ) should be: + +@verbatim +Bus 001 Device 024: ID 0525:c0de Netchip Technology, Inc. +@end verbatim + +If you see the device on the target, you are good to continue to the next step. + +@node Patch BBB's g_dbgp module optional but highly recommended +@subsection Patch BBB's g_dbgp module (optional, but highly recommended) +@anchor{#patch-bbbs-g_dbgp-module-optional-but-highly-recommended} +For the reasons why you need this, see: @uref{http://www.coreboot.org/EHCI_Gadget_Debug,EHCI Gadget Debug}.@*Make sure that you have cross compiling environment for arm-linux-gnueabihf setup on your @emph{host}. + +@itemize +@item +On BBB: uname -r - this will give you version number like 3.8.13-bone70 (I will refer to this as: $mav.$miv-$lv: where mav=3.8, miv=13, lv=bone70 +@item +Get the BBB kernel ready on your host for cross-compiling: +@end itemize + +@verbatim +$ cd $work_dir +$ git clone https://github.com/beagleboard/kernel.git +$ cd kernel +$ git checkout $mav (see above) +$ ./patch.sh +$ wget http://arago-project.org/git/projects/?p=am33x-cm3.git\;a=blob_plain\;f=bin/am335x-pm-firmware.bin\;hb=HEAD -O kernel/firmware/am335x-pm-firmware.bin +$ cp configs/beaglebone kernel/arch/arm/configs/beaglebone_defconfig +@end verbatim + +@itemize +@item +Download the patch from @uref{http://www.coreboot.org/images/8/88/Ehci-debug-gadget-patches.tar.gz,here} +@item +tar -xf Ehci-debug-gadget-patches.tar.gz (will create dir: usbdebug-gadget) +@item +Note that there are two patches (patch_1 and patch_2) for each of the two different version of the kernel (3.8 and 3.10). I will use 3.8. (If using kernel 3.12 patch_1 is not needed) +@item +cd kernel (note that this is one more level: you should be in $work_dir/kernel/kernel) +@item +Apply the patches: +@end itemize + +@verbatim +git apply ../usbdebug-gadget/v3.8-debug-gadget/0001-usb-dbgp-gadget-Fix-re-connecting-after-USB-disconne.patch +git apply ../usbdebug-gadget/v3.8-debug-gadget/0002-usb-serial-gadget-no-TTY-hangup-on-USB-disconnect-WI.patch +; +make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- beaglebone_defconfig -j4@ +@end verbatim + +@itemize +@item +You should also apply the linux-libre @emph{deblob} script to turn it into linux-libre (deletes all the blobs from the linux kernel). @uref{http://www.fsfla.org/ikiwiki/selibre/linux-libre/,fsfla website} - see @uref{http://www.fsfla.org/svn/fsfla/software/linux-libre/scripts/,scripts}. +@item +Get your current BBB kernel config (from: /boot/config-<ver>) and copy it to your host as $work_dir/kernel/kernel/.config +@item +Set proper version number: +@itemize +@item +On your host, edit $work_dir/kernel/kernel/.config (the one you've just copied from BBB), find the line CONFIG_LOCALVERSION="<something or empty>" and change it to CONFIG_LOCALVERSION="-$lv", so it will look something like: CONFIG_LOCALVERSION="-bone70" +@end itemize + +@item +Also, make sure that: CONFIG_USB_G_DBGP=m (If not, make menuconfig, and set @@Device Drivers-> USB Support -> USB Gadget Support -> EHCI Debug Device Gadget=m +@item +Build the module: +@end itemize + +@verbatim +$ make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- -j4 (is it possoble to build only the gadget modules) +$ mkdir ../tmp && make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- INSTALL_MOD_PATH=../tmp modules_install +@end verbatim + +@itemize +@item +on BBB, backup /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget (i.e. mv /lib/modules/3.8.13-bone70/kernel/drivers/usb/gadget $HOME) +@item +copy the freshly compiled usb/gadget dir to /lib/modules/3.8.13-bone70/kernel/drivers/usb +@item +restart BBB +@item +Remove all g_* modules (rmmod g_<>) +@item +modprobpe g_dbgp +@end itemize + +@node Configure libreboot with EHCI debug +@subsection Configure libreboot with EHCI debug +@anchor{#configure-libreboot-with-ehci-debug} +Libreboot(coreboot) should be configured with debug turned on and to push debug messages to the EHCI debug port.@*If you've downloaded the binary distribution, you can check if it is properly configured in the following way: + +@itemize +@item +Go to the libreboot dist root directory cd $libreboot_bin +@item +Locate the rom image for your target (I will call it: $img_path) +@item +Running the following command will extract the config in a file ./my_config: +@end itemize + +@verbatim +./cbfstool/i686/cbfstool $img_path extract -n config -f ./my_config +@end verbatim + +@itemize +@item +Make sure that the following params in the config are set as following: +@end itemize + +@verbatim +CONFIG_USBDEBUG=y (Generic Drivers -> USB 2.0 EHCI debug dongle support) +CONFIG_USBDEBUG_IN_ROMSTAGE=y (Generic Drivers -> Enable early (pre-RAM) usbdebug) +CONFIG_USBDEBUG_HCD_INDEX=<HCD Index of usb controller - see below> (Generic Drivers -> Index for EHCI controller to use with usbdebug) +CONFIG_USBDEBUG_DEFAULT_PORT=<USB Debug port - see below> (Generic Drivers -> Default USB port to use as Debug Port) +@end verbatim + +The following three are behind radio button in the menu. Only the first one@textsuperscript{@ref{#___fn2,2}} should be = y + +@verbatim +USBDEBUG_DONGLE_STD=y (Generic Drivers -> Type of dongle (Net20DC or compatible) -> Net20DC or compatible) +CONFIG_USBDEBUG_DONGLE_BEAGLEBONE=n (Generic Drivers -> Type of dongle (Net20DC or compatible) -> BeagleBone) +CONFIG_USBDEBUG_DONGLE_BEAGLEBONE_BLACK=n (Generic Drivers -> Type of dongle (Net20DC or compatible) -> BeagleBone Black) +@end verbatim + +@textsuperscript{2} The g_dbgp module on BeagleBone Black (Rev. C) reports it self as Net20DC, the other options are for older BB(B) - ver1. This is documented @uref{https://johnlewis.ie/coreboot-ehci-debug-gadget-demonstration/,here} (also tested/verified). + +Then:@* + +@verbatim +CONFIG_CONSOLE_USB=y (Console -> USB dongle console output) +@end verbatim + +Also Debugging ---> Output verbose XYZ ) (@strong{FIXME} somebody verify these): + +@verbatim +CONFIG_DEBUG_CBFS=y (Output verbose CBFS debug messages ) +CONFIG_HAVE_DEBUG_RAM_SETUP=y (??? What/where is this) +CONFIG_DEBUG_RAM_SETUP=y (Output verbose RAM init debug messages) +CONFIG_DEBUG_SMI=y (Output verbose SMI debug messages) +CONFIG_DEBUG_ACPI=y (Output verbose ACPI debug messages ) +CONFIG_DEBUG_USBDEBUG=y (Output verbose USB 2.0 EHCI debug dongle messages) +@end verbatim + +If some of the above mentioned configuration options are not as specified, you have to configure and compile libreboot yourself. Please refer to the doc(@strong{FIXME: link} about compiling libreboot. +@menu +* Selecting HCD Index and USB Debug port:: +@end menu + +@node Selecting HCD Index and USB Debug port +@subsubsection Selecting HCD Index and USB Debug port +@anchor{#selecting-hcd-index-and-usb-debug-port} +This applies (and works) only if the USB controller that supports debug (found in the first section) is from Intel.@*If the PCI ID of the port you found in the first section is 0000:00:1a.0 or 0000:00:1d.0 , you are ok. Otherwise you have to try without guarantee that will work. + +If the externally exposed port is on a bus with PCI ID == 0000:00:1a.0 then for CONFIG_USBDEBUG_HCD_INDEX choose 2, otherwise choose 0 . + +For CONFIG_USBDEBUG_DEFAULT_PORT choose the port from the first section that correspond to the PCI ID + +Notes:@*The above is based on the implementation of coreboot/src/southbridge/intel/common/usb_debug.c : pci_ehci_dbg_dev() .@*This is enough as it applies for the supported GM45/G45 Thinkpads. coreboot support some other contollers too, but they are irellevent for libreboot (for now). + +@itemize +@item +On T500 (with switchable GPU) the debug ports for both intel controllers is exposed. +@item +On x200t the debug ports for both intel controllers is exposed. +@end itemize + +@node How to get the debug logs +@subsection How to get the debug logs +@anchor{#how-to-get-the-debug-logs} +@itemize +@item +Plug the USB cable in the target's debug port (the one you found in step 1) and BBB's mini-B USB +@item +Make sure no other then g_dbgp of the g_* modules is loaded on your BBB +@item +On the BBB: +@end itemize + +@verbatim +stty -icrnl -inlcr -F /dev/ttyGS0 +cat /dev/ttyGS0 +@end verbatim + +@itemize +@item +Power on the target with libreboot +@item +You should see debug logs comming on your BBB console +@end itemize + +Note that this is not permanent on BBB, if you reboot it, you have to rmmod g_* and modprobe g_dbgp + +@node Eneble EHCI Debug on the target's kernel optional recommended +@subsection Eneble EHCI Debug on the target's kernel (optional, recommended) +@anchor{#eneble-ehci-debug-on-the-targets-kernel-optional-recommended} +You have to know how to compile kernel for your target. + +@enumerate +@item +Check if early debugging is already enabled: grep CONFIG_EARLY_PRINTK_DBGP /boot/config-<ver> +@item +If enabled, you do not have to compile the kernel (skip this step). Otherwise, prepare kernel source for your distribution and select (Kernel hacking -> Early printk via EHCI debug port). Compile and install the new kernel. +@item +Edit your grub configuration and add following to the kenel parameters@textsuperscript{@ref{#___fn20,20}}@textsuperscript{@ref{#___fn21,21}}: earlyprintk=dbgp,keep. Also, try: earlyprintk=dbgp<N>,keep where N is the debug port id if the first does not work. +@end enumerate + +@node References +@subsection References +@anchor{#references} +@textsuperscript{10} @uref{http://www.coreboot.org/EHCI_Debug_Port,EHCI Debug Port} + +@textsuperscript{11} @uref{https://johnlewis.ie/coreboot-ehci-debug-gadget-demonstration/,coreboot EHCI debug gadget demonstration} + +@textsuperscript{12} @uref{http://www.coreboot.org/EHCI_Gadget_Debug,EHCI Gadget Debug} + +@textsuperscript{13} @uref{http://www.coreboot.org/images/8/88/Ehci-debug-gadget-patches.tar.gz,Ehci-debug-gadget-patches.tar.gz} + +@textsuperscript{14} @uref{http://wiki.beyondlogic.org/index.php/BeagleBoneBlack_Building_Kernel,Compiling the BeagleBone Black Kernel} + +@textsuperscript{15} http://dumb-looks-free.blogspot.ca/2014/06/beaglebone-black-bbb-compile-kernel.html + +@textsuperscript{16} http://dumb-looks-free.blogspot.fr/2014/06/beaglebone-black-bbb-kernal-headers.html + +@textsuperscript{17} @uref{http://elinux.org/Building_BBB_Kernel,Building BBB Kernel} + +@textsuperscript{18} http://komposter.com.ua/documents/USB-2.0-Debug-Port%28John-Keys%29.pdf + +@textsuperscript{19} @uref{http://cs.usfca.edu/~cruse/cs698s10/,Exploring USB at the Hardware/Software Interface} + +@textsuperscript{20} https://www.kernel.org/doc/Documentation/x86/earlyprintk.txt + +@textsuperscript{21} https://wiki.ubuntu.com/Kernel/Debugging/USBearlyprintk + +@strong{TODO}: + +@enumerate +@item +grub does not send messages to EHCI debug. Investigate. +@item +The section “Configure libreboot with EHCI debug” can be skipped/simplified if a common configuration works for all relevant targets is selected as defualt +@item +Patch and compule g_dbgp on BBB instead cross-compile +@item +Find a simple way to send debug messages from targets userland +@end enumerate + +Copyright © 2015 Alex David <opdecirkel@@gmail.com>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye diff --git a/docs/install/bbb_setup.html b/docs/install/bbb_setup.html deleted file mode 100644 index f3f93d5..0000000 --- a/docs/install/bbb_setup.html +++ /dev/null @@ -1,469 +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</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">How to program an SPI flash chip with the BeagleBone Black</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. - BeagleBone Black rev. C was used when creating this guide, but earlier revisions - may also work. - </p> - <p><a href="index.html">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> - External SPI programmer: <b>BeagleBone Black</b> (rev. C) - is highly recommended. Sometimes referred to as 'BBB'. - <a href="http://beagleboard.org/black">This page</a> contains a list of distributors. - farnell sells them - <a href="http://farnell.com/">http://farnell.com/</a> - - If you can't get a BBB, there are other programmers listed on flashrom.org, but - not all of them will be suitable for libreboot's purpose. (some may also require blobs. all BBs and BBBs though can be used without blobs). - There are also some programmers not listed on flashrom.org, that can also work. - A BB (original beaglebone) should work as well, though you might have to replace the distro - that it came with. - </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. - easy to find in most hardware/electronics stores - </li> - <li> - Clip for connecting to the flash chip: if you have a SOIC-16 - flash chip (16 pins), you will need the <b>Pomona 5252</b> - or equivalent. For SOIC-8 flash chips (8 pins), you will - need the <b>Pomona 5250</b> or equivalent. Do check which chip you have, - before ordering a clip. Also, make sure to buy at least two clips - (they break easily). - - Farnell sells these, and ships to many countries. <a href="http://farnell.com/">http://farnell.com/</a> - - Some people find these difficult to get, especially in South America. If you have more links to suppliers, - please contact the libreboot project with the relevant information. - - <b>if you can't get a pomona clip, some other clips might work (eg 3M) but 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.</b> - </li> - <li> - <b>External 3.3V DC power supply</b>, 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). Etc. - <ul> - <li>Getting a multimeter might be worthwhile, to verify that it's supplying 3.3V</li> - </ul> - </li> - <li> - <b>External 5V DC power supply</b> (barrel connector), for powering the BBB. - The BeagleBone 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. - <b>OPTIONAL. Only needed if not powering with the USB cable, or if you want - to use <a href="bbb_ehci.html">EHCI debug</a></b> - </li> - <li> - <b>Pin header / jumper cables</b> (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: - <ul> - <li>flying leads</li> - <li>dupont (this is just one possible brand name)</li> - <li>Often used on breadboards, so they might be called breadboard cables</li> - <li>Maybe they are called <b>wires</b> instead of cables or leads</li> - <li>They are also the same cables used on the GPIOs on the RPi</li> - <li><b>adafruit.com</b> sells them, and there are others</li> - <li><b>Some people find these difficult to buy. Contact the libreboot project if you have more links to sellers.</b></li> - <li>You might also be able to make these cables yourself.</li> - </ul> - For PSU connections, long cables (e.g. 20cm) is fine, and you can extend it 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="bbb_ehci.html">EHCI debug</a> or for serial/ssh access without ethernet cable (g_multi kernel module)</b> - </li> - <li> - <b>FTDI TTL cable or debug board</b>, for accessing the serial console on your BBB. - <a href="http://elinux.org/Beagleboard:BeagleBone_Black_Serial">This page</a> contains - a list. - <b>OPTIONAL - only needed for serial console on the BBB, if not using SSH via ethernet cable</b> - </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 are on <a href="https://en.wikipedia.org/wiki/Power_supply_unit_%28computer%29#Wiring_diagrams">wikipedia</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> - <b>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 take 3.3V)</b> - </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 Francis Rowe <info@gluglug.org.uk><br/> - Copyright © 2015 Patrick "P. J." McDermott <pj@pehjota.net><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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.texi b/docs/install/bbb_setup.texi new file mode 100644 index 0000000..040885f --- /dev/null +++ b/docs/install/bbb_setup.texi @@ -0,0 +1,284 @@ +\input texinfo +@documentencoding UTF-8 + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title How to program an SPI flash chip with the BeagleBone Black +@end titlepage + +@node Top +@top How to program an SPI flash chip with the BeagleBone Black + +@menu +* How to program an SPI flash chip with the BeagleBone Black:: +* Hardware requirements:: +* Setting up the 33V DC PSU:: +* Accessing the operating system on the BBB:: +* Setting up spidev on the BBB:: +* Connecting the Pomona 5250/5252:: +* Notes about stability:: +@end menu + +@node How to program an SPI flash chip with the BeagleBone Black +@chapter How to program an SPI flash chip with the BeagleBone Black +@anchor{#how-to-program-an-spi-flash-chip-with-the-beaglebone-black} +This document exists as a guide for reading from or writing to an SPI flash chip with the BeagleBone Black, using the @uref{http://flashrom.org/Flashrom,flashrom} software. BeagleBone Black rev. C was used when creating this guide, but earlier revisions may also work. + +@uref{index.html,Back to previous index} + +@node Hardware requirements +@chapter Hardware requirements +@anchor{#hardware-requirements} +Shopping list (pictures of this hardware is shown later): + +@itemize +@item +External SPI programmer: @strong{BeagleBone Black} (rev. C) is highly recommended. Sometimes referred to as 'BBB'. @uref{http://beagleboard.org/black,This page} contains a list of distributors. farnell sells them - @uref{http://farnell.com/,http://farnell.com/} - If you can't get a BBB, there are other programmers listed on flashrom.org, but not all of them will be suitable for libreboot's purpose. (some may also require blobs. all BBs and BBBs though can be used without blobs). There are also some programmers not listed on flashrom.org, that can also work. A BB (original beaglebone) should work as well, though you might have to replace the distro that it came with. +@item +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. - easy to find in most hardware/electronics stores +@item +Clip for connecting to the flash chip: if you have a SOIC-16 flash chip (16 pins), you will need the @strong{Pomona 5252} or equivalent. For SOIC-8 flash chips (8 pins), you will need the @strong{Pomona 5250} or equivalent. Do check which chip you have, before ordering a clip. Also, make sure to buy at least two clips (they break easily). - Farnell sells these, and ships to many countries. @uref{http://farnell.com/,http://farnell.com/} - Some people find these difficult to get, especially in South America. If you have more links to suppliers, please contact the libreboot project with the relevant information. - @strong{if you can't get a pomona clip, some other clips might work (eg 3M) but 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.} +@item +@strong{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). Etc. +@itemize +@item +Getting a multimeter might be worthwhile, to verify that it's supplying 3.3V +@end itemize + +@item +@strong{External 5V DC power supply} (barrel connector), for powering the BBB. The BeagleBone 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 @uref{bbb_ehci.html,EHCI debug}} +@item +@strong{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: +@itemize +@item +flying leads +@item +dupont (this is just one possible brand name) +@item +Often used on breadboards, so they might be called breadboard cables +@item +Maybe they are called @strong{wires} instead of cables or leads +@item +They are also the same cables used on the GPIOs on the RPi +@item +@strong{adafruit.com} sells them, and there are others +@item +@strong{Some people find these difficult to buy. Contact the libreboot project if you have more links to sellers.} +@item +You might also be able to make these cables yourself. +@end itemize + +For PSU connections, long cables (e.g. 20cm) is fine, and you can extend it longer than that if needed. +@item +@strong{Mini USB A-B cable} (the BeagleBone probably already comes with one.) - @strong{OPTIONAL - only needed for @uref{bbb_ehci.html,EHCI debug} or for serial/ssh access without ethernet cable (g_multi kernel module)} +@item +@strong{FTDI TTL cable or debug board}, for accessing the serial console on your BBB. @uref{http://elinux.org/Beagleboard:BeagleBone_Black_Serial,This page} contains a list. - @strong{OPTIONAL - only needed for serial console on the BBB, if not using SSH via ethernet cable} +@end itemize + +@ref{#pagetop,Back to top of page.} + +@node Setting up the 33V DC PSU +@chapter Setting up the 3.3V DC PSU +@anchor{#setting-up-the-3.3v-dc-psu} +ATX PSU pinouts are on @uref{https://en.wikipedia.org/wiki/Power_supply_unit_%28computer%29#Wiring_diagrams,wikipedia} + +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). + +@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 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:@* @image{images/x200/psu33,,,,jpg} + +@node Accessing the operating system on the BBB +@chapter Accessing the operating system on the BBB +@anchor{#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. +@menu +* Alternatives to SSH in case SSH fails:: +@end menu + +@node Alternatives to SSH in case SSH fails +@section Alternatives to SSH (in case SSH fails) +@anchor{#alternatives-to-ssh-in-case-ssh-fails} +You can also use a serial FTDI debug board with GNU Screen, to access the serial console.@* # @strong{screen /dev/ttyUSB0 115200}@* Here are some example photos:@* @image{images/x200/ftdi,,,,jpg} @image{images/x200/ftdi_port,,,,jpg}@* + +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:@* # @strong{screen /dev/ttyACM0 115200} + +You can also access the uboot console, using the serial method instead of SSH. + +@node Setting up spidev on the BBB +@chapter Setting up spidev on the BBB +@anchor{#setting-up-spidev-on-the-bbb} +Log on as root on the BBB, using either SSH or a serial console as defined in @ref{#bbb_access,#bbb_access}. Make sure that you have internet access on your BBB. + +Follow the instructions at @uref{http://elinux.org/BeagleBone_Black_Enable_SPIDEV#SPI0,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 @uref{https://groups.google.com/forum/?_escaped_fragment_=msg/beagleboard/LPjCn4LEY2I/alozBGsbTJMJ#!msg/beagleboard/LPjCn4LEY2I/alozBGsbTJMJ,work around a bug} 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: + +@verbatim +#!/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 +@end verbatim + +Run @strong{apt-get update} and @strong{apt-get upgrade} then reboot the BBB, before continuing. + +Check that the firmware exists:@* # @strong{ls /lib/firmware/BB-SPI0-01-00A0.*}@* Output: + +@verbatim +/lib/firmware/BB-SPI0-01-00A0.dtbo +@end verbatim + +Then:@* # @strong{echo BB-SPI0-01 > /sys/devices/bone_capemgr.*/slots}@* # @strong{cat /sys/devices/bone_capemgr.*/slots}@* Output: + +@verbatim + 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 +@end verbatim + +Verify that the spidev device now exists:@* # @strong{ls -al /dev/spid*}@* Output: + +@verbatim +crw-rw---T 1 root spi 153, 0 Nov 19 21:07 /dev/spidev1.0 +@end verbatim + +Now the BBB is ready to be used for flashing. Make this persist across reboots:@* In /etc/default/capemgr add @strong{CAPE=BB-SPI0-01} at the end (or change the existing @strong{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:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512}@* Output: + +@verbatim +Calibrating delay loop... OK. +No EEPROM/flash device found. +Note: flashrom can never write if the flash chip isn't found automatically. +@end verbatim + +This means that it's working (the clip isn't connected to any flash chip, so the error is fine). + +@node Connecting the Pomona 5250/5252 +@chapter Connecting the Pomona 5250/5252 +@anchor{#connecting-the-pomona-52505252} +Use this image for reference when connecting the pomona to the BBB: @uref{http://beagleboard.org/Support/bone101#headers,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): + +@verbatim + 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 +@end verbatim + +The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): + +@verbatim + 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 +@end verbatim + +@strong{NC = no connection} + +@strong{DO NOT connect 3.3V (PSU) yet. ONLY connect this once the pomona is connected to the flash chip.} + +@strong{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, @strong{but} keep all other leads short (10cm or less) + +You should now have something that looks like this:@* @image{images/x200/5252_bbb0,,,,jpg} @image{images/x200/5252_bbb1,,,,jpg} + +@ref{#pagetop,Back to top of page.} + +@node Notes about stability +@chapter Notes about stability +@anchor{#notes-about-stability} +@uref{http://flashrom.org/ISP,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: + +@itemize +@item +"coax" with 0.1 mm core and aluminum foley (from my kitchen), add 100 Ohm resistors (serial) +@item +put heatshrink above the foley, for: CS, CLK, D0, D1 +@item +Twisted pair used as core (in case more capacitors are needed) +@item +See this image: @uref{http://i.imgur.com/qHGxKpj.jpg,http://i.imgur.com/qHGxKpj.jpg} +@item +He was able to flash at 50MHz (lower speeds are also fine). +@end itemize + +Copyright © 2014, 2015 Francis Rowe <info@@gluglug.org.uk>@* Copyright © 2015 Patrick "P. J." McDermott <pj@@pehjota.net>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye diff --git a/docs/install/c201.html b/docs/install/c201.html deleted file mode 100644 index d0a8085..0000000 --- a/docs/install/c201.html +++ /dev/null @@ -1,306 +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/index.html#build">../git/index.html#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> - </ul> - - <p> - <a href="../index.html">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/index.html#recovery_mode_screen">recovery mode screen</a> and <a href="../depthcharge/index.html#enabling_developer_mode">enabling developer mode</a> are available on the page dedicated to <a href="../depthcharge/index.html">depthcharge</a>. - </p> - - <p> - Once developer mode is enabled, the device will boot to the <a href="../depthcharge/index.html#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 <b>Ctrl</b>+<b>Alt</b>+<b>Previous</b>. The <b>Previous</b> 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/index.html#developer_mode_screen">developer mode screen</a> and to <a href="../depthcharge/index.html#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 7 screws to remove from the bottom of the device, as shown on the picture below. One is hidden under the top right pad. After removing the screws, the keyboard plastic part can be carefully detached from the rest. <b>Beware: there are cables attached to it!</b> 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 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-firmware-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 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-firmware-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> - - <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 GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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.texi b/docs/install/c201.texi new file mode 100644 index 0000000..2ed3506 --- /dev/null +++ b/docs/install/c201.texi @@ -0,0 +1,163 @@ +\input texinfo +@documentencoding UTF-8 + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title ASUS Chromebook C201 installation guide +@end titlepage + +@node Top +@top ASUS Chromebook C201 installation guide + +@menu +* ASUS Chromebook C201 installation guide:: +* Installing Libreboot to the SPI flash:: +@end menu + +@node ASUS Chromebook C201 installation guide +@chapter ASUS Chromebook C201 installation guide +@anchor{#asus-chromebook-c201-installation-guide} +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. + +@strong{If you are using libreboot_src or git, then make sure that you built the sources first (see @uref{../git/index.html#build,../git/index.html#build}).} + +Look at the @ref{#rom,list of ROM images} 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 @strong{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. + +@strong{Google's modified version of flashrom} is free software and its source code is made available by Google: @uref{https://chromium.googlesource.com/chromiumos/third_party/flashrom/,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. + +@itemize +@item +@ref{#root_chromeos,Gaining root privileges on ChromeOS} +@item +@ref{#preparing_device,Preparing the device for the installation} +@itemize +@item +@ref{#configuring_verified_boot_parameters,Configuring verified boot parameters} +@item +@ref{#removing_write_protect_screw,Removing the write protect screw} +@end itemize + +@item +@uref{,Installing Libreboot to the SPI flash} +@itemize +@item +@ref{#installing_libreboot_internally,Installing Libreboot internally, from the device} +@item +@ref{#installing_libreboot_externally,Installing Libreboot externally, with a SPI flash programmer} +@end itemize + +@end itemize + +@uref{../index.html,Back to main index} + +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. + +Instructions to access the @uref{../depthcharge/index.html#recovery_mode_screen,recovery mode screen} and @uref{../depthcharge/index.html#enabling_developer_mode,enabling developer mode} are available on the page dedicated to @uref{../depthcharge/index.html,depthcharge}. + +Once developer mode is enabled, the device will boot to the @uref{../depthcharge/index.html#developer_mode_screen,developer mode screen}. ChromeOS can be booted by waiting for 30 seconds (the delay is shortened in Libreboot) or by pressing @strong{Ctrl + D} + +After the system has booted, root access can be enabled by clicking on the @strong{Enable debugging features} link. A confirmation dialog will ask whether to proceed.@* After confirming by clicking @strong{Proceed}, the device will reboot and ask for the root password to set. Finally, the operation has to be confirmed by clicking @strong{Enable}. + +After setting the root password, it becomes possible to log-in as root. A tty prompt can be obtained by pressing @strong{Ctrl}+@strong{Alt}+@strong{Previous}. The @strong{Previous} key is the one on the top left of the keyboard. + +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. +@menu +* Configuring verified boot parameters:: +* Removing the write protect screw:: +@end menu + +@node Configuring verified boot parameters +@section Configuring verified boot parameters +@anchor{#configuring-verified-boot-parameters} +It is recommended to have access to the @uref{../depthcharge/index.html#developer_mode_screen,developer mode screen} and to @uref{../depthcharge/index.html#configuring_verified_boot_parameters,configure the following verified boot parameters}: + +@itemize +@item +Kernels signature verification: @emph{disabled} +@item +External media boot: @emph{enabled} +@end itemize + +Those changes can be reverted later, when the device is known to be in a working state. + +@node Removing the write protect screw +@section Removing the write protect screw +@anchor{#removing-the-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 @emph{read-only} part of the flash. + +To access the screw, the device has to be opened. There are 7 screws to remove from the bottom of the device, as shown on the picture below. One is hidden under the top right pad. After removing the screws, the keyboard plastic part can be carefully detached from the rest. @strong{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. + +@uref{images/c201/screws.jpg,@image{images/c201/screws,,,Screws,jpg}} @uref{images/c201/wp-screw.jpg,@image{images/c201/wp-screw,,,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. + +@node Installing Libreboot to the SPI flash +@chapter Installing Libreboot to the SPI flash +@anchor{#installing-libreboot-to-the-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 @emph{read-only} coreboot partition, that becomes writable after removing the write-protect screw. +@menu +* Installing Libreboot internally from the device:: +* Installing Libreboot externally with a SPI flash programmer:: +@end menu + +@node Installing Libreboot internally from the device +@section Installing Libreboot internally, from the device +@anchor{#installing-libreboot-internally-from-the-device} +Before installing Libreboot to the SPI flash internally, the device has to be reassembled. + +All the files from the @strong{veyron_speedy} release (or build) have to be transferred to the device. + +The SPI flash has to be read first:@* # @strong{flashrom -p host -r flash.img}@* @strong{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 @strong{cros-flash-replace} script has to be executed as such:@* # @strong{./cros-firmware-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:@* # @strong{flashrom -p host -w flash.img}@* + +You should also see within the output the following:@* @strong{"Verifying flash... VERIFIED."} + +Shut down. The device will now boot to Libreboot. + +@node Installing Libreboot externally with a SPI flash programmer +@section Installing Libreboot externally, with a SPI flash programmer +@anchor{#installing-libreboot-externally-with-a-spi-flash-programmer} +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 @strong{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. + +@uref{images/c201/spi-flash-layout.jpg,@image{images/c201/spi-flash-layout,,,SPI flash layout,jpg}} @uref{images/c201/battery-connector.jpg,@image{images/c201/battery-connector,,,Battery connector,jpg}} + +All the files from the @strong{veyron_speedy} release (or build) have to be transferred to the host. + +The SPI flash has to be read first (using the right spi programmer):@* # @strong{flashrom -p @emph{programmer} -r flash.img}@* @strong{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 @strong{cros-flash-replace} script has to be executed as such:@* # @strong{./cros-firmware-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):@* # @strong{flashrom -p @emph{programmer} -w flash.img}@* + +You should also see within the output the following:@* @strong{"Verifying flash... VERIFIED."} + +The device will now boot to Libreboot. + +@ref{#pagetop,Back to top of page.} + +Copyright © 2015 Paul Kocialkowski <contact@@paulk.fr>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye diff --git a/docs/install/index.html b/docs/install/index.html deleted file mode 100644 index 0482e35..0000000 --- a/docs/install/index.html +++ /dev/null @@ -1,519 +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> - <a href="../index.html">Back to previous index</a> - </p> - - </div> - - <div class="section"> - - <h2>Software methods</h2> - <ul> - <li><a href="#rom">List of ROM images in libreboot</a></li> - <li><a href="#flashrom">How to update or install libreboot (if you are already running libreboot or coreboot)</a></li> - <li><a href="#flashrom">KFSN4-DRE: initial installation guide (if running the proprietary firmware or libreboot)</a></li> - <li><a href="#flashrom_lenovobios">ThinkPad X60/T60: Initial installation guide (if running the proprietary firmware)</a></li> - <li><a href="#flashrom_macbook21">MacBook2,1: Initial installation guide (if running the proprietary firmware)</a></li> - <li><a href="c201.html">ASUS Chromebook C201 installation guide</a> (Installing Libreboot internally, from the device)</li> - </ul> - - <h2>Hardware methods</h2> - <ul> - <li><a href="bbb_setup.html">How to program an SPI flash chip with the BeagleBone Black</a></li> - <li><a href="bbb_ehci.html">How to configure EHCI debugging on the BeagleBone Black</a></li> - <li><a href="kgpe-d16.html">KGPE-D16 (needed if running the proprietary firmware, or to unbrick)</a></li> - <li><a href="x60_unbrick.html">ThinkPad X60: Recovery guide</a></li> - <li><a href="x60tablet_unbrick.html">ThinkPad X60 Tablet: Recovery guide</a></li> - <li><a href="t60_unbrick.html">ThinkPad T60: Recovery guide</a></li> - <li><a href="x200_external.html">ThinkPad X200/X200S/X200T (needed if running the proprietary firmware, or to unbrick)</a></li> - <li><a href="r400_external.html">ThinkPad R400 (needed if running the proprietary firmware, or to unbrick)</a></li> - <li><a href="r500_external.html">ThinkPad R500 (needed if running the proprietary firmware, or to unbrick)</a></li> - <li><a href="t400_external.html">ThinkPad T400 (needed if running the proprietary firmware, or to unbrick)</a></li> - <li><a href="t500_external.html">ThinkPad T500 (needed if running the proprietary firmware, or to unbrick)</a></li> - <li><a href="c201.html">ASUS Chromebook C201 installation guide</a> (Installing Libreboot externally, with a SPI flash programmer)</li> - </ul> - - </div> - - <div class="section"> - - <h1 id="rom">List of ROM images in libreboot</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/index.html#grub_keyboard">../grub/index.html#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/index.html#build">../git/index.html#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>, - R500 users refer to <a href="r500_external.html">r500_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>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/R500/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 (00:F5:F0:40:71:FE), 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> - - <p> - <b> - R500 users: your laptop lacks a GbE region, because it has a different NIC. You do not need to change the MAC - address on this laptop; it will already be correct. You can simply flash the available ROM images for the R500, as-is. - See <a href="../hcl/r500.html#nogbe">../hcl/r500.html#nogbe</a>. - </b> - </p> - - <h2>Flash chip size</h2> - - <p> - Use this to find out:<br/> - # <b>dmidecode | grep ROM\ Size</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/index.html#supported_t60_list">../hcl/index.html#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/index.html#build">../git/index.html#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. - Apply this patch to the BASH script named <i>flash</i> (this is the script for flashing - libreboot into your X60): <a href="x60flashscript.patch">x60flashscript.patch</a>. - This patch is merged in the main git repository, and in all releases after 20150518. - </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/index.html#macbook11">../hcl/index.html#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/index.html#macbook21">../hcl/index.html#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/index.html#build">../git/index.html#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 Francis Rowe <info@gluglug.org.uk><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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.texi b/docs/install/index.texi new file mode 100644 index 0000000..de443d3 --- /dev/null +++ b/docs/install/index.texi @@ -0,0 +1,274 @@ +\input texinfo +@documentencoding UTF-8 + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title Installing libreboot +@end titlepage + +@node Top +@top Installing libreboot + +@menu +* Installing libreboot:: +* List of ROM images in libreboot:: +* How to update or install libreboot if you are already running libreboot or coreboot:: +* ThinkPad X60/T60 Initial installation guide if running the proprietary firmware:: +* MacBook21 Initial installation guide if running the proprietary firmware:: +@end menu + +@node Installing libreboot +@chapter Installing libreboot +@anchor{#installing-libreboot} +This section relates to installing libreboot on supported targets. + +@uref{../index.html,Back to previous index} +@menu +* Software methods:: +* Hardware methods:: +@end menu + +@node Software methods +@section Software methods +@anchor{#software-methods} +@itemize +@item +@ref{#rom,List of ROM images in libreboot} +@item +@ref{#flashrom,How to update or install libreboot (if you are already running libreboot or coreboot)} +@item +@ref{#flashrom,KFSN4-DRE: initial installation guide (if running the proprietary firmware or libreboot)} +@item +@ref{#flashrom_lenovobios,ThinkPad X60/T60: Initial installation guide (if running the proprietary firmware)} +@item +@ref{#flashrom_macbook21,MacBook2,1: Initial installation guide (if running the proprietary firmware)} +@item +@uref{c201.html,ASUS Chromebook C201 installation guide} (Installing Libreboot internally, from the device) +@end itemize + +@node Hardware methods +@section Hardware methods +@anchor{#hardware-methods} +@itemize +@item +@uref{bbb_setup.html,How to program an SPI flash chip with the BeagleBone Black} +@item +@uref{bbb_ehci.html,How to configure EHCI debugging on the BeagleBone Black} +@item +@uref{kgpe-d16.html,KGPE-D16 (needed if running the proprietary firmware, or to unbrick)} +@item +@uref{x60_unbrick.html,ThinkPad X60: Recovery guide} +@item +@uref{x60tablet_unbrick.html,ThinkPad X60 Tablet: Recovery guide} +@item +@uref{t60_unbrick.html,ThinkPad T60: Recovery guide} +@item +@uref{x200_external.html,ThinkPad X200/X200S/X200T (needed if running the proprietary firmware, or to unbrick)} +@item +@uref{r400_external.html,ThinkPad R400 (needed if running the proprietary firmware, or to unbrick)} +@item +@uref{r500_external.html,ThinkPad R500 (needed if running the proprietary firmware, or to unbrick)} +@item +@uref{t400_external.html,ThinkPad T400 (needed if running the proprietary firmware, or to unbrick)} +@item +@uref{t500_external.html,ThinkPad T500 (needed if running the proprietary firmware, or to unbrick)} +@item +@uref{c201.html,ASUS Chromebook C201 installation guide} (Installing Libreboot externally, with a SPI flash programmer) +@end itemize + +@node List of ROM images in libreboot +@chapter List of ROM images in libreboot +@anchor{#list-of-rom-images-in-libreboot} +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: @strong{_@emph{keymap}_@emph{mode}.rom} + +Available @emph{modes}: @strong{vesafb} or @strong{txtmode}. The @emph{vesafb} ROM images are recommended, in most cases; @emph{txtmode} ROM images come with MemTest86+, which requires text-mode instead of the usual framebuffer used by coreboot native graphics initialization. + +@emph{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 @uref{../grub/index.html#grub_keyboard,../grub/index.html#grub_keyboard} +@menu +* QEMU:: +@end menu + +@node QEMU +@section QEMU +@anchor{#qemu} +Libreboot comes with ROM images built for QEMU, by default: + +Examples of how to use libreboot ROM images in QEMU: + +@itemize +@item +$ @strong{qemu-system-i386 -M q35 -m 512 -bios qemu_q35_ich9_keymap_mode.rom} +@item +$ @strong{qemu-system-i386 -M pc -m 512 -bios qemu_i440fx_piix4_keymap_mode.rom} +@end itemize + +You can optionally specify the @strong{-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. + +@ref{#pagetop,Back to top of page.} + +@node How to update or install libreboot if you are already running libreboot or coreboot +@chapter How to update or install libreboot (if you are already running libreboot or coreboot) +@anchor{#how-to-update-or-install-libreboot-if-you-are-already-running-libreboot-or-coreboot} +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. + +@strong{If you are using libreboot_src or git, then make sure that you built the sources first (see @uref{../git/index.html#build,../git/index.html#build}).} + +Look at the @ref{#rom,list of ROM images} to see which image is compatible with your device. +@menu +* Are you currently running the original proprietary firmware?:: +* ASUS KFSN4-DRE?:: +* ASUS KGPE-D16?:: +* Are you currently running libreboot or coreboot?:: +* MAC address on GM45 X200/R400/T400/T500:: +* Flash chip size:: +* All good?:: +@end menu + +@node Are you currently running the original proprietary firmware? +@section Are you currently running the original, proprietary firmware? +@anchor{#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 @ref{#flashrom_lenovobios,#flashrom_lenovobios}. MacBook2,1 users running Apple EFI should refer to @ref{#flashrom_macbook21,#flashrom_macbook21} + +X200 users, refer to @uref{x200_external.html,x200_external.html}, R400 users refer to @uref{r400_external.html,r400_external.html}, R500 users refer to @uref{r500_external.html,r500_external.html}, T400 users refer to @uref{t400_external.html,t400_external.html}, T500 users refer to @uref{t500_external.html,t500_external.html} + +@node ASUS KFSN4-DRE? +@section ASUS KFSN4-DRE? +@anchor{#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. + +@strong{DO NOT hot-swap the chip with your bare hands. Use a PLCC chip extractor. These can be found online. See @uref{http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools,http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools}} + +Do check the HCL entry: @uref{../hcl/kfsn4-dre.html,../hcl/kfsn4-dre.html} + +@node ASUS KGPE-D16? +@section ASUS KGPE-D16? +@anchor{#asus-kgpe-d16} +If you have the proprietary BIOS, you need to flash libreboot externally. See @uref{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). + +@strong{DO NOT hot-swap the chip with your bare hands. Use a PDIP-8 chip extractor. These can be found online. See @uref{http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools,http://www.coreboot.org/Developer_Manual/Tools#Chip_removal_tools}} + +Do check the HCL entry: @uref{../hcl/kgpe-d16.html,../hcl/kgpe-d16.html} + +@node Are you currently running libreboot or coreboot? +@section Are you currently running libreboot (or coreboot)? +@anchor{#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 @uref{x60_unbrick.html,x60_unbrick.html}, @uref{x60tablet_unbrick.html,x60tablet_unbrick.html} or @uref{t60_unbrick.html,t60_unbrick.html}. @emph{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/R500/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 (@strong{@emph{libreboot does not write-protect the flash chip by default, so this probably applies to you}}), read on! + +@node MAC address on GM45 X200/R400/T400/T500 +@section MAC address on GM45 (X200/R400/T400/T500) +@anchor{#mac-address-on-gm45-x200r400t400t500} +@strong{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 (00:F5:F0:40:71:FE), but this is not what you want. @emph{Make sure to change the MAC address inside the ROM image, before flashing it. The instructions on @uref{../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. + +@strong{R500 users: your laptop lacks a GbE region, because it has a different NIC. You do not need to change the MAC address on this laptop; it will already be correct. You can simply flash the available ROM images for the R500, as-is. See @uref{../hcl/r500.html#nogbe,../hcl/r500.html#nogbe}.} + +@node Flash chip size +@section Flash chip size +@anchor{#flash-chip-size} +Use this to find out:@* # @strong{dmidecode | grep ROM\ Size} + +@node All good? +@section All good? +@anchor{#all-good} +Excellent! Moving on... + +Download the @emph{libreboot_util.tar.xz} archive, and extract it. Inside, you will find a directory called @emph{flashrom}. This contains statically compiled executable files of the @emph{flashrom} utility, which you will use to re-flash your libreboot system. + +Simply use @emph{cd} on your terminal, to switch to the @emph{libreboot_util} directory. Inside, there is a script called @emph{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. + +How to update the flash chip contents:@* $ @strong{sudo ./flash update @ref{#rom,yourrom.rom}} + +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:@* $ @strong{sudo ./flash forceupdate @ref{#rom,yourrom.rom}} + +You should see @strong{"Verifying flash... VERIFIED."} written at the end of the flashrom output. @strong{Shut down} after you see this, and then boot up again after a few seconds. + +@ref{#pagetop,Back to top of page} + +@node ThinkPad X60/T60 Initial installation guide if running the proprietary firmware +@chapter ThinkPad X60/T60: Initial installation guide (if running the proprietary firmware) +@anchor{#thinkpad-x60t60-initial-installation-guide-if-running-the-proprietary-firmware} +@strong{This is for the ThinkPad X60 and T60 while running Lenovo BIOS. If you already have coreboot or libreboot running, then go to @ref{#flashrom,#flashrom} instead!} + +@strong{If you are flashing a Lenovo ThinkPad T60, be sure to read @uref{../hcl/index.html#supported_t60_list,../hcl/index.html#supported_t60_list}} + +@strong{If you are using libreboot_src or git, then make sure that you built the sources first (see @uref{../git/index.html#build,../git/index.html#build}).} + +@strong{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 @uref{http://www.coreboot.org/Board:lenovo/x60/Installation,http://www.coreboot.org/Board:lenovo/x60/Installation}.} + +@strong{If you're using libreboot 20150518, note that there is a mistake in the flashing script. Apply this patch to the BASH script named @emph{flash} (this is the script for flashing libreboot into your X60): @uref{x60flashscript.patch,x60flashscript.patch}. This patch is merged in the main git repository, and in all releases after 20150518.} + +The first half of the procedure is as follows:@* $ @strong{sudo ./flash i945lenovo_firstflash @ref{#rom,yourrom.rom}.} + +You should see within the output the following:@* @strong{"Updated BUC.TS=1 - 64kb address ranges at 0xFFFE0000 and 0xFFFF0000 are swapped"}. + +You should also see within the output the following:@* @strong{"Your flash chip is in an unknown state"}, @strong{"FAILED"} and @strong{"DO NOT REBOOT OR POWEROFF"}@* Seeing this means that the operation was a @strong{resounding} success! @strong{DON'T PANIC}. + +See this link for more details: @uref{http://thread.gmane.org/gmane.linux.bios.flashrom/575,http://thread.gmane.org/gmane.linux.bios.flashrom/575}. + +If the above is what you see, then @strong{SHUT DOWN}. Wait a few seconds, and then boot; libreboot is running, but there is a 2nd procedure @strong{*needed*} (see below). + +When you have booted up again, you must also do this:@* $ @strong{sudo ./flash i945lenovo_secondflash @ref{#rom,yourrom.rom}} + +If flashing fails at this stage, try the following:@* $ @strong{sudo ./flashrom/i686/flashrom -p internal:laptop=force_I_want_a_brick -w @ref{#rom,yourrom.rom}} + +You should see within the output the following:@* @strong{"Updated BUC.TS=0 - 128kb address range 0xFFFE0000-0xFFFFFFFF is untranslated"} + +You should also see within the output the following:@* @strong{"Verifying flash... VERIFIED."} + +@ref{#pagetop,Back to top of page.} + +@node MacBook21 Initial installation guide if running the proprietary firmware +@chapter MacBook2,1: Initial installation guide (if running the proprietary firmware) +@anchor{#macbook21-initial-installation-guide-if-running-the-proprietary-firmware} +@strong{If you have a MacBook1,1, refer to @uref{../hcl/index.html#macbook11,../hcl/index.html#macbook11} for flashing instructions.} + +@strong{This is for the MacBook2,1 while running Apple EFI firmware. If you already have coreboot or libreboot running, then go to @ref{#flashrom,#flashrom} instead!} + +Be sure to read the information in @uref{../hcl/index.html#macbook21,../hcl/index.html#macbook21}. + +@strong{Warning: this guide will not instruct the user how to backup the original Apple EFI firmware. For that, please refer to @uref{http://www.coreboot.org/Board:apple/macbook21,http://www.coreboot.org/Board:apple/macbook21}.} + +@strong{If you are using libreboot_src or git, then make sure that you built the sources first (see @uref{../git/index.html#build,../git/index.html#build}).} + +Look at the @ref{#rom,list of ROM images} to see which image is compatible with your device. + +Use this flashing script, to install libreboot:@* $ @strong{sudo ./flash i945apple_firstflash @ref{#rom,yourrom.rom}} + +You should also see within the output the following:@* @strong{"Verifying flash... VERIFIED."} + +Shut down. + +@ref{#pagetop,Back to top of page.} + +Copyright © 2014, 2015 Francis Rowe <info@@gluglug.org.uk>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye diff --git a/docs/install/kgpe-d16.html b/docs/install/kgpe-d16.html deleted file mode 100644 index 6ddb78d..0000000 --- a/docs/install/kgpe-d16.html +++ /dev/null @@ -1,125 +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 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> - <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> - 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="index.html">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 Francis Rowe <info@gluglug.org.uk><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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.texi b/docs/install/kgpe-d16.texi new file mode 100644 index 0000000..5405a66 --- /dev/null +++ b/docs/install/kgpe-d16.texi @@ -0,0 +1,66 @@ +\input texinfo +@documentencoding UTF-8 + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title KGPE-D16 external flashing instructions +@end titlepage + +@node Top +@top KGPE-D16 external flashing instructions + +@menu +* KGPE-D16 external flashing instructions:: +* KGPE-D16 boards and full systems with libreboot preinstalled:: +* External programmer:: +@end menu + +@node KGPE-D16 external flashing instructions +@chapter KGPE-D16 external flashing instructions +@anchor{#kgpe-d16-external-flashing-instructions} +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. + +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. + +For more general information about this board, refer to @uref{../hcl/kgpe-d16.html,../hcl/kgpe-d16.html}. + +TODO: show photos here, and other info. + +@itemize +@item +@ref{#preinstall,KGPE-D16 boards (and full systems) with libreboot preinstalled} +@item +@ref{#programmer,External programmer} +@end itemize + +@uref{index.html,Back to main index} + +@node KGPE-D16 boards and full systems with libreboot preinstalled +@chapter KGPE-D16 boards (and full systems) with libreboot preinstalled +@anchor{#kgpe-d16-boards-and-full-systems-with-libreboot-preinstalled} +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 @uref{../../suppliers,suppliers} page for more information. + +@node External programmer +@chapter External programmer +@anchor{#external-programmer} +Refer to @uref{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. @strong{DO NOT} remove the chip with your hands. Use a chip extractor tool. + +Copyright © 2015 Francis Rowe <info@@gluglug.org.uk>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye diff --git a/docs/install/r400_external.html b/docs/install/r400_external.html deleted file mode 100644 index c5024d5..0000000 --- a/docs/install/r400_external.html +++ /dev/null @@ -1,599 +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="index.html">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"> - - <h1 id="lcd_compatibility">LCD compatibly</h1> - <p> - Not all LCD panels are compatible yet. See <a href="../hcl/gm45_lcd.html">../hcl/gm45_lcd.html</a>. - </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> - Although blocked by lenovobios (as was reported), it is reported that there are quad-core CPUs - for GM45. This laptop has socketed CPUs, so it might be possible to use them - (they are untested in coreboot; support may have to be added). - Core 2 Quad Q9000, Q9100 or QX9300. - </p> - - <p> - Look at this link:<br/> - <a href="https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors">https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors</a> - </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>dmidecode | grep ROM\ Size</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/index.html#recommended_wifi">../hcl/index.html#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> - 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/index.html">install GNU/Linux</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Francis Rowe <info@gluglug.org.uk><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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.texi b/docs/install/r400_external.texi new file mode 100644 index 0000000..dd8ee94 --- /dev/null +++ b/docs/install/r400_external.texi @@ -0,0 +1,296 @@ +\input texinfo +@documentencoding UTF-8 + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title ThinkPad R400: flashing tutorial (BeagleBone Black) +@end titlepage + +@node Top +@top ThinkPad R400: flashing tutorial (BeagleBone Black) + +@menu +* Flashing the R400 with a BeagleBone Black:: +* Libreboot T400:: +* LCD compatibly:: +* A note about CPUs:: +* A note about GPUs:: +* CPU paste required:: +* Flash chip size:: +* MAC address:: +* Initial BBB configuration:: +* Thermal paste IMPORTANT:: +* Wifi:: +* WWAN:: +* Memory:: +@end menu + +@node Flashing the R400 with a BeagleBone Black +@chapter Flashing the R400 with a BeagleBone Black +@anchor{#flashing-the-r400-with-a-beaglebone-black} +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) + +@uref{index.html,Back to main index} + +@node Libreboot T400 +@chapter Libreboot T400 +@anchor{#libreboot-t400} +You may also be interested in the smaller, more portable @uref{t400_external.html,Libreboot T400}. +@menu +* Serial port:: +@end menu + +@node Serial port +@section Serial port +@anchor{#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. + +@node LCD compatibly +@chapter LCD compatibly +@anchor{#lcd-compatibly} +Not all LCD panels are compatible yet. See @uref{../hcl/gm45_lcd.html,../hcl/gm45_lcd.html}. + +@node A note about CPUs +@chapter A note about CPUs +@anchor{#a-note-about-cpus} +@uref{http://www.thinkwiki.org/wiki/Category:R400,ThinkWiki} 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. @strong{The Core 2 Duo T5870/5670 and Celeron M 575/585 are untested!} +@menu +* Quad-core CPUs:: +@end menu + +@node Quad-core CPUs +@section Quad-core CPUs +@anchor{#quad-core-cpus} +Although blocked by lenovobios (as was reported), it is reported that there are quad-core CPUs for GM45. This laptop has socketed CPUs, so it might be possible to use them (they are untested in coreboot; support may have to be added). Core 2 Quad Q9000, Q9100 or QX9300. + +Look at this link:@* @uref{https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors,https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors} + +@node A note about GPUs +@chapter A note about GPUs +@anchor{#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 @emph{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. + +@node CPU paste required +@chapter CPU paste required +@anchor{#cpu-paste-required} +See @ref{#paste,#paste}. + +@node Flash chip size +@chapter Flash chip size +@anchor{#flash-chip-size} +Use this to find out:@* # @strong{dmidecode | grep ROM\ Size}@* + +@ref{#pagetop,Back to top of page.} + +@node MAC address +@chapter MAC address +@anchor{#mac-address} +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: + +@image{images/t400/macaddress0,,,,jpg} @image{images/t400/macaddress1,,,,jpg} @image{images/x200/disassembly/0001,,,,jpg} + +@node Initial BBB configuration +@chapter Initial BBB configuration +@anchor{#initial-bbb-configuration} +Refer to @uref{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): + +@verbatim +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. +@end verbatim + +The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): + +@verbatim +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. +@end verbatim + +@menu +* Disassembly:: +@end menu + +@node Disassembly +@section Disassembly +@anchor{#disassembly} +Remove all screws:@* @image{images/r400/0000,,,,jpg}@* Remove the HDD and optical drive:@* @image{images/r400/0001,,,,jpg}@* Remove the hinge screws:@* @image{images/r400/0002,,,,jpg} @image{images/r400/0003,,,,jpg} + +Remove the palm rest and keyboard:@* @image{images/r400/0004,,,,jpg} @image{images/r400/0005,,,,jpg} + +Remove these screws, and then remove the bezel:@* @image{images/r400/0006,,,,jpg} @image{images/r400/0007,,,,jpg} + +Remove the speaker screws, but don't remove the speakers yet (just set them loose):@* @image{images/r400/0008,,,,jpg} @image{images/r400/0009,,,,jpg} @image{images/r400/0010,,,,jpg} + +Remove these screws, and then remove the metal plate:@* @image{images/r400/0011,,,,jpg} @image{images/r400/0012,,,,jpg} @image{images/r400/0013,,,,jpg} + +Remove the antennas from the wifi card, and then start unrouting them:@* @image{images/r400/0014,,,,jpg} @image{images/r400/0015,,,,jpg} @image{images/r400/0016,,,,jpg} @image{images/r400/0017,,,,jpg} @image{images/r400/0018,,,,jpg} @image{images/r400/0019,,,,jpg} + +Disconnect the LCD cable from the motherboard:@* @image{images/r400/0020,,,,jpg} @image{images/r400/0021,,,,jpg} @image{images/r400/0022,,,,jpg} @image{images/r400/0023,,,,jpg} + +Remove the hinge screws, and then remove the LCD panel:@* @image{images/r400/0024,,,,jpg} @image{images/r400/0025,,,,jpg} @image{images/r400/0026,,,,jpg} @image{images/r400/0027,,,,jpg} + +Remove this:@* @image{images/r400/0028,,,,jpg} @image{images/r400/0029,,,,jpg} + +Remove this long cable (there are 3 connections):@* @image{images/r400/0030,,,,jpg} @image{images/r400/0031,,,,jpg} @image{images/r400/0032,,,,jpg} @image{images/r400/0033,,,,jpg} + +Disconnect the speaker cable, and remove the speakers:@* @image{images/r400/0034,,,,jpg} + +Remove the heatsink screws, remove the fan and then remove the heatsink/fan:@* @image{images/r400/0035,,,,jpg} @image{images/r400/0036,,,,jpg} @image{images/r400/0037,,,,jpg} @image{images/r400/0038,,,,jpg} + +Remove the NVRAM battery:@* @image{images/r400/0039,,,,jpg} @image{images/r400/0040,,,,jpg} + +Remove this screw:@* @image{images/r400/0041,,,,jpg} @image{images/r400/0042,,,,jpg} + +Disconnect the AC jack:@* @image{images/r400/0043,,,,jpg} @image{images/r400/0044,,,,jpg} + +Remove this screw and then remove what is under it:@* @image{images/r400/0045,,,,jpg} + +Remove this:@* @image{images/r400/0046,,,,jpg} + +Lift the motherboard (which is still inside the cage) from the side on the right, removing it completely:@* @image{images/r400/0047,,,,jpg} @image{images/r400/0048,,,,jpg} + +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: @image{images/r400/0049,,,,jpg} @image{images/r400/0050,,,,jpg} + +Remove the motherboard from the cage, and the SPI flash chip will be next to the memory slots:@* @image{images/r400/0051,,,,jpg} @image{images/r400/0052,,,,jpg} + +Connect your programmer, then connect GND and 3.3V@* @image{images/t400/0065,,,,jpg} @image{images/t400/0066,,,,jpg} @image{images/t400/0067,,,,jpg} @image{images/t400/0069,,,,jpg} @image{images/t400/0070,,,,jpg} @image{images/t400/0071,,,,jpg} + +A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is also fine:@* @image{images/t400/0072,,,,jpg} + +Of course, make sure to turn on your PSU:@* @image{images/x200/disassembly/0013,,,,jpg} + +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 @uref{bbb_setup.html#bbb_access,bbb_setup.html#bbb_access}. + +Test that flashrom works:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512}@* In this case, the output was: + +@verbatim +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. +@end verbatim + +How to backup factory.rom (change the -c option as neeed, for your flash chip):@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom}@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom}@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom}@* Note: the @strong{-c} option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in @emph{flashchips.c} have been removed.@* Now compare the 3 images:@* # @strong{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 @uref{../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. @strong{Make sure to always change the MAC address to one that is correct for your system.} + +Now flash it:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V} + +@image{images/x200/disassembly/0015,,,,jpg} + +You might see errors, but if it says @strong{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 @strong{Chip content is identical to the requested image} is also an indication of a successful installation. + +Example output from running the command (see above): + +@verbatim +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. +@end verbatim + +@ref{#pagetop,Back to top of page.} + +@node Thermal paste IMPORTANT +@chapter Thermal paste (IMPORTANT) +@anchor{#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. + +@image{images/t400/paste,,,,jpg} + +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. + +@node Wifi +@chapter Wifi +@anchor{#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 @uref{../hcl/index.html#recommended_wifi,../hcl/index.html#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:@* @image{images/t400/0012,,,,jpg} @image{images/t400/ar5b95,,,,jpg} + +@node WWAN +@chapter WWAN +@anchor{#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). + +@node Memory +@chapter Memory +@anchor{#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. + +The following photo shows 8GiB (2x4GiB) of RAM installed:@* @image{images/t400/memory,,,,jpg} +@menu +* Boot it!:: +@end menu + +@node Boot it! +@section Boot it! +@anchor{#boot-it} +You should see something like this: + +@image{images/t400/boot0,,,,jpg} @image{images/t400/boot1,,,,jpg} + +Now @uref{../gnulinux/index.html,install GNU/Linux}. + +Copyright © 2014, 2015 Francis Rowe <info@@gluglug.org.uk>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye diff --git a/docs/install/r500_external.html b/docs/install/r500_external.html deleted file mode 100644 index 0360c09..0000000 --- a/docs/install/r500_external.html +++ /dev/null @@ -1,480 +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 R500: flashing tutorial (BeagleBone Black)</title> -</head> - -<body> - - <div class="section"> - <h1 id="pagetop">Flashing the R500 with a BeagleBone Black</h1> - <p>Initial flashing instructions for R500.</p> - <p> - This guide is for those who want libreboot on their ThinkPad R500 - while they still have the original Lenovo BIOS present. This guide - can also be followed (adapted) if you brick your R500, 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> - <b> - NOTE: This board is unsupported in libreboot 20150518. To use it in libreboot, for now, you - must build for it from source using the libreboot git repository. - </b> - </p> - - <p><a href="index.html">Back to main index</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"> - - <h1 id="lcd_compatibility">LCD compatibly</h1> - <p> - Not all LCD panels are known to be compatible yet. See <a href="../hcl/gm45_lcd.html">../hcl/gm45_lcd.html</a>. - </p> - - </div> - - <div class="section" id="cpu_compatibility"> - - <h1>A note about CPUs</h1> - <p> - <a href="http://www.thinkwiki.org/wiki/Category:R500">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 Core 2 Duo T9600 was confirmed to work (on a different laptop, but still GM45), 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> - Although blocked by lenovobios (as was reported), it is reported that there are quad-core CPUs - for GM45. This laptop has socketed CPUs, so it might be possible to use them - (they are untested in coreboot; support may have to be added). - Core 2 Quad Q9000, Q9100 or QX9300. - </p> - - <p> - Look at this link:<br/> - <a href="https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors">https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors</a> - </p> - - </div> - - <div class="section" id="switchable_graphics"> - - <h1>A note about GPUs</h1> - - <p> - <a href="http://www.thinkwiki.org/wiki/Category:R500">ThinkWiki</a> lists - two possible GPUs: Intel or ATI. Only the Intel GPUs work in libreboot; the ATI - GPUs require a proprietary Video BIOS, and so those are unsupported in libreboot. - </p> - <p> - On other GM45 laptops in libreboot (e.g. T400, T500), so-called <i>switchable graphics</i> - is used, which means that the laptop will have <b>both</b> an ATI and Intel GPU, or it will - only have Intel, depending on which variation you have. On the systems with ATI and Intel, - you can disable the ATI GPU and use only the Intel GPU, which works in libreboot. - </p> - <div class="important"> - <p> - <b> - It is unknown whether R500 laptops with an ATI GPU still have an Intel GPU, where you could - disable the ATI GPU and use the Intel GPU. These are budget laptops, so it's highly likely - that Lenovo decided on this model to ship with one GPU or the other, but not both (GPUs cost money). - </b> - </p> - <p> - <b> - It is **HIGHLY** recommended, when ordering an R500 laptop, to **ENSURE** that the - one you're ordering has an Intel GPU. - </b> - </p> - </div> - - <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>dmidecode | grep ROM\ Size</b><br> - </p> - <p> - It is believed that all R500 laptops have only SOIC-8 (4MiB) chips. - </p> - - <p> - <a href="#pagetop">Back to top of page.</a> - </p> - - </div> - - <div class="section photos"> - - <h1 id="macaddress">MAC address</h1> - - <p> - Unlike other GM45 thinkpads, the R500 has a different onboard gigabit NIC, - where the MAC address is built-in. You do not need to change the MAC address - at all on this laptop; simply flash the provided ROM images, as-is. - </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-8 (clip: Pomona 5250): - </p> -<pre> -POMONA 5250 (correlate with the BBB guide) -=== VGA and ethernet socket === - 18 - - 1 - 22 - - NC - NC - - 21 - 3.3V (PSU) - - 17 - this is pin 1 on the flash chip -=== DVD drive === -<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/r500/flashchip.jpg" alt="" /> -</pre> - - <h2 id="disassembly">Disassembly</h2> - - <p> - <img src="images/r500/0001.JPG" alt="" /> - <img src="images/r500/0002.JPG" alt="" /> - <img src="images/r500/0003.JPG" alt="" /> - <img src="images/r500/0004.JPG" alt="" /> - <img src="images/r500/0005.JPG" alt="" /> - <img src="images/r500/0006.JPG" alt="" /> - <img src="images/r500/0007.JPG" alt="" /> - <img src="images/r500/0008.JPG" alt="" /> - <img src="images/r500/0009.JPG" alt="" /> - <img src="images/r500/0010.JPG" alt="" /> - <img src="images/r500/0011.JPG" alt="" /> - <img src="images/r500/0012.JPG" alt="" /> - <img src="images/r500/0013.JPG" alt="" /> - <img src="images/r500/0014.JPG" alt="" /> - <img src="images/r500/0015.JPG" alt="" /> - <img src="images/r500/0016.JPG" alt="" /> - <img src="images/r500/0017.JPG" alt="" /> - <img src="images/r500/0018.JPG" alt="" /> - <img src="images/r500/0019.JPG" alt="" /> - <img src="images/r500/0020.JPG" alt="" /> - <img src="images/r500/0021.JPG" alt="" /> - <img src="images/r500/0022.JPG" alt="" /> - <img src="images/r500/0023.JPG" alt="" /> - <img src="images/r500/0024.JPG" alt="" /> - <img src="images/r500/0025.JPG" alt="" /> - <img src="images/r500/0026.JPG" alt="" /> - <img src="images/r500/0027.JPG" alt="" /> - <img src="images/r500/0028.JPG" alt="" /> - <img src="images/r500/0029.JPG" alt="" /> - <img src="images/r500/0030.JPG" alt="" /> - <img src="images/r500/0031.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/r500/0032.JPG" alt="" /> - <img src="images/r500/flashchip.jpg" alt="" /> - </p> - - <p> - The following image is for illustration only, to show how a SOIC-8 clip is connected. - This photo is from a T500, which has a different arrangement to the R500:<br/> - <img src="images/t500/0061.jpg" alt="" /> - </p> - <p> - Connect your programmer, then connect GND and 3.3V<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> - 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 Silver 5 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. AS5 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 R500 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/index.html#recommended_wifi">../hcl/index.html#recommended_wifi</a>. - </p> - - <p> - Some R500 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 R500 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> - 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/index.html">install GNU/Linux</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2015 Francis Rowe <info@gluglug.org.uk><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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/r500_external.texi b/docs/install/r500_external.texi new file mode 100644 index 0000000..1ff5d0a --- /dev/null +++ b/docs/install/r500_external.texi @@ -0,0 +1,241 @@ +\input texinfo +@documentencoding UTF-8 + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title ThinkPad R500: flashing tutorial (BeagleBone Black) +@end titlepage + +@node Top +@top ThinkPad R500: flashing tutorial (BeagleBone Black) + +@menu +* Flashing the R500 with a BeagleBone Black:: +* LCD compatibly:: +* A note about CPUs:: +* A note about GPUs:: +* CPU paste required:: +* Flash chip size:: +* MAC address:: +* Initial BBB configuration:: +* Thermal paste IMPORTANT:: +* Wifi:: +* WWAN:: +* Memory:: +@end menu + +@node Flashing the R500 with a BeagleBone Black +@chapter Flashing the R500 with a BeagleBone Black +@anchor{#flashing-the-r500-with-a-beaglebone-black} +Initial flashing instructions for R500. + +This guide is for those who want libreboot on their ThinkPad R500 while they still have the original Lenovo BIOS present. This guide can also be followed (adapted) if you brick your R500, 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) + +@strong{NOTE: This board is unsupported in libreboot 20150518. To use it in libreboot, for now, you must build for it from source using the libreboot git repository.} + +@uref{index.html,Back to main index} +@menu +* Serial port:: +@end menu + +@node Serial port +@section Serial port +@anchor{#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. + +@node LCD compatibly +@chapter LCD compatibly +@anchor{#lcd-compatibly} +Not all LCD panels are known to be compatible yet. See @uref{../hcl/gm45_lcd.html,../hcl/gm45_lcd.html}. + +@node A note about CPUs +@chapter A note about CPUs +@anchor{#a-note-about-cpus} +@uref{http://www.thinkwiki.org/wiki/Category:R500,ThinkWiki} has a list of CPUs for this system. The Core 2 Duo P8400, P8600 and P8700 are believed to work in libreboot. The Core 2 Duo T9600 was confirmed to work (on a different laptop, but still GM45), so the T9400 probably also works. @strong{The Core 2 Duo T5870/5670 and Celeron M 575/585 are untested!} +@menu +* Quad-core CPUs:: +@end menu + +@node Quad-core CPUs +@section Quad-core CPUs +@anchor{#quad-core-cpus} +Although blocked by lenovobios (as was reported), it is reported that there are quad-core CPUs for GM45. This laptop has socketed CPUs, so it might be possible to use them (they are untested in coreboot; support may have to be added). Core 2 Quad Q9000, Q9100 or QX9300. + +Look at this link:@* @uref{https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors,https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors} + +@node A note about GPUs +@chapter A note about GPUs +@anchor{#a-note-about-gpus} +@uref{http://www.thinkwiki.org/wiki/Category:R500,ThinkWiki} lists two possible GPUs: Intel or ATI. Only the Intel GPUs work in libreboot; the ATI GPUs require a proprietary Video BIOS, and so those are unsupported in libreboot. + +On other GM45 laptops in libreboot (e.g. T400, T500), so-called @emph{switchable graphics} is used, which means that the laptop will have @strong{both} an ATI and Intel GPU, or it will only have Intel, depending on which variation you have. On the systems with ATI and Intel, you can disable the ATI GPU and use only the Intel GPU, which works in libreboot. + +@strong{It is unknown whether R500 laptops with an ATI GPU still have an Intel GPU, where you could disable the ATI GPU and use the Intel GPU. These are budget laptops, so it's highly likely that Lenovo decided on this model to ship with one GPU or the other, but not both (GPUs cost money).} + +@strong{It is **HIGHLY** recommended, when ordering an R500 laptop, to **ENSURE** that the one you're ordering has an Intel GPU.} + +@node CPU paste required +@chapter CPU paste required +@anchor{#cpu-paste-required} +See @ref{#paste,#paste}. + +@node Flash chip size +@chapter Flash chip size +@anchor{#flash-chip-size} +Use this to find out:@* # @strong{dmidecode | grep ROM\ Size}@* + +It is believed that all R500 laptops have only SOIC-8 (4MiB) chips. + +@ref{#pagetop,Back to top of page.} + +@node MAC address +@chapter MAC address +@anchor{#mac-address} +Unlike other GM45 thinkpads, the R500 has a different onboard gigabit NIC, where the MAC address is built-in. You do not need to change the MAC address at all on this laptop; simply flash the provided ROM images, as-is. + +@node Initial BBB configuration +@chapter Initial BBB configuration +@anchor{#initial-bbb-configuration} +Refer to @uref{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-8 (clip: Pomona 5250): + +@verbatim +POMONA 5250 (correlate with the BBB guide) +=== VGA and ethernet socket === + 18 - - 1 + 22 - - NC + NC - - 21 + 3.3V (PSU) - - 17 - this is pin 1 on the flash chip +=== DVD drive === +This is how you will connect. Numbers refer to pin numbers on the BBB, on the plugs near the DC jack. +@end verbatim + +@menu +* Disassembly:: +@end menu + +@node Disassembly +@section Disassembly +@anchor{#disassembly} +@image{images/r500/0001,,,,JPG} @image{images/r500/0002,,,,JPG} @image{images/r500/0003,,,,JPG} @image{images/r500/0004,,,,JPG} @image{images/r500/0005,,,,JPG} @image{images/r500/0006,,,,JPG} @image{images/r500/0007,,,,JPG} @image{images/r500/0008,,,,JPG} @image{images/r500/0009,,,,JPG} @image{images/r500/0010,,,,JPG} @image{images/r500/0011,,,,JPG} @image{images/r500/0012,,,,JPG} @image{images/r500/0013,,,,JPG} @image{images/r500/0014,,,,JPG} @image{images/r500/0015,,,,JPG} @image{images/r500/0016,,,,JPG} @image{images/r500/0017,,,,JPG} @image{images/r500/0018,,,,JPG} @image{images/r500/0019,,,,JPG} @image{images/r500/0020,,,,JPG} @image{images/r500/0021,,,,JPG} @image{images/r500/0022,,,,JPG} @image{images/r500/0023,,,,JPG} @image{images/r500/0024,,,,JPG} @image{images/r500/0025,,,,JPG} @image{images/r500/0026,,,,JPG} @image{images/r500/0027,,,,JPG} @image{images/r500/0028,,,,JPG} @image{images/r500/0029,,,,JPG} @image{images/r500/0030,,,,JPG} @image{images/r500/0031,,,,JPG} + +Remove the motherboard from the cage, and the SPI flash chip will be next to the memory slots:@* @image{images/r500/0032,,,,JPG} @image{images/r500/flashchip,,,,jpg} + +The following image is for illustration only, to show how a SOIC-8 clip is connected. This photo is from a T500, which has a different arrangement to the R500:@* @image{images/t500/0061,,,,jpg} + +Connect your programmer, then connect GND and 3.3V@* @image{images/t400/0067,,,,jpg} @image{images/t400/0069,,,,jpg} @image{images/t400/0070,,,,jpg} @image{images/t400/0071,,,,jpg} + +A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is also fine:@* @image{images/t400/0072,,,,jpg} + +Of course, make sure to turn on your PSU:@* @image{images/x200/disassembly/0013,,,,jpg} + +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 @uref{bbb_setup.html#bbb_access,bbb_setup.html#bbb_access}. + +Test that flashrom works:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512}@* In this case, the output was: + +@verbatim +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. +@end verbatim + +How to backup factory.rom (change the -c option as neeed, for your flash chip):@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom}@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom}@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom}@* Note: the @strong{-c} option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in @emph{flashchips.c} have been removed.@* Now compare the 3 images:@* # @strong{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. + +Now flash it:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V} + +@image{images/x200/disassembly/0015,,,,jpg} + +You might see errors, but if it says @strong{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 @strong{Chip content is identical to the requested image} is also an indication of a successful installation. + +Example output from running the command (see above): + +@verbatim +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. +@end verbatim + +@ref{#pagetop,Back to top of page.} + +@node Thermal paste IMPORTANT +@chapter Thermal paste (IMPORTANT) +@anchor{#thermal-paste-important} +Because part of this procedure involved removing the heatsink, you will need to apply new paste. Arctic Silver 5 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. AS5 is also much better than the default paste used on these systems. + +@image{images/t400/paste,,,,jpg} + +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. + +@node Wifi +@chapter Wifi +@anchor{#wifi} +The R500 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 @uref{../hcl/index.html#recommended_wifi,../hcl/index.html#recommended_wifi}. + +Some R500 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 R500 came with:@* @image{images/t400/0012,,,,jpg} @image{images/t400/ar5b95,,,,jpg} + +@node WWAN +@chapter WWAN +@anchor{#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). + +@node Memory +@chapter Memory +@anchor{#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. + +The following photo shows 8GiB (2x4GiB) of RAM installed:@* @image{images/t400/memory,,,,jpg} +@menu +* Boot it!:: +@end menu + +@node Boot it! +@section Boot it! +@anchor{#boot-it} +You should see something like this: + +@image{images/t400/boot0,,,,jpg} @image{images/t400/boot1,,,,jpg} + +Now @uref{../gnulinux/index.html,install GNU/Linux}. + +Copyright © 2015 Francis Rowe <info@@gluglug.org.uk>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye diff --git a/docs/install/t400_external.html b/docs/install/t400_external.html deleted file mode 100644 index ef8e8b2..0000000 --- a/docs/install/t400_external.html +++ /dev/null @@ -1,582 +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><a href="index.html">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"> - - <h1 id="lcd_compatibility">LCD compatibly</h1> - <p> - Not all LCD panels are compatible yet. See <a href="../hcl/gm45_lcd.html">../hcl/gm45_lcd.html</a>. - </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> - Although blocked by lenovobios (as was reported), it is reported that there are quad-core CPUs - for GM45. This laptop has socketed CPUs, so it might be possible to use them - (they are untested in coreboot; support may have to be added). - Core 2 Quad Q9000, Q9100 or QX9300. - </p> - - <p> - Look at this link:<br/> - <a href="https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors">https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors</a> - </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>dmidecode | grep ROM\ Size</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/index.html#recommended_wifi">../hcl/index.html#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> - 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/index.html">install GNU/Linux</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2015 Francis Rowe <info@gluglug.org.uk><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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.texi b/docs/install/t400_external.texi new file mode 100644 index 0000000..afef825 --- /dev/null +++ b/docs/install/t400_external.texi @@ -0,0 +1,296 @@ +\input texinfo +@documentencoding UTF-8 + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title ThinkPad T400: flashing tutorial (BeagleBone Black) +@end titlepage + +@node Top +@top ThinkPad T400: flashing tutorial (BeagleBone Black) + +@menu +* Flashing the T400 with a BeagleBone Black:: +* T400 laptops with libreboot pre-installed:: +* LCD compatibly:: +* A note about CPUs:: +* A note about GPUs:: +* CPU paste required:: +* Flash chip size:: +* MAC address:: +* Initial BBB configuration:: +* Thermal paste IMPORTANT:: +* Wifi:: +* WWAN:: +* Memory:: +@end menu + +@node Flashing the T400 with a BeagleBone Black +@chapter Flashing the T400 with a BeagleBone Black +@anchor{#flashing-the-t400-with-a-beaglebone-black} +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. + +@uref{index.html,Back to main index} + +@node T400 laptops with libreboot pre-installed +@chapter T400 laptops with libreboot pre-installed +@anchor{#t400-laptops-with-libreboot-pre-installed} +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 @uref{../../suppliers,suppliers} page for more information. +@menu +* Serial port:: +@end menu + +@node Serial port +@section Serial port +@anchor{#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. + +@node LCD compatibly +@chapter LCD compatibly +@anchor{#lcd-compatibly} +Not all LCD panels are compatible yet. See @uref{../hcl/gm45_lcd.html,../hcl/gm45_lcd.html}. + +@node A note about CPUs +@chapter A note about CPUs +@anchor{#a-note-about-cpus} +@uref{http://www.thinkwiki.org/wiki/Category:T400,ThinkWiki} 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. +@menu +* Quad-core CPUs:: +@end menu + +@node Quad-core CPUs +@section Quad-core CPUs +@anchor{#quad-core-cpus} +Although blocked by lenovobios (as was reported), it is reported that there are quad-core CPUs for GM45. This laptop has socketed CPUs, so it might be possible to use them (they are untested in coreboot; support may have to be added). Core 2 Quad Q9000, Q9100 or QX9300. + +Look at this link:@* @uref{https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors,https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors} + +@node A note about GPUs +@chapter A note about GPUs +@anchor{#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 @emph{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. + +@node CPU paste required +@chapter CPU paste required +@anchor{#cpu-paste-required} +See @ref{#paste,#paste}. + +@node Flash chip size +@chapter Flash chip size +@anchor{#flash-chip-size} +Use this to find out:@* # @strong{dmidecode | grep ROM\ Size} + +@ref{#pagetop,Back to top of page.} + +@node MAC address +@chapter MAC address +@anchor{#mac-address} +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: + +@image{images/t400/macaddress0,,,,jpg} @image{images/t400/macaddress1,,,,jpg} @image{images/x200/disassembly/0001,,,,jpg} + +@node Initial BBB configuration +@chapter Initial BBB configuration +@anchor{#initial-bbb-configuration} +Refer to @uref{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): + +@verbatim +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. +@end verbatim + +The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): + +@verbatim +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. +@end verbatim + +@menu +* The procedure:: +@end menu + +@node The procedure +@section The procedure +@anchor{#the-procedure} +Remove @emph{all} screws, placing them in the order that you removed them:@* @image{images/t400/0001,,,,jpg} @image{images/t400/0002,,,,jpg} + +Remove those three screws then remove the rear bezel:@* @image{images/t400/0003,,,,jpg} @image{images/t400/0004,,,,jpg} @image{images/t400/0005,,,,jpg} @image{images/t400/0006,,,,jpg} + +Remove the speakers:@* @image{images/t400/0007,,,,jpg} @image{images/t400/0008,,,,jpg} @image{images/t400/0009,,,,jpg} @image{images/t400/0010,,,,jpg} @image{images/t400/0011,,,,jpg} + +Remove the wifi:@* @image{images/t400/0012,,,,jpg} @image{images/t400/0013,,,,jpg} + +Remove this cable:@* @image{images/t400/0014,,,,jpg} @image{images/t400/0015,,,,jpg} @image{images/t400/0016,,,,jpg} @image{images/t400/0017,,,,jpg} @image{images/t400/0018,,,,jpg} + +Unroute those antenna wires:@* @image{images/t400/0019,,,,jpg} @image{images/t400/0020,,,,jpg} @image{images/t400/0021,,,,jpg} @image{images/t400/0022,,,,jpg} @image{images/t400/0023,,,,jpg} + +Remove the LCD assembly:@* @image{images/t400/0024,,,,jpg} @image{images/t400/0025,,,,jpg} @image{images/t400/0026,,,,jpg} @image{images/t400/0027,,,,jpg} @image{images/t400/0028,,,,jpg} @image{images/t400/0029,,,,jpg} @image{images/t400/0030,,,,jpg} @image{images/t400/0031,,,,jpg} + +Disconnect the NVRAM battery:@* @image{images/t400/0033,,,,jpg} + +Disconnect the fan:@* @image{images/t400/0034,,,,jpg} + +Unscrew these:@* @image{images/t400/0035,,,,jpg} @image{images/t400/0036,,,,jpg} @image{images/t400/0037,,,,jpg} @image{images/t400/0038,,,,jpg} + +Unscrew the heatsink, then lift it off:@* @image{images/t400/0039,,,,jpg} @image{images/t400/0040,,,,jpg} + +Disconnect the power jack:@* @image{images/t400/0041,,,,jpg} @image{images/t400/0042,,,,jpg} + +Loosen this:@* @image{images/t400/0043,,,,jpg} + +Remove this:@* @image{images/t400/0044,,,,jpg} @image{images/t400/0045,,,,jpg} @image{images/t400/0046,,,,jpg} @image{images/t400/0047,,,,jpg} @image{images/t400/0048,,,,jpg} + +Unscrew these:@* @image{images/t400/0049,,,,jpg} @image{images/t400/0050,,,,jpg} + +Remove this:@* @image{images/t400/0051,,,,jpg} @image{images/t400/0052,,,,jpg} + +Unscrew this:@* @image{images/t400/0053,,,,jpg} + +Remove the motherboard (the cage is still attached) from the right hand side, then lift it out:@* @image{images/t400/0054,,,,jpg} @image{images/t400/0055,,,,jpg} @image{images/t400/0056,,,,jpg} + +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): @image{images/t400/0057,,,,jpg} @image{images/t400/0058,,,,jpg} @image{images/t400/0059,,,,jpg} @image{images/t400/0060,,,,jpg} @image{images/t400/0061,,,,jpg} @image{images/t400/0062,,,,jpg} + +Separate the motherboard:@* @image{images/t400/0063,,,,jpg} @image{images/t400/0064,,,,jpg} + +Connect your programmer, then connect GND and 3.3V@* @image{images/t400/0065,,,,jpg} @image{images/t400/0066,,,,jpg} @image{images/t400/0067,,,,jpg} @image{images/t400/0069,,,,jpg} @image{images/t400/0070,,,,jpg} @image{images/t400/0071,,,,jpg} + +A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is also fine:@* @image{images/t400/0072,,,,jpg} + +Of course, make sure to turn on your PSU:@* @image{images/x200/disassembly/0013,,,,jpg} + +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 @uref{bbb_setup.html#bbb_access,bbb_setup.html#bbb_access}. + +Test that flashrom works:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512}@* In this case, the output was: + +@verbatim +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. +@end verbatim + +How to backup factory.rom (change the -c option as neeed, for your flash chip):@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom}@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom}@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom}@* Note: the @strong{-c} option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in @emph{flashchips.c} have been removed.@* Now compare the 3 images:@* # @strong{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 @uref{../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. @strong{Make sure to always change the MAC address to one that is correct for your system.} + +Now flash it:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V} + +@image{images/x200/disassembly/0015,,,,jpg} + +You might see errors, but if it says @strong{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 @strong{Chip content is identical to the requested image} is also an indication of a successful installation. + +Example output from running the command (see above): + +@verbatim +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. +@end verbatim + +@ref{#pagetop,Back to top of page.} + +@node Thermal paste IMPORTANT +@chapter Thermal paste (IMPORTANT) +@anchor{#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. + +@image{images/t400/paste,,,,jpg} + +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. + +@node Wifi +@chapter Wifi +@anchor{#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 @uref{../hcl/index.html#recommended_wifi,../hcl/index.html#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:@* @image{images/t400/0012,,,,jpg} @image{images/t400/ar5b95,,,,jpg} + +@node WWAN +@chapter WWAN +@anchor{#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). + +@node Memory +@chapter Memory +@anchor{#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. + +The following photo shows 8GiB (2x4GiB) of RAM installed:@* @image{images/t400/memory,,,,jpg} +@menu +* Boot it!:: +@end menu + +@node Boot it! +@section Boot it! +@anchor{#boot-it} +You should see something like this: + +@image{images/t400/boot0,,,,jpg} @image{images/t400/boot1,,,,jpg} + +Now @uref{../gnulinux/index.html,install GNU/Linux}. + +Copyright © 2015 Francis Rowe <info@@gluglug.org.uk>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye diff --git a/docs/install/t500_external.html b/docs/install/t500_external.html deleted file mode 100644 index 769fad5..0000000 --- a/docs/install/t500_external.html +++ /dev/null @@ -1,592 +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="index.html">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"> - - <h1 id="lcd_compatibility">LCD compatibly</h1> - <p> - Not all LCD panels are compatible yet. See <a href="../hcl/gm45_lcd.html">../hcl/gm45_lcd.html</a>. - </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> - Although blocked by lenovobios (as was reported), it is reported that there are quad-core CPUs - for GM45. This laptop has socketed CPUs, so it might be possible to use them - (they are untested in coreboot; support may have to be added). - Core 2 Quad Q9000, Q9100 or QX9300. - </p> - - <p> - Look at this link:<br/> - <a href="https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors">https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors</a> - </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>dmidecode | grep ROM\ Size</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/index.html#recommended_wifi">../hcl/index.html#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> - 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/index.html">install GNU/Linux</a>. - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2015 Francis Rowe <info@gluglug.org.uk><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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.texi b/docs/install/t500_external.texi new file mode 100644 index 0000000..698a430 --- /dev/null +++ b/docs/install/t500_external.texi @@ -0,0 +1,296 @@ +\input texinfo +@documentencoding UTF-8 + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title ThinkPad T500: flashing tutorial (BeagleBone Black) +@end titlepage + +@node Top +@top ThinkPad T500: flashing tutorial (BeagleBone Black) + +@menu +* Flashing the T500 with a BeagleBone Black:: +* Libreboot T400:: +* LCD compatibly:: +* A note about CPUs:: +* A note about GPUs:: +* CPU paste required:: +* Flash chip size:: +* MAC address:: +* Initial BBB configuration:: +* Thermal paste IMPORTANT:: +* Wifi:: +* WWAN:: +* Memory:: +@end menu + +@node Flashing the T500 with a BeagleBone Black +@chapter Flashing the T500 with a BeagleBone Black +@anchor{#flashing-the-t500-with-a-beaglebone-black} +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. + +@uref{index.html,Back to main index} + +@node Libreboot T400 +@chapter Libreboot T400 +@anchor{#libreboot-t400} +You may also be interested in the smaller, more portable @uref{t400_external.html,Libreboot T400}. +@menu +* Serial port:: +@end menu + +@node Serial port +@section Serial port +@anchor{#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. + +@node LCD compatibly +@chapter LCD compatibly +@anchor{#lcd-compatibly} +Not all LCD panels are compatible yet. See @uref{../hcl/gm45_lcd.html,../hcl/gm45_lcd.html}. + +@node A note about CPUs +@chapter A note about CPUs +@anchor{#a-note-about-cpus} +@uref{http://www.thinkwiki.org/wiki/Category:T500,ThinkWiki} 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. +@menu +* Quad-core CPUs:: +@end menu + +@node Quad-core CPUs +@section Quad-core CPUs +@anchor{#quad-core-cpus} +Although blocked by lenovobios (as was reported), it is reported that there are quad-core CPUs for GM45. This laptop has socketed CPUs, so it might be possible to use them (they are untested in coreboot; support may have to be added). Core 2 Quad Q9000, Q9100 or QX9300. + +Look at this link:@* @uref{https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors,https://en.wikipedia.org/wiki/List_of_Intel_Core_2_microprocessors#Quad-Core_Notebook_processors} + +@node A note about GPUs +@chapter A note about GPUs +@anchor{#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 @emph{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. + +@node CPU paste required +@chapter CPU paste required +@anchor{#cpu-paste-required} +See @ref{#paste,#paste}. + +@node Flash chip size +@chapter Flash chip size +@anchor{#flash-chip-size} +Use this to find out:@* # @strong{dmidecode | grep ROM\ Size} + +@ref{#pagetop,Back to top of page.} + +@node MAC address +@chapter MAC address +@anchor{#mac-address} +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: + +@image{images/t400/macaddress0,,,,jpg} @image{images/t400/macaddress1,,,,jpg} @image{images/x200/disassembly/0001,,,,jpg} + +@node Initial BBB configuration +@chapter Initial BBB configuration +@anchor{#initial-bbb-configuration} +Refer to @uref{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): + +@verbatim +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. +@end verbatim + +The following shows how to connect clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): + +@verbatim +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. +@end verbatim + +@menu +* The procedure:: +@end menu + +@node The procedure +@section The procedure +@anchor{#the-procedure} +Remove all screws:@* @image{images/t500/0000,,,,jpg}@* 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:@* @image{images/t500/0001,,,,jpg} @image{images/t500/0002,,,,jpg} + +Remove the HDD/SSD and optical drive:@* @image{images/t500/0003,,,,jpg} @image{images/t500/0004,,,,jpg} + +Remove the palm rest:@* @image{images/t500/0005,,,,jpg} @image{images/t500/0006,,,,jpg} + +Remove the keyboard and rear bezel:@* @image{images/t500/0007,,,,jpg} @image{images/t500/0008,,,,jpg} @image{images/t500/0009,,,,jpg} @image{images/t500/0010,,,,jpg} @image{images/t500/0011,,,,jpg} @image{images/t500/0012,,,,jpg} + +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:@* @image{images/t500/0013,,,,jpg} @image{images/t500/0017,,,,jpg} @image{images/t500/0018,,,,jpg} + +Remove this frame, and then remove the wifi chip:@* @image{images/t500/0014,,,,jpg} @image{images/t500/0015,,,,jpg} @image{images/t500/0016,,,,jpg} + +Remove the speakers:@* @image{images/t500/0019,,,,jpg} @image{images/t500/0020,,,,jpg} @image{images/t500/0021,,,,jpg} @image{images/t500/0022,,,,jpg} @image{images/t500/0023,,,,jpg} @image{images/t500/0024,,,,jpg} @image{images/t500/0025,,,,jpg} + +Remove the NVRAM battery (already removed in this photo):@* @image{images/t500/0026,,,,jpg} + +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:@* @image{images/t500/0027,,,,jpg} + +Unroute the antenna wires:@* @image{images/t500/0028,,,,jpg} @image{images/t500/0029,,,,jpg} @image{images/t500/0030,,,,jpg} @image{images/t500/0031,,,,jpg} + +Disconnect the LCD cable from the motherboard:@* @image{images/t500/0032,,,,jpg} @image{images/t500/0033,,,,jpg} + +Remove the LCD assembly hinge screws, and then remove the LCD assembly:@* @image{images/t500/0034,,,,jpg} @image{images/t500/0035,,,,jpg} @image{images/t500/0036,,,,jpg} + +Remove the fan and heatsink:@* @image{images/t500/0037,,,,jpg} @image{images/t500/0038,,,,jpg} @image{images/t500/0039,,,,jpg} + +Remove this screw:@* @image{images/t500/0040,,,,jpg} + +Remove these cables, keeping note of how and in what arrangement they are connected:@* @image{images/t500/0041,,,,jpg} @image{images/t500/0042,,,,jpg} @image{images/t500/0043,,,,jpg} @image{images/t500/0044,,,,jpg} @image{images/t500/0045,,,,jpg} @image{images/t500/0046,,,,jpg} @image{images/t500/0047,,,,jpg} @image{images/t500/0048,,,,jpg} @image{images/t500/0049,,,,jpg} + +Disconnect the power jack:@* @image{images/t500/0050,,,,jpg} @image{images/t500/0051,,,,jpg} + +Remove the motherboard and cage from the base (the marked hole is where those cables were routed through):@* @image{images/t500/0052,,,,jpg} @image{images/t500/0053,,,,jpg} + +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):@* @image{images/t500/0054,,,,jpg} @image{images/t500/0055,,,,jpg} + +Also remove this:@* @image{images/t500/0056,,,,jpg} @image{images/t500/0057,,,,jpg} + +Separate the motherboard from the cage:@* @image{images/t500/0058,,,,jpg} @image{images/t500/0059,,,,jpg} + +The flash chip is next to the memory slots. On this system, it was a SOIC-8 (4MiB or 32Mb) flash chip:@* @image{images/t500/0060,,,,jpg} + +Connect your programmer, then connect GND and 3.3V@* @image{images/t500/0061,,,,jpg}@* @image{images/t400/0067,,,,jpg} @image{images/t400/0069,,,,jpg} @image{images/t400/0070,,,,jpg} @image{images/t400/0071,,,,jpg} + +A dedicated 3.3V PSU was used to create this guide, but at ATX PSU is also fine:@* @image{images/t400/0072,,,,jpg} + +Of course, make sure to turn on your PSU:@* @image{images/x200/disassembly/0013,,,,jpg} + +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 @uref{bbb_setup.html#bbb_access,bbb_setup.html#bbb_access}. + +Test that flashrom works:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512}@* In this case, the output was: + +@verbatim +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. +@end verbatim + +How to backup factory.rom (change the -c option as neeed, for your flash chip):@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom}@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom}@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom}@* Note: the @strong{-c} option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in @emph{flashchips.c} have been removed.@* Now compare the 3 images:@* # @strong{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 @uref{../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. @strong{Make sure to always change the MAC address to one that is correct for your system.} + +Now flash it:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V} + +@image{images/x200/disassembly/0015,,,,jpg} + +You might see errors, but if it says @strong{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 @strong{Chip content is identical to the requested image} is also an indication of a successful installation. + +Example output from running the command (see above): + +@verbatim +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. +@end verbatim + +@ref{#pagetop,Back to top of page.} + +@node Thermal paste IMPORTANT +@chapter Thermal paste (IMPORTANT) +@anchor{#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. + +@image{images/t400/paste,,,,jpg} + +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. + +@node Wifi +@chapter Wifi +@anchor{#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 @uref{../hcl/index.html#recommended_wifi,../hcl/index.html#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:@* @image{images/t400/0012,,,,jpg} @image{images/t400/ar5b95,,,,jpg} + +@node WWAN +@chapter WWAN +@anchor{#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). + +@node Memory +@chapter Memory +@anchor{#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. + +The following photo shows 8GiB (2x4GiB) of RAM installed:@* @image{images/t400/memory,,,,jpg} +@menu +* Boot it!:: +@end menu + +@node Boot it! +@section Boot it! +@anchor{#boot-it} +You should see something like this: + +@image{images/t500/0062,,,,jpg} + +Now @uref{../gnulinux/index.html,install GNU/Linux}. + +Copyright © 2015 Francis Rowe <info@@gluglug.org.uk>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye diff --git a/docs/install/t60_unbrick.html b/docs/install/t60_unbrick.html deleted file mode 100644 index 9bcdb12..0000000 --- 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="index.html">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 Francis Rowe <info@gluglug.org.uk><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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.texi b/docs/install/t60_unbrick.texi new file mode 100644 index 0000000..e774b83 --- /dev/null +++ b/docs/install/t60_unbrick.texi @@ -0,0 +1,152 @@ +\input texinfo +@documentencoding UTF-8 + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title ThinkPad T60: Recovery guide +@end titlepage + +@node Top +@top ThinkPad T60: Recovery guide + +@menu +* ThinkPad T60 Recovery guide:: +* Brick type 1 bucts not reset:: +* bad rom or user error system won't boot:: +@end menu + +@node ThinkPad T60 Recovery guide +@chapter ThinkPad T60: Recovery guide +@anchor{#thinkpad-t60-recovery-guide} +This section documents how to recover from a bad flash that prevents your ThinkPad T60 from booting. + +@uref{index.html,Back to previous index} +@menu +* Table of Contents:: +@end menu + +@node Table of Contents +@section Table of Contents +@anchor{#table-of-contents} +@itemize +@item +Types of brick: +@itemize +@item +@ref{#bucts_brick,Brick type 1: bucts not reset} +@item +@ref{#recovery,Brick type 2: bad rom (or user error), system won't boot} +@end itemize + +@end itemize + +@node Brick type 1 bucts not reset +@chapter Brick type 1: bucts not reset. +@anchor{#brick-type-1-bucts-not-reset.} +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:@* @image{../images/t60_dev/0006,,,,JPG}@*@* *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: @uref{http://www.coreboot.org/Board:lenovo/x60/Installation,http://www.coreboot.org/Board:lenovo/x60/Installation}. (it says x60, but instructions for t60 are identical) + +@node bad rom or user error system won't boot +@chapter bad rom (or user error), system won't boot +@anchor{#bad-rom-or-user-error-system-wont-boot} +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:@* @image{../images/t60_dev/0001,,,,JPG} @image{../images/t60_dev/0002,,,,JPG} + +Lift off the palm rest:@* @image{../images/t60_dev/0003,,,,JPG} + +Lift up the keyboard, pull it back a bit, flip it over like that and then disconnect it from the board:@* @image{../images/t60_dev/0004,,,,JPG} @image{../images/t60_dev/0005,,,,JPG} @image{../images/t60_dev/0006,,,,JPG} + +Gently wedge both sides loose:@* @image{../images/t60_dev/0007,,,,JPG} @image{../images/t60_dev/0008,,,,JPG} + +Remove that cable from the position:@* @image{../images/t60_dev/0009,,,,JPG} @image{../images/t60_dev/0010,,,,JPG} + +Now remove that bezel. Remove wifi, nvram battery and speaker connector (also remove 56k modem, on the left of wifi):@* @image{../images/t60_dev/0011,,,,JPG} + +Remove those screws:@* @image{../images/t60_dev/0012,,,,JPG} + +Disconnect the power jack:@* @image{../images/t60_dev/0013,,,,JPG} + +Remove nvram battery:@* @image{../images/t60_dev/0014,,,,JPG} + +Disconnect cable (for 56k modem) and disconnect the other cable:@* @image{../images/t60_dev/0015,,,,JPG} @image{../images/t60_dev/0016,,,,JPG} + +Disconnect speaker cable:@* @image{../images/t60_dev/0017,,,,JPG} + +Disconnect the other end of the 56k modem cable:@* @image{../images/t60_dev/0018,,,,JPG} + +Make sure you removed it:@* @image{../images/t60_dev/0019,,,,JPG} + +Unscrew those:@* @image{../images/t60_dev/0020,,,,JPG} + +Make sure you removed those:@* @image{../images/t60_dev/0021,,,,JPG} + +Disconnect LCD cable from board:@* @image{../images/t60_dev/0022,,,,JPG} + +Remove those screws then remove the LCD assembly:@* @image{../images/t60_dev/0023,,,,JPG} @image{../images/t60_dev/0024,,,,JPG} @image{../images/t60_dev/0025,,,,JPG} + +Once again, make sure you removed those:@* @image{../images/t60_dev/0026,,,,JPG} + +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:@* @image{../images/t60_dev/0027,,,,JPG} @image{../images/t60_dev/0028,,,,JPG} @image{../images/t60_dev/0029,,,,JPG} @image{../images/t60_dev/0031,,,,JPG} @image{../images/t60_dev/0032,,,,JPG} @image{../images/t60_dev/0033,,,,JPG} + +Now wire up the BBB and the Pomona with your PSU.@* Refer to @uref{bbb_setup.html,bbb_setup.html} for how to setup the BBB for flashing.@* @strong{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)}@* @image{../images/t60_dev/0030,,,,JPG}@* Correlate the following with the BBB guide linked above: + +@verbatim +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. +@end verbatim + +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:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom} + +It should be @strong{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:@* @image{../images/t60_dev/0047,,,,JPG} + +Put it back into lower chassis:@* @image{../images/t60_dev/0048,,,,JPG} + +Attach LCD and insert screws (also, attach the lcd cable to the board):@* @image{../images/t60_dev/0049,,,,JPG} + +Insert those screws:@* @image{../images/t60_dev/0050,,,,JPG} + +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@* @image{../images/t60_dev/0051,,,,JPG} + +Attach the heatsink and install the screws (also, make sure to install the AC jack as highlighted):@* @image{../images/t60_dev/0052,,,,JPG} + +Reinstall that upper bezel:@* @image{../images/t60_dev/0053,,,,JPG} + +Do that:@* @image{../images/t60_dev/0054,,,,JPG} @image{../images/t60_dev/0055,,,,JPG} + +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:@* @image{../images/t60_dev/0056,,,,JPG} @image{../images/t60_dev/0057,,,,JPG} + +Place keyboard and (sorry, forgot to take pics) reinstall the palmrest and insert screws on the underside:@* @image{../images/t60_dev/0058,,,,JPG} + +It lives!@* @image{../images/t60_dev/0071,,,,JPG} @image{../images/t60_dev/0072,,,,JPG} @image{../images/t60_dev/0073,,,,JPG} + +Always stress test ('stress -c 2' and xsensors. below 90C is ok) when replacing cpu paste/heatsink:@* @image{../images/t60_dev/0074,,,,JPG} + +Copyright © 2014, 2015 Francis Rowe <info@@gluglug.org.uk>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye diff --git a/docs/install/x200_external.html b/docs/install/x200_external.html deleted file mode 100644 index 1d1e583..0000000 --- a/docs/install/x200_external.html +++ /dev/null @@ -1,475 +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="index.html">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>dmidecode | grep ROM\ Size</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/index.html#recommended_wifi">../hcl/index.html#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> - 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/index.html">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 Francis Rowe <info@gluglug.org.uk><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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.texi b/docs/install/x200_external.texi new file mode 100644 index 0000000..4f1c620 --- /dev/null +++ b/docs/install/x200_external.texi @@ -0,0 +1,277 @@ +\input texinfo +@documentencoding UTF-8 + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title ThinkPad X200: flashing tutorial (BeagleBone Black) +@end titlepage + +@node Top +@top ThinkPad X200: flashing tutorial (BeagleBone Black) + +@menu +* Flashing the X200 with a BeagleBone Black:: +* X200 laptops with libreboot pre-installed:: +* Flash chip size:: +* MAC address:: +* Initial BBB configuration:: +* Wifi:: +* WWAN:: +* Memory:: +@end menu + +@node Flashing the X200 with a BeagleBone Black +@chapter Flashing the X200 with a BeagleBone Black +@anchor{#flashing-the-x200-with-a-beaglebone-black} +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. + +@itemize +@item +@ref{#preinstall,X200 laptops with libreboot pre-installed} +@item +@ref{#flashchips,Flash chips} +@item +@ref{#macaddress,MAC address} +@item +@ref{#clip,Initial BBB configuration and installation procedure} +@item +@ref{#boot,Boot it!} +@item +@ref{#wifi,Wifi} +@item +@ref{#wwan,wwan} +@item +@ref{#memory,Memory} +@item +@ref{#gpio33,X200S and X200 Tablet users: GPIO33 trick will not work.} +@end itemize + +@uref{index.html,Back to main index} + +@node X200 laptops with libreboot pre-installed +@chapter X200 laptops with libreboot pre-installed +@anchor{#x200-laptops-with-libreboot-pre-installed} +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 @uref{../../suppliers,suppliers} page for more information. + +@node Flash chip size +@chapter Flash chip size +@anchor{#flash-chip-size} +Use this to find out:@* # @strong{dmidecode | grep ROM\ Size} + +The X200S and X200 Tablet will use a WSON-8 flash chip, on the bottom of the motherboard (this requires removal of the motherboard). @strong{Not all X200S/X200T are supported; see @uref{../hcl/x200.html#x200s,../hcl/x200.html#x200s}.} + +@ref{#pagetop,Back to top of page.} + +@node MAC address +@chapter MAC address +@anchor{#mac-address} +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: + +@image{images/x200/disassembly/0002,,,,jpg} @image{images/x200/disassembly/0001,,,,jpg} + +@node Initial BBB configuration +@chapter Initial BBB configuration +@anchor{#initial-bbb-configuration} +Refer to @uref{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): + +@verbatim +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: + +@end verbatim + +The following shows how to connect the clip to the BBB (on the P9 header), for SOIC-8 (clip: Pomona 5250): + +@verbatim +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? +@end verbatim + +@strong{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:}@* @image{images/x200/wson_soldered,,,,jpg} @* 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 @uref{../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. +@menu +* The procedure:: +@end menu + +@node The procedure +@section The procedure +@anchor{#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:@* @image{images/x200/disassembly/0003,,,,jpg} + +Push the keyboard forward, gently, then lift it off and disconnect it from the board:@* @image{images/x200/disassembly/0004,,,,jpg} @image{images/x200/disassembly/0005,,,,jpg} + +Pull the palm rest off, lifting from the left and right side at the back of the palm rest:@* @image{images/x200/disassembly/0006,,,,jpg} + +Lift back the tape that covers a part of the flash chip, and then connect the clip:@* @image{images/x200/disassembly/0007,,,,jpg} @image{images/x200/disassembly/0008,,,,jpg} + +On pin 2 of the BBB, where you have the ground (GND), connect the ground to your PSU:@* @image{images/x200/disassembly/0009,,,,jpg} @image{images/x200/disassembly/0010,,,,jpg} + +Connect the 3.3V supply from your PSU to the flash chip (via the clip):@* @image{images/x200/disassembly/0011,,,,jpg} @image{images/x200/disassembly/0012,,,,jpg} + +Of course, make sure that your PSU is also plugged in and turn on:@* @image{images/x200/disassembly/0013,,,,jpg} + +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):@* @image{images/x200/disassembly/0014,,,,jpg} + +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 @uref{bbb_setup.html#bbb_access,bbb_setup.html#bbb_access}. + +Test that flashrom works:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512}@* In this case, the output was: + +@verbatim +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. +@end verbatim + +How to backup factory.rom (change the -c option as neeed, for your flash chip):@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory.rom}@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory1.rom}@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -r factory2.rom}@* Note: the @strong{-c} option is not required in libreboot's patched flashrom, because the redundant flash chip definitions in @emph{flashchips.c} have been removed.@* Now compare the 3 images:@* # @strong{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 @uref{../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. @strong{Make sure to always change the MAC address to one that is correct for your system.} + +Now flash it:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w path/to/libreboot/rom/image.rom -V} + +@image{images/x200/disassembly/0015,,,,jpg} + +You might see errors, but if it says @strong{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 @strong{Chip content is identical to the requested image} is also an indication of a successful installation. + +Example output from running the command (see above): + +@verbatim +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. +@end verbatim + +@ref{#pagetop,Back to top of page.} + +@node Wifi +@chapter Wifi +@anchor{#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 @uref{../hcl/index.html#recommended_wifi,../hcl/index.html#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:@* @image{images/x200/disassembly/0016,,,,jpg} @image{images/x200/disassembly/0017,,,,jpg} + +@node WWAN +@chapter WWAN +@anchor{#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). + +@node Memory +@chapter Memory +@anchor{#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. + +In this photo, 8GiB of RAM (2x4GiB) is installed:@* @image{images/x200/disassembly/0018,,,,jpg} +@menu +* Boot it!:: +* X200S and X200 Tablet users GPIO33 trick will not work:: +@end menu + +@node Boot it! +@section Boot it! +@anchor{#boot-it} +You should see something like this: + +@image{images/x200/disassembly/0019,,,,jpg} + +Now @uref{../gnulinux/index.html,install GNU/Linux}. + +@node X200S and X200 Tablet users GPIO33 trick will not work +@section X200S and X200 Tablet users: GPIO33 trick will not work. +@anchor{#x200s-and-x200-tablet-users-gpio33-trick-will-not-work.} +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):@* @image{../hcl/images/x200/gpio33_location,,,,jpg} + +By default we would see this in lenovobios, when trying flashrom -p internal -w rom.rom: + +@verbatim +FREG0: Warning: Flash Descriptor region (0x00000000-0x00000fff) is read-only. +FREG2: Warning: Management Engine region (0x00001000-0x005f5fff) is locked. +@end verbatim + +With GPIO33 grounded during boot, this disabled the flash protections as set by descriptor, and stopped the ME from starting. The output changed to: + +@verbatim +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. +@end verbatim + +The part in bold is what got us. This was still observed: + +@verbatim +PR0: Warning: 0x007e0000-0x01ffffff is read-only. +PR4: Warning: 0x005f8000-0x005fffff is locked. +@end verbatim + +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: @uref{http://www.coreboot.org/Board:lenovo/x200/internal_flashing_research,http://www.coreboot.org/Board:lenovo/x200/internal_flashing_research} + +On a related note, libreboot has a utility that could help with investigating this: @uref{../hcl/gm45_remove_me.html#demefactory,../hcl/gm45_remove_me.html#demefactory} + +Copyright © 2014, 2015 Francis Rowe <info@@gluglug.org.uk>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye diff --git a/docs/install/x60_unbrick.html b/docs/install/x60_unbrick.html deleted file mode 100644 index d626143..0000000 --- a/docs/install/x60_unbrick.html +++ /dev/null @@ -1,318 +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="index.html">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> - Trisquel live USB menu (using the GRUB ISOLINUX parser):<br/> - <img src="../images/x60_unbrick/0048.jpg" alt="" /> - </p> - <p> - Trisquel live desktop:<br/> - <img src="../images/x60_unbrick/0049.jpg" alt="" /> - </p> - - </div> - - <div class="section"> - - <p> - Copyright © 2014, 2015 Francis Rowe <info@gluglug.org.uk><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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.texi b/docs/install/x60_unbrick.texi new file mode 100644 index 0000000..ba7a072 --- /dev/null +++ b/docs/install/x60_unbrick.texi @@ -0,0 +1,164 @@ +\input texinfo +@documentencoding UTF-8 + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title ThinkPad X60: Recovery guide +@end titlepage + +@node Top +@top ThinkPad X60: Recovery guide + +@menu +* ThinkPad X60 Recovery guide:: +* Table of Contents:: +* Brick type 1 bucts not reset:: +* bad rom or user error system won't boot:: +@end menu + +@node ThinkPad X60 Recovery guide +@chapter ThinkPad X60: Recovery guide +@anchor{#thinkpad-x60-recovery-guide} +This section documents how to recover from a bad flash that prevents your ThinkPad X60 from booting. + +@uref{index.html,Back to previous index} + +@node Table of Contents +@chapter Table of Contents +@anchor{#table-of-contents} +@itemize +@item +Types of brick: +@itemize +@item +@ref{#bucts_brick,Brick type 1: bucts not reset} +@item +@ref{#recovery,Brick type 2: bad rom (or user error), system won't boot} +@end itemize + +@end itemize + +@node Brick type 1 bucts not reset +@chapter Brick type 1: bucts not reset. +@anchor{#brick-type-1-bucts-not-reset.} +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:@* @image{../images/x60_unbrick/0004,,,,jpg}@*@* *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: @uref{http://www.coreboot.org/Board:lenovo/x60/Installation,http://www.coreboot.org/Board:lenovo/x60/Installation}. + +@node bad rom or user error system won't boot +@chapter bad rom (or user error), system won't boot +@anchor{#bad-rom-or-user-error-system-wont-boot} +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:@* @image{../images/x60_unbrick/0000,,,,jpg} + +Push the keyboard forward (carefully):@* @image{../images/x60_unbrick/0001,,,,jpg} + +Lift the keyboard up and disconnect it from the board:@* @image{../images/x60_unbrick/0002,,,,jpg} + +Grab the right-hand side of the chassis and force it off (gently) and pry up the rest of the chassis:@* @image{../images/x60_unbrick/0003,,,,jpg} + +You should now have this:@* @image{../images/x60_unbrick/0004,,,,jpg} + +Disconnect the wifi antenna cables, the modem cable and the speaker:@* @image{../images/x60_unbrick/0005,,,,jpg} + +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:@* @image{../images/x60_unbrick/0006,,,,jpg} + +Disconnect the monitor from the motherboard, and unroute the grey antenna cable, carefully lifting the tape that holds it into place:@* @image{../images/x60_unbrick/0008,,,,jpg} + +Carefully lift the remaining tape and unroute the left antenna cable so that it is loose:@* @image{../images/x60_unbrick/0009,,,,jpg} + +Remove the screw that is highlighted (do NOT remove the other one; it holds part of the heatsink (other side) into place):@* @image{../images/x60_unbrick/0011,,,,jpg} + +Remove those screws:@* @image{../images/x60_unbrick/0012,,,,jpg} + +Carefully remove the plate, like so:@* @image{../images/x60_unbrick/0013,,,,jpg} + +Remove the SATA connector:@* @image{../images/x60_unbrick/0014,,,,jpg} + +Now remove the motherboard (gently) and cast the lcd/chassis aside:@* @image{../images/x60_unbrick/0015,,,,jpg} + +Lift back that tape and hold it with something. Highlighted is the SPI flash chip:@* @image{../images/x60_unbrick/0016,,,,jpg} + +Now wire up the BBB and the Pomona with your PSU.@* Refer to @uref{bbb_setup.html,bbb_setup.html} for how to setup the BBB for flashing.@* @strong{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)} @image{../images/x60_unbrick/0017,,,,jpg}@* Correlate the following with the BBB guide linked above: + +@verbatim +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. +@end verbatim + +Connecting the BBB and pomona (in this image, an external 3.3v DC PSU was used):@* @image{images/x60/th_bbb_flashing,,,,jpg} + +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:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom} + +It should be @strong{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:@* @image{../images/x60_unbrick/0026,,,,jpg} + +Your empty chassis:@* @image{../images/x60_unbrick/0027,,,,jpg} + +Put the motherboard back in:@* @image{../images/x60_unbrick/0028,,,,jpg} + +Reconnect SATA:@* @image{../images/x60_unbrick/0029,,,,jpg} + +Put the plate back and re-insert those screws:@* @image{../images/x60_unbrick/0030,,,,jpg} + +Re-route that antenna cable around the fan and apply the tape:@* @image{../images/x60_unbrick/0031,,,,jpg} + +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:@* @image{../images/x60_unbrick/0032,,,,jpg} + +Re-insert that screw:@* @image{../images/x60_unbrick/0033,,,,jpg} + +Route the black antenna cable like so:@* @image{../images/x60_unbrick/0034,,,,jpg} + +Tuck it in neatly like so:@* @image{../images/x60_unbrick/0035,,,,jpg} + +Route the modem cable like so:@* @image{../images/x60_unbrick/0036,,,,jpg} + +Connect modem cable to board and tuck it in neatly like so:@* @image{../images/x60_unbrick/0037,,,,jpg} + +Route the power connection and connect it to the board like so:@* @image{../images/x60_unbrick/0038,,,,jpg} + +Route the antenna and modem cables neatly like so:@* @image{../images/x60_unbrick/0039,,,,jpg} + +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):@* @image{../images/x60_unbrick/0040,,,,jpg} + +Connect the modem cable:@* @image{../images/x60_unbrick/0041,,,,jpg} + +Connect the speaker:@* @image{../images/x60_unbrick/0042,,,,jpg} + +You should now have this:@* @image{../images/x60_unbrick/0043,,,,jpg} + +Re-connect the upper chassis:@* @image{../images/x60_unbrick/0044,,,,jpg} + +Re-connect the keyboard:@* @image{../images/x60_unbrick/0045,,,,jpg} + +Re-insert the screws that you removed earlier:@* @image{../images/x60_unbrick/0046,,,,jpg} + +Power on!@* @image{../images/x60_unbrick/0047,,,,jpg} + +Trisquel live USB menu (using the GRUB ISOLINUX parser):@* @image{../images/x60_unbrick/0048,,,,jpg} + +Trisquel live desktop:@* @image{../images/x60_unbrick/0049,,,,jpg} + +Copyright © 2014, 2015 Francis Rowe <info@@gluglug.org.uk>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye diff --git a/docs/install/x60tablet_unbrick.html b/docs/install/x60tablet_unbrick.html deleted file mode 100644 index 23a770b..0000000 --- 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="index.html">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 Francis Rowe <info@gluglug.org.uk><br/> - Permission is granted to copy, distribute and/or modify this document - under the terms of the GNU Free Documentation License, Version 1.3 - or any later version published by the Free Software Foundation; - with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. - A copy of the license can be found at <a href="../gfdl-1.3.txt">../gfdl-1.3.txt</a> - </p> - - <p> - Updated versions of the license (when available) can be found at - <a href="https://www.gnu.org/licenses/licenses.html">https://www.gnu.org/licenses/licenses.html</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.texi b/docs/install/x60tablet_unbrick.texi new file mode 100644 index 0000000..199732a --- /dev/null +++ b/docs/install/x60tablet_unbrick.texi @@ -0,0 +1,112 @@ +\input texinfo +@documentencoding UTF-8 + +@ifnottex +@paragraphindent 0 +@end ifnottex +@titlepage +@title ThinkPad X60 Tablet: Recovery guide +@end titlepage + +@node Top +@top ThinkPad X60 Tablet: Recovery guide + +@menu +* ThinkPad X60 Tablet Recovery guide:: +* Brick type 1 bucts not reset:: +* bad rom or user error system won't boot:: +@end menu + +@node ThinkPad X60 Tablet Recovery guide +@chapter ThinkPad X60 Tablet: Recovery guide +@anchor{#thinkpad-x60-tablet-recovery-guide} +This section documents how to recover from a bad flash that prevents your ThinkPad X60 Tablet from booting. + +@uref{index.html,Back to previous index} +@menu +* Table of Contents:: +@end menu + +@node Table of Contents +@section Table of Contents +@anchor{#table-of-contents} +@itemize +@item +Types of brick: +@itemize +@item +@ref{#bucts_brick,Brick type 1: bucts not reset} +@item +@ref{#recovery,Brick type 2: bad rom (or user error), system won't boot} +@end itemize + +@end itemize + +@node Brick type 1 bucts not reset +@chapter Brick type 1: bucts not reset. +@anchor{#brick-type-1-bucts-not-reset.} +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:@* @image{../images/x60t_unbrick/0008,,,,JPG}@*@* *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: @uref{http://www.coreboot.org/Board:lenovo/x60/Installation,http://www.coreboot.org/Board:lenovo/x60/Installation}. + +@node bad rom or user error system won't boot +@chapter bad rom (or user error), system won't boot +@anchor{#bad-rom-or-user-error-system-wont-boot} +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). + +@image{../images/x60t_unbrick/0000,,,,JPG} + +Remove those screws:@* @image{../images/x60t_unbrick/0001,,,,JPG} + +Remove the HDD:@* @image{../images/x60t_unbrick/0002,,,,JPG} + +Push keyboard forward to loosen it:@* @image{../images/x60t_unbrick/0003,,,,JPG} + +Lift:@* @image{../images/x60t_unbrick/0004,,,,JPG} + +Remove those:@* @image{../images/x60t_unbrick/0005,,,,JPG} + +@image{../images/x60t_unbrick/0006,,,,JPG} + +Also remove that (marked) and unroute the antenna cables:@* @image{../images/x60t_unbrick/0007,,,,JPG} + +For some X60T laptops, you have to unroute those too:@* @image{../images/x60t_unbrick/0010,,,,JPG} + +Remove the LCD extend board screws. Also remove those screws (see blue marks) and remove/unroute the cables and remove the metal plate:@* @image{../images/x60t_unbrick/0008,,,,JPG} + +Remove that screw and then remove the board:@* @image{../images/x60t_unbrick/0009,,,,JPG} + +Now wire up the BBB and the Pomona with your PSU.@* Refer to @uref{bbb_setup.html,bbb_setup.html} for how to setup the BBB for flashing.@* @strong{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)} @image{../images/x60t_unbrick/0011,,,,JPG}@* Correlate the following with the BBB guide linked above: + +@verbatim +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. +@end verbatim + +Connecting the BBB and pomona (in this image, an external 3.3v DC PSU was used):@* @image{images/x60/th_bbb_flashing,,,,jpg} + +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:@* # @strong{./flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=512 -w yourrom.rom} + +It should be @strong{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. + +Copyright © 2014, 2015 Francis Rowe <info@@gluglug.org.uk>@* Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license can be found at @uref{../gfdl-1.3.txt,../gfdl-1.3.txt} + +Updated versions of the license (when available) can be found at @uref{https://www.gnu.org/licenses/licenses.html,https://www.gnu.org/licenses/licenses.html} + +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. + +@bye |