Difference between revisions of "Board:lenovo/x60/Installation"

From coreboot
Jump to: navigation, search
(explain power cycle)
Line 26: Line 26:
 
# Run <code>bucts 1</code>
 
# Run <code>bucts 1</code>
 
# Run <code>flashrom -p internal:laptop=force_I_want_a_brick -w coreboot.rom</code>
 
# Run <code>flashrom -p internal:laptop=force_I_want_a_brick -w coreboot.rom</code>
#: This will be slow, and shall generate an erase error at e.g. 0x1f0000 when working with a 2 Mbyte flash chip. See [http://www.flashrom.org/pipermail/flashrom/2012-April/009121.html Peter's mail] before you start to panic.
+
#: This will be slow, it will output errors for addresses 0x0 and 0x1f0000 when working with a 2 Mbyte flash chip, and it will say "FAILED!" at the end, see [http://www.flashrom.org/pipermail/flashrom/2012-April/009121.html Peter's mail] before you panic.
 
# Power cycle the machine (i.e. a cold boot, not just a reboot), now starting with coreboot
 
# Power cycle the machine (i.e. a cold boot, not just a reboot), now starting with coreboot
 
# Undo the flashrom patch, so that you have a stock flashrom
 
# Undo the flashrom patch, so that you have a stock flashrom
# Run <code>bucts 0</code> (if you run bucts 0, do not power off and run the next command(s))
+
# Run <code>bucts 0</code> (do '''NOT''' power off before running flashrom in the next step, or you '''will''' brick the machine!)
 
# Run <code>flashrom -p internal:laptop=force_I_want_a_brick -w coreboot.rom</code>.
 
# Run <code>flashrom -p internal:laptop=force_I_want_a_brick -w coreboot.rom</code>.
 
#: This will successfully overwrite the entire flash chip, including the last 64k that were write protected with the factory BIOS.
 
#: This will successfully overwrite the entire flash chip, including the last 64k that were write protected with the factory BIOS.

Revision as of 19:12, 24 September 2012

Flashing on the laptop instructions.

Lenovo X60, X60s, T60 and T60p flashing instructions.

These Lenovo laptops have a register that must be flipped before coreboot can be flashed.

For those/some models with SPI flash chips you have also to modify flashrom. Because the chipset locks down the available commands that flashrom can send to the flash chip, you also need to change the flashrom source in a way that is not suitable to upstream. Flash chips can be identified by various commands (REMS*, RDID etc.). Some of them reply with an ID for the vendor and the exact chip model; others just reply with a single byte which is fine if there is only a small number of chips to distinguish, but won't work for the huge number of flash chips known to flashrom. The problem with the vendor BIOS is that it forbids the higher quality identification commands, so you need to force flashrom to use the lower quality opcode for the chip in your Thinkpad. You have to know the chip model beforehand (e.g. by inspection).

You will need: the flashrom source, a small patch for it, and the bucts utility.

  1. Patch flashrom to use RES1 SPI identification and spi_chip_write_1 for your flash chip, as well as change the flash chip model id to fit the RES1 command.
    Alternatively, you can copy the existing definition first as it is done in this patch. Choose either method: apply the patch in the link, or do the patch yourself, as per instruction below.
    • Find the definition of your flash chip in flashrom's flashchips.c
    • Change the .probe field to probe_spi_res1
    • Modify .model_id field to the RES1 ID given in the datasheet of the flash chip
    • Change the .write field to spi_chip_write1
  2. Run flashrom -p internal:laptop=force_I_want_a_brick -r factory.bin
    This step is IMPORTANT since the factory BIOS in your machine is tied to your particular system board (or "planar" in IBM FRU terms) with a unique ID not present in factory BIOS updates.
  3. Run dd if=coreboot.rom of=top64k.bin bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x10000] count=64k
  4. Run dd if=coreboot.rom bs=1 skip=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k | hexdump
    Verify that the complete range is filled with ff bytes before proceeding! The above command must output:
    0000000 ffff ffff ffff ffff ffff ffff ffff ffff
    *
    0010000
    If this is not the case, the coreboot image needs to be rebuilt with the second-to-last 64kbyte block unused.
  5. Run dd if=top64k.bin of=coreboot.rom bs=1 seek=$[$(stat -c %s coreboot.rom) - 0x20000] count=64k conv=notrunc
  6. Run bucts 1
  7. Run flashrom -p internal:laptop=force_I_want_a_brick -w coreboot.rom
    This will be slow, it will output errors for addresses 0x0 and 0x1f0000 when working with a 2 Mbyte flash chip, and it will say "FAILED!" at the end, see Peter's mail before you panic.
  8. Power cycle the machine (i.e. a cold boot, not just a reboot), now starting with coreboot
  9. Undo the flashrom patch, so that you have a stock flashrom
  10. Run bucts 0 (do NOT power off before running flashrom in the next step, or you will brick the machine!)
  11. Run flashrom -p internal:laptop=force_I_want_a_brick -w coreboot.rom.
    This will successfully overwrite the entire flash chip, including the last 64k that were write protected with the factory BIOS.


See also http://thread.gmane.org/gmane.linux.bios/69354 http://thread.gmane.org/gmane.linux.bios.flashrom/575

Recovery

If you had a bad flash you will need a recovery method. you will need:

  • the x60 manual (for disassembling the laptop)
  • some clip, like a pomona for instance.
  • an external flashrom programmer

<to be continued>

Status

<insert the status here>