Hi Magnus,

On Sat, 2015-11-28 at 16:46 +0100, Magnus Lundmark wrote:
> In all cases it worked flawlessly and found the LWLA1034 every time.
> I also checked sample acquisition with treiggering in Pulseview and
> this went well.

Thanks for testing, it helps a lot!

OK, could you please generate logs from the acquisition, too? The
output from

  pulseview -l 5

will do. I put some debug messages in the code to alert about short
transfers. If you don't see them, the device may be working fine
accidentally -- in my experience, the problem occurs only sporadically.

I'm not sure I actually want to see the short transfer hackery from
that branch in sigrok proper. It slows down the memory read quite
noticeably. Perhaps as a last resort, if we cannot find another way to
handle this.

By the way, further investigation has confirmed that this is in fact a bug in 
the FX2 firmware of the device. I was able to reproduce it on Windows, too, 
with the original software.

I'm now in contact with the manufacturer about this. Not sure yet though how 
easy/difficult it will be to replace the FX2 firmware.

Cheers,
--Daniel


------------------------------------------------------------------------------
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Reply via email to