On 04/27/2012 08:07 PM, [email protected] wrote: > UPDATE 2: > > With fx2lafw the problem is also related to the fact that the software > does not wait for re-enumeration. A blunt > > sr_info("fx2lafw: Waiting 3 seconds for re-enumeration"); > sleep(3); > > after the call to ezusb_upload_firmware fixes it. > > Question is why the software does not wait for re-enumeration in the first > place. The second problem is that the firmware gets loaded again and > again, so the program hangs 3 seconds on each invocation of sigrok.
This last bit is a bug that was fixed a couple days ago, can you try this with the latest from git? But in any case, the problem isn't in this, or the size of the re-enumeration timeout, but rather the fact that the driver doesn't appear to wait at all. It should log "fx2lafw: Waiting for device to reset." before waiting up to MAX_RENUM_DELAY (3 seconds), periodically checking. I don't see a path through the code that could cause this. After a firmware upload, the timestamp (ctx->fw_updated) is set, and it's always checked before the device is opened. -- Bert Vermeulen [email protected] email/xmpp ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
