docs/{hardware,install}/e6430.md: Fix inaccuracies
Most of the issues were just leftover from the E6400 docs which are not accurate for the E6430. Signed-off-by: Nicholas Chin <nic.c3.14@gmail.com>master
parent
42814e9326
commit
b52b93ebad
|
@ -15,14 +15,14 @@ Dell Latitude E6430
|
||||||
| **Variants** | E6430 with Intel GPU supported |
|
| **Variants** | E6430 with Intel GPU supported |
|
||||||
| **Released** | 2012 |
|
| **Released** | 2012 |
|
||||||
| **Chipset** | Intel Ivy Bridge |
|
| **Chipset** | Intel Ivy Bridge |
|
||||||
| **CPU** | Intel Core i3, i5 or i7 . |
|
| **CPU** | Intel Core i3, i5 or i7 |
|
||||||
| **Graphics** | Intel HD 4000 and unsupported NVidia NVS 5200M |
|
| **Graphics** | Intel HD 4000 and unsupported Nvidia NVS 5200M |
|
||||||
| **Display** | 1366x768/1600x900 TFT |
|
| **Display** | 1366x768/1600x900 TFT |
|
||||||
| **Memory** | 4 or 8GB (Upgradable to 16GB) |
|
| **Memory** | 4 or 8GB (Upgradable to 16GB) |
|
||||||
| **Architecture** | x86_64 |
|
| **Architecture** | x86_64 |
|
||||||
| **EC** | SMSC MEC5055 with proprietary firmware |
|
| **EC** | SMSC MEC5055 with proprietary firmware |
|
||||||
| **Original boot firmware** | Dell UEFI |
|
| **Original boot firmware** | Dell UEFI |
|
||||||
| **Intel ME/AMD PSP** | Present. Can be completely disabled. |
|
| **Intel ME/AMD PSP** | Present, neutered |
|
||||||
| **Flash chip** | 2xSOIC-8, 12MiB (8MiB and 4MiB in combination) |
|
| **Flash chip** | 2xSOIC-8, 12MiB (8MiB and 4MiB in combination) |
|
||||||
|
|
||||||
|
|
||||||
|
|
|
@ -114,16 +114,17 @@ is included in that program's directory, or you can read it online here:
|
||||||
|
|
||||||
<https://browse.libreboot.org/lbmk.git/plain/util/dell-flash-unlock/README.md>
|
<https://browse.libreboot.org/lbmk.git/plain/util/dell-flash-unlock/README.md>
|
||||||
|
|
||||||
Literally just run that program, and do what it says. You run it once, and shut
|
Literally just run that program, and do what it says. You run it once, shut
|
||||||
down, and when you do, the system brings itself back up automatically. Then
|
down, and then power on the machine. Then run it again to confirm that the
|
||||||
you run it and flash it unlocked. Then you run it again. The source code is
|
flash is unlocked. The source code is intuitive enough that you can easily get
|
||||||
intuitive enough that you can easily get the gist of it; it's writing some EC
|
the gist of it; it's writing some EC commands and changing some chipset config
|
||||||
commands and changing some chipset config bits. The EC on this machine is
|
bits. The EC on this machine is hooked up to the `HDA_SDO` signal, also known
|
||||||
hooked up to the `GPIO33` signal, sometimes called `HDA_DOCK_EN`, which sets
|
as the Flash Descriptor Override (FDO), which disables any flash protection by
|
||||||
the flash descriptor override thus disabling any flash protection by the IFD.
|
the IFD. When booted with the FDO set, the original Dell firmware disables all
|
||||||
It also bypasses the SMM BIOS lock protection by disabling SMIs, and Dell's
|
other BIOS write protections such as SMM BIOS lock bits.
|
||||||
BIOS doesn't set any other type of protection either such as writing to
|
|
||||||
Protected Range registers.
|
*Make sure* to make a backup of the original firmware before proceeding to
|
||||||
|
flash; see the instructions below.
|
||||||
|
|
||||||
When you flash it, you can use this command:
|
When you flash it, you can use this command:
|
||||||
|
|
||||||
|
@ -163,11 +164,11 @@ How to flash externally
|
||||||
|
|
||||||
Refer to [spi.md](spi.md) as a guide for external re-flashing.
|
Refer to [spi.md](spi.md) as a guide for external re-flashing.
|
||||||
|
|
||||||
The SPI flash chip shares a voltage rail with the ICH9 southbridge, which is
|
The SPI flash chip shares a voltage rail with the chipset, which is not
|
||||||
not isolated using a diode. As a result, powering the flash chip externally
|
isolated using a diode. As a result, powering the flash chip externally may
|
||||||
causes the ICH9 to partially power up and attempt to drive the SPI clock pin
|
cause the QM77 chipset to partially power up and drive the SPI pins, which can
|
||||||
low, which can interfere with programmers such as the Raspberry Pi. See
|
interfere with programmers such as the Raspberry Pi. See [RPi Drive
|
||||||
[RPi Drive Strength](spi.md#rpi-drive-strength) for a workaround.
|
Strength](spi.md#rpi-drive-strength) for a workaround.
|
||||||
|
|
||||||
Have a look online for videos showing how to disassemble, if you wish to
|
Have a look online for videos showing how to disassemble, if you wish to
|
||||||
externally re-flash.
|
externally re-flash.
|
||||||
|
|
Loading…
Reference in New Issue