Piotr Król
|
After Width: | Height: | Size: 381 KiB |
|
After Width: | Height: | Size: 402 KiB |
|
After Width: | Height: | Size: 389 KiB |
|
After Width: | Height: | Size: 149 KiB |
|
After Width: | Height: | Size: 55 KiB |
|
After Width: | Height: | Size: 262 KiB |
|
After Width: | Height: | Size: 93 KiB |
|
After Width: | Height: | Size: 118 KiB |
|
After Width: | Height: | Size: 177 KiB |
|
After Width: | Height: | Size: 255 KiB |
|
After Width: | Height: | Size: 191 KiB |
|
After Width: | Height: | Size: 399 KiB |
|
After Width: | Height: | Size: 306 KiB |
|
After Width: | Height: | Size: 149 KiB |
@@ -121,6 +121,18 @@ keys during updates.
|
||||
|
||||
### Flashing Dasharo
|
||||
|
||||
**WARNING**: If you use and external/discrete GPU and migrate to Dasharo, be
|
||||
sure to unplug the dGPU first (when machine is powered off before proceeding
|
||||
with flashing), as Dasharo firmware does not support all GPU cards properly yet
|
||||
(as of version v1.0.0). There is high risk for the graphical output to break in
|
||||
the firmware when dGPU is connected. Effectively it leaves the only option to
|
||||
boot in blind into previously installed OS (if the platform does not brick and
|
||||
if an OS is present on a disk). The first boot may take up to 2 minutes to
|
||||
fully train the memory, so be patient and wait for the Dasharo logo to appear,
|
||||
subsequent boots will take only seconds. MSI EZ debug leds are not supported by
|
||||
Dasharo and you may notice red led to be lit. If the platform boots with
|
||||
integrated GPU, you may try to plug the external GPU back and boot again.
|
||||
|
||||
To flash Dasharo on the platform, execute the following command:
|
||||
|
||||
> Replace the `VERSION` in firmware file name with the version you want to
|
||||
@@ -130,10 +142,10 @@ To flash Dasharo on the platform, execute the following command:
|
||||
sudo flashrom -p internal -w msi_ms7d25_vVERSION.rom --ifd -i bios
|
||||
```
|
||||
|
||||
After the command succeeds, invoke `poweroff` or click the power off in the GUI
|
||||
to shutdown the board. Press `ENTER` when prompted on the screen. Power on the
|
||||
board back. Reboot will not work as some memory settings are preserved after
|
||||
reboot and FSP fails to train the memory. Poweroff is required.
|
||||
After the command succeeds, invoke `sudo poweroff` or click the power off in
|
||||
the GUI to shutdown the board. Press `ENTER` when prompted on the screen. Power
|
||||
on the board back. Reboot will not work as some memory settings are preserved
|
||||
after reboot and FSP fails to train the memory. Poweroff is required.
|
||||
|
||||
### Flashing back vendor firmware
|
||||
|
||||
|
||||
@@ -19,6 +19,8 @@ platform.
|
||||
|
||||
### External flashing with programmer
|
||||
|
||||
#### RTE
|
||||
|
||||
In this case, using external programmer is necessary. We are using
|
||||
[RTE](https://3mdeb.com/open-source-hardware/#rte)
|
||||
here.
|
||||
@@ -45,6 +47,131 @@ flashrom -p linux_spi:dev=/dev/spidev1.0,spispeed=16000 -w 7D25v13/E7D25IMS.130
|
||||
|
||||
* First boot after the recovery process is significantly longer
|
||||
|
||||
### CH341A
|
||||
|
||||
#### Prerequisites
|
||||
|
||||
1. CH341A kit with 1.8V level-shifter. Can be bought on e.g. [Amazon](https://www.amazon.com/programmer-ch341a-Programmer-Adapter-Converter/dp/B07WP9FKZ2)
|
||||
|
||||
|
||||
|
||||
2. WSON8 probe. Can be bought from China on Aliexpress or eBay.
|
||||
|
||||
|
||||
|
||||
3. USB2.0 Female-Male extension cord 0.5m or longer (optional)
|
||||
|
||||
|
||||
|
||||
4. Machine with Linux and flashrom.
|
||||
|
||||
#### Connection
|
||||
|
||||
First start with assembling the CH341A and the 1.8V adapter. Pay attention to
|
||||
which holes you attach the adapter. You should use the holes marked as 25XX
|
||||
(closer to the USB plug):
|
||||
|
||||
|
||||
|
||||
Place the 1.8V adapter in the holes and lock it with the lever. Be sure that
|
||||
the arrow on the adapter is facing the black lever (opposite side of USB plug):
|
||||
|
||||
|
||||
|
||||
Now take the breakout board with pin headers:
|
||||
|
||||
|
||||
|
||||
and plug it int other 1.8V adapter, be sure that numbers 1-4 on the breakout
|
||||
match the numbers 1 and 4 on the adapter:
|
||||
|
||||
|
||||
|
||||
Numbers should be visible on the upper side after assembling:
|
||||
|
||||
|
||||
|
||||
Next, take the WSON8 probe and locate the white dot on the needles side (it
|
||||
will indicate the first reference pin, although you may use any corner pin you
|
||||
want):
|
||||
|
||||
|
||||
|
||||
Check which wire is connecting to this pin (the connection should be 1 to 1).
|
||||
In my case it is white wire and it will be used as reference to connect the
|
||||
wires to the breakout board:
|
||||
|
||||
|
||||
|
||||
The wires should follow the same order of colors as on the probe (keep them
|
||||
straight, do not cross). Repeat with the other 4 wires on the other side of the
|
||||
probe:
|
||||
|
||||
|
||||
|
||||
Now the connection is ready. Time to locate the flash chip of the board.
|
||||
|
||||
#### Flashing
|
||||
|
||||
Connect the CH341A USB plug to the host machine which will be doing the
|
||||
flashing process (optionally use the USB extension cord for convenience).
|
||||
Locate the flash chip on the MSI PRO Z690-A DDR4 board:
|
||||
|
||||
|
||||
|
||||
Locate the first pin on the flash chip (marked with a circle on the flash chip
|
||||
package and indicated by number 1 printed on the board - red circle):
|
||||
|
||||
|
||||
|
||||
Attach the WSON8 probe matching the first pin of the probe (white wire) and
|
||||
first pin of the flash chip:
|
||||
|
||||
|
||||
|
||||
Now on the Linux machine check if the flash is detected using a sample command
|
||||
|
||||
```bash
|
||||
sudo flashrom -p ch341a_spi -r firmware.bin
|
||||
```
|
||||
|
||||
You should see something like this:
|
||||
|
||||
```bash
|
||||
flashrom v1.2-567-gf4eb405 on Linux 5.19.9-200.fc36.x86_64 (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 Winbond flash chip "W25Q256.W" (32768 kB, SPI) on ch341a_spi.
|
||||
Reading flash... done.
|
||||
```
|
||||
|
||||
You don't need to wait for the command completion and interrupt it with Ctrl+C
|
||||
shortcut, it just serves as a confirmation of good connection. If yo udecide to
|
||||
interrupt it, reset the CH341A programmer bu unpluging and repluging it to USB
|
||||
port. Now stabilize your hand holding the WSON8 probe on the flash chip and
|
||||
invoke the real flashing command (e.g. if your original/working firmware backup
|
||||
is saved as `firmware_backup.bin`):
|
||||
|
||||
```bash
|
||||
sudo flashrom -p ch341a_spi -w firmware_backup.bin
|
||||
```
|
||||
|
||||
Note that USB programmers are pretty slow, the whole operation make take
|
||||
several minutes (can be 10-15 minutes in worst case). At the end of operation
|
||||
you should see:
|
||||
|
||||
```bash
|
||||
flashrom v1.2-567-gf4eb405 on Linux 5.19.9-200.fc36.x86_64 (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 Winbond flash chip "W25Q256.W" (32768 kB, SPI) on ch341a_spi.
|
||||
Reading old flash chip contents... done.
|
||||
Erasing and writing flash chip... Erase/write done.
|
||||
Verifying flash... VERIFIED.
|
||||
```
|
||||
|
||||
## SMBIOS unique data recovery
|
||||
|
||||
### Serial number format and recovery
|
||||
|
||||