diff --git a/usb_config.md b/usb_config.md index 2e3af65..4900772 100644 --- a/usb_config.md +++ b/usb_config.md @@ -69,7 +69,7 @@ A log (`femtofox-config.log`) is saved to `/home/femto` and the USB drive (excep ### Boot codes When the Femtofox is finished booting, it will blink its User LED (see below) in a pattern which can be used to gather info on its status or help diagnose issues.  -| LED blink pattern | Meaning | Possible causes | Solutions | +| LED blink pattern| Meaning| Possible causes| Solutions| |--|--|--|--| |
⚠️
**──────────**
1 very long blink, lasting 5 seconds| • Failed to mount USB drive. Ignoring.| Invalid filesystem
•Corrupted partition table
• Defective USB drive
• Defective USB OTG adapter| • Use a supported partition (FAT32, exFAT, NTFS, ext4)
• Repair partition table
• Try another USB drive
• Try another USB OTG adapter|
|
⚠️
**─── ───**
2 long blinks, each lasting 1.5 seconds|femtofox-config.txt is configured to skip if log exists.| femtofox-config.txt is configured to skip if USB drive mounted successfully but femtofox-config.txt contains `dont_run_if_log_exists="true"` and a log is present on the USB drive. Ignoring.| • Remove log from USB drive.
• Remove `dont_run_if_log_exists` line from femtofox-config.txt.|
@@ -81,5 +81,5 @@ When the Femtofox is finished booting, it will blink its User LED (see below) in
> \[!NOTE\]
> Boot codes can appear in sequence - for example: one long (4 second) blink, followed by 5 medium (half second) blinks means the USB drive failed to mount, and that the boot sequence is complete.
\ No newline at end of file