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 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
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: Ope
On Mon, 2023-01-30 at 18:52 -0500, John D'Ausilio wrote:
>
> sr: kingst-la2016: Unexpected run state, want 0x85eX, got 0x00e1.
> sr: kingst-la2016: Cannot write 4 bytes to USB: LIBUSB_ERROR_NO_DEVICE.
> sr: kingst-la2016: Cannot set threshold voltage 1.40V.
> sr: session: Could not start kingst-la2
Attached output and usbmon after unplugging and replugging device
On Mon, Jan 30, 2023 at 6:52 PM John D'Ausilio wrote:
> sr: kingst-la2016: Unexpected run state, want 0x85eX, got 0x00e1.
> sr: kingst-la2016: Cannot write 4 bytes to USB: LIBUSB_ERROR_NO_DEVICE.
> sr: kingst-la2016: Cannot set th
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.bits
sr: kingst-la2016: Unexpected run state, want 0x85eX, got 0x00e1.
sr: kingst-la2016: Cannot write 4 bytes to USB: LIBUSB_ERROR_NO_DEVICE.
sr: kingst-la2016: Cannot set threshold voltage 1.40V.
sr: session: Could not start kingst-la2016 device usb/1-1.2 acquisition.
sr: kingst-la2016: Cannot write 1
thanks Gerhard .. I'll refresh from git and try again this evening, and
will report back with the results
john
On Mon, Jan 30, 2023, 13:25 Gerhard Sittig wrote:
> On Sun, 2023-01-29 at 21:25 -0500, John D'Ausilio wrote:
> >
> > Looking back through the archives, I see that nobody had hardware
On Sun, 2023-01-29 at 21:25 -0500, John D'Ausilio wrote:
>
> Looking back through the archives, I see that nobody had hardware for
> testing LA1010.
I understand that the kingst-la2016 driver is complete and
supports all known models in the series. See the
https://sigrok.org/wiki/Kingst_LA_Series
I've had some input to the Kingst LA1016/LA2016 driver. They use the
same hardware and I reverse engineered the schematic for them, it's on
the sigrok wiki.
Peter - the LA1016 is supported in current builds, you shouldn't need to
build anything yourself, unless you want to.
John - the LA1010
Interesting, I looked into this about a year ago because I have a
kingst la1016 but never got the building environment working. Is it
building easily now for windows or linux?
On Sun, Jan 29, 2023 at 10:26 PM John D'Ausilio wrote:
> Looking back through the archives, I see that nobody had hardwa
Looking back through the archives, I see that nobody had hardware for
testing LA1010.
I have one, which I'd like to see working .. and I'm a retired C
developer with plenty of spare time :)
I've been working my way through the kingst driver trying to figure
out what's going on. I've managed to get
11 matches
Mail list logo
