edgetx
edgetx copied to clipboard
EdgeTX
Jumper T18 can not boot after flash 2.10 rc(1, 2, 3) via edgetx buddy
Is there an existing issue for this problem?
- [X] I have searched the existing issues
What part of EdgeTX is the focus of this bug?
Transmitter firmware
Current Behavior
Jumper T18 can not boot after flashed 2.10 rc(1, 2, 3) via edgetx buddy. But if I flash it by bootloader method, it works well. Maybe this has something to do with the changes in the bootloader in 2.10.
Expected Behavior
Boot normally
Steps To Reproduce
Flash 2.10rc3 to T18 via edgetx buddy and then boot it.
Version
Other (Please specify below)
Transmitter
Jumper T18
Operating System (OS)
Windows
OS Version
Windows 11 23H2
Anything else?
No response
Just tested it, working fine here
I can boot into bootloader or main firmware without issues
@3djc Hello! Is your radio flashed via edgetx buddy? In my radio, after press and hold the power button, the led will flash a while and then just stop.
Yes, flashed with buddy
https://github.com/EdgeTX/edgetx/assets/5167938/1c3f9343-f697-4e59-b9f7-e62eaf669b5e
@3djc Strange.. Uh, maybe cause by tx18s? But it has the same PCB with T18 and can use t18's firmwire before. Is there any changes in boot process? 2.10rc3:
https://github.com/EdgeTX/edgetx/assets/19733878/507823cf-77de-46a5-ab38-c38c32fe73a5
2.9.4:
https://github.com/EdgeTX/edgetx/assets/19733878/893af5fe-41c3-4ada-8181-ad3e5ce9ab19
Sorry but this radio is not supported, cannot help since we don't have any information or samples of this radio
As JC has commented, Radioking is not a supported radio family, even though it just happens to work (usually - there have been issues with noise and sticks before).
Most likely, it is affected by a change in how the emergency mode watchdog handling works in 2.10, and some difference with the PCB or QC has been exposed. So at best it can only be supported at a community level, as none of us even have any hardware.
At the present time, your best option is to stay with the last working version for you, and if this is in fact an issue that extends to a supported radio, or someone with the hardware is about attach a hardware debugger to see what is going on, we may be able to fix it.
Unfortunately it seems that is only one of the two necessary IOs for SWD. It seems the pad labelled CLK is PA14 (SWCLK), but the one marked IO is PI3, whereas you want PA13 for SWDIO. Just waiting to hear back if that is available somewhere else. If I'm reading things right for the T18 it is the TX pin for the external module, so just a matter of where to best tap into it.
Actually, it seems like IO actually is SWDIO/PA13, so that should be usable as a SWD header.
Thanks for help. I have connected the SWD port to jlink, but there is nothing can be read via jlink CDC UART port currently. I'm checking what went wrong. I'll let you know if I get more information.
You are on the wrong path with UART. Let a debug build run e.g. via Segger Ozone with your J-Link and magic will happen. Or if you are not after in-circuit-debugging, just flash your radio using Segger J-Flash.
