I have the official TTGO Meshtastic T-Beam V1.1 ESP32 433/868/915/923Mhz WiFi Bluetooth ESP32 GPS NEO-6M SMA 18650 Battery Holder With OLED (Aliexpress description) that I am trying to pair with a Samsung Galaxy10e (Android). The TTGO board boots with a banner message “SoftRF” and the OLED shows the ID (6 chars), Protocol 0, Rx 0, and Tx 0. The app on the phone is version1.1.5. I never see the TTGO device in the bluetooth pairing device list, but there is listed a wifi network, SoftRF-XXXXXX, where XXXXXX is the ID code displayed on the OLED. I thought the app connected vie BLE? How do I proceed?
I would start by following the link below to the github page. Scroll down to firmware installation. Click on the ‘releases’ link and download the zip file with the latest firmware files. Also download the ESPHome Flasher app. Unzip the file and find the firmware for your hardware. Then just connect your T-Beam to your laptop with a usb cable the first time. Use the ESPHOME Flasher to install your firmware file. After that you will be able to pair via BT and any future firmware updates will be done from within the app.
Scott
1 Like
Those screens don’t sound familiar. They may have sent you a device with the wrong firmware.
Check out step 7 on this page to get updated firmware on your board:
I flashed the firmware as per your instructions. Everything went as described in the link you provided. The OLED now shows nothing at all. The only sign of life is the on-board red led is lit, but everything else is DOA.
Here’s the console output showing the flash of the esp32. looks pretty normal to me. The device now does not function at all.
I gave up waiting for something to happen with v 1.1.7 and re-flashed an earlier code version , 1.1.0. Now the device shows some signs of life. The OLED flashes with the Meshtastic logo and a red led next to the NEO-6M also flashes. I still cannot find this device to pair with using the Galaxy S10e. How do I proceed?
@star70, sorry I wasnt paying attention when I read your first post. I too experienced issues with the 1.1.7 firmware and blank screen. Though I was using a TTGO Lora32. I dont think I have flashed any of my TBeams with 1.1.7 yet. Rolling back 1.1.6 did fix the screen problem.
Try going back to 1.0.0 as this was the lastest stable release, 1.1.0 is the first Beta.
@star70 I don’t see the console output. Can you post it and perhaps a photo of the device? Pushing the right-most button will reboot. Then you should see the Meshtastic logo and version. In the app, click the settings icon (tiny gear in a box) on the right. Now you should see a screen that looks similar to this:
In my case, my device is Meshtastic_49d8. When I select it on this screen, the OLED shows this:
I go up to the top of my phone screen where I have a pairing request and type in the number from the OLED. Then, back in the app, I type my name in the ‘Your name’ field and press enter or check mark or whatever your keyboard uses. And it’s done.
I’m not sure if any of that helps. I just flashed two of mine with the firmware-tbeam-US-1.1.7.bin file.
1 Like
Here is the console output:
~/Meshtastic/firmware-1.1.0$ ./device-install.sh -f firmware-tbeam0.7-US-1.1.0.bin
Trying to flash firmware-tbeam0.7-US-1.1.0.bin, but first erasing and writing system information
esptool.py v3.0
Found 2 serial ports
Serial port /dev/ttyUSB0
Connecting…___
Detecting chip type… ESP32
Chip is ESP32-D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c4:4f:33:6a:a2:29
Uploading stub…
Running stub…
Stub running…
Changing baud rate to 921600
Changed.
Erasing flash (this may take a while)…
Chip erase completed successfully in 4.6s
Hard resetting via RTS pin…
esptool.py v3.0
Found 2 serial ports
Serial port /dev/ttyUSB0
Connecting…
Detecting chip type… ESP32
Chip is ESP32-D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c4:4f:33:6a:a2:29
Uploading stub…
Running stub…
Stub running…
Changing baud rate to 921600
Changed.
Configuring flash size…
Compressed 61440 bytes to 11950…
Wrote 61440 bytes (11950 compressed) at 0x00001000 in 0.2 seconds (effective 3052.8 kbit/s)…
Hash of data verified.
Leaving…
Hard resetting via RTS pin…
esptool.py v3.0
Found 2 serial ports
Serial port /dev/ttyUSB0
Connecting…
Detecting chip type… ESP32
Chip is ESP32-D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c4:4f:33:6a:a2:29
Uploading stub…
Running stub…
Stub running…
Changing baud rate to 921600
Changed.
Configuring flash size…
Compressed 1134496 bytes to 664441…
Wrote 1134496 bytes (664441 compressed) at 0x00010000 in 9.3 seconds (effective 971.9 kbit/s)…
Hash of data verified.
Leaving…
Hard resetting via RTS pin…
@star70 Ok, that looks like firmware for the original version of the T-Beam. You might try the firmware-tbeam-US-1.0.0.bin for your hardware or the firmware-tbeam-US-1.1.7.bin. The first is a full release. The 1.1.7 has been pretty stable as well.
In the app screen I only see the first line (None…); the device name never appears. Nor does the device show up in the android bluetooth pairing list.
I think I already said that 1.1.7 caused it to be DOA. Are you suggesting I reflash again?
Currently, the device has 1.1.0 and I cannot pair.
You can try the 1.1.0 or the 1.1.7, but in the second line of your console log, it shows the firmware for the 0.7 hardware, but I think you’re using the 1.1 hardware. I’m hoping that if you reflash with either version of the firmware for the 1.1 hardware, you might be in good shape.
Either firmware-tbeam-US-1.1.0.bin or firmware-tbeam-US-1.1.7.bin
for completeness…I flashed the 1.0.0 firmware onto my device. The upload looks normal; the OLED says Meshtastic 1.0.0, and there is no opportunity to pair with this device.
Ok good. Can you post the log again?
Thanks
Scott,
I unzip the firmware-1.1.0 .zip file in a directory. Here are the contents:
ls
device-install.sh firmware-tbeam-EU433-1.1.0.bin
device-update.sh firmware-tbeam-EU865-1.1.0.bin
firmware-1.1.0.zip firmware-tbeam-JP-1.1.0.bin
firmware-heltec-ANZ-1.1.0.bin firmware-tbeam-US-1.1.0.bin
firmware-heltec-CN-1.1.0.bin firmware-tlora-v1-ANZ-1.1.0.bin
firmware-heltec-EU433-1.1.0.bin firmware-tlora-v1-CN-1.1.0.bin
firmware-heltec-EU865-1.1.0.bin firmware-tlora-v1-EU433-1.1.0.bin
firmware-heltec-JP-1.1.0.bin firmware-tlora-v1-EU865-1.1.0.bin
firmware-heltec-US-1.1.0.bin firmware-tlora-v1-JP-1.1.0.bin
firmware-lora-relay-v1-ANZ-1.1.0.uf2 firmware-tlora-v1-US-1.1.0.bin
firmware-lora-relay-v1-CN-1.1.0.uf2 firmware-tlora-v2-1-1.6-ANZ-1.1.0.bin
firmware-lora-relay-v1-EU433-1.1.0.uf2 firmware-tlora-v2-1-1.6-CN-1.1.0.bin
firmware-lora-relay-v1-EU865-1.1.0.uf2 firmware-tlora-v2-1-1.6-EU433-1.1.0.bin
firmware-lora-relay-v1-JP-1.1.0.uf2 firmware-tlora-v2-1-1.6-EU865-1.1.0.bin
firmware-lora-relay-v1-US-1.1.0.uf2 firmware-tlora-v2-1-1.6-JP-1.1.0.bin
firmware-tbeam0.7-ANZ-1.1.0.bin firmware-tlora-v2-1-1.6-US-1.1.0.bin
firmware-tbeam0.7-CN-1.1.0.bin firmware-tlora-v2-ANZ-1.1.0.bin
firmware-tbeam0.7-EU433-1.1.0.bin firmware-tlora-v2-CN-1.1.0.bin
firmware-tbeam0.7-EU865-1.1.0.bin firmware-tlora-v2-EU433-1.1.0.bin
firmware-tbeam0.7-JP-1.1.0.bin firmware-tlora-v2-EU865-1.1.0.bin
firmware-tbeam0.7-US-1.1.0.bin firmware-tlora-v2-JP-1.1.0.bin
firmware-tbeam-ANZ-1.1.0.bin firmware-tlora-v2-US-1.1.0.bin
firmware-tbeam-CN-1.1.0.bin system-info.bin
for the T-Beam, US there seems to be only 1 option, the one I have underlined and the one I have flashed to the device. What am I doing wrong?
here you go:
~/Meshtastic/firmware-1.1.0$ ./device-install.sh -f firmware-tbeam0.7-US-1.1.0.bin
Trying to flash firmware-tbeam0.7-US-1.1.0.bin, but first erasing and writing system information
esptool.py v3.0
Found 2 serial ports
Serial port /dev/ttyUSB0
Connecting…
Detecting chip type… ESP32
Chip is ESP32-D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c4:4f:33:6a:a2:29
Uploading stub…
Running stub…
Stub running…
Changing baud rate to 921600
Changed.
Erasing flash (this may take a while)…
Chip erase completed successfully in 4.5s
Hard resetting via RTS pin…
esptool.py v3.0
Found 2 serial ports
Serial port /dev/ttyUSB0
Connecting…
Detecting chip type… ESP32
Chip is ESP32-D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c4:4f:33:6a:a2:29
Uploading stub…
Running stub…
Stub running…
Changing baud rate to 921600
Changed.
Configuring flash size…
Compressed 61440 bytes to 11950…
Wrote 61440 bytes (11950 compressed) at 0x00001000 in 0.2 seconds (effective 3060.4 kbit/s)…
Hash of data verified.
Leaving…
Hard resetting via RTS pin…
esptool.py v3.0
Found 2 serial ports
Serial port /dev/ttyUSB0
Connecting…
Detecting chip type… ESP32
Chip is ESP32-D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: c4:4f:33:6a:a2:29
Uploading stub…
Running stub…
Stub running…
Changing baud rate to 921600
Changed.
Configuring flash size…
Compressed 1134496 bytes to 664441…
Wrote 1134496 bytes (664441 compressed) at 0x00010000 in 9.4 seconds (effective 968.7 kbit/s)…
Hash of data verified.
Leaving…
Hard resetting via RTS pin…
Ok, first let me say that I am sorry this is such a hassle. It usually isn’t. The file listing doesn’t show me which file you underlined, but I nabbed a screenshot and highlighted in the yellow the file you want. The file that is underlined in red is the one that has been flashed, but that isn’t the one you need. I’m hoping if you can get the highlighted file flashed, you’ll be in good shape. I can’t be sure, but that is my hope.
2 Likes