MeshTower v2 - Unable to mount as USB storage

#1

Just received a MeshTower v2 (the 30dbm higher power model). It came pre-flashed with Meshtastic, but I would like to install the Meshcore v1.16 firmware (https://flasher.meshcore.io/heltec-meshsolar-meshtower/repeater/v1.16.0).

Following the flashing instructions, I charged the device (with power switch in the ON position) for a few hours to fully charge the batteries. I then connected a standard USB-C cable from MeshTower to MacOS laptop. I double-pressed the RST button to switch into USB storage mode, but no device appears in the Finder or System Report (under USB or Storage sections).

With some help from Gemini & Claude, I tried the following rest procedure:

  • Disconnect USB
  • Press & holder USER button
  • Connected USB cable
  • Pressed RST button once
  • Released USER button

But I am still unable to mount the USB volume. I have also attempted to use the standard Meshcore Web Flasher over USB, but the MeshTower device is never recognized as a serial USB device for direct flashing.

Any suggestions?

#2

I think the board may be in a bad state. When I connect a dedicated high power USB-C charger or toggle the power switch from OFF to ON, the power LED will illuminate briefly, then fade to off.

When connected to a USB C charging hub (a fancy Anker model with real-time display), the device does not appear to be consuming any power.

#3

I am able to get the device to mount as USB storage on my android mobile, and I can read files off the file system - for example, the INFO_UF2.TXT file has the following contents:

UF2 Bootloader 0.9.0-2-g836c8dc-dirty lib/nrfx (v2.0.0) lib/tinyusb (0.12.0-145-g9775e7691) lib/uf2 (remotes/origin/configupdate-9-gadbb8c7)
Model: HT-n5262
Board-ID: HT-n5262
Date: Jul  9 2024
SoftDevice: S140 6.1.1

When connected to an Android device, here is the USB device info reported:

Device Info 
Device Path: /dev/bus/usb/001/003
Device Class: Miscellaneous (0xef)
Vendor ID:  239a
Vendor Name (reported):  Heltec AutoMation
Vendor Name (from DB):  Adafruit
Product ID:  0071
Product Name (reported):  HT-n5262
Product Name (from DB):  Not found

Interface #0 
ID:  0
Name:  nRF Serial
Alternate Setting: 0
Class: Communication Device (0x2)
Subclass: Unknown (0x2)
Protocol: 0
Endpoint: #0
Address        : 0x81 (10000001)
Number         : 1
Direction      : Inbound (0x80)
Type           : Interrupt (0x3)
Poll Interval  : 16
Max Packet Size: 8
Attributes     : 00000011
 
Interface #1 
ID:  1
Name:  null
Alternate Setting: 0
Class: Communication Device Class (CDC) (0xa)
Subclass: Unknown (0x0)
Protocol: 0
Endpoint: #0
Address        : 0x02 (00000010)
Number         : 2
Direction      : Outbound (0x0)
Type           : Bulk (0x2)
Poll Interval  : 0
Max Packet Size: 64
Attributes     : 00000010
Endpoint: #1
Address        : 0x82 (10000010)
Number         : 2
Direction      : Inbound (0x80)
Type           : Bulk (0x2)
Poll Interval  : 0
Max Packet Size: 64
Attributes     : 00000010
 
Interface #2 
ID:  2
Name:  nRF UF2
Alternate Setting: 0
Class: Mass Storage Device (0x8)
Subclass: Unknown (0x6)
Protocol: 80
Endpoint: #0
Address        : 0x03 (00000011)
Number         : 3
Direction      : Outbound (0x0)
Type           : Bulk (0x2)
Poll Interval  : 0
Max Packet Size: 64
Attributes     : 00000010
Endpoint: #1
Address        : 0x83 (10000011)
Number         : 3
Direction      : Inbound (0x80)
Type           : Bulk (0x2)
Poll Interval  : 0
Max Packet Size: 64
Attributes     : 00000010

Configuration #0 
ID:  1
Name:  
Max Power:  100
Self Powered: false
Remote Wakeup: false
#4

Hey, FWIW, I ran into the same problem with a T114, same base chip as your Tower model. Swapped the known good USB A-C for another half the length. Worked like a champ. DFU mode (the thumb drive mode you’re trying to enter) really hates a long usb cable. I went from a 3m to 1m cable. Never tried C to C, only A to C, but it may help.

#5

It turns out that on MacOS, when a device advertises dual capabilities (serial communication and mass storage) it will often fail to auto-mount the mass storage device. So I wound up downloading the firmware to an Android device, and using the Files app to transfer it to the Heltec with a USB-C to USB-A converter and a USB-A to C cable. That finally worked.

But I then learned that the MeshTower v2 only works with the custom firmware proved by Heltec:

https://resource.heltec.cn/download/MeshTower-V2/firmware

They provide both Meshtastic and Meshcore builds.

1 Like
#6

Hi jbuberel I too have Meshtower V2 in low power version, not yet programmed or deployed do you have any pictures of circuit board as I am trying to determine the difference between the high power and low power version, I think the PA is present on all board versions H or L power but just needs rf pig tails putting in correct configuration

#7

Sorry Karl, but I already have the device up on my flagpole mount. Next time it comes down for service, I’ll try to remember to snap a pic for you.

#9

Hey there.
My meshtower behaved weirdly too. What helped was using USB hub. on hub the device stays discovered, connecting it directly to my computer it appeared in the ports in flasher for 1-2 s and then it disappeared.
Also DFU mode is: push and hold USR, click RESET, release USR.