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 .. On Mon, Jan 30, 2023 at 6:30 PM John D'Ausilio <j...@sort.net> wrote: > 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 <gerhard.sit...@gmx.net> 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 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 wiki page. >> >> The LA1010 model is listed as untested, but ShouldWork(TM) from >> what I understand. It does not have local memory, so cannot >> capture to local memory before downloading sample data to the >> host. Exclusively supports streaming mode which is constrained >> by USB bandwidth. Consider the LA1010 "an LA1016 without RAM". >> >> > I've been working my way through the kingst driver trying to figure >> > out what's going on. I've managed to get libsigrok building >> > from git and I'm using sigrok-cli to test. It looks like it loads the >> > firmware OK, but is having issues talking to the FPGA? >> >> What a coincidence! User Dave Platt just happened to identify and >> address an omission in the firmware extraction utility last week. >> The vendor software holds firmware blobs in the executable in Qt >> resources, which optionally can be compressed, which the tool was >> not aware of. Few images were affected, among them LA1010 >> netlists. The symptom is that sending this netlist to the device >> won't take effect (the FPGA does not recognize its format), hence >> the register set remains unavailable. >> >> I'd suggest you get a sigrok-utils update and re-run the firmware >> extraction utility. Or use an older vendor binary, versions 3.5.x >> were tested, while 3.6.0 was not. >> >> https://sigrok.org/gitaction/sigrok-util.git/ce4722e..249b79d >> https://sigrok.org/bugzilla/show_bug.cgi?id=1825 >> >> Occassionally the vendor assigns previously unseen ID bytes to >> more recent models. But these are easy to add after getting >> identified. >> >> https://sigrok.org/gitaction/libsigrok.git/0db1b18..e7c7aa1 >> >> >> Guess you will tell here when the Kingst LA1010 works for you. So >> that the wiki page can get updated after all models were verified. >> >> >> 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
