Hi Sascha, On Mon, Mar 30, 2020 at 07:26:30AM +0200, Sascha Hauer wrote: > DFU stopped working for me quite a while ago and I tracked it down to > this dfu-util commit: > > | commit 377f6f136d3369529f44578acaeee82d7c7d7af9 > | Author: Paul Fertser <fercerpav@xxxxxxxxx> > | Date: Sun Aug 10 14:26:05 2014 +0400 > | > | dfu_util: Ignore alt_index/alt_name specification in runtime mode > | > | When the device is in runtime mode it needs to be reset first into DFU > | mode for the list of alternate settings to appear, so unless it is > | already in the right mode, matching on alt setting number or name > | should be skipped. > | > | Fixes regression on OpenMoko Freerunner. > | > | Signed-off-by: Paul Fertser <fercerpav@xxxxxxxxx> > > Are you using a recent dfu-util version? Is your patch the fix for this > commit? Yes, I am using dfu-util version 0.9. I didn't search in dfu-util commit history but yeah my patch seems to be a fix for this commit. The current DFU gadget do not handle USB reset and thus cannot change mode, it cannot go from runtime to DFU mode. The solution is to always be in the DFU ready mode. Thanks for sharing this commit, it explain well what I was experiencing: dfu-util was correctly listing partitions but failed to found a device when trying to update a partition that is still in runtime mode. Jules _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
