-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
Fix confusing "Passthrough" flashing method description #698
Comments
No, they are two different ways of flashing the backpack! UART means that the module has switches to connect the backpack to the USB connector. Passthrough means that the serial data is passed through the main MCU to the backpack for flashing. |
What I am trying to say is that for other TXs there is not "Passthrough" option, only "UART" and "WiFi". So maybe this is not just a description issue, some options are missing for some devices. |
So the problem is, when you connect a TX via USB port, there should be a "UART" option for supported TXs. |
But you can't do UART flashing of the backpack on those modules! |
Emmm, I know the underlying mechanism. The title of this issue says "Passthrough description is confusing when you plug the TX via USB port", if you connect via USB, there is nothing to do with Passthrough. So you're saying change the description to something like "connect via USB port is not passthrough, connect your TX to your radio to use Passthrough method", right? |
The current description for passthrough is confusing. It needs to say something like "Flash the backpack via the USB port on the TX module". |
I got it know, so there are two Passthrough for backpack, one is USB Passthrough, the other is Edgetx Passthrough. And for connecting via USB port, there are also two situations, one is using serial chip if TX has it, the other is Passthrough |
When you have a TX module connected directly through the USB-C cable to your PC this "Passthrough" flashing method description looks really confusing:
The text was updated successfully, but these errors were encountered: