usb_config.md updated from https://stackedit.io/

This commit is contained in:
noon92 2025-02-03 16:08:39 +02:00
parent d32bc35bb8
commit 08ab057bae

View file

@ -72,19 +72,14 @@ When the Femtofox is finished booting, it will blink its User LED (see below) in
| LED blink pattern | Meaning | Possible causes | Solutions |
|--|--|--|--|
| <p align="center">⚠️<br>**──────────**<br>1 very long blink, lasting 5 seconds</center>| • Failed to mount USB drive. Ignoring.| Invalid filesystem<br>•Corrupted partition table<br>• Defective USB drive<br>• Defective USB OTG adapter| • Use a supported partition (FAT32, exFAT, NTFS, ext4)<br>• Repair partition table<br>• Try another USB drive<br>• Try another USB OTG adapter|
| <p align="center">⚠️<br>**───&nbsp;&nbsp;&nbsp;───**<br>2 long blinks, each lasting 1.5 seconds</center>|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 or remove `dont_run_if_log_exists` line from femtofox-config.txt |
| <p align="center">⚠️<br>**───&nbsp;&nbsp;&nbsp;───&nbsp;&nbsp;&nbsp;───**<br>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.|
| <p align="center">⚠️<br>**───&nbsp;&nbsp;&nbsp;───&nbsp;&nbsp;&nbsp;───&nbsp;&nbsp;&nbsp;───&nbsp;&nbsp;&nbsp;───**<br>5 long blinks, each lasting 1.5 seconds</center> | 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. |
| <p align="center">⚠️<br>**──&nbsp;&nbsp;&nbsp;──&nbsp;&nbsp;&nbsp;-&nbsp;&nbsp;&nbsp;-**<br>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.<br>• Configuration file may contain improper data. | • Try again.<br>• Check configuration file contents as described above.<br>• Check the log.<br><br>This pattern may flash before other patterns. The pattern will repeat once for each failed setting. |
| <p align="center">✅<br>**·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·**<br>10 very fast blinks, each lasting 1/8th of a second</center> | 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.<br>Note that the "success" boot code will flash if at least one setting is successfully read - even if the setting was not implemented successfully. | |
| <p align="center">✅<br>**─&nbsp;&nbsp;&nbsp;─&nbsp;&nbsp;&nbsp;─&nbsp;&nbsp;&nbsp;─&nbsp;&nbsp;&nbsp;─**<br> 5 medium blinks, each lasting 0.5 seconds</center> | Boot complete. Appears on every successful boot and always appears last.| | Hooray! |
| <p align="center">⚠️<br>**───&nbsp;&nbsp;&nbsp;───**<br>2 long blinks, each lasting 1.5 seconds</center>|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.<br>• Remove `dont_run_if_log_exists` line from femtofox-config.txt.|
| <p align="center">⚠️<br>**───&nbsp;&nbsp;&nbsp;───&nbsp;&nbsp;&nbsp;───**<br>3 long blinks, each lasting 1.5 seconds | USB drive mounted successfully but femtofox-config.txt was not found.| Config file missing.| Create configuration file as described above.|
| <p align="center">⚠️<br>**───&nbsp;&nbsp;&nbsp;───&nbsp;&nbsp;&nbsp;───&nbsp;&nbsp;&nbsp;───&nbsp;&nbsp;&nbsp;───**<br>5 long blinks, each lasting 1.5 seconds</center> | USB drive mounted successfully and femtofox-config.txt was found but did not contain readable configuration data.| Configuration file improperly formatted or contains no data.| Check configuration file contents as described above.|
| <p align="center">⚠️<br>**──&nbsp;&nbsp;&nbsp;──&nbsp;&nbsp;&nbsp;-&nbsp;&nbsp;&nbsp;-**<br>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.<br>• Configuration file may contain improper data.| • Try again.<br>• Check configuration file contents as described above.<br>• Check the log.<br><br>This pattern may flash before other patterns. The pattern will repeat once for each failed setting. |
| <p align="center">✅<br>**·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·&nbsp;&nbsp;&nbsp;·**<br>10 very fast blinks, each lasting 1/8th of a second</center>| 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.<br>Note that the "success" boot code will flash if at least one setting is successfully read - even if the setting was not implemented successfully. ||
| <p align="center">✅<br>**─&nbsp;&nbsp;&nbsp;─&nbsp;&nbsp;&nbsp;─&nbsp;&nbsp;&nbsp;─&nbsp;&nbsp;&nbsp;─**<br> 5 medium blinks, each lasting 0.5 seconds</center>| Boot complete. Appears on every successful boot and always appears last.| | Hooray! |
> \[!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.
<!--stackedit_data:
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.
<!--stackedit_data:
eyJoaXN0b3J5IjpbLTE5MzkwMTkyOTFdfQ==
eyJoaXN0b3J5IjpbMTc5MDE4ODE0XX0=
-->