-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update dfu-util to v0.8 #29
Conversation
Updating dfu-util and ensuring consistency across platforms. Windows was v0.1, now is v0.8 - structure changed to match other platforms. Linux was v0.8, no change needed. Linux64 was v0.7, updated to v0.8. OSX was v0.8, no change needed.
Not entirely sure that this is associated (or solely associated) with dfu-util.
This repo was originally based on https://github.com/rogerclarkmelbourne/Arduino_STM32/tree/master/tools/ |
That makes sense, from memory STM32GENERIC (which I think also inherited the tools setup from Roger) also had outdated dfu-util versions initially. I see Roger has added dfu-util v0.9 to his repo for "F4 DFU testing", but hasn't replaced the older dfu-util version with it yet - possibly because v0.9 is x64 only, as I mentioned previously. I think v0.8 works well enough. There is a changelog here - I don't see anything that would be needed in the STM32 upload process. I think the main problem was that the version for Windows here was very old (v0.1) - it looks like anything after v0.5 (where they added DfuSe support) should work with most STM32 chips. |
There was definitely a problem with the version of DFU which supported DFUSe, as it would not work with the STM32duino booloader, (I can't remember the details) BTW. And people seem fairly OK with using the dfu based bootloader at the moment, as you still need to load drivers (or udev rules) for the Serial, and hence the installation would be no easier even with the HID bootloader |
Updating dfu-util and ensuring consistency across platforms.
win
wasv0.1+svn
, updated tov0.8
- folder structure changed to match other platforms.linux
isv0.8
, no change needed.linux64
wasv0.7
, updated tov0.8
.macosx
isv0.8
, no change needed.I settled on
v0.8
even thoughv0.9
is available because it looks likev0.9
only has x64 Windows binaries, which might cause problems for anyone running x86.v0.8
seems to work fine and was already in use forlinux
andmacosx
platforms anyway.Things that I'd like some input on:
win
dir to its own dfu-util subdir, as this is howlinux
,linux64
andmacosx
are structured. This keeps things tidier (there are a few dfu-util files) and consistent across platforms. Does anyone know a reason not to do that?