Whilst powered on and inserting USB lead connected to pc, radio powers off every time 2.11.0 RC #5899
Comments
Kevltan
added
bug 🪲
Kevltan
changed the title
|
@philmoz |
|
Cannot reproduce, the the USB choice menu pops like it should here. Tested on both MK1 and MK2 |
|
What can possibly be the issue here then? The usb connection works on 2.10.6 does not work on 2.11.0 rc. New SD card basic 2.10.6 loaded on no additions whatsoever on it, start radio, says there a files missing as expected then goes into stick calibration as expected put usb cable in to top of radio and instantly powers down every single time. Could there be something residual left in rom when loading firmware? Is worth doing a chip erase in STM32CUBE. I am lost for ideas here. |
|
Do you have a default usb mode set, or should it prompt ? |
|
Usually I have default usb mode set. But this is not the case with the last try as there was nothing set on a fresh SD card with no additions in 2.10.6 software on it, no models sound files radio data etc. I just plugged usb into the top and the radio just powered off into to sort of boot mode with the left hand led of six on. Screen blank and off, with a sharp click from the speaker as it powers off. |
|
Hello, I have the same error now that I have the new v2.11.0-RC1 on the transmitter. |
|
This issue has been kreeping up for ages but no one has seemed to be able to replicate it when I have created the issue request. I have already had problems with this in the past and raised the issue in the 2.11.0 nightlies. It is much more pronounced now than it was and is instantaneous in the latest 2.11.0 RC. Because I had the problem in the nightlies for safety reasons I decided to revert back to the 2.10's firmwares which seem relatively stable in this respect. |
|
Are you able to build the firmware yourself? |
|
Yes will have ago.
…On Wed, 12 Feb 2025, 21:25 philmoz, ***@***.***> wrote:
Are you able to build the firmware yourself?
If so can you try using the source from PR #5902
<#5902> and commenting out line 488
in radio/src/main.cpp (call to handleUsbConnection).
—
Reply to this email directly, view it on GitHub
<#5899 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANPFAWZI5KSJXHVTNSDDQU32PO33XAVCNFSM6AAAAABW63NDZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJUHA3TMNZSGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
|
@philmoz
Have built this and this removes the usb capabilities completely - there is
now no option for usb and a little black usb logo (next to volume indicator) appears in the top right of the screen and a drive is no longer created in windows when plugged in!
VERS: 3.0.0-selfbuild (ad2c6de)
Can you clarify that I have the correct firmware build please?
…On Wed, 12 Feb 2025, 21:38 Kev the Rev, ***@***.***> wrote:
Yes will have ago.
On Wed, 12 Feb 2025, 21:25 philmoz, ***@***.***> wrote:
> Are you able to build the firmware yourself?
> If so can you try using the source from PR #5902
> <#5902> and commenting out line 488
> in radio/src/main.cpp (call to handleUsbConnection).
>
> —
> Reply to this email directly, view it on GitHub
> <#5899 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ANPFAWZI5KSJXHVTNSDDQU32PO33XAVCNFSM6AAAAABW63NDZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJUHA3TMNZSGI>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
|
|
That's the correct version, and what I would expect to happen. If you put line 488 back does it now crash when plugging in the USB? If it crashes can you change the USB mode to joystick (Radio Setup) instead and see what happens please. Just trying to narrow down where it i crashing. |
|
OK will do |
|
Unedited 3.0.0 firmware the same..... USB: crashes! |
Crashes when USB mode is set to Joystick? |
|
What about 'Storage' and 'Ask' modes for USB? |
|
Doesn't crash in ask mode until either storage or joystick is selected from this. Crashes immediately if any one of these 2 modes is already selected/active and if lead is inserted or already inserted when Tx is powered up. |
|
You should not be able to power on the radio if the USB lead is plugged in. It should go into DFU mode if you plug in the USB cable when turned off. Did you flash both bootloader and firmware? It would be helpful if you could narrow down at what commit the problem started happening; but this can be a very tedious process. |
|
Yes meant inserting the lead after it is has started to power on. Yes it drops into dfu mode when you insert the lead when in usb mode running 2.11.0 Yes I have tried both 2.10.6 bootloader and 2.11.0 bootloader and directly from STM32CUBE from the PC - same results. Can any data be left on the internal flash/rom in the chip that could be affecting this? Or is this some sort of firmware glitch or conflict? I have NO internal modifications in this radio either i.e. IMU etc. It is as standard as regards electronics. Dfu mode works no problem using STM32CUBE which says to me there has got to be a firmware conflict with this radio somewhere👌 |
|
It's not easily reproducible which makes things harder. You said the problem is not there in 2.10 - have you reverted and retested to be sure? If 2.10 works then some change in the code is not behaving on your camera - if we can isolate which commit it started happening in that might help identify the cause. |
|
Absolutely, it does not happen in 2.10.6 it is instant on 2.11.0 and reproducable every time. I have put minimum software on the SD card as well and still does it when 2.11.0 firmware loaded. It's definately firmware related I think. |
|
If radio works in dfu mode (with usb lead) surely it should work in usb mode unless there is problem with the coding for the TX16S MK1 as it would appear I am not the only one with this problem. Question is what has my radio and his radio got in common🤔 |
|
What about in the bootloader - can you connect the USB and see the SD card mounted on your PC? |
|
Yes it connects in bootloader mode - in device manager comes up as a universal serial bus device - STM32 bootloader. I am able to upload firmware to the radio using STMcubeprogramer succesfully. But as expected in this mode there is no disk drive created on the pc. |
|
That sounds like DFU not bootloader. Do you see the bootloader screen?
|
|
You learn new things every day 😂! Yes connects successfully in bootloader mode and creates an editable drive on the pc. Reads "USB Connected" on the radio display. |
|
At this point all we can do is try and identify where in all the 2.11 changes the problem starts. |
|
@philmoz |
|
@philmoz I know you wouldn't do it in flight but what worries me Phil is by connecting a usb lead you can effectively power the radio off, and that a conflict resides somewhere in the firmware to do this! |
|
Are you familiar with the nightlies? It sounds like you might need to try some of the older 2.11 nightlies to see if you can fine one that still works. That will let the devs know which of the new commits broke the feature for your hardware. |
|
I have exactly the same problem with the same radio and for me the latest nightlie that works correctly is "2.11.0-selfbuilt (a35246b) from 2024-09-03 but I haven't tried them all. |
|
Tried this one as above a35246b exactly the same instant off when usb lead plugged into pc. |
|
@philmoz Going back to another issue I highlighted a couple of days ago the 2.11.0 RC1 scrolling betwen main views is not as smooth as in 2.10.6. and the above 2.11.0 self build nightly is the same in this respect - so it looks like this may have been indroduced as well into 2.11.0. |
|
Hello, I have tested the last 3 versions with the result that the version from 17.12.24 was OK. |
|
Have tried (12e84b5) still crashes imediately when usb lead inserted on mine. This is very strange that some peoples do and some peoples don't!!! What the hell is the difference in these radios!? |
There is nothing changed between 17.12.2024 and 22.12.2024 that would affect USB. |
Bad RAM or bad FLASH memory. |
|
That could explain the variations in testing results |
|
Why would this only effect the usb and nothing else???? Would I be right in saying STM32CUBE verifies when writing to the flash and RAM? Is it possible to erase the chip completely on STM32CUBE or is this not a good idea as this will erase bootloader too? |
|
@philmoz |
|
@philmoz |
Depends on what you mean by "bootloader". If you mean bootloader as it is described by EdgeTX, then yes it will be erased, and will be written back when you write the firmware back (via STM32Cube /DFU). The DFU "bootloader" is in ROM, and CANNOT be erased. This is why these radios are generally referred to as unbeickable, as you can always use DFU to reflash firmware (except for hardware failure, naturally).
There is a specific verify option you can enable / tick where you configure firmware writing. |
|
@pfeerick On investigation it appears that the processors FLASH and RAM are the same but allocated by "pins" by the manufacturer !? |
|
Any update (its gone quiete) of a possible resolution for this issue devs ?🤔 I believe that once a few more people take the plunge and start updating to 2.11.0 that there are going to be few more instances of this problem arrising! |
Is there an existing issue for this problem?
What part of EdgeTX is the focus of this bug?
Transmitter firmware
Current Behavior
Radio powers off when inserting usb lead connected to PC every time in 2.11.0 RC - TX16S mk1.
Works fine in 2.10.6.
Expected Behavior
Expect to enter into usb mode and not power off.
Steps To Reproduce
As above
Version
2.11.0-rc
Transmitter
RadioMaster TX16S / TX16SMK2
Operating System (OS)
No response
OS Version
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: