New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: T-Beam Supreme No USB CLI #3856
Comments
As an additional note - the tbeam is stuck on the comport used for flashing. So stuck in DFU mode? Running ESP tool detects it on com 27 but doesn't manage to reset it back to the port normally used - com 28 in this case: esptool.py v4.7.0 |
I have reverted to 2.3.4. Here is my =dmesg= plugging in with 2.3.6 after reset. (Where the python cli hangs) Same behavior with 2.3.9.
After reinstalling 2.3.4
And python CLI works with 2.3.4 ... Of course I'd prefer to run a newer version of stable, but I prefer configuring with the CLI more... |
This might have been fixed in #3912 ? |
Seems likely... next release I guess. (the update bit in purple) https://github.com/meshtastic/firmware/releases/tag/v2.3.9.f06c56a |
I can confirm this issue is closed in 2.3.10a |
Category
Serial
Hardware
T-Beam S3
Firmware Version
2.3.9.f06c56a Alpha
Description
T-Beam supreme.
Noting this bug fix: Revert "Fix T-Beam S3 USB CLI #3736" by @thebentern in #3809, to fix the loss of CLI comms on 2.3.6 & 2.3.7
Even with this version flashed there is no USB CLI.
As the previous poster noted, reverting to 2.3.4 works
Flashing to 2.3.9 via the webflasher also put the device in a state where the webflasher could not flash the device - i had to flash via CLI to get 2.3.4b on to it.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: