Trying to initialize COM10 @ 460800
Enabling serial passthrough...
CMD: 'serialpassthrough rfmod 0 460800'
======== PASSTHROUGH DONE ========
esptool.py v4.2.1
Serial port COM10
WARNING: Pre-connection option "no_reset" was selected. Connection may fail if the chip is not in bootloader or flasher stub mode.
Connecting...
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.```
i messed something up on my jumper t20 somehow and now it gets stuck on loading whenever i try to load up the expresslrs lua script
laptop didnt recognize the radio initially and had a yellow triangle in device manager
- tried downloading the CP210x drivers from silicon labs but those did nothing
- tried downloading the STM32 virtual COM port driver from myST which got rid of the yellow triangle but now i get the error above
i dont think the radio settings are wrong, internal RF set to CRSF at 400k and external RF off
dont think i have the v2 / wrong model as i dont have the fan at the back either
#expresslrs flashing
179 messages · Page 1 of 1 (latest)
usb port also works when using it as a joystick instead of the serial usb
so im probably not using the charging port
flashing guide is here:
https://www.expresslrs.org/quick-start/transmitters/jumper-t20-internal/#via-etx-passthrough
FOLLOW the flashing guide
one other thing: open the radio and make sure the wiring for the internal module is still intact and properly wired up to the mainboard of the radio
those connecting dots say the configurator cannot find the esp32 device
i downloaded the stm32 virtual com driver following this guide
the jumper t20 should be fine up to 1.87M baud rate
so just make sure nothings come off or anything right
i just got into this sry
if you decide to open up the radio, post a photo of the internal rf module and its wiring
okay
do i have to take all this apart?? or is there an easier way
just realised i mightve been using uart instead of etxpassthrough
Trying to initialize COM10 @ 460800
Traceback (most recent call last):
File "runpy.py", line 196, in _run_module_as_main
File "runpy.py", line 86, in _run_code
File "C:\Users\user\AppData\Roaming\ExpressLRS Configurator\firmwares\cloud\ExpressLRS\41daca2a4ff782188c38fbef3c4f1a36e320b1a3\firmware\flasher.pyz\__main__.py", line 3, in <module>
if __name__ == '__main__':
File "C:\Users\user\AppData\Roaming\ExpressLRS Configurator\firmwares\cloud\ExpressLRS\41daca2a4ff782188c38fbef3c4f1a36e320b1a3\firmware\flasher.pyz\_bootstrap\__init__.py", line 253, in bootstrap
File "C:\Users\user\AppData\Roaming\ExpressLRS Configurator\firmwares\cloud\ExpressLRS\41daca2a4ff782188c38fbef3c4f1a36e320b1a3\firmware\flasher.pyz\_bootstrap\__init__.py", line 38, in run
return binary_flash.upload(options, args)
File "C:\Users\user\.shiv\flasher.pyz_b81ad73652af257cc616d772669414c276740dc65a6bef28ce921f0af6cd0a59\site-packages\binary_flash.py", line 193, in upload
return upload_esp32_etx(args)
File "C:\Users\user\.shiv\flasher.pyz_b81ad73652af257cc616d772669414c276740dc65a6bef28ce921f0af6cd0a59\site-packages\binary_flash.py", line 119, in upload_esp32_etx
ETXinitPassthrough.etx_passthrough_init(args.port, args.baud)
File "C:\Users\user\.shiv\flasher.pyz_b81ad73652af257cc616d772669414c276740dc65a6bef28ce921f0af6cd0a59\site-packages\ETXinitPassthrough.py", line 24, in etx_passthrough_init
rl.expect_bytes(b"set: ", timeout=1.0)
File "C:\Users\user\.shiv\flasher.pyz_b81ad73652af257cc616d772669414c276740dc65a6bef28ce921f0af6cd0a59\site-packages\external\streamexpect.py", line 516, in expect_bytes
return self.expect(BytesSearcher(b), timeout)
File "C:\Users\user\.shiv\flasher.pyz_b81ad73652af257cc616d772669414c276740dc65a6bef28ce921f0af6cd0a59\site-packages\external\streamexpect.py", line 666, in expect
incoming = self._stream_adapter.poll(end - time.time())
File "C:\Users\user\.shiv\flasher.pyz_b81ad73652af257cc616d772669414c276740dc65a6bef28ce921f0af6cd0a59\site-packages\external\streamexpect.py", line 455, in poll
raise ExpectTimeout()
external.streamexpect.ExpectTimeout```
now its giving me this
sorry i had to split it in two
hit the discord character limit
or you could've saved the !log file and uploaded the file as is
I linked the flashing guide above..
but like
i cant even follow the first step
because i cant load the lua script
ive followed everything afterwards
your image above doesn't show which module you actually have
wdym
the internal module is on the back shell
reasons why the lua script will be stuck at the loading screen:
- baud rate too low for the packet rate set
- baud rate too high for the module and radio's mcu/cpu
- module is not connected properly to the radio mainboard or external bay pins
- the model on the radio is not properly configured (CRSF is not the protocol selected)
- you don't have an expressLRS module
just tried to take it apart but realised i dont have any hex screwdrivers
ill buy one this weekend
thanks
uh
i rounded one of the screws
and i cant open the radio anymore
is there a way of getting it out
its like really deep
and in a narrow hole
should i just get an external module
im sorry 💀
oh.. you don't have to say sorry to me.. it isn't my radio..
nvm my dads somehow managed to get it out
use the appropriate tool for the job.. else you'd be making more work for yourself
the board mounted to the back case
okay, it is the ELRS version
make sure all cables are connected properly
dont see any loose wires
have you tried flashing with the V1 instead?
if you're following the flashing guide closely, there shouldn't be any issues
1.87M baud should be set for the radio
Lua Script should load witth the right model set up
seems you've skipped a bunch of things at the beginning of the guide
e.g. making sure the lua script loads and that the USB-VCP is set with CLI mode
wait where is that
i might be blind
this is the first step on the page
or do u mean in the general guide
not this one
the whole issue was that i couldnt load the lua script
thats why ive had to do this
what about the edgeTX version that comes even before the lua script
the wizard loader?
(unrelated, edited: disabl ADC filter from the hardware page, just below usb-vcp setting)
EdgeTX firmware version
there's 2.10.4 now
wait whys it v2
here
the radio could be v2, but the module itself could be v1, per the writing on the PCB
so i shld flash the one according to the module
ill update it now
for the expressLRS firmware, v1
for the T20 edgeTX firmware, V2 (https://buddy.edgetx.org/#/flash?version=v2.10.4&target=t20v2)
there's a different way to update the radio..
it's part of the flashing procedure in an expandable section
the t20 doesn't have a sd card
it does, but not an actual one.. it's an on-board storage chip
o
you can plug the usb into the t20, select usb-storage mode
transfer firmware binary into the firmware folder
reboot in bootloader menu and flash away
the sounds are optional
for EdgeTX, you have V2
i.e. T20 V2 on EdgeTX side
what is the trim switch
is it the little buttons inside
nvm i found it
updateed
do i flash it now
with expresslrs
recheck the model settings and the radio settings, in particular, the hardware settings
more so if you formatted your sd card (which you shouldn't have to do)
just check if internal rf is on crsf 1.87m, external rf is off, adc filter is off
?
yes.. if you didn't format the sd card, then you don't have to do much.. just make sure those relevant settings are intact and correct
yes
is there such a method in the docs for that?
can you try the v2 target if that would work?
okay
the lua script is not the firmware
same results as when trying with v1?
no
v1 gives me the dots
the one where u said it couldnt connect to the esp32 device
could you try a second time with v2 please
same error
Contact Jumper
This shouldn't be this hard.
let them know deadbyte is the one who advised you to do so. you can link this convo.
ask them to send at least the tx module
do i need like warranty for that
let me know what Jumper would do and I'll try to contact them from my side.
does this mean i flash edgetx for the v1 version or did they mean the elrs firmware
wouldnt the radio be bricked if it had the wrong edgetx firmware
the radio..
it won't get bricked.. t20 v2 and v1 is using the same mcu