stratux: T-Beam Flashing fails in multiple ways

  1. Stratux version:

  2. Stratux config:

    SDR

    • single
    • dual

    GPS

    • yes
    • no type:

    AHRS

    • yes
    • no

    power source: 5V 20000mAh Powerbank

    usb cable: Generic USB-MicroUSB Cable 7cm

  3. EFB app and version: (e.g., WingX Pro7 8.6.2)

    EFB platform: (e.g., iOS 9.2)

    EFB hardware: (e.g., iPad Mini 2)

  4. Description of your issue:

When I try to flash the T-Beam, I get following stack trace error:

pi@stratux:/opt/stratux/ogn $ sudo /opt/stratux/ogn/install-ogntracker-firmware-pi.sh ogn-tracker-bin-tbeams3-sx1262-ubx
ogn-tracker-bin-tbeams3-sx1262-ubx.zip
Archive:  ogn-tracker-bin-tbeams3-sx1262-ubx.zip
  inflating: /tmp/bootloader.bin     
  inflating: /tmp/firmware.bin
  inflating: /tmp/partitions.bin     
  inflating: /tmp/esptool.py
esptool.py v2.7-dev
Serial port /dev/serialin
Connecting....
Traceback (most recent call last):
  File "/tmp/esptool.py", line 3065, in <module>
    _main()
  File "/tmp/esptool.py", line 3058, in _main
    main()
  File "/tmp/esptool.py", line 2757, in main
    esp.connect(args.before)
  File "/tmp/esptool.py", line 463, in connect
    last_error = self._connect_attempt(mode=mode, esp32r0_delay=False)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/tmp/esptool.py", line 441, in _connect_attempt
    self.flush_input()
  File "/tmp/esptool.py", line 377, in flush_input
    self._port.flushInput()
  File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 588, in flushInput
    self.reset_input_buffer()
  File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 683, in reset_input_buffer
    self._reset_input_buffer()
  File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 677, in _reset_input_buffer
    termios.tcflush(self.fd, termios.TCIFLUSH)
termios.error: (5, 'Input/output error')

Device is showing under the list of USB Devices, when I call lsusb: Bus 001 Device 010: ID 303a:8133 SoftRF Prime Edition Mk.3

I own following device: U-blox MAX-M10S-00B, SX1262 868MHz, CHINA (https://de.aliexpress.com/item/1005005418286231.html - UBLOX 868 Variant)

image

what am I doing wrong? SOFT-RF Hotspot gets created and GPS Fix is also there so the device is fine

image

Am I using the wrong software? On chip, it says v3.0 and it is a U-BLOX variant so the only U-BLOX in the list is sudo /opt/stratux/ogn/install-ogntracker-firmware-pi.sh ogn-tracker-bin-tbeams3-sx1262-ubx. At the same time, the T-Beam UI shows a version 1.2 but the only 1.2 version to flash is with sx1276 chip, so it is probably not compatible neither.

I would like to try the other methods as well, but unfortunately the both links here are down and leading to a 404: https://github.com/b3nn0/stratux/wiki/TTGO-T-Beam-Firmware-for-Stratux#flashing-from-linux

Only lead I got was, after the failing, the T-Beam is not showing up on USB devices anymore. I don’t know if it is by design so. But install-ogntracker-firmware-pi.sh doesn’t show any “disconnect USB Device” code

Help would be much appreciated. Best Regards Stefan Kosker

If possible, enable “Replay Logs”, reproduce the problem, and provide a copy of the logs in http://192.168.10.1/logs/stratux/ and http://192.168.10.1/logs/stratux.log.

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 27 (12 by maintainers)

Most upvoted comments

It seems that the T-Beam S3 Core module is no longer available separately. I’ll make a note in my doc.

The firmware binary is almost definitely not the problem, they are built correctly. maybe a too-old version of esptool.py (which is used for flashing) is. Unfortunately I can’t really test that here. In that case you should still be able to flash the firmware by other means. I already fixed the download links, you can find the zip files here: https://github.com/b3nn0/stratux/tree/master/ogn

Another question. Maybe I should try the 10-1262 firmware. After all, the board says v3.0 but the number after T22 is still a11 and according to docs, I should use 10-1262 firmware. What do you think?

No, this package is for the ESP32 CPU. You need ESP32S3 versions.

There is no confirmation about the service mode - only if e.g. you have booted SoftRF before and have an TX counter running, then in service mode this counter and the entire screen will freeze.