WildernessLabs / Meadow_Issues

Public repo for bugs and issues with Meadow
15 stars 0 forks source link

Operation not supported or unimplemented on this platform #735

Closed zwiglm closed 3 months ago

zwiglm commented 4 months ago

meadow firmware write with

CLI: 2.0.51 DFU 0.11

currently 1.12.0 on the F7FeatherV2

PS C:\Users\thinkingUser> dotnet --list-sdks 5.0.416 [C:\Program Files\dotnet\sdk] 6.0.423 [C:\Program Files\dotnet\sdk] 8.0.106 [C:\Program Files\dotnet\sdk]

PS C:\Users\thinkingUser> dotnet --list-runtimes Microsoft.AspNetCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 6.0.31 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 6.0.31 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 6.0.31 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 7.0.20 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 8.0.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

adrianstevens commented 4 months ago

Hi @zwiglm - this is an error message from dfu-util unfortunately. This may be an issue with the USB cable or the specific USB port.

In my experience, devices will deploy successfully but may not flash without being connected directly to your development machine (e.g. no USB hub) or require a different cable.

And we'll look into providing a more meaningful error message in this situation.

zwiglm commented 4 months ago

Hey, thanks for getting back to me regarding this issue. Unfortunately, I am on a business trip and can only try out a different cable mid-next week. Unfortunately, I had no other cable on hand at the time of trying, but that was also on my list. I'll let you know next week, and then I'll close the issue.

zwiglm commented 4 months ago

Hi. Reporting back.

My go-to cable always used to work on the same explicit USB port. The same exact setup does not work anymore. IMO can therefore exclude cable or port issue

Kind regards

zwiglm commented 4 months ago

How does one write with dfu-util? So that I get better debug/error information

adrianstevens commented 3 months ago

Are you on Windows? If so, are you seeing the device as STM32 BOOTLOADER in the Device Manager?

https://developer.wildernesslabs.co/Meadow/Getting_Started/Updating_Meadow/

zwiglm commented 3 months ago

"STM Device in DFU Mode" Hmmm... Only thing I did to the device has been updating to 1.12. Has this removed the STM32 Bootloader?

Edit: "STTub30 (v3.0.6.1)" - That's what Zadig currently finds.

zwiglm commented 3 months ago

So, I reinstalled the driver, and that fixed the problem. Nevertheless - how it got deleted/overwritten is unknown to me in the first place.

adrianstevens commented 3 months ago

thx!