From cdab771f07bc96606eb63aa28b016c7672a0e97d Mon Sep 17 00:00:00 2001
From: noon92 <40807970+noon92@users.noreply.github.com>
Date: Sat, 25 Jan 2025 02:26:46 +0200
Subject: [PATCH] usb_config.md updated from https://stackedit.io/
---
usb_config.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/usb_config.md b/usb_config.md
index cdae01b..a3c0e3b 100644
--- a/usb_config.md
+++ b/usb_config.md
@@ -75,9 +75,9 @@ When the Femtofox is finished booting, it will blink its User LED (see below) in
|
⚠️
**─── ───**
2 long blinks, each lasting 1.5 seconds | femtofox-config.txt is configured to skip if log exists. | 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 or remove `dont_run_if_log_exists` line from femtofox-config.txt |
| ⚠️
**─── ─── ───**
3 long blinks, each lasting 1.5 seconds | USB drive mounted successfully but femtofox-config.txt was not found. Ignoring. | Config file missing. | Create configuration file as described above. |
| ⚠️
**─── ─── ─── ─── ───**
5 long blinks, each lasting 1.5 seconds | USB drive mounted successfully and femtofox-config.txt was found but did not contain readable configuration data. Ignoring. | Configuration file improperly formatted or contains no data. | Check configuration file contents as described above. |
-| ⚠️
**── ── **⁃ ⁃**
2 long blinks, each lasting 1 second, then 2 short blinks, each lasting 1/4 of a second. Repeats twice | Error while trying to implement a Meshtastic setting after 3 attempts. Some settings may have been implemented successfully. | • The error may be transient.
• Configuration file may contain improper data. | • Try again.
• Check configuration file contents as described above.
• Check the log.
This pattern may flash before other patterns. The pattern will repeat once for each failed setting. |
-| ✅
• • • • • • • • • •
10 very fast blinks, each lasting 1/8th of a second | USB drive mounted successfully, and femtofox-config.txt was found and contained configuration data which was sent for deployment. Any affected services will now restart. You can disconnect the USB drive. | This does not mean that the information in the config file is correct - only that it was readable.
Note that the "success" boot code will flash if at least one setting is successfully read - even if the setting was not implemented successfully. | |
-| ✅
\_\_ \_\_ \_\_ \_\_ \_\_
5 medium blinks, each lasting 0.5 seconds | Boot complete. Appears on every successful boot and always appears last. | | \_\_ \_\_
5 medium blinks, each lasting 0.5 seconds | Boot complete. Appears on every successful boot and always appears last.| | |
+| ⚠️
**── ── - -**
2 long blinks, each lasting 1 second, then 2 short blinks, each lasting 1/4 of a second. Repeats twice | Error while trying to implement a Meshtastic setting after 3 attempts. Some settings may have been implemented successfully. | • The error may be transient.
• Configuration file may contain improper data. | • Try again.
• Check configuration file contents as described above.
• Check the log.
This pattern may flash before other patterns. The pattern will repeat once for each failed setting. |
+| ✅
**· · · · · · · · · ·**
10 very fast blinks, each lasting 1/8th of a second | USB drive mounted successfully, and femtofox-config.txt was found and contained configuration data which was sent for deployment. Any affected services will now restart. You can disconnect the USB drive. | This does not mean that the information in the config file is correct - only that it was readable.
Note that the "success" boot code will flash if at least one setting is successfully read - even if the setting was not implemented successfully. | |
+| ✅
**─**
5 medium blinks, each lasting 0.5 seconds | Boot complete. Appears on every successful boot and always appears last. | | \_\_ \_\_
5 medium blinks, each lasting 0.5 seconds | Boot complete. Appears on every successful boot and always appears last.| | |
> \[!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.
@@ -88,5 +88,5 @@ eyJoaXN0b3J5IjpbLTE5OTAxODA3OSwtMjYyOTMyNDldfQ==
> \[!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