mirror of
https://github.com/femtofox/femtofox.git
synced 2026-10-25 18:40:20 -04:00
usb_config.md updated from https://stackedit.io/
This commit is contained in:
noon92
parent
8753ae4ce2
commit
2ae64a7073
1 changed files with 6 additions and 6 deletions
|
|
@ -79,13 +79,13 @@ When the Femtofox is finished booting, it will blink its User LED (see below) in
|
|||
|
||||
| LED blink pattern | Meaning | Possible causes | Solutions |
|
||||
| ---------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
| <center>⚠️<br>**________________**<br>1 very long blink, lasting 5 seconds | Failed to mount USB drive. Ignoring. | <li>Invalid filesystem<li>Corrupted partition table<li>Defective USB drive<li>Defective USB OTG adapter | <li>Use a supported partition (FAT32, exFAT, NTFS, ext4)<li>Repair partition table<li>Try another USB drive<li>Try another USB OTG adapter |
|
||||
| <center>⚠️<br>**__**<br>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 driver><li>Remove `dont_run_if_log_exists` line from femtofox-config.txt |
|
||||
| <center>⚠️<br>━━━ ━━━ ━━━**<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. |
|
||||
| <center>⚠️<br>**─── ─── ─── ─── ───**<br>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. |
|
||||
| <center>⚠️<br>**──────────**<br>1 very long blink, lasting 5 seconds | Failed to mount USB drive. Ignoring. | <li>Invalid filesystem<li>Corrupted partition table<li>Defective USB drive<li>Defective USB OTG adapter | <li>Use a supported partition (FAT32, exFAT, NTFS, ext4)<li>Repair partition table<li>Try another USB drive<li>Try another USB OTG adapter |
|
||||
| <center>⚠️<br>**─── ───**<br>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 driver><li>Remove `dont_run_if_log_exists` line from femtofox-config.txt |
|
||||
| <center>⚠️<br>**─── ─── ───**<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. |
|
||||
| <center>⚠️<br>**─── ─── ─── ─── ───**<br>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. |
|
||||
| <center>⚠️<br>**── ── - -**<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. | <li>The error may be transient.<li>Configuration file may contain improper data. | <li>Try again.<li>Check configuration file contents as described above.<li>Check the log.<br><br>This pattern may flash before other patterns. The pattern will repeat once for each failed setting. |
|
||||
| <center>✅<br>**. . . . . . . . . .**<br>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.<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. | |
|
||||
| <center>✅<br>**__ _ _ _ _**<br>5 medium blinks, each lasting 0.5 seconds | Boot complete. Appears on every successful boot and always appears last. | | |
|
||||
| <center>✅<br>**─ ─ ─ ─ ─ &nb**<br>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.
|
||||
|
|
@ -182,5 +182,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.
|
||||
<!--stackedit_data:
|
||||
eyJoaXN0b3J5IjpbLTQzMzMyMjAzM119
|
||||
eyJoaXN0b3J5IjpbLTk3MzA1NjI3Nl19
|
||||
-->
|
||||
Loading…
Add table
Add a link
Reference in a new issue