From 47fc702fbcae003b433ab94549583bcc5c011782 Mon Sep 17 00:00:00 2001 From: noon92 <40807970+noon92@users.noreply.github.com> Date: Sat, 25 Jan 2025 02:20:36 +0200 Subject: [PATCH] usb_config.md updated from https://stackedit.io/ --- usb_config.md | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/usb_config.md b/usb_config.md index 618e937..35abefe 100644 --- a/usb_config.md +++ b/usb_config.md @@ -71,16 +71,22 @@ When the Femtofox is finished booting, it will blink its User LED (see below) in ![LEDs](assets/images/leds.png) | LED blink pattern | Meaning | Possible causes | Solutions | | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| LED blink pattern ai ilessoution | 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 .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 driveremove `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. | -|
⚠️
\__\_\__\_\__\_\__ 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.| | | +|
⚠️
\_______________\_
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. | 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.| | | + +> \[!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