Documentation for “Zerocat Flash Access”
Generated on: Sat, 18 Jun 2022 13:16:56 +0200
Repository: git://zerocat.org/zerocat/projects/zerocat-flash-access
Version: v0.3.2
Branch: master

Zerocat Flash Access
– Interfacing BIOS Chips in Hardware Protection Mode

../images/t430/flash_access_header.jpg

T430 flashing, no clip required.

Copyright (C) 2021, 2022 Kai Mertens kmx@posteo.net
Copyright (C) 2022 Jorgo Triantafilidis jorgo_zc@posteo.de

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 is included in the section entitled "GNU Free Documentation License".

Section #../doc/NEWS.md

NEWS

Version Tags

Within this project’s git repository, versions are tagged according to the following pattern:

    v<major>.<minor>.<revision>

Recent Changes

v0.3.2

v0.3.1

v0.3.0

v0.2.1

v0.2.0

v0.1.0

v0.0.0

February of 2022: The project starts with essential content.

Section #../doc/README.md

README

Project Goal

The goal of Zerocat Flash Access is to provide you with a variety of methods to flash in situ SPI BIOS chips, as found on selected motherboards.

Paths

All paths within this document are relative in respect to the original location of this source file, which is located in the project’s doc/ folder.

Prerequisites

It is assumed that you are running a GNU/Linux-libre operating system.

Use git to clone the project’s sources:

    git clone git://zerocat.org/zerocat/projects/zerocat-flash-access

Change into the project’s documentation folder:

    cd zerocat-flash-access/doc/

Study this README.md to get started:

    cat ../doc/README.md

GNU Guix System

If you are on GNU Guix System, use make to create a dedicated profile, once. This allows you to match your environment to the one used by Zerocat, thus producing bit-identical results:

    make -C ../guix pull

Create an empty environment with dedicated guix channel:

    make -C ../guix environment

Create a shell with all prerequisites set up:

    make -C ../guix shell

To leave the shell and the environment, later on, when you are done with this project, type:

    exit
    exit

To remove this project’s handy guix profile, type:

    make -C ../guix clean

This will remove symlinks only. If you want to remove the profile from your system, run the GNU Guix Garbage Collector.

To list all available targets, type:

    make -C ../guix help

Other Distro

If you are on another distro, check file ../guix/manifest.scm and install the listed packages with your package manager, manually. Adapt package names as required.

Make Documentation

To build the documentation, type:

    make -C ../doc

To get a full list of available targets, type:

    make -C ../doc help

To clean-up, type:

    make -C ../doc clean
Section #../doc/COPYING.md

Copying

Zerocat Flash Access ships copyrighted work.

Zerocat Flash Access is free software. It makes use of free software approved licenses only and should be freely distributable:

Authorship, copyright and license information may be provided in more detail on a per-folder and/or per-file basis. Check the sources.

Please report a bug if you find the distribution hindered.
See Zerocat Website for contact information.

Section #../doc/CONTRIBUTING.md

Contributing

Documentation Files

Documentation source files are written in markdown syntax. They should carry their individual copyright and license notices right below the title giving headline, e.g.:

    <Title-of-Document>
    ===================

    Copyright (C) <Year>  <Name-of-Author> <Email-Address>  

    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 is included in the section entitled
    "GNU Free Documentation License".

    <Other-Headline>
    ----------------

    ...content...

The generated documentation carries a license notice right at top on its title page, with copyright statements generated from git log output.

Sections of the generated documentation are build from selected markdown source files, with their individual copyright and license notice stripped.

In order to enrich the generated documentation ...

... and adapt ../doc/Makefile to produce nice output.

In case more tools are needed, don't forget to update ../guix/manifest.scm.

Images

To make your image look nice within the documentation, select a landscape layout of 16:9 aspect ratio.

Use ImageMagick to prepare your image, e.g.:

If your image is big, reduce it to a maximal width of 2000 pixel:

    mogrify -resize 2000x <image>

Please clean image files from metadata, before committing, i.e.:

    mogrify -strip <image>

If you embed your image into a markdown documentation file, use this syntax:

   ![<path/to/image>][]

   [<path/to/image>]:     <path/to/image>     "title message"

or alternatly:

   ![<path/to/image>][my-image-shortcut]

   [my-image-shortcut]:   <path/to/image>     "title message"

These patterns will guarantee that <img> tags will have their src, alt and title attributes properly set within the html output.

Gschem Schematics

Within your circuit schematic, you can use specific texts as placeholder objects. They will be replaced with generated values by the documentation build process. When used within the informational fields of a titleblock, use the specified sizes and alignments:

In case you are going to embed images, make sure to use a relative path. Per default, gschem uses absolute paths that might reveal a private username or folder. You can use nano to edit your schematics outside of gschem.

Code Files

Please use this license header for code source files:

    Zerocat Flash Access --- Interfacing BIOS Chips in Hardware Protection Mode

    Copyright (C) <Year>  <Name-of-Author> <Email-Address>

    This file is part of Zerocat Flash Access.

    Zerocat Flash Access is free software: you can redistribute it
    and/or modify it under the terms of the GNU General Public
    License as published by the Free Software Foundation, either
    version 3 of the License, or (at your option) any later
    version.

    Zerocat Flash Access is distributed in the hope that it will be
    useful, but WITHOUT ANY WARRANTY; without even the implied
    warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
    PURPOSE. See the GNU General Public License for more details.

    You should have received a copy of the GNU General Public License
    along with Zerocat Flash Access.
    If not, see <http://www.gnu.org/licenses/>.

Shell Scripts

If you intend to write shell scripts, use this skeleton to make them work for GNU Guix:

    #!/bin/sh

    # Re-exec if we are not using Bash or are using Bash in POSIX mode.
    if [ -z "$BASH" ] || [ "$BASH" = "/bin/sh" ]; then
      bash=`command -v bash`
      if [ -z "$bash" ]; then
        echo "Couldn't find Bash, sorry!"
        exit 1
      else
        exec "$bash" "$0" "$@"
      fi
    fi

    # We're using Bash now.
    set -o errexit
    set -o nounset
    set -o pipefail

    # Your code goes here ...

ChangeLog

Update ../doc/NEWS.md and list your contributions.

You can use git shortlog to get a starting point for your edit.

Section #../doc/THANKS.md

THANKS

This documentation comes with special thanks to ...

--- K. Mertens

Section #../doc/unused-sockets.md

Unused Sockets

Which mainboards offer unused sockets, close to their SPI Flash?

SPI Flash Environment of a ThinkPad W530

Unused pads available, do they provide access to SPI Flash?

../images/w530/DSCN9416.JPG

SPI Flash Environment of a ThinkPad W530

SPI Flash Environment of a ThinkPad T530

This motherboard does not offer unused sockets for SPI Flash Pinheaders.

SPI Flash Environment of a ThinkPad T430

This motherboard offers unused through-hole sockets for SPI Flash Pinheaders.

SPI Flash Environment of a ThinkPad T520/T520i

This motherboard offers an unused through-hole socket for an SPI Flash Pinheader: J100

../images/t520i/DSCN9350.JPG

SPI Flash Environment of a ThinkPad T520i

SPI Flash Environment of a ThinkPad X1 Carbon Gen1

No unused through-hole for an SPI Flash Pinheader available.

Section #../doc/t430-spi-chip-replacement.md

T430 SPI Chip Replacement

One SPI chip of a client’s T430 happened to be damaged and needed to be replaced. The required SOIC8 form factor was not available, thus a tiny XWSON8 was used as drop-in.

Notices

Photo Documentation

../images/t430-repair/DSCN9663.JPG

Image 1(13): Fix board onto the table, free up chips from foil.

../images/t430-repair/DSCN9666.JPG

Image 2(13): Broken chip successfully removed. Too much heat melted foil, burned table.

../images/t430-repair/DSCN9674.JPG

Image 3(13): In the background: Tool and chip that has been removed.

../images/t430-repair/DSCN9680.JPG

Image 4(13): New XWSON chip waiting to be placed at U99 socket.

../images/t430-repair/DSCN9685.JPG

Image 5(13): Glue chip into place, using hot glue.

../images/t430-repair/DSCN9699.JPG

Image 6(13): Add solder to board’s SPI pads.

../images/t430-repair/DSCN9701.JPG

Image 7(13): Apply mirrored connections, one by one.

../images/t430-repair/DSCN9715.JPG

Image 8(13): All connections done, center pad filled with solder.

../images/t430-repair/DSCN9716.JPG

Image 9(13): Add wires to jumper socket. Bent down wires, very caryfully.

../images/t430-repair/DSCN9720.JPG

Image 10(13): Repair foil with tape.

../images/t430-repair/DSCN9724.JPG

Image 11(13): Remove foil that became too hot, use tape to protect board and wires.

../images/t430-repair/DSCN9730.JPG

Image 12(13): Attach chipflasher to new connector.

../images/t430-repair/screenshot-20220203-133420.png

Image 13(13): Probe chip... Success!

Section #../doc/t530-spi-flash-connector.md

T530 SPI Flash Connector

This how-to helps you to add an SPI flash connector to your T530 machine, and to apply Hardware Protection Mode (HPM) in the same go.

The ROM of the depicted T530 has been created with: Zerocat Coreboot Machines.

Make sure to remove DC Power before attaching to the SPI flash connector.

Equipment and Tools

Circuit Schematic

Schematics are based on visual and instrumental examination of the T530 mainboard, only. Some connections have been guessed and might be wrong.

Terms top side and bottom side refer to the orientation of the motherboard being properly mounted into the laptop.

../gschem/t530-spi-flash-connector-page01.sch.png

T530 SPI Flash Connector Schematic, Page 1(1): Status Quo + SPI Flash Connector + Guessed System Signals

Photo Documentation

../images/t530/IMG<em>0723.JPG

Image 1(19): Find place for the new connector below RAM cover.

../images/t530/IMG</em>0725.JPG

Image 2(19): Protect mainboard surface with tape.

../images/t530/IMG<em>0729.JPG

Image 3(19): Glue connector into place.

../images/t530/IMG</em>0737.JPG

Image 4(19): Remove handle, dismantel mainboard, add solder.

../images/t530/IMG<em>0741.JPG

Image 5(19): Prepare selected pins of SPI chips with solder.

../images/t530/IMG</em>0767.JPG

Image 6(19): Solder four wires to SPI2, route them to other side through Goldfinger GF1 cutout.

../images/t530/IMG<em>0770.JPG

Image 7(19): Flip board to other side, route wires from SPI2 to connector.

../images/t530/IMG</em>0780.JPG

Image 8(19): Flatten wires carefully.

../images/t530/IMG<em>0786.JPG

Image 9(19): Solder wires to SPI1, route them to other side.

../images/t530/IMG</em>0788.JPG

Image 10(19): Flatten wires, again carefully.

../images/t530/IMG<em>0792.JPG

Image 11(19): Cover SPI chips with tape.

../images/t530/IMG</em>0798.JPG

Image 12(19): Flip board to other side, route wires to connector, use tape to fix and protect them.

../images/t530/IMG<em>0805.JPG

Image 13(19): Assemble board into chassis, see how well the connector fits into place.

../images/t530/IMG</em>0806.JPG

Image 14(19): Configure Hardware Protection Mode (HPM) for bottom chip SPI1 ...

../images/t530/screenshot-20220423-175709.png

Image 15(19): ... by setting corresponding bits of its Status Register.

../images/t530/IMG<em>0814.JPG

Image 16(19): ... as well as for top chip SPI2 ...

../images/t530/screenshot-20220423-175843.png

Image 17(19): ... by setting corresponding bits of its Status Register.

../images/t530/IMG</em>0821.JPG

Image 18(19): Finally, enable HPM via Jumper.

../images/t530/IMG_0859.JPG

Image 19(19): The machine now boots with protected firmware.

Connector Pinout Table

    Connector_10x1 Pinout Table       (Image 13)
    ============================================

    Pin     Function      Comment
    ---     --------      ----------------------
      1     #HOLD1        top/left on image
      2     +3.3V
      3     #HOLD0
      4     SCL
      5     MOSI
      6     #CS1
      7     MISO
      8     #CS0
      9     #WP
     10     GND           bottom/right on image

Notices

Section #../doc/t430-spi-flash-connector.md

T430 SPI Flash Connector

This how-to helps you to add an SPI flash connector to your T430 machine, and to apply Hardware Protection Mode (HPM) in the same go.

The ROM used in this how-to has been created with: Zerocat Coreboot Machines

Equipment and Tools

Circuit Schematic

Schematics are based on visual and instrumental examination of the T430 mainboard, only. Some connections have been guessed and might be wrong.

../gschem/t430-spi-flash-connector-page01.sch.png

T430 SPI Flash Connector Schematic, Page 1(5): Status Quo

../gschem/t430-spi-flash-connector-page02.sch.png

T430 SPI Flash Connector Schematic, Page 2(5): Blocking Caps

../gschem/t430-spi-flash-connector-page03.sch.png

T430 SPI Flash Connector Schematic, Page 3(5): Guessed Signal Sources

../gschem/t430-spi-flash-connector-page04.sch.png

T430 SPI Flash Connector Schematic, Page 4(5): Write Protection Network

../gschem/t430-spi-flash-connector-page05.sch.png

T430 SPI Flash Connector Schematic, Page 5(5): SPI Flash Connector

Photo Documentation

../images/t430/DSCN9486.JPG

Image 1(26): Get prepared with new parts.

../images/t430/DSCN9477.JPG

Image 2(26): Locate spare place below cover.

../images/t430/DSCN9490.JPG

Image 3(26): Glue connector into place using hot glue, use angled pinheader as handle.

../images/t430/DSCN9496.JPG

Image 4(26): Use not as much glue as we did!

../images/t430/DSCN9514.JPG

Image 5(26): Locate devices U49, U99 and J27.

../images/t430/DSCN9520.JPG

Image 6(26): Locate J27 on bottom side.

../images/t430/DSCN9528.JPG

Image 7(26): Fill J27 vias with solder.

../images/t430/DSCN9531.JPG

Image 8(26): Make sure J27 vias are properly filled on top side as well.

../images/t430/DSCN9542.JPG

Image 9(26): Route #WP Pins to J27:7, which seems to be unused.

../images/t430/DSCN9546.JPG

Image 10(26): Flatten wires. Wires are 0.25mm CuL with clear varnish isolation.

../images/t430/DSCN9548.JPG

Image 11(26): Cover routes and protect them.

../images/t430/DSCN9504.JPG

Image 12(26): Cut foil on bottom side, carefully.

../images/t430/DSCN9538.JPG

Image 13(26): Prepare glued connector with solder.

../images/t430/DSCN9540.JPG

Image 14(26): Add wires to J27 on bottom side.

../images/t430/DSCN9551.JPG

Image 15(26): Route wires from J27 to new connector. See table for pinout.

../images/t430/DSCN9555.JPG

Image 16(26): Flatten wires.

../images/t430/DSCN9563.JPG

Image 17(26): Cover routes, repair foil.

../images/t430/DSCN9567.JPG

Image 18(26): Mount PCB back into cage.

../images/t430/DSCN9583.JPG

Image 19(26): Use connector to flash bottom 8MB chip.

../images/t430/DSCN9581.JPG

Image 20(26): Use connector to flash top 4MB chip.

../images/t430/DSCN9587.JPG

Image 21(26): Boot the machine once, to allow your GbE controller to copy its configuration data.

../images/t430/DSCN9581.JPG (Register Access)

Image 22(26): Attach top 4MB chip again, ...

../images/t430/screenshot-20220122-094719.png

Image 23(26): ... then set register bits to configure Hardware Protection Mode (HPM).

../images/t430/DSCN9583.JPG (Register Access)

Image 24(26): Attach bottom 8MB chip again, ...

../images/t430/screenshot-20220122-093813.png

Image 25(26): ... then as well set register bits to configure Hardware Protection Mode (HPM).

../images/t430/DSCN9585.JPG

Image 26(26): Bridge Pin9 and Pin10, thus activating HPM. Your machine will boot with a protected ROM.

Connector Pinout Table

    Connector_10x1 Pinout Table with J27 (Image 15)
    ===============================================

    J27   Pin    Function   Comment
    ---   ---    --------   -----------------------
      1     1    #HOLD1     leftmost on image
      4     2    +3.3V
      6     3    #HOLD0
      8     4    SCL
     10     5    MOSI
      2     6    #CS1
      5     7    MISO
      3     8    #CS0
      7     9    #WP
      9    10    GND        rightmost on image

Notices

Section #../doc/x230-spi-flash-connector.md

X230 SPI Flash Connector

This how-to helps you to add an SPI flash connector to your X230 machine, and to apply Hardware Protection Mode (HPM) in the same go.

The ROM used in this how-to has been created with: Zerocat Coreboot Machines

Equipment and Tools

Circuit Schematic

Schematics are based on visual and instrumental examination of the X230 mainboard, only. Some connections have been guessed and might be wrong.

Terms top side and bottom side refer to the orientation of the motherboard being properly mounted into the laptop.

../gschem/x230-spi-flash-connector-page01.sch.png

X230 SPI Flash Connector Schematic, Page 1(2): Status Quo + SPI Flash Connector + Guessed System Signals

