Hello Kevin, I will certainly stick around and see what happens with the Kingst LA2016.
I got it just yesterday from Amazon, where it was billed as "Innomaker LA2016." It is housed in a roughly rectangular housing, which slightly tapers between the broad faces. At one end there are twenty test leads emerging from a twenty pin socket. I describe it in this way because there is a complication others on the list might be able to help me with. I am totally blind, and have only limited access to anybody sighted who knows anything at all about electronics. On the broad face of the box there are legends reading: CH0 CH1 CH2 CH3 CH4 CH5 CH6 CH7 GND PWM1 CH8 CH9 CH10 CH11 CH12 CH13 CH14 CH15 GND PWM2 I have managed to read this using an app on my iPhone called SeeingAI that can read short text of this kind. But I am not certain which line of ten connectors is the first 8 channels, plus GND and PWM, and which is the second. If there is a sighted person out there who can confirm for me that would be useful. With the box held with the bigger broad face uppermost and the leads sprouting from the right like the tentacles of a jellyfish, I assume CH0 is the furthest lead and the top one as I face the box. I further assume that PWM2 then must be the bottom row of tentacles and the closest to me. I will be carrying out some tests over the weekend. sigrok-cli represents something wonderful for me as a blind MCU hacker. I don't have to worry about visual stuff like pulseview or KingstVIS, and can dump tests into text files for scrutiny in the cli or further analysis with stuff like Python scripts etc. Here is the patch: --snip-- --- sigrok-fwextract-kingst-la2016 2021-02-19 21:15:17.945430928 +0000 +++ sigrok-fwextract-kingst-la2016x 2021-02-19 21:21:51.970380611 +0000 @@ -192,5 +192,5 @@ res = qt_resources(sys.argv[1]) writer = res_writer(res) - writer.extract("fwfpga/LA2016A", "kingst-la2016a-fpga.bitstream") + writer.extract("fwfpga/LA2016A1", "kingst-la2016a-fpga.bitstream") writer.extract_re(r"fwusb/fw(.*)", r"kingst-la-\1.fw", decoder=maybe_intel_hex_as_blob) --snip-- Keep me posted if I can help further. Mike On 20/02/2021 11:08, Kevin Grant wrote: > On 2021-02-19 21:43, Michael A Ray via sigrok-devel wrote: > >> ... >> There is an error in the extract of fwfpga/LA2016A. >> The Qt resource in version 3.5.0 is: >> fwfpga/LA2016A1 >> Line 196 of the sigrok-fwextract-kingst-la2016 utility leaves off the >> "1" at the end of the resource name. >> Now, to send a patch to the list, do I send it as an attachment, or >> embedded in the email, perhaps between '--snip--' tags? >> The patch is only nine lines in length. >> Mike > > Hi Mike, > > Welcome to the mailing list. There are some problems with the LA2016 > suppport in sigrok so you may find other issues when you try to use it. > A few of us here are working to fix those issues and it would be useful > if you could hang around to help with some testing in the next few weeks > :-) > > Since your patch is very short just post it here on the mailing list, > thanks. I think this might have been fixed already in (as yet) > unreleased code. > > Rgds > > Kevin > > > _______________________________________________ > sigrok-devel mailing list > sigrok-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sigrok-devel > -- Michael A. Ray Analyst/Programmer Witley, Surrey, South-east UK "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- A. de Saint-Exupery https://cromarty.github.io/ http://eyesfreelinux.ninja/ http://www.raspberryvi.org/ _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel