Am 07.01.2021 um 21:03 schrieb Kevin Grant: > > Ray, > > FYI to extract the bitstream from USB packets I used (Windows, sorry) > Eltima Software USB Analyzer, free 14 day evaluation. > > Run it, select LA2014, start Kingst software. Select all the 4096 size > packets (INs and OUTs, so 90 frames) and select export to bin. This > will give you the bitstream already padded with zeros at the end (to > reach whole number of 4096 packets, plus one packet of 4096 zeros at > the end). File size 184,320 bytes CRC32 == 0x31a1cffe. I suspect there > is also some obfuscation of the bitstream size sent to the FX2 just > prior to the bitstream, so use the size from the control transfer > immediately preceding the 4096 bulk packets (size 0x02b8ba) in line > protocol.c line 126. I'll tidy up my python a bit before posting. >
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
