Hi Helge,
I am glad to hear you have the analyser somewhat working on Windows,
that is good progress. I still suspect there are some issues, like
setting triggers and logic thresholds, and I suspect the FPGA bitstream
is not quite correct (maybe I am wrong). I think I have a good
understanding of all the control commands and have a few python scripts
to give full control of the analyser - fw and bitstream download,
setting triggers and thresholds, running and retrieving data. Most of it
is based on Florian's code but with some changes that were deemed
necessary after looking at the hardware, in particular the SPI bus
between FX2 and the FPGA used for control of FPGA functions by accessing
a set of 8-bit registers (via USB vendor command 32). I will tidy the
python code and share it somewhere, that is the best documentation of
what I have found. TBA, give me a day or two.
The bitstream size is deliberately misleading and must be a correct
'magic' number to load the bitstream correctly. I do not know the
algorithm but it generates a number which is close to, but never
matching the true bitstream length. Note that the FX2 has no real reason
to know the bitstream size in advance, other than some interlock scheme,
since it is framed by control transfers at start/end of upload.
I think a forum works better than mailing list for discussing details.
Is there a forum frequented by sigrok folks? If not, we could add to
this perhaps? :
https://www.eevblog.com/forum/testgear/looking-for-kingst-la2016-users/
Rgds
Kevin
On 2021-01-08 07:39, Helge Kruse wrote:
Hi Kevin,
My OEM software version 3.4.3 also uploads a bitstream to EP#2. The
exported file has the same CRC32 here, the size is 184,320 (0x2D000)
bytes. Nevertheless the Control Out Transfer before the bitstream is
(req:50 val:00 inx:00 len:04 [BA B8 02 00]). This doesn't match the
size
of the bitstream.
The bitstream to be extracted with the sigrok python script has 178,233
(0x2B839) and a CRC32=0x3E8A71F0.
I read from Florian, that he implemented the sigrok kingst-la2016
driver
with the intention that it mimics the behavior of the OEM software. Of
course, to control the analyzer we must understand the USB transfers
and
adapt the data to get the desired result. So we are all gathering
information about that protocol.
I also tried to get an idea about the meaning of the transfers.
Unfortunately I don't know any location to share these information.
Regards,
Helge
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
_______________________________________________
sigrok-devel mailing list
sigrok-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sigrok-devel
