Hendry Kaak

Dfu-util user feedback optimisation

I have now pushed the changes to git. One way to test it out is to pack a DfuSe file from multiple binary files with several alternate interfaces, and for the non-flash targets, use a RAM address (one that doesn't clash with bootloader operation!): ./dfuse-pack.py \ -b 0x08001000@0:/tmp/at4k.bin \ -b 0x08002000@0:/tmp/at8k2k.bin \ -b 0x20004000@1:/tmp/at4k.bin \ -b 0x20004400@2:/tmp/at4k.bin \ -b 0x20004800@2:/tmp/at4k.bin \ ../testalt.dfu The resulting DfuSe file can be verified with: ./dfuse-pack.py...

Console output of the download that went well.

@tormod I did a couple of tests with the dfuse-pack.py script and it seems to work well if the alternateSetting is set with '@x'. The only con I saw when using this option is that people can still unknowingly enter 2 or more different '@x' parameters and depending on the sequence of the build parameters it will always pick the last alternateSetting in the command line as the alternateSetting for the whole target suffix (without warning the user). If this is the case, it should probably create a new...

I'll see what I can do. Perhaps I can write a few optional bytes for now to verify if dfu-util works with multiple images.

Nice! That's some quick progress. This makes testing a lot easier, thanks.

I'll see what I can do. Perhaps I can write a few optional bytes for now to very if dfu-util works with multiple images.

Nice, that seems to be working well already! The only log output to mention is probably this memory leakage at the end of the upload log, but the upload process seems to be working correct with a single image indeed. libusb: debug [libusb_close] libusb: debug [libusb_exit] libusb: debug [libusb_exit] destroying default context libusb: warning [libusb_exit] some libusb_devices were leaked