../gschem/x230-spi-flash-connector-page02.sch.png

X230 SPI Flash Connector Schematic, Page 2(2): SPI Power

Photo Documentation

../images/x230/DSCN9786.JPG

Image 1(29): Lift keyboard and locate space for new connector with jumper attached.

../images/x230/DSCN9803.JPG

Image 2(29): Glue connector with hot glue, use angled pinheader as handle.

../images/x230/DSCN9805.JPG

Image 3(29): Dismantel motherboard.

../images/x230/DSCN9810.JPG

Image 4(29): Lift adhesive protection foil, carefully.

../images/x230/DSCN9854.JPG

Image 5(29): Locate SPI1, SPI2, R1377, R1378 and R122.

../images/x230/DSCN9860.JPG

Image 6(29): Apply fresh solder to R1377 and R1378; solder first wire to R122 carefully.

../images/x230/DSCN9876.JPG

Image 7(29): Add wires to R1377 and R1378.

../images/x230/DSCN9877.JPG

Image 8(29): Flatten wires, secure them with adhesive tape.

../images/x230/DSCN9882.JPG

Image 9(29): Cut foil like 3 centimeters.

../images/x230/DSCN9884.JPG

Image 10(29): Secure cut with tape, such that it will not grow.

../images/x230/DSCN9886.JPG

Image 11(29): Apply fresh solder to new connector.

../images/x230/DSCN9888.JPG

Image 12(29): Route first three wires.

../images/x230/DSCN9891.JPG

Image 13(29): Add power wires to chip pins.

../images/x230/DSCN9895.JPG

Image 14(29): Add remaining wires to chip pins.

../images/x230/DSCN9900.JPG

Image 15(29): Flatten wires carefully, route them to the connector.

../images/x230/DSCN9905.JPG

Image 16(29): Secure wires with tape.

../images/x230/DSCN9908.JPG

Image 17(29): Repair foil.

../images/x230/DSCN9928.JPG

Image 18(29): Fit motherboard back into chassis.

../images/x230/DSCN9929.JPG

Image 19(29): Apply palm rest and bezel.

../images/x230/DSCN9943.JPG

Image 21(29): Probe and flash lower chip with newly created ROM (lower 8MB binary).

../images/x230/DSCN9949.JPG

Image 22(29): Probe and flash upper chip with newly created ROM (upper 4MB binary).

../images/x230/DSCN9942.JPG

Image 20(29): Boot once to allow the GbE Controller to copy its configuration data.

../images/x230/DSCN9949.JPG

Image 25(29): Access upper chip again, ...

../images/x230/screenshot-20220215-093458.png

Image 24(29): ... and configure Hardware Protection Mode (HPM).

../images/x230/DSCN9943.JPG

Image 23(29): Access lower chip again, ...

../images/x230/screenshot-20220215-093251.png

Image 26(29): ... and configure Hardware Protection Mode (HPM).

../images/x230/DSCN9956.JPG

Image 27(29): Activate HPM with jumper.

../images/x230/DSCN9958.JPG

Image 28(29): Make sure the jumper will not interfere with the trackpoint case.

../images/x230/DSCN9963.JPG

Image 29(29): Your machine now boots with protected ROM.

Connector Pinout Table

    Connector_10x1 Pinout Table (Image 15)
    ======================================

    Pin     Function    Comment
    ---     --------    ------------------
     10     GND         leftmost on image
      9     #WP
      8     #CS0
      7     MISO
      6     #CS1
      5     MOSI
      4     SCL
      3     #HOLD0
      2     +3.3V
      1     #HOLD1      rightmost on image

Notices

Section #../doc/x220-spi-flash-connector.md

X220 SPI Flash Connector

This how-to helps you to add an SPI flash connector to your X220 machine, and to apply Hardware Protection Mode (HPM) in the same go.

The ROM used in this how-to has been created with: Zerocat Coreboot Machines

Equipment and Tools

Circuit Schematic

Schematics are based on visual and instrumental examination of the X220 mainboard, only. Some connections have been guessed and might be wrong.

Terms top side and bottom side refer to the orientation of the motherboard being properly mounted into the laptop.

../gschem/x220-spi-flash-connector-page01.sch.png

X220 SPI Flash Connector Schematic, Page 1(2): Status Quo + SPI Flash Connector + Guessed System Signals

../gschem/x220-spi-flash-connector-page02.sch.png

X220 SPI Flash Connector Schematic, Page 2(2): SPI Power Supply

Photo Documentation

../images/x220/IMG<em>0037.JPG

Image 1(14): Locate space for new connector and its jumper.

../images/x220/IMG</em>0042.JPG

Image 2(14): Use hot glue to fix new connector.

../images/x220/IMG<em>0045.JPG

Image 3(14): Remove palm rest and bezel.

../images/x220/IMG</em>0069.JPG

Image 4(14): Free up systemboard, remove protection foil of BIOS chips.

../images/x220/IMG<em>0076.JPG

Image 5(14): Solder first wire to R430.

../images/x220/IMG</em>0079.JPG

Image 6(14): Route wire nicely to new connector, use tape to fix it.

../images/x220/IMG<em>0084.JPG

Image 7(14): Solder next wires to: SPI1:4, SPI1:3, SPI1:1

../images/x220/IMG</em>0086.JPG

Image 8(14): Route wires across chip case to new connector.

../images/x220/IMG<em>0093.JPG

Image 9(14): Solder next wires to: SPI1:5, SPI1:6, SPI1:7, SPI1:8

../images/x220/IMG</em>0094.JPG

Image 10(14): Again, route wires across chip towards connector.

../images/x220/IMG<em>0107.JPG

Image 11(14): Cover chips and routed wires with protection foil. Use tape to repair.

../images/x220/IMG</em>0112.JPG

Image 12(14): Place systemboard into chassis, cover connector with tape.

../images/x220/IMG<em>0115.JPG

Image 13(14): Reapply bezel and palm rest.

../images/x220/IMG</em>0118.JPG

Image 14(14): Use Chipflasher to flash Zerocat ROM, then boot once, then apply HPM register bits, then set jumper across connector pins 10 and 9. Your machine will then boot with protected firmware.

Connector Pinout Table

    Connector_10x1 Pinout Table   (Image 13)
    ========================================

    Pin     Function    Comment
    ---     --------    --------------------
     10     GND         top/right on image
      9     #WP
      8     #CS0
      7     MISO
      6     -
      5     MOSI
      4     SCL
      3     #HOLD0
      2     +3.3V
      1     -           bottom/left on image

Notices

Section #../doc/t60-spi-flash-connector.md

T60 SPI Flash Connector

This how-to helps you to add an SPI flash connector to your T60 machine, and to apply Hardware Protection Mode (HPM) in the same go.

The ROM used in this how-to has been created with: Zerocat Coreboot Machines

Equipment and Tools

Circuit Schematic (T60 with ATI GPU)

Schematics are based on visual and instrumental examination of the T60 mainboard (with ATI GPU), only. Some connections have been guessed and might be wrong.

Terms top side and bottom side refer to the orientation of the motherboard being properly mounted into the laptop.

../gschem/t60-spi-flash-connector-page01.sch.png

T60 SPI Flash Connector Schematic, Page 1(3): Status Quo + Connector

../gschem/t60-spi-flash-connector-page02.sch.png

T60 SPI Flash Connector Schematic, Page 2(3): Signal Sources

../gschem/t60-spi-flash-connector-page03.sch.png

T60 SPI Flash Connector Schematic, Page 3(3): SPI Power

Photo Documentation (T60 with ATI GPU)

../images/t60/IMG<em>0867.JPG

Image 1(15): Find a place for new SPI connector in unused slot of Modem Daughter Card.

../images/t60/IMG</em>0875.JPG

Image 2(15): Get prepared with new parts.

../images/t60/IMG<em>0885.JPG

Image 3(15): Glue connector onto bottom side of daughter card, use pinheader as handle and distance keeper.

../images/t60/IMG</em>0899.JPG

Image 4(15): Mount daughter card into place as a test.

../images/t60/DSCF0071.JPG

Image 5(15): Route wires along chip edges towards daughter card.

../images/t60/DSCF0075.JPG

Image 6(15): Mount motherboard back into cage.

../images/t60/DSCF0081.JPG

Image 7(15): Turn daughter card into proper position.

../images/t60/DSCF0091.JPG

Image 8(15): Fix daughter card with screws.

../images/t60/DSCF0098.JPG

Image 9(15): Apply heatsink.

../images/t60/DSCF0116.JPG

Image 10(15): Finish mounting.

../images/t60/DSCF0127.JPG

Image 11(15): Attach chipflasher.

../images/t60/screenshot-20220519-181935.png

Image 12(15): Start `kick2` as of *v0.6.7*, then probe chip.

../images/t60/screenshot-20220519-182042.png

Image 13(15): Configure Hardware Protection Mode (HPM).

../images/t60/DSCF0139.png

Image 14(15): Set jumper in order to enable HPM.

../images/t60/DSCF0142.JPG

Image 15(15): The laptop now boots with protected firmware.

Connector Pinout Table

    Connector_8x1 Pinout Table       (Image 4)
    ==========================================

    Pin     Function      Comment
    ---     --------      --------------------
      8     GND           top/right on image
      7     #WP
      6     #CS
      5     MISO
      4     MOSI
      3     SCL
      2     #HOLD
      1     +3.3V         bottom/left on image

Photo Documentation (T60 with Intel GPU only)

This mainboard provides more space, as it lacks the ATI GPU and related power parts. Put protective tape on the flat mainboard area and glue the connector on top of it. See images for alternate routing.

../images/t60/DSCF0227.JPG

Image 1(2): Alternate route and place for SPI Flash Connector.

../images/t60/DSCF0247.JPG

Image 2(2): Keyboard attached, HPM Jumper applied.

Connector Pinout Table

    Connector_8x1 Pinout Table       (Image 2)
    ==========================================

    Pin     Function      Comment
    ---     --------      --------------------
      8     GND           top/left on image
      7     #WP
      6     #CS
      5     MISO
      4     MOSI
      3     SCL
      2     #HOLD
      1     +3.3V         bottom/right on image

Notices

Section #../doc/GNU-FDL.md

GNU Free Documentation License

Version 1.3, 3 November 2008

Copyright (C) 2000, 2001, 2002, 2007, 2008 Free Software Foundation, Inc. http://fsf.org/

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

0. PREAMBLE

The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.

This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.

We have designed this License in order to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

1. APPLICABILITY AND DEFINITIONS

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.

The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.

The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.

A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".

Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.

The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

The "publisher" means any person or entity that distributes copies of the Document to the public.

A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.

2. VERBATIM COPYING

You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.

You may also lend copies, under the same conditions stated above, and you may publicly display copies.

3. COPYING IN QUANTITY

If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.

If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.

If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.

It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.

4. MODIFICATIONS

You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:

If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.

You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties—for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.

You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.

The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.

5. COMBINING DOCUMENTS

You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.

The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.

In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".

6. COLLECTIONS OF DOCUMENTS

You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.

You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.

7. AGGREGATION WITH INDEPENDENT WORKS

A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.

If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.

8. TRANSLATION

Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.

If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.

9. TERMINATION

You may not copy, modify, sublicense, or distribute the Document except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, or distribute it is void, and will automatically terminate your rights under this License.

However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.

Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.

Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, receipt of a copy of some or all of the same material does not give you any rights to use it.

10. FUTURE REVISIONS OF THIS LICENSE

The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.

Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. If the Document specifies that a proxy can decide which future versions of this License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Document.

11. RELICENSING

"Massive Multiauthor Collaboration Site" (or "MMC Site") means any World Wide Web server that publishes copyrightable works and also provides prominent facilities for anybody to edit those works. A public wiki that anybody can edit is an example of such a server. A "Massive Multiauthor Collaboration" (or "MMC") contained in the site means any set of copyrightable works thus published on the MMC site.

"CC-BY-SA" means the Creative Commons Attribution-Share Alike 3.0 license published by Creative Commons Corporation, a not-for-profit corporation with a principal place of business in San Francisco, California, as well as future copyleft versions of that license published by that same organization.

"Incorporate" means to publish or republish a Document, in whole or in part, as part of another Document.

An MMC is "eligible for relicensing" if it is licensed under this License, and if all works that were first published under this License somewhere other than this MMC, and subsequently incorporated in whole or in part into the MMC, (1) had no cover texts or invariant sections, and (2) were thus incorporated prior to November 1, 2008.

The operator of an MMC Site may republish an MMC contained in the site under CC-BY-SA on the same site at any time before August 1, 2009, provided the MMC is eligible for relicensing.

ADDENDUM: How to use this License for your documents

To use this License in a document you have written, include a copy of the License in the document and put the following copyright and license notices just after the title page:

    Copyright (C)  YEAR  YOUR NAME.
    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 is included in the section entitled "GNU
    Free Documentation License".

If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with … Texts." line with this:

    with the Invariant Sections being LIST THEIR TITLES, with the
    Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.

If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.

If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.