EdgeTX / buddy

The next generation tool for EdgeTX. A cross platform app, with browser compatibility.
https://buddy.edgetx.org
MIT License
37 stars 19 forks source link

Unable to flash protected devices #20

Closed vbabiy closed 2 years ago

vbabiy commented 2 years ago

I get this error:

Special DfuSe command 65 failed Details

My Setup:

OS: Manjaro Linux x86_64
Host: X570 I AORUS PRO WIFI -CF
Kernel: 5.15.21-1-MANJARO
Uptime: 1 day, 8 hours, 21 mins
Packages: 2243 (pacman), 39 (flatpak), 9 (snap)
Shell: zsh 5.8
Resolution: 2560x1440, 2560x1440, 2560x1440, 2560x1440
DE: GNOME 41.3
WM: Mutter
WM Theme: Qogir-dark
Theme: Qogir [GTK2/3]
Icons: Qogir [GTK2/3]
Terminal: alacritty
CPU: AMD Ryzen 9 5900X (24) @ 3.700GHz
GPU: AMD ATI Radeon Pro WX 4100
Memory: 20919MiB / 64316MiB
freshollie commented 2 years ago

Hey! Could you send a screenshot?

freshollie commented 2 years ago

Also might be helpful if you could screenshot the JS console when you get the error, and would be good to know what type of radio you are using

vbabiy commented 2 years ago

image

image

image image

freshollie commented 2 years ago

So it's failing to run the DFuse command to erase a sector from your radio, I've pushed a change which might give some more info on the error. Can you try that again in about 30 mins when the build goes live, and send me another screenshot of the console error?

vbabiy commented 2 years ago

@freshollie Looks like I got the same output: image

vbabiy commented 2 years ago

Also when I try to use the edgetx-flasher (The desktop version) I get this error: image

freshollie commented 2 years ago

This is still very helpful, thanks!

freshollie commented 2 years ago

So we think this issue is become of write protection in some radio models, in Flasher you can correctly flash your radio by enabling Force flashing. For Buddy this is not yet available. Can you try this?

vbabiy commented 2 years ago

image image

@freshollie if I did it right, looks like the same issue

freshollie commented 2 years ago

Oh interesting, maybe that's not the case :/

pfeerick commented 2 years ago

Once you've done the force unprotect, try flashing the firmware a second time... (shouldn't need the force unprotect... i.e. if that command did it's job, buddy should work now). Basically the dfu-util tool needs to be run twice if force unprotect is needed... first time clears the flag, second time does the actual firmware update.

vbabiy commented 2 years ago

@pfeerick indeed that seems to be working now. image

freshollie commented 2 years ago

Nice! Will look into automatically unlocking protected devices

freshollie commented 2 years ago

Thanks for the report, if this happens to others they will be prompted to use the new "Unlocker" tool image image

At some point I will build this into the main flashing flow without having to redirect to a new tool