Fix invalid device ID check
Hi, thanks for the bug report and the suggested patch. However I don't understand the attached patch. Apparently it is not the same patch as was used in your testing. What is wrong in the original code that makes it an "invalid check"?
Add support for STM32WBA5xxx and STM32WBA6xxx
Thanks Antonio and Francesco!
Then what if some other chip also reports 200 ms but doesn't need 35 seconds, maybe even correctly needs less than 200 ms? :) How many seconds does the datasheet say?
Poll timeout 200 ms on command MASS_ERASE (state=dfuDNBUSY) The chip tells dfu-util to wait 200 ms before asking about status again, but that is probably too short and the chip is still busy erasing and not able to communicate so our get_status request times out.
Can you please format the STM32H7 output? You can see in the STM32F407 output: "Setting timeout to 35 seconds". This is a quirk because we know some devices report wrong erase time. Maybe the F767 also reports wrong erase time. Please use -v -v to see more debug information. You can also use -v -v -v but that is so verbose you'd better attach the output as a file.
Windows git snapshot binaries can be found here: https://dfu-util.sourceforge.net/snapshots/ (2024-04-16 is practically latest git)