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.
-- Martin
> UPDATE:
>
> With saleae firmware extracted from 1.0.21 step 3 and following just work.
> The problem with step 3 and following was clearly related to the (lack of)
> support for fw 1.1.5.
>
> Just remains the re-enumeration timeout.
>
> -- Martin
>
>>> Hmm, so it's still not clear to me what the bug really is, but I think
>>> CMD_GET_FW_VERSION should be retired. biot's use of the usb dscr makes
>>> much
>>> more sense.
>>
>>>> B: libsigrok version 0574e4c04dac739d758ec609c3737f1a64fea7ac with
>>>> Saleae 1.1.5 firmware
>>
>>>> B: fails first run (with libusb error), works on second run, and fails
>>>> every following run with "status 2 received 0 bytes". After resetting
>>>> the
>>>> device, the same behaviour is seen.
>>
>> I looked into the logs for B, and this is what I see.
>>
>> Run 1: the device is at 1.6, it receives the saleae firmware, will
>> re-enumerate and come back as 1.7. However debug info shows bus 1 is
>> empty, so the software has not given the system enough time for the
>> re-enumeration and bails out.
>>
>> Run 2: this device is now at 1.7, it receives the saleae firmware
>> (again).
>> However, the device does not re-enumerate and stays at 1.7. This may be
>> a
>> nice feature of the saleae firmware, that only re-enumerates when
>> required. That would be nice for fx2lafw as well. The rest of the
>> software
>> sees the device at 1.7 and uses it without problem.
>>
>> Run 3: same as 2 (device stays at 1.7 even with new firmware being
>> downloaded). However, something in the handshake with the firmware went
>> wrong at the end of run2 and the firmware does not provide anymore data.
>>
>> One problem that may be easily addressed here is to provide more time
>> for
>> the re-enumeration.
>
>
>
>
> ------------------------------------------------------------------------------
> 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
>
------------------------------------------------------------------------------
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
