⚠️
**──────────**
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.| | 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.
-
\ No newline at end of file
From fcf612de65ce54b698397fe51341d8437ed1c2e5 Mon Sep 17 00:00:00 2001
From: noon92 <40807970+noon92@users.noreply.github.com>
Date: Mon, 3 Feb 2025 16:02:13 +0200
Subject: [PATCH 17/26] 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 b8cce97..3b37061 100644
--- a/usb_config.md
+++ b/usb_config.md
@@ -73,12 +73,12 @@ When the Femtofox is finished booting, it will blink its User LED (see below) in
|--|--|--|--|
|
⚠️
**──────────**
1 very long blink, lasting 5 seconds LED blink pattern ai ilessoution | •| Failed to mount USB drive. Ignoring.| Invalid filesystem
• li>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 long5 seconds |g exists. | femtofox-config.txt is configured to skip if lo 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 blinks, each lasting 1. | USB drive mounted successfully but femtofox-config.txt was not found. Ignoring. | Config file missing. | Create configuration file as described above. |
+|
⚠️
**─── ─── ───**
3 long blinks, each lasting 1.5 seconds blinks, each lasting 1. | 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.| | Hooray! |
+|
✅
**─ ─ ─ ─ ─**
+
✅5 medium blinks, each lasting 0.5 seconds | 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. \ No newline at end of file From 39460086d2c0fec00ceee07b8bad09302e23b2f9 Mon Sep 17 00:00:00 2001 From: noon92 <40807970+noon92@users.noreply.github.com> Date: Mon, 3 Feb 2025 16:03:52 +0200 Subject: [PATCH 18/26] usb_config.md updated from https://stackedit.io/ --- usb_config.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/usb_config.md b/usb_config.md index 3b37061..d9ea7bc 100644 --- a/usb_config.md +++ b/usb_config.md @@ -71,14 +71,13 @@ When the Femtofox is finished booting, it will blink its User LED (see below) in  | LED blink pattern | Meaning | Possible causes | Solutions | |--|--|--|--| -|
⚠️
**──────────**
1 very long blink, lasting 5 seconds LED blink pattern ai ilessoution | •| Failed to mount USB drive. Ignoring.| Invalid filesystem
• li>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 |
+|
⚠️
**──────────**
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 long5 seconds |g exists. | femtofox-config.txt is configured to skip if lo 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 blinks, each lasting 1. | 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.| | Hooray! | +|
✅
**─ ─ ─ ─ ─**
5 medium blinks, each lasting 0.5 seconds | 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.
\ No newline at end of file
From c548b4f78d28dac412608c6fc8f8310d6ed39421 Mon Sep 17 00:00:00 2001
From: noon92 <40807970+noon92@users.noreply.github.com>
Date: Mon, 3 Feb 2025 16:05:28 +0200
Subject: [PATCH 19/26] usb_config.md updated from https://stackedit.io/
---
usb_config.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/usb_config.md b/usb_config.md
index d9ea7bc..42bdb54 100644
--- a/usb_config.md
+++ b/usb_config.md
@@ -72,7 +72,7 @@ When the Femtofox is finished booting, it will blink its User LED (see below) in
| 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 long5 seconds |g exists. | femtofox-config.txt is configured to skip if lo 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 |
+|
⚠️
**─── ───**
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 or remove `dont_run_if_log_exists` line from femtofox-config.txt |
|
⚠️
**─── ─── ───**
3 long blinks, each lasting 1.5 seconds blinks, each lasting 1. | 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. |
@@ -86,5 +86,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
From d32bc35bb828abd7bbc16082a8320ff53f482c24 Mon Sep 17 00:00:00 2001
From: noon92 <40807970+noon92@users.noreply.github.com>
Date: Mon, 3 Feb 2025 16:07:03 +0200
Subject: [PATCH 20/26] usb_config.md updated from https://stackedit.io/
---
usb_config.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/usb_config.md b/usb_config.md
index 42bdb54..a74317f 100644
--- a/usb_config.md
+++ b/usb_config.md
@@ -71,11 +71,11 @@ When the Femtofox is finished booting, it will blink its User LED (see below) in

| 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 or remove `dont_run_if_log_exists` line from femtofox-config.txt |
-|
⚠️
**─── ─── ───**
3 long blinks, each lasting 1.5 seconds blinks, each lasting 1. | USB drive mounted successfully but femtofox-config.txt was not found. Ignoring. | Config file missing. | Create configuration file as described above. |
+|
⚠️
**──────────**
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 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. |
+|
⚠️
**── ── - -**
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.| | Hooray! |
> \[!NOTE\]
@@ -86,5 +86,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
From 08ab057baed4a74fdae453e1c8a2fcb7ed147ab3 Mon Sep 17 00:00:00 2001
From: noon92 <40807970+noon92@users.noreply.github.com>
Date: Mon, 3 Feb 2025 16:08:39 +0200
Subject: [PATCH 21/26] usb_config.md updated from https://stackedit.io/
---
usb_config.md | 19 +++++++------------
1 file changed, 7 insertions(+), 12 deletions(-)
diff --git a/usb_config.md b/usb_config.md
index a74317f..2e3af65 100644
--- a/usb_config.md
+++ b/usb_config.md
@@ -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 |
|--|--|--|--|
|
⚠️
**──────────**
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 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.| | Hooray! |
+|
⚠️
**─── ───**
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.|
+|
⚠️
**─── ─── ───**
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.|
+|
⚠️
**─── ─── ─── ─── ───**
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.| 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.| | 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.
\ No newline at end of file
From 9260ffaf07ed44529298f8be1c6e5ce03949ca77 Mon Sep 17 00:00:00 2001
From: noon92 <40807970+noon92@users.noreply.github.com>
Date: Mon, 3 Feb 2025 16:10:25 +0200
Subject: [PATCH 22/26] usb_config.md updated from https://stackedit.io/
---
usb_config.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
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
From e0c4d6718ce639a8905f1920a09e3d6a988dd7e0 Mon Sep 17 00:00:00 2001
From: noon92 <40807970+noon92@users.noreply.github.com>
Date: Mon, 3 Feb 2025 16:15:04 +0200
Subject: [PATCH 23/26] usb_config.md updated from https://stackedit.io/
---
usb_config.md | 3 ---
1 file changed, 3 deletions(-)
diff --git a/usb_config.md b/usb_config.md
index 4900772..7da67f2 100644
--- a/usb_config.md
+++ b/usb_config.md
@@ -80,6 +80,3 @@ When the Femtofox is finished booting, it will blink its User LED (see below) in
|
✅
**─ ─ ─ ─ ─**
5 medium blinks, each lasting 0.5 seconds| 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.
-
\ No newline at end of file
From da13fa5dde24ec989f63e8ee8d86aa9ad2be7863 Mon Sep 17 00:00:00 2001
From: noon92 <40807970+noon92@users.noreply.github.com>
Date: Mon, 3 Feb 2025 16:16:35 +0200
Subject: [PATCH 24/26] usb_config.md updated from https://stackedit.io/
---
usb_config.md | 3 +++
1 file changed, 3 insertions(+)
diff --git a/usb_config.md b/usb_config.md
index 7da67f2..4900772 100644
--- a/usb_config.md
+++ b/usb_config.md
@@ -80,3 +80,6 @@ When the Femtofox is finished booting, it will blink its User LED (see below) in
|
✅
**─ ─ ─ ─ ─**
5 medium blinks, each lasting 0.5 seconds| 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.
+
\ No newline at end of file
From 91b0160259f030c5a9b1f7416ac035769ecf55c1 Mon Sep 17 00:00:00 2001
From: noon92 <40807970+noon92@users.noreply.github.com>
Date: Tue, 4 Feb 2025 12:53:15 +0200
Subject: [PATCH 25/26] Update usb_config.md
---
usb_config.md | 25 ++++++++++++++-----------
1 file changed, 14 insertions(+), 11 deletions(-)
diff --git a/usb_config.md b/usb_config.md
index 4900772..1ace2d6 100644
--- a/usb_config.md
+++ b/usb_config.md
@@ -11,7 +11,7 @@ Configurable settings are:
- Activity LED (blinky light - disable for minor power savings)
- Meshtastic:
- [LoRa radio model](https://github.com/femtofox/femtofox/blob/main/supported_hardware.md)
- - [URL](https://meshtastic.org/docs/software/python/cli/#--seturl-seturl) (used to configure LoRa settingschannels and generate the QR code)
+ - [URL](https://meshtastic.org/docs/software/python/cli/#--seturl-seturl) (used to configure LoRa settings/channels and generate the QR code)
- Security: [public key](https://meshtastic.org/docs/configuration/radio/security/#public-key)
- Security: [private key](https://meshtastic.org/docs/configuration/radio/security/#private-key)
- Security: Add [Admin Key](https://meshtastic.org/docs/configuration/radio/security/#admin-key)
@@ -69,17 +69,20 @@ 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.|
-|
⚠️
**─── ─── ───**
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.|
-|
⚠️
**─── ─── ─── ─── ───**
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.| 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.| | Hooray! |
+|
⚠️
**──────────**
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.| | 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.
\ No newline at end of file
+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.
From a4657e9582b84467cadfecd1d9763a82d9ce3cf1 Mon Sep 17 00:00:00 2001
From: Tom <116762865+Nestpebble@users.noreply.github.com>
Date: Tue, 4 Feb 2025 10:57:58 +0000
Subject: [PATCH 26/26] Update README.md
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index a3b8310..afe523b 100644
--- a/README.md
+++ b/README.md
@@ -38,7 +38,7 @@ The Luckfox Pico Mini is the postage stamp sized heart of the Femtofox - a compa
- [x] Meshtasticd to run LoRa radio over SPI (accomplished, updated image and instructions coming soon)
- [x] Allow editing of config files by plugging in thumb drive
- [x] Ability to activate or deactivate WIFI via Meshtastic admin
-
+
> [!NOTE]
> The information on this page is given without warranty or guarantee. Links to vendors of products are for informational purposes only.
> Meshtastic® is a registered trademark of Meshtastic LLC. Meshtastic software components are released under various licenses, see GitHub for details. No warranty is provided - use at your own risk.