mirror of
https://github.com/Dasharo/docs.git
synced 2026-06-13 10:16:57 -07:00
dell_optiplex initial documentation
Signed-off-by: Piotr Król <piotr.krol@3mdeb.com>
This commit is contained in:
Piotr Król
Binary file not shown.
|
After Width: | Height: | Size: 1.1 MiB |
@@ -34,9 +34,12 @@ To build coreboot image, follow the steps below:
|
||||
docker run --rm -it \
|
||||
-v $PWD:/home/coreboot/coreboot \
|
||||
-w /home/coreboot/coreboot \
|
||||
coreboot/coreboot-sdk:0ad5fbd48d /bin/bash
|
||||
coreboot/coreboot-sdk:VERSION /bin/bash
|
||||
```
|
||||
|
||||
* `VERSION` should be replaced according to version you building:
|
||||
- `v0.1.0` - `2021-09-23_b0d87f753c`
|
||||
|
||||
5. Inside of the container, configure and start the build process:
|
||||
|
||||
```bash
|
||||
|
||||
@@ -4,84 +4,60 @@
|
||||
|
||||
---
|
||||
|
||||
## **Prequisitions**
|
||||
Following documentation describe process of recovering hardware from brick
|
||||
state with [RTE]() and Dasharo open-source firmware. Following procedure is
|
||||
supported for following models
|
||||
|
||||
1. To proceed with recovery `.rom` file with backup vendor firmware will be
|
||||
neccesary eg. `backup.rom`.
|
||||
<center>
|
||||
|
||||
Backup file should be generated before making any changes in device flash
|
||||
chip according to documentation in
|
||||
[BIOS backup](https://docs.dasharo.com/variants/dell_optiplex/initial-deployment/#bios-backup)
|
||||
section.
|
||||
| Vendor | Model |
|
||||
:-------:|:-----:|
|
||||
|Dell | OptiPlex 7010 SFF |
|
||||
|Dell | OptiPlex 7010 DT |
|
||||
|Dell | OptiPlex 9010 SFF |
|
||||
|
||||
1. Set jumper according to
|
||||
[hardware preparation](https://docs.dasharo.com/variants/dell_optiplex/initial-deployment/#hardware-preparation)
|
||||
</center>
|
||||
|
||||
1. Install flashrom using
|
||||
[flashrom installation guide](https://docs.dasharo.com/variants/dell_optiplex/initial-deployment/#flashrom-installation)
|
||||
## Step 1: Prepare hardware
|
||||
|
||||
---
|
||||
1. To prepare hardware please follow
|
||||
[hardware preparation](../initial-deployment/#hardware-preparation) procedure.
|
||||
2. Follow instruction in the video to remove heatsink:
|
||||
<center>
|
||||
<iframe width="640" height="480"
|
||||
src="http://www.youtube.com/embed/TiUSTo-XwPo">
|
||||
</iframe>
|
||||
</center>
|
||||
|
||||
## **Internal flashing**
|
||||
## Step 2: Connect SOIC-8 Pomona clip between RTE and target
|
||||
|
||||
Flash firmware on you Dell OptiPlex machine using below command:
|
||||
## Step 2: Connect RTE
|
||||
|
||||
```bash
|
||||
sudo flashrom -p internal -i me -w <optiplex_firmware>
|
||||
```
|
||||
<center>
|
||||
|
||||
</center>
|
||||
|
||||
for example:
|
||||
1. Connect J2 Orange Pi Zero system debug output
|
||||
2. Power the board and confirm it boots
|
||||
3. **Please note** typical convention of USB-UART converter colors is as follows
|
||||
- black - GND
|
||||
- red - +5V
|
||||
- green - TX
|
||||
- white - RX
|
||||
4. Connect terminal to RTE and read OS version:
|
||||
```shell
|
||||
sudo minicom -b 115200 -D /dev/ttyUSB0 -o -C /tmp/minicom.cap
|
||||
```
|
||||
* `-b 115200` sets baudrate
|
||||
* `-D /dev/ttyUSB0` points to USB-UART converter device, it can be different if
|
||||
you already have some devices connected or you use different operating system
|
||||
* `-o` skip initialization
|
||||
* `-C /tmp/minicom.cap` capture serial terminal output, if you will have
|
||||
problems with exercises please post this file
|
||||
5. Login using following credentials:
|
||||
```shell
|
||||
login: root
|
||||
password: meta-rte
|
||||
```
|
||||
|
||||
```bash
|
||||
sudo flashrom -p internal -i me -w /tmp/backup.rom
|
||||
```
|
||||
|
||||
output:
|
||||
|
||||
```bash
|
||||
flashrom v1.2-551-gf47ff31 on Linux 5.10.0-9-amd64 (x86_64)
|
||||
flashrom is free software, get the source code at https://flashrom.org
|
||||
|
||||
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
|
||||
Found chipset "Intel Q77".
|
||||
Enabling flash write... SPI Configuration is locked down.
|
||||
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.
|
||||
Enabling hardware sequencing due to multiple flash chips detected.
|
||||
OK.
|
||||
Found Programmer flash chip "Opaque flash chip" (12288 kB, Programmer-specific) mapped at physical address 0x0000000000000000.
|
||||
Reading ich descriptor... done.
|
||||
Using regions: "me", "bios".
|
||||
Reading old flash chip contents... done.
|
||||
Erasing and writing flash chip... Erase/write done.
|
||||
Verifying flash... VERIFIED.
|
||||
```
|
||||
|
||||
If you get a warning:
|
||||
|
||||
```bash
|
||||
WARNING! You may be running flashrom on an unsupported laptop.
|
||||
```
|
||||
|
||||
And programmer initialization failed, run command:
|
||||
|
||||
```bash
|
||||
flashrom -p internal:laptop=this_is_not_a_laptop -w /tmp/backup.rom -i me
|
||||
```
|
||||
|
||||
If you have placed the jumper correctly, you should see the following message
|
||||
in flashrom's output:
|
||||
|
||||
```bash
|
||||
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.
|
||||
```
|
||||
|
||||
A newer version of flashrom may not display the warning about unsupported
|
||||
chipset as it already may be marked as tested. Our team has verified that
|
||||
the flashrom updates firmware reliably on this chipset.
|
||||
|
||||
If you will face any issues please refer to
|
||||
[troubleshooting section](https://docs.dasharo.com/variants/dell_optiplex/initial-deployment/#troubleshooting).
|
||||
|
||||
+1
-1
@@ -184,7 +184,7 @@ nav:
|
||||
- 'Introduction': transparent-validation/rte/introduction.md
|
||||
- 'Specification': transparent-validation/rte/v1.1.0/specification.md
|
||||
- 'Getting Started': transparent-validation/rte/v1.1.0/getting-started.md
|
||||
- 'RTE and PC Engines': transparent-validation/rte/pcengines.md
|
||||
# - 'RTE and PC Engines': transparent-validation/rte/pcengines.md
|
||||
- 'RTE Reference OS': transparent-validation/rte/v1.1.0/reference-os.md
|
||||
- 'Revision History': transparent-validation/rte/revision-history.md
|
||||
- 'SD Wire':
|
||||
|
||||
Reference in New Issue
Block a user