Hello Gerhard,
On 2021-03-08 18:25, Gerhard Sittig wrote:
Is the basic operation fundamentally broken, or are just not all
of the product's features available while the device _can_ be
used to get captures and inspect or process the waveforms? In the
former case I'd agree to "not supported", in the latter I would
not.
It appears to work at least partially for some users.
Input threshold adjustment uses the wrong FPGA registers and wrong
algorithm for threshold voltage DAC setting.
Trigger setups use the wrong FPGA registers (won't work).
Sampling setups also use the wrong FPGA registers.
So, quite broken IMHO.
This could be the result of the OEM changing the FPGA bitstream, perhaps
deliberately to scupper sigrok support. Or just some mistakes.
And it would be nice if you'd spell the project's name correctly.
Big 'S' is a big no. Got it.
That's when I had to
assume that it's just another echo of Helge's interesting idea
that the device would not be supported at all because its driver
hasn't shipped yet with a release. Or that his platform would not
be supported by design while the reason was mere non-portable
programming. Which can be fixed, just needs to be done. Properly.
I have tested the patch from Helge and it fixes the byte packing for
windows.
Coupled with some other changes from me, we should have fully functional
support for LA2016 and LA1016.
I sent an experimental patch to Helge K. and Ray M. a week or
so ago but haven't had any feedback yet.
Coincidentally last week I tried to address those unresolved
feedback issues which Helge would not address, and nobody else
stepped up to make it happen or help make it happen.
Helge is eager to help.
Perhaps in some cases your requests are not specific or clear enough to
be understood and acted upon.
The driver source code suffers from a few more issues (format
strings, diagnostics style, choice of data types, unfortunate
dependencies between distant code paths
I am an electronics engineer and am contributing to improve sigrok
support for a device I find useful.
Writing firmware or software is not my speciality but I 'get by', and I
suspect
that could be true for many potential contributors to sigrok.
My functional patches may not meet the standard for submission.
With some guidance I will get there I'm sure.
magic incantations due to lack of a protocol spec
The protocol spec for a proprietary device is a workaround, and a
workaround should not be confused with a solution :-)
Rather than spending time on a protocol spec I just wrote open firmware
for the FX2.
https://bitbucket.org/magellanic-clouds/sigrok-firmware-klafw/src/master/
The FPGA bitstream is still required for now but it's interface is much
easier to document than a proprietary USB protocol.
Regards,
Kevin
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
