commit 132e433c3963905febbb64299aa0cfb8862a9c8f
author Jan Kundrát <jan.kundrat@cesnet.cz> Mon Oct 21 12:08:18 2024 +0200
committer Jan Kundrát <jan.kundrat@cesnet.cz> Mon Oct 21 12:08:18 2024 +0200
tree c9170ed0e1665f27938d499b0ba03f1b83e2321e
parent 22e21413e439ed93a0c9a62fe3292b5e4567d97a

docs: plug the USB drive while the power is off

Apparently, there are some USB flash drives which do not work when
hot-plugged. I have never seen a behavior like that, but Michal says
that it works like that for him all the time.

Change-Id: Ifd3d5a4a5e5e28b9f6b31eb7be031d02932ffb0a
Reported-by: Michal Altmann <m.altmann@trillinis.com>

README.md

diff --git a/README.md b/README.md
index d45c42b..58414b3 100644
--- a/README.md
+++ b/README.md
@@ -72,18 +72,20 @@
 
 On a regular Clearfog Base with an eMMC, one has to bootstrap the device first.
 If recovering a totally bricked board (or one that is fresh from factory), use the `kwboot` command to upload the initial, new enough U-Boot via the console.
-Ensure that the jumpers are set to `0 1 0 0 1` (default for eMMC boot is `0 0 1 1 1`):
+Power the system down, and ensure that the jumpers are set to `0 1 0 0 1` (default for eMMC boot is `0 0 1 1 1`):
 
 ![DIP switch positins for ClearFog eMMC/UART booting](./doc/img/clearfog-booting.jpeg)
 
+Prepare a USB flash disk with a raw bootable image, `images/usb-flash.img`.
+Use a tool such as `dd` to overwrite the raw block device, do not copy the image file.
+Plug the USB flash disk in.
 Then, use U-Boot's `kwboot` tool:
 
 ```sh
 ./host/bin/kwboot -b ./u-boot-spl.kwb -t -p /dev/ttyUSB0
 ```
-Prepare a USB flash disk with a raw bootable image, `images/usb-flash.img`.
-Use a tool such as `dd` to overwrite the raw block device, do not copy the image file.
-Once in U-Boot, plug the USB flash disk and execute:
+...and turn the power on.
+Once in U-Boot, execute:
 
 ```sh
 usb start; fatload usb 0:1 00800000 boot.scr; source 00800000