diff --git a/usbconfig.md b/usbconfig.md index 0cabd2e..4b9bc03 100644 --- a/usbconfig.md +++ b/usbconfig.md @@ -55,54 +55,23 @@ Options are:

To add an admin key, copy it from the app and add base64: to the beginning (meshtastic_admin_key="base64:T/b8EGvi/Nqi6GyGefJt/jOQr+5uWHHZuBavkNcUwWQ=").

Clearing the admin key list: The admin key list can contain up to three keys - if more are added they will be ignored. The USB configuration tool supports clearing the admin key list, after which you will need to re-add your admin key/s in a second operation. To clear the admin key list, enter meshtastic_admin_key="0", without base64:.

-

To apply your configuration, reboot the Femtofox with the USB drive plugged in. No other USB drives can be plugged in at the same time.
-

-

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.
-LEDs

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
LED blink patternMeaningPossible causesSolutions
⚠️ One very long blink, lasting 4 secondsFailed to mount USB drive. Ignoring.
  • Invalid filesystem
  • Corrupted partition table
  • Defective USB drive
  • Use a supported partition (FAT32, exFAT, NTFS, ext4)
  • Repair partition table
  • Try another USB drive
  • ⚠️ 3 long blinks, each lasting 1.5 secondsUSB 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 secondsUSB 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.
    ✅ 10 very fast blinks, each lasting 1/8th of a secondUSB drive mounted successfully, and femtofox-config.txt was found and contained valid configuration data which was deployed. 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 some data was not read successfully.
    ✅ 5 medium blinks, each lasting 0.5 secondsBoot complete. Always appears last.
    +
    +

    [!WARNING]
    +Attempting to set wifi settings via USB configuration tool without a USB adapter connected will lead to a hard crash - you will need to disconnect and reconnect power to recover.

    +
    +

    To apply your configuration, reboot the Femtofox with the USB drive plugged in. No other USB drives can be plugged in at the same time.

    +
    +### 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. +![LEDs](https://github.com/noon92/femtofox/blob/main/leds.png) +| LED blink pattern | Meaning | Possible causes | Solutions | +|--|--|--|--| +|⚠️ One very long blink, lasting 4 seconds | Failed to mount USB drive. Ignoring. |
  • Invalid filesystem
  • Corrupted partition table
  • Defective USB drive |
  • Use a supported partition (FAT32, exFAT, NTFS, ext4)
  • Repair partition table
  • Try another USB drive | +|⚠️ 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. | +|✅ 10 very fast blinks, each lasting 1/8th of a second | USB drive mounted successfully, and femtofox-config.txt was found and contained valid configuration data which was deployed. 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 some data was not read successfully.| +|✅ 5 medium blinks, each lasting 0.5 seconds | Boot complete. 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 attempt to mount the USB drive failed, and that boot is complete.