Closed xpulabs closed 1 year ago
Oh, well, I thought the gd32vf103 would work, but I know that chip does weird stuff. I will definitely look into it, but IIRC it might help to run twice.
I mean even in the dfu-util output you can see this:
DFU state(10) = dfuERROR, status(14) = Something went wrong, but the device does not know what it was Clearing status
It might also be worth a shot to try a commit before the move to dfu-libusb (eg. 6b79d67ff8099adc49373cf493094c9513162778) because as I wrote I think I remember doing something about exactly that problem.
It sounds familiar indeed.
If I recall, the device status should be cleared optionally if the device is already in error status. You can see that's what dfu-util does.
Determining device status... DFU state(10) = dfuERROR, status(14) = Something went wrong, but the device does not know what it was Clearing status Determining device status... DFU state(2) = dfuIDLE, status(0) = No error condition is present
Looking at the code, that's what dfu-core does already: https://github.com/dfu-rs/dfu-core/blob/main/src/get_status.rs#L132
It might give some useful information if you can enable the trace logs.
hello,
as below:
I want to flash a bin file like hello.bin, I use:
but I use dfu-util is Ok