Ryan Malloy e3642cbc4e Initial commit: Heltec Wireless Tracker documentation site
Astro/Starlight documentation covering hardware specs, pinout,
schematics, GNSS protocol, LoRa frequencies, and getting started
guides. Includes extracted datasheet images and Docker deployment.
2026-02-21 18:39:46 -07:00

1.8 KiB

Wireless Tracker Frequently Asked Questions

Q: How do I access boot mode manually if I'm unable to upload code?

A: The Wireless Tracker uses ESP32S3's internal USB, which may fail to enter bootloader in low-power mode or when certain pins are occupied. To manually enter boot mode:

  • Device not connected: Press the USER button before plugging into a USB port
  • Device already connected: Hold USER button → Press RESET → Release RESET → Release USER button

Timing requirement: TRST ≥ 10 ms


Q: Why isn't Meshtastic firmware working properly on V1.1 hardware?

A: The V1.1 hardware changed the GNSS chip power supply control pin to GPIO3, causing compatibility issues with official Meshtastic firmware.

Solution: Download the temporary firmware package from Heltec's resources and flash using the CLI command: device-install.bat -f firmware.factory.bin

Note: This was resolved in Meshtastic 2.2.17 Beta, which auto-detects device version.


Q: Why is my screen not displaying?

A: Two common causes:

  1. When running LoRa/LoRaWAN sample code: Check the serial port and press RST. Verify device activation via the licensing documentation.

  2. When running Meshtastic: Confirm you've downloaded the correct firmware version for your device.


Q: What are the key GPIO differences between V1.0 and V1.1?

A: The main change in V1.1:

  • GPIO3 now controls GNSS power (set HIGH to enable)
  • Added dedicated LDO for UC6580 GNSS module
  • Improved power isolation between LoRa and GNSS subsystems

Q: How do I check which hardware version I have?

A: Look for the version marking on the PCB near the USB connector, or check:

  • V1.0: GNSS power tied to main rail
  • V1.1: GNSS has independent power control via GPIO3