Right .. I plan on running it on a windows box and grab wireshark of the USB.
On Tue, Jan 31, 2023, 13:53 Gerhard Sittig <gerhard.sit...@gmx.net> wrote: > On Mon, 2023-01-30 at 18:52 -0500, John D'Ausilio wrote: > > > > Well, there's good news and bad news ;) > > > > The bitstream upload is successful, but the run state is bad : > > sr: [00:00.050178] kingst-la2016: Uploading FPGA bitstream > > 'kingst-la1010a2-fpga.bitstream'. > > sr: [00:00.050382] resource: Opened > > '/home/john/.local/share/sigrok-firmware/kingst-la1010a2-fpga.bitstream'. > > sr: [00:01.235831] kingst-la2016: FPGA bitstream upload (343172 bytes) > done. > > sr: [00:01.308258] kingst-la2016: Run state: 0x00e1 (idle). > > sr: [00:01.309024] kingst-la2016: Unexpected run state, want 0x85eX, got > > 0x00e1. > > sr: [00:01.309852] kingst-la2016: Device should be initialized. > > sr: [00:01.310694] hwdriver: Scan found 1 devices (kingst-la2016). > > The following devices were found: > > sr: [00:01.311777] hwdriver: sr_config_get(): key 20000 (conn) sdi > > 0x5560019180 cg NULL -> '1.11' > > kingst-la2016:conn=1.11 - Kingst LA1010 with 18 channels: CH0 CH1 CH2 CH3 > > CH4 CH5 CH6 CH7 CH8 CH9 CH10 CH11 CH12 CH13 CH14 CH15 PWM1 PWM2 > > sr: [00:01.312619] hwdriver: Cleaning up all drivers. > > > > It does plow past the error and brings up a reasonable looking display in > > pulseview, but has problems starting acquisition .. > > The above log looks good to me. There is just the unexpected run > state, but that's not fatal, just a warning. The check for those > bits is an arbitrary choice anyway, could not tell how certain > that expectation even is, or whether the first supported devices > just happened to always come up with this bit pattern, while none > of it is essential. Check the git history if you are interested > in the evolution of that driver and the set of supported devices. > > The above log stops after the detection, does not include the > start of an acquisition. The other log in the other message says > "no device" when trying to configure an acquisition. Which could > have a different cause than speaking the wrong protocol (like > cable/connection issue, device unplugged, power outage, etc). So > that needs verification (re-execution after cable and port > checks, checks for power drops, etc). > > > virtually yours > Gerhard Sittig > -- > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. > > > _______________________________________________ > 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
