Update bricked, and gui doesn't work....

[fantacmet]

A little bit tech stuff on LINUX (Version Linux Mint 21.3 Virginia 64-bit), just for diagnosis to compare with working virtual COM port from Typhoon H. No drivers or applications to work with, just standard LINUX OS.

"lsusb" w/o connection:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 30fa:0400 USB OPTICAL MOUSE
Bus 001 Device 002: ID 046d:c248 Logitech, Inc. G105 Gaming Keyboard
Bus 001 Device 004: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

"lsusb" with connection to MCU-board:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 30fa:0400 USB OPTICAL MOUSE
Bus 001 Device 002: ID 046d:c248 Logitech, Inc. G105 Gaming Keyboard
Bus 001 Device 005: ID 0483:5740 STMicroelectronics Virtual COM Port
Bus 001 Device 004: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

"dmesg | grep usb" shows following after plug-in USB to MCU-board:

[ 56.232010] usb 1-6: new full-speed USB device number 5 using xhci_hcd
[ 56.382089] usb 1-6: New USB device found, idVendor=0483, idProduct=5740, bcdDevice= 2.00
[ 56.382102] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 56.382108] usb 1-6: Product: YUNEEC TyphoonH
[ 56.382113] usb 1-6: Manufacturer: Yuneec Electric Aviation
[ 56.382118] usb 1-6: SerialNumber: 0
[ 56.406755] usbcore: registered new interface driver cdc_acm

"tail -f /var/log/syslog":
Jun 18 20:24:27 XEON kernel: [ 481.306010] usb 1-6: new full-speed USB device number 6 using xhci_hcd
Jun 18 20:24:27 XEON kernel: [ 481.455926] usb 1-6: New USB device found, idVendor=0483, idProduct=5740, bcdDevice= 2.00
Jun 18 20:24:27 XEON kernel: [ 481.455941] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jun 18 20:24:27 XEON kernel: [ 481.455948] usb 1-6: Product: YUNEEC TyphoonH
Jun 18 20:24:27 XEON kernel: [ 481.455953] usb 1-6: Manufacturer: Yuneec Electric Aviation
Jun 18 20:24:27 XEON kernel: [ 481.455958] usb 1-6: SerialNumber: 0
Jun 18 20:24:27 XEON kernel: [ 481.458994] cdc_acm 1-6:1.0: ttyACM0: USB ACM device
Jun 18 20:24:27 XEON mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6"
Jun 18 20:24:27 XEON mtp-probe: bus: 1, device: 6 was not an MTP device
Jun 18 20:24:27 XEON mtp-probe: checking bus 1, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6"
Jun 18 20:24:27 XEON mtp-probe: bus: 1, device: 6 was not an MTP device
Jun 18 20:24:29 XEON ModemManager[1060]: <info> [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-6': not supported by any plugin

I'll do this when I get home with my linux machine. I'll copy/paste the results. Assuming nothing special needs to be downloaded?

 

[fantacmet]

Without Board connected:

mike@LinBox:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
Bus 001 Device 003: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

With board connected:

mike@LinBox:~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0438:7900 Advanced Micro Devices, Inc. Root Hub
Bus 001 Device 003: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

mike@LinBox:~$ sudo dmesg | grep usb
[sudo] password for mike:
[ 0.470690] usbcore: registered new interface driver usbfs
[ 0.470690] usbcore: registered new interface driver hub
[ 0.470690] usbcore: registered new device driver usb
[ 0.582649] pci 0000:00:12.0: quirk_usb_early_handoff+0x0/0x190 took 11509 usecs
[ 0.646691] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
[ 0.646696] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.646699] usb usb1: Product: EHCI Host Controller
[ 0.646702] usb usb1: Manufacturer: Linux 6.8.0-31-generic ehci_hcd
[ 0.646704] usb usb1: SerialNumber: 0000:00:12.0
[ 0.888376] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 1.109799] usb 1-1: New USB device found, idVendor=0438, idProduct=7900, bcdDevice= 0.18
[ 1.109812] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 1.285925] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.08
[ 1.285937] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.285941] usb usb2: Product: xHCI Host Controller
[ 1.285944] usb usb2: Manufacturer: Linux 6.8.0-31-generic xhci-hcd
[ 1.285947] usb usb2: SerialNumber: 0000:00:10.0
[ 1.335776] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[ 1.335837] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.08
[ 1.335842] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.335846] usb usb3: Product: xHCI Host Controller
[ 1.335849] usb usb3: Manufacturer: Linux 6.8.0-31-generic xhci-hcd
[ 1.335852] usb usb3: SerialNumber: 0000:00:10.0
[ 1.393626] usb 1-1.4: new full-speed USB device number 3 using ehci-pci
[ 1.487253] usb 1-1.4: New USB device found, idVendor=0bda, idProduct=b00a, bcdDevice= 1.10
[ 1.487264] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1.487267] usb 1-1.4: Product: Bluetooth Radio
[ 1.487269] usb 1-1.4: Manufacturer: Realtek
[ 1.487271] usb 1-1.4: SerialNumber: 00e04c000001
[ 1.551882] usb 2-1: new high-speed USB device number 2 using xhci_hcd
[ 1.693496] usb 2-1: New USB device found, idVendor=05c8, idProduct=03d2, bcdDevice= 0.05
[ 1.693514] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.693520] usb 2-1: Product: HP TrueVision HD Camera
[ 1.693525] usb 2-1: Manufacturer: SunplusIT Inc
[ 6.815274] usbcore: registered new interface driver btusb
[ 6.861709] usb 2-1: Found UVC 1.00 device HP TrueVision HD Camera (05c8:03d2)
[ 6.950926] usbcore: registered new interface driver uvcvideo
[ 1954.406476] usb 1-1.4: reset full-speed USB device number 3 using ehci-pci
[ 2383.062208] usb 2-2: new full-speed USB device number 3 using xhci_hcd
[ 2383.185473] usb 2-2: device descriptor read/64, error -71
[ 2383.415547] usb 2-2: device descriptor read/64, error -71
[ 2383.639200] usb 2-2: new full-speed USB device number 4 using xhci_hcd
[ 2383.762584] usb 2-2: device descriptor read/64, error -71
[ 2383.991463] usb 2-2: device descriptor read/64, error -71
[ 2384.100959] usb usb2-port2: attempt power cycle
[ 2384.488195] usb 2-2: new full-speed USB device number 5 using xhci_hcd
[ 2384.488766] usb 2-2: Device not responding to setup address.
[ 2384.692739] usb 2-2: Device not responding to setup address.
[ 2384.900178] usb 2-2: device not accepting address 5, error -71
[ 2384.900502] usb 2-2: WARN: invalid context state for evaluate context command.
[ 2385.014187] usb 2-2: new full-speed USB device number 6 using xhci_hcd
[ 2385.014756] usb 2-2: Device not responding to setup address.
[ 2385.220730] usb 2-2: Device not responding to setup address.
[ 2385.428176] usb 2-2: device not accepting address 6, error -71
[ 2385.428502] usb 2-2: WARN: invalid context state for evaluate context command.
[ 2385.428732] usb usb2-port2: unable to enumerate USB device

mike@LinBox:~$ sudo tail -f /var/log/syslog
2024-06-18T16:37:01.909682-07:00 LinBox kernel: usb 2-2: Device not responding to setup address.
2024-06-18T16:37:02.115604-07:00 LinBox kernel: usb 2-2: Device not responding to setup address.
2024-06-18T16:37:02.323530-07:00 LinBox kernel: usb 2-2: device not accepting address 6, error -71
2024-06-18T16:37:02.323569-07:00 LinBox kernel: usb 2-2: WARN: invalid context state for evaluate context comm
and.
2024-06-18T16:37:02.323574-07:00 LinBox kernel: usb usb2-port2: unable to enumerate USB device
2024-06-18T16:36:47.491559-07:00 LinBox wpa_supplicant[924]: message repeated 8 times: [ wlo1: CTRL-EVENT-BEAC
ON-LOSS ]
2024-06-18T16:37:58.067652-07:00 LinBox kwin_x11[2751]: qml: PlasmaExtras.ScrollArea is deprecated. Use Plasma
Components3.ScrollView instead.
2024-06-18T16:40:19.290335-07:00 LinBox systemd[1]: Starting sysstat-collect.service - system activity account
ing tool...
2024-06-18T16:40:19.320166-07:00 LinBox systemd[1]: sysstat-collect.service: Deactivated successfully.
2024-06-18T16:40:19.320522-07:00 LinBox systemd[1]: Finished sysstat-collect.service - system activity account
ing tool.

 

[h-elsner]

At this point I'm thinking that the bootloader of the STM32 on the flight controller is broken. Even if the FW is not proper installed it can be overwritten (in this case even with the same or older FW) all the time as long as the bootloader is in place. FW update will not touch the bootloader. This is only possible via debug port.

The bad thing: We have no bootloader FW from Yuneec and it cannot be copied from a working one due to security feature of STM32.
If someone has an idea how to overcome this situation I will be very interested in because I have some MCU boards with an unknown PX4 FW. I can overwrite this with a new bootloader and install Thunderbird FW but I have not found a way to go back to legacy Yuneec FW.

 

[fantacmet]

For me the cost of doing g what they want and buying the latest they have to offer is prohibitive.

I know there are people out there who could easily bypass that security feature, those people have zero interest in drones. So far st least.

Too bad we can't use that micro SD card slot for anything.

 

[h-elsner]

Yes, the SD card is not (no more?) supported by the firmware. The SD card slot is only mounted at very old MCU boards. You are lucky if you have one of those rare exemplars.

A way to bring life into this thing is to use the customized PX4 firmware from Toni called Thunderbird FW. SD card is then usable for flight logs and missions. You will get an open and agile drone but sonar and gimbal (except tilt) will not supported any more.

I have reflashed bootloader and flashed with Thunderbird FW up one and I love it. But there is no way back as explained above (missing Yuneec bootloader).

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[fantacmet]

I'll probably save that as a last resort, as I'm quite fond of the gimble to be honest. I'll try the swapping if the IMU, and if that doesn't work, then I will go this route. Does the Thunderbird also still have the GPS and Preprogrammable flight plan ability?

 

[h-elsner]

Does the Thunderbird also still have the GPS and Preprogrammable flight plan ability?

Yes. Positioning (GPS support) works and Missions are possible. It's like H520 then. As mission planner use QGroundControl. You have a SD card slot and can upload more and more complex missions to the drone.
Unfortunately you cannot turn the camera around which is a great feature, all other functions are still there.

 

[fantacmet]

The big thing with the camera for me is doing the flight plan with the way points and having it automatically pan through. I live in a beautiful area..

This is my second flight for instance. This is just outside my door.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[h-elsner]

I live in a beautiful area..

True! Beautiful.

 

[komodo]

Neighbor bought this drone new, tried it, and it spooked him so he decided no drones for him.


Me doing alot of RC including helicopters and other drones, bought it from him a short time ago(couple weeks), and had fun flying it. I prefer thr controller over the toy like simplistic controllers of DJI. I love the 6 rotor design, etc.

So I checked for updates and only update it needed was autopilot. So I grabbed the file from YuneecSkins and ran the update. Seemed to work fine. Took it out for a flight after and all seemed well.

Tried to fly the next day and it would only beep once. Camera would center if I held power long enough but that's it. I connect USB and battery it lights up, and does the boot sound and then just sits there with a regular descending 2 tone beep like it's waiting for an update.

I have tried and tried and can NOT get this thing to connect to GUI, all the way down to this.

Fresh wipe of a Windows 10 laptop. I installed firefox, and then using links from this forum, downloaded the GUI 1.2.13. Downloaded firmware 1.28_24_9_2016.yuneec.

I then went to MS and downloaded the 2017 C++ redistributables. Installed, rebooted.

Set the installer for the GUI to run in compatability mode for Windows 7, and ran as admin. All the drivers and everything else installed correctly(I did this on another laptop without compatability mode and same difference, both Win10 and Win11).

Set compatability mode to Win7 and run as administrator, for the installed GUI.

I opened up the updater, loaded the afformentiones .yuneec file made sure battery was removed from the drone, connected the USB and it just sits there and does nothing. No matter how long I let it sit there.

Do I need to buy a Win7 Native laptop or dig up one of my old XP laptops that take an hour and a half to boot?

Sunk a bunch $$ into this thing to only fly it a few times.

I have a background in IT and 30 years experience on the tech side of computers.

at least you were not dumb enough to buy the typhoon brand new w/4 batteries for 1800. then long distance antennea for reciever and transmitter 250., backpack 60. and the yuneec skyview fpv headset at 300.my 2 morpilot batteries I bought seperate have swollen to the point of not fitting into the drone and look extremely unsafe they have never been used due to this. the two original batteries are still running strong with at least a hundred charges on both of them. personally, my opinion is us typhoon h flyers are unwillingly being phased out for even bigger spenders. you cant even download software updares from yuneec and customer service sucks! but I still love this hexacoptor flying this one is sooo easy and a blast for filming wildlife. my dji phantom 3 pro with 4 batteries, long distance antennea upgrades and a fat shark and camera. because due to yuneecs typhoon h with 360 degree swivel and landing gear that retract from camera view has yet to come out of its backpack and hit the sky. yuneec typhoon h is far superior to the dji phantoms that I cant bear to leave typhoon h at home for the phantom. just my opinion without listening to my wallet.

 

[komodo]

True! Beautiful.

would you be talking about oregon or your hexacoptor? LOL

 

[fantacmet]

would you be talking about oregon or your hexacoptor? LOL

Washington actually.

 

[komodo]

Washington actually.

both. washington has a beautiful coastline that is almost as beautiful as oregon, just ask my drone.

 

[fantacmet]

Yes, the SD card is not (no more?) supported by the firmware. The SD card slot is only mounted at very old MCU boards. You are lucky if you have one of those rare exemplars.

A way to bring life into this thing is to use the customized PX4 firmware from Toni called Thunderbird FW. SD card is then usable for flight logs and missions. You will get an open and agile drone but sonar and gimbal (except tilt) will not supported any more.

I have reflashed bootloader and flashed with Thunderbird FW up one and I love it. But there is no way back as explained above (missing Yuneec bootloader).

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

I went and checked all the documentation. I can't do this either, as none of the computers, give it a com port, or even a virtual comp port.

 

[fantacmet]

Well this is interesting.

The MCU boards from WTFD arrived.

Before I tried swapping IMU, I tried both to see if the drone would power on. Same issue as before.

I swapped the IMU on the older one, and tried. Same issue. I tried each one connecting to the computer with the update, and the same issue. The newer board I didn't even remove the IMU. Nothing. Same issue on the drone, same issue on the PC.

If H-Elsner wants to to remote in to one of my machhines and try it, I can set it up. I have the Windows 10 machine, that's a fresh install. I also have the Linux box. I don't let anyone remote into my main machine. For obvious reasons.

While that may end up resolving connecting to the MCU(which will be needed one way or the other eventually), it doesn't resolve the issue of still not powering up.

 

[WTFDproject]

....I tried each one connecting to the computer with the update...

Were the boards installed to the drone when you tried?

You mentioned the scary word "update". Were you connecting to the GUI update page?

Let's try this experiment:
1.) Unplug the FC from the pins on the Drone.
2.) Plug the USB cable into the drone USB adapter:

3.) Plug the drone USB adapter extension into the FC board:

4.) Start the GUI.
5.) Ensure the GUI is showing the "Device Information" page:

6.) Plug the USB cable into the computer.
7.) Check if any LED activity is shown on the FC board:

8.) Check if the GUI shifted to the Sensor Page, regardless of whether any values are showing:

 

[WTFDproject]

.... it doesn't resolve the issue of still not powering up.

Have you checked to ensure the power button connector is plugged in and has good connection on both pins?


Try this:
1.) Remove the FC board.
2.) Leave the battery in.
3.) Push the power button.
4.) Do you get a quick flash of the blue LEDs on the ESC board?

 

[WTFDproject]

Another quick check:
Plug the PC end of the USB into a phone charger and look for LED activity.
Note this only checks the power connection, not the data.

 

[fantacmet]

I did it both ways, Connected to drone and not connected to drone. LED lights, light up as they are supposed to.
When I press and hold the power switch, the LED's all come on. The 6 on the ESC board flash, and the one on the back stays on as long as button is held.

I tried with the gui info page. i only tried one with the update. Same issue occurs, USB device has malfunctioned error.

A question had been asked back in the beginning if the GUI had ever worked, and I said i never tried it. Thats not accurate, i remembered I had tried it, and had only been able to mess with the motor test a little bit. Nothing else ever showed up.

The 6 LED's flash regardless if the FC board is plugged in or not.

Anyway here is a video redoing some of it so you can see for yourself exactly what is going on. This is on my Win11 machine.

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

 

[WTFDproject]

When I press and hold the power switch, the LED's all come on. The 6 on the ESC board flash, and the one on the back stays on as long as button is held.

That is the "Normal" LED response on the main ESC Board if no FC module is mounted. It is also the "Normal" response if the FC module is plugged in 1 row back from normal (see pic).

The front four pins on each side are power from the ESC board. Check if all pins have power when you are holding the power button down.