Another Logic Analyzer Question (this one about drivers) - Page 1
Forum section: electronics / beginners

author: Electro Fan
author_rank: Super Contributor
timestamp: April 10, 2020, 09:49:27 pm
content: As a follow up to my other recent thread on trying to get decode RS232 while working at voltage levels tolerable by a Logic Analyzer I recently acquired a "Saleae Logic16" clone that is spec'd for +/-50V. Supposedly it is on the list of supported Sigrok devices which I presume means it is based on fx2law. Rather than use Saleae's software (out of respect for their IP) I'm using PulseView but I haven't been able to get PulseView to recognize the LA.I'm getting an error message in Sigrok PulseView that says PulseView failed to open device. Generic /unspecified error.I have the WinUSB WCID Driver installed in Zadig.In the control panel device manager I can see that the "Saleae Logic USB Analyzer" is installed and properly working under Universal Serial Bus devices.In PulseView under Connect to Device... the dropdown shows Saleae Logic16, but it continues to give the error message. I have also tried scanning devices using driver above with both USB and Serial Port while looking for both Saleae Logic16 and also fx2lafw, but so far no luck.I've tried a couple USB cables - don't think there is any issue with either cable.Any suggestions on how to fix this? Thx

author: kjr18
author_rank: Regular Contributor
timestamp: April 11, 2020, 08:44:12 am
content: I had some problems with these as well. Turns out that if you connect it through a dell d3100 dock sigrok won't find it. Have you tried different usb port?

author: Gyro
author_rank: Super Contributor
timestamp: April 11, 2020, 09:21:26 am
content: I don't know if it helps, but you need a recent version of libsigrok, see the Firmware section ofhttps://sigrok.org/wiki/Mcupro_Logic16_cloneI would have thought that would be automatically included by now though.You may also need to do a firmware extract from the Saleae Linux binary, or use the open source firmware (reference ), if you scroll down to the 'Firmware' section ofhttps://sigrok.org/wiki/Noname_XL-LOGIC16-100MI think it depends which clone.P.S. If looking at a 'true' RS232 interface, you may want to include series resistors - that +/-50V is more of a 'protection' rating!

author: Electro Fan
author_rank: Super Contributor
timestamp: April 11, 2020, 06:19:55 pm
content: Thanks for the help. I loaded the lastest version of PulseView but still no luck. I might just have to go with resistor approach, but one more question....In using Zadig to load the WinUSB driver it shows a USB ID but not a WCID (it just has a red checkmark). Any chance the system is asking for a new or different set of ID info?Update: After installing the latest PulseView I tried running Zadig again. This time the process took much longer than previously (the other tries indicated the WinUSB update had run successfully); this time I got a running monolog from the author of Zadig… stuff like "So how is your day going?" and "I've actually seen this process take 5 minutes on a Windows Vista machine", etc. So, if nothing else, the new PulseView version seems to be causing Zadig to behave different. Not that it fixed anything, but different....

author: Gyro
author_rank: Super Contributor
timestamp: April 11, 2020, 06:29:55 pm
content: Not sure on that one but this thread, and specifically Comment 25, might be of help...https://sigrok.org/bugzilla/show_bug.cgi?id=650

author: Electro Fan
author_rank: Super Contributor
timestamp: April 11, 2020, 08:34:34 pm
content: Hi Gryo,Thanks for the very relevant thread. I did my best to follow the advice in post 25 - it seemed very promising but it didn't seem to work in my setup. I tried interpreting and following the steps several times. As part of the effort I installed, removed, and reinstalled both Pulseview 32 bit and 64 bit programs. I tried following/interpreting the instructions in the thread various ways with both the 32 and 64 bit versions, but no luck.Pulseview does seem to recognize the device as Saleae Logic16 but it continues to give the "Failed to open device, generic/unspecified error".FWIW here is some more detail:PulseView shows 2 other LAs that I'm using. One is an original USBee SX that it recognizes as "fx2lafw (generic driver for FX2 based LAs) (fx2law), CWAV USBee SX with 8 channels". The other is a clone that it recognizes as "fx2lafw (generic driver for FX2 based LAs) (fx2law), Saleae Logic with 8 channels". Both of these start right up and run with no issues.For some reason while PulseView recognizes the third LA (that is supposedly higher voltage tolerant than the first two) as Saleae Logic16, it won't start up.The first two LAs can be found after selecting "fx2lafw (generic driver for FX2 based LAs) (fx2law)", then selecting USB as the interface, then "Scan(ing) for devices using the driver above".The Saleae Logic16 can be found after selecting "choose the driver" for "Saleae Logic16 (saleae-logic16)", then selecting USB as the interface, then "Scan(ing) for devices using the driver above" which brings up "Saleae Logic16 with 16 channels" - but hitting OK brings up the "Failed to open device, generic/unspecified error". I think it's close, but it's definitely not all the way there. Kinda frustrating

author: Electro Fan
author_rank: Super Contributor
timestamp: April 11, 2020, 11:04:58 pm
content: Ok, going somewhat off topic on my own thread.First, Big Disclaimer here: major rookie here... enthusiastic rookie, but major rookie - so go easy. ThxRecap:In dorking around with trying to get a Logic Analyzer that is voltage tolerant to RS232 I've been trying to use a LA that claims to be spec'd for +/-50V but so far no luck getting it to play nicely with PulseView.When I run a RS232 signal straight out of a PC port it shows a Peak to Peak of 12.4V on my scope. When I try to measure the current with a DMM while decoding on the scope I get about 40uA.So.... I have a second LA that is only spec'd for -0.5V to 5.25V and I figured I'd like to protect that device by adding a series resistor. I found that with a 10MOhm (0.5 Watt) resistor the Peak to Peak drops to 6.4V but the average is about 400mV and the VRMS is about about 2.6V (the scope numbers jump around a bunch). Perhaps now maybe I'm close or within the -0.5V to 5.25V spec for the second LA? This raises the question: is the LA spec referring to Peak to Peak? Maybe/probably - but how much does that really matter vs. say the average or the RMS? Further, maybe the current (and the wattage) also matter? And maybe the duty cycle matters? So if I'm just running at 2400 bps maybe the signal is stressing the LA less than at 4800 bps which would be less than a 9600 bps? Or is it really just the voltage that matters?According to my DMM, where I show a 40uA current draw when running at 2400 bps, when the text file from the PC to the scope is completed the idle current increases to about 300uA.Getting bold (or fatigued with the process), I took the 10MOhm resistor out of the path and ran the LA with no resistor at 2400 bps and the LA with PulseView ran fine - so maybe it isn't just a concern about Peak to Peak Voltage but current, which is somewhat dependent on duty cycle? Or maybe I was a few seconds or minutes away from overheating/burning out the circuit in the LA?Thoughts/Help? Thx!!

author: Gyro
author_rank: Super Contributor
timestamp: April 12, 2020, 11:14:42 am
content: Sorry to hear that you're still having issues with the '16' and Pulseview - I think I remember there being at least one Sigrok guy around here, so all is not lost yet.Well done for being cautious with the inputs. Assuming that your other analyser is one of the cheapie 8 bit ones, the inputs go through a few hundred ohms with maybe a high value pullup resistor and then straight into a 74HC buffer.You're right that current is the important thing. 10M is a bit too cautious in terms of getting decent edges into the LA - probably more of an issue at higher baud rates. The ESD protection diodes (clamping to the supply rails) on 74HC are good for about 5mA max, so as long as you keep the maximum current below about 1mA you'll be fine. It's a bit arbitrary, but I'd go for something in the vicinity of 22k (say 15k - 47k) which will give you good clean LA transitions without over-stressing the input protection.

author: Electro Fan
author_rank: Super Contributor
timestamp: April 12, 2020, 08:12:10 pm
content: Gyro, thanks for the resistor value info and the encouragement.I think I saw the impact of the 10M resistor in the not so clean waveform edges on the scope.I'm hoping the Sigrok guy shows up with some good ideas about how to get PulseView to fully recognize the LAIn the meantime I've been looking around in the Control Panel / Device Manager. I think the 16 channel high voltage tolerant clone is showing up in the Universal Serial Bus controllers section -either as a greyed out Saleae Logic16 USB Logic Analyzer or maybe also as "Unknown USB Device (Device Descriptor Request Failed). I saw somewhere that there might have been some users with issues about IDs, either USB ID or maybe WCID. Just a guess / straw grasp....EF

author: Renate
author_rank: Super Contributor
timestamp: April 12, 2020, 10:09:07 pm
content: The thing with FX2 things is that they userenumeration.That means that they boot up with a USB VID/PID from the ROM or an external EEPROM.On my FX2LP that is 04b4/8613, the stock Cypress value.That incarnation needs the WinUSB driver installed (with Zadig or otherwise).After you upload the firmware to the FX2 and issue a reboot, it does.It comes back with whatever USB VID/PID is inside the firmware that you uploaded.That incarnation needs the WinUSB driver installed (as a second installation).Sigrok is doing something a bit screwy.They keep the same VID/PID, but they add a "serial number" of "Cypress FX2".This could confuse Windows, I'm not sure.So, from a cold boot, plug in your LA, find it in Device Manager (devmgmt.msc)Find the LA in Device Manager, what's the "Device instance path"?Try to run PulseView.Find the LA in Device Manager, what's the "Device instance path" now?If it changed from USB\VID_04B4&PID_8613\6&21C9C6&0&2 (<- arbitrary gooble-dee-gook)to USB\VID_04B4&PID_8613\CYPRESS_FX2 then we know that the firmware upload worked at least.Now see if it has a driver.(My experience comes from writing software for the Hantek 6052BE which uses an FX2LP but uses different VID/PID for bootloader vs. oscope.)

author: Renate
author_rank: Super Contributor
timestamp: April 12, 2020, 10:24:18 pm
content: Err, two more things:"Device Descriptor Request Failed" often means a bad USB connection (since that's the first request).Try connecting as directly as possible (no external hubs) to the PC using a different cable.Check the USB voltage, it should certainly be over 4.8VWCID is Microsoft gobble-dee-gook to tag a device as needing the WinUSB driver without any user intervention.(I mean, why the heck do we need OS-specific descriptors on an agnostic USB device?)My LA (after firmware download) doesn't have it either.

author: Electro Fan
author_rank: Super Contributor
timestamp: April 12, 2020, 11:00:55 pm
content: Hi Ranate,Thanks for all the good info and help.I have been bit by a USB port or cable not working properly in the past but I'm pretty sure I'm good with both of those items now.I've made a little progress - might just be an adjustment or two away.I can now get the LA to show up as expected in Device Manager under Universal Serial Bus devices as a Saleae Logic16 USB Logic Analyzer. Under properties the General tab says This device is working properly. The driver provider is libwdi, Feb 10 2017. The Digital Signer says: USB/VID_21A9&PID_1001 (libwdi autogenerated)Under the Events tab everything looks good except one line that says "Device not migrated", and then below it says Device USB\VID_21A9&PID_1001\7&1bf188e&0&2 requires further installation.Then it says:Device USB\VID_21A9&PID_1001\7&1bf188e&0&2 was not migrated due to partial or ambiguous match.Last Device Instance Id: USB\VID_1DF7&PID_2500\6&308d2105&0&4Class Guid: {88bae032-5a81-49f0-bc3d-a4ff138216d6}Location Path:Migration Rank: 0xF000FFFF0000F102Present: falseStatus: 0xC0000719This is all time stamped and as we continue on it gets somewhat more promising.Next (later in time by a few minutes) it says Device configured, Device started, Device installedI think what you were trying to explain in the post about the VID and PID might be the issue but I can't quite get it sorted.I think it's now installed, but maybe not migrated. Any thoughts on how to deal with "Device not migrated"

author: Renate
author_rank: Super Contributor
timestamp: April 13, 2020, 02:16:03 am
content: You didn't answer my question:Is before running PulseView and after the exact same Device instance path?Does Windows go "bong" (USB disconnect) when you run PulseView?Did you try using Zadig again?

author: Electro Fan
author_rank: Super Contributor
timestamp: April 13, 2020, 04:08:09 am
content: Quote from: Renate on April 13, 2020, 02:16:03 amThxSome more...I have 3 other LAs: Intronix LogicPort, USBeeSX, a 8 channel clone, plus the 16 channel clone. The first three all show a manufacturer's name on the Device Manager/Properties/General tab. The 16 channel clone says Undefined Vendor. I think this along with some VID and PID confusion is near the source of the problem. Thx again- sorry for not being more precise about the path info; if you wouldn't mind trying to direct me on where/how to determine the specific path info you are looking for I'll give it another go. Thx- further update: I was one layer off on the Device instance path but now I know exactly where you wanted me to look. Nothing in that path seems to change no matter how many times I replug the device or relaunch PulseView. Not sure if that's what you were looking to determine but at least I know where to find the Device instance path with certainty. Thx- another update: I used Zadig to reinstall WinUSB again - it was successful according to Zadig but still no luck- please talk me through the preferred step by step process for this:After you upload the firmware to the FX2 and issue a reboot, it does.It comes back with whatever USB VID/PID is inside the firmware that you uploaded.I'd like to precisely revisit the process of uploading the firmware to the FX2. Thx again.

author: Renate
author_rank: Super Contributor
timestamp: April 13, 2020, 01:34:54 pm
content: Try using the (old, but still trusty) USBView.exehttps://www.ftdichip.com/Support/Utilities.htm#MicrosoftUSBViewFrom a fresh plug-in, copy/paste the block like below:Code:Device Descriptor:bcdUSB: 0x0200bDeviceClass: 0xFFbDeviceSubClass: 0xFFbDeviceProtocol: 0xFFbMaxPacketSize0: 0x40 (64)idVendor: 0x04B4 (Cypress Semiconductor)idProduct: 0x8613bcdDevice: 0xA001iManufacturer: 0x00iProduct: 0x00iSerialNumber: 0x00bNumConfigurations: 0x01Then try after running PulseView.It doesn't sound like it's "bonging" so, it can't be uploading the firmware correctly.Check the device descriptor afterwards.If you are still getting "Device Descriptor Request Failed" or the printout under USBView for that device is very short,then you have some sort of hardware USB problem, even if your cables are gold plated.If you want to try some software USB protocol analyzer, that might help.I've never had much luck with them, I prefer my Beagle 480 hardware analyzer.This might boil down to some PulseView issue.

author: Electro Fan
author_rank: Super Contributor
timestamp: April 13, 2020, 09:57:05 pm
content: Hi Renate,Thanks again for your very generous time and efforts. I looked at the code and link you provided - I'm sure you are more capable than me with this stuff and I think you might also be at least a tad or two more courageous than me with driver exploits. I've found that sometimes in an effort to fix something I can break something elseEven though the Device status in the General tab saysThis device is working properly, it's possible that the migration message in the Events tab is saying something needs fixing:Device USB\VID_21A9&PID_1001\7&1bf188e&0&2 was not migrated due to partial or ambiguous match.Last Device Instance Id: USB\VID_0403&PID_6001\5&15c311e1&0&1Class Guid: {36fc9e60-c465-11cf-8056-444553540000}Location Path:Migration Rank: 0xF000FFFF0000F122Present: falseStatus: 0xC0000719If I had to guess, those VID and PID values should be better aligned (ie, they should be the same) but I've worn down on deleting rebooting, reinstalling, washing, rinsing, drying, repeating, etc.It's very likely that it's something beyond my skillset to resolve. (I'm also thinking that there is at least a small chance that despite what the LA seller says/thinks maybe this LA will work with Saleae software but not PulseView.)In any event, thanks again for all the kind help. If I somehow get the this LA working with PulseView I'll report back.Very Best Regards, EF

author: abraxa
author_rank: Frequent Contributor
timestamp: April 13, 2020, 11:13:55 pm
content: QuoteIf you open the settings menu, you'll find an entry named "Logging". Setting the log level to 5, closing it, trying to connect to your device and then going back to the log will give more of a clue. Feel free to paste the text here and I'll have a look. My guess would be that you're missing the firmware files needed to program the LA hardware:https://sigrok.org/wiki/Saleae_Logic16#Firmware

author: Electro Fan
author_rank: Super Contributor
timestamp: April 14, 2020, 02:04:01 am
content: Quote from: abraxa on April 13, 2020, 11:13:55 pmThanks abraxaSyntaxError: Failed to load decoder signature: import by name failed: invalid syntax (pd.py, line 138)srd: Traceback (most recent call last):srd: File "C:\Program Files\Sigrok\PulseView\share\libsigrokdecode\decoders\signature\__init__.py", line 25, insrd: from .pd import Decodersrd: File "C:\Program Files\Sigrok\PulseView\share\libsigrokdecode\decoders\signature\pd.py", line 138srd: incoming = (bin(shiftreg & 0b0000_0010_1001_0001).count('1') + data) & 1srd: ^SyntaxError: invalid syntaxSyntaxError: Failed to load decoder signature: import by name failed: invalid syntax (pd.py, line 138)srd: Traceback (most recent call last):srd: File "C:\Program Files\Sigrok\PulseView\share\libsigrokdecode\decoders\signature\__init__.py", line 25, insrd: from .pd import Decodersrd: File "C:\Program Files\Sigrok\PulseView\share\libsigrokdecode\decoders\signature\pd.py", line 138srd: incoming = (bin(shiftreg & 0b0000_0010_1001_0001).count('1') + data) & 1srd: ^SyntaxError: invalid syntaxsr: ftdi-la: Failed to get the FTDI strings: -4sr: resource: Failed to open resource 'saleae-logic16-fx2.fw' (use loglevel 5/spew for details).sr: saleae-logic16: Firmware upload failed, name saleae-logic16-fx2.fw.saleae-logic16: Failed to open device: LIBUSB_ERROR_ACCESS.sr: saleae-logic16: Unable to open device.Notifying user of session error: "generic/unspecified error"sr: log: libsigrok loglevel set to 4.srd: libsigrokdecode loglevel set to 4.sr: log: libsigrok loglevel set to 5.srd: libsigrokdecode loglevel set to 5.Update 2: abraxa, this is getting exciting.... and maybe a little closer.....I just looked in the Sigrok/PulseView/share/sigrok-firmware folder and among other things I see:fx2lafw-sigrok-fx2-16ch.fwSo maybe when I plug the LA it should look in there and see what it needs? Unfortunately the LA doesn't find/see the firmware file, but I'm starting to slightly better understand what's what... at least I know where the firmware files are hiding now. I'm thinking something is confusing a USB look-up somewhere, maybe it's a USB driver issue more than the firmware... if the USB driver knew what it's supposed to be doing it would talk to the OS and find the firmware. Just a SWAG.Thinking further.... when I plug the LA and tell PulseView to Choose the driver and specify Saleae Logic16 and scan for it it shows Saleae Logic16 with 16 channels - it just doesn't connect. Another example/data point: my USBSX LA does find the firmware file in the same directory - a file called fx2lafw-cwav-usbeesx.fw, and it does connect and run fine in PulseView. Also, I have a no-name 8 channel LA and PulseView finds it when I select fx2lafw - after a scan it finds "Saleae Logic with 8 channels", which I'm guessing might be a firmware file called fx2lafw-sigrok-fx2-8ch.fw So, it would seem that the the USB / Com port connector apparatus is kinda working, just not for my (hopefully) high voltage tolerant 16 channel LA. Maybe a dll or inf file missing or goofed up somewhere? Hard to figure....Thx!

author: abraxa
author_rank: Frequent Contributor
timestamp: April 14, 2020, 06:47:53 am
content: QuoteSo far we only know that libsigrok was able to find/identify the device and attempted to upload the firmware, and failed. So USB issues are not relevant at this point and I suggest you grab a log of the driver trying to connect with log level set to 5. In the log above, that wasn't the case as the log level was set to 5 only after the attempt was already made. If you either restart PV or manually scan for your device, you'll see log level 5 in effect.Your assumptions regarding the other firmware files is correct - if your other LA can be used, the firmware path is correct as the other firmware files would be loaded then.

author: Electro Fan
author_rank: Super Contributor
timestamp: April 14, 2020, 08:11:11 pm
content: Hi abraxa,I might be making some progress as I learn to use the log with level5. I have found this:sr: resource: Attempt to open 'C:\Program Files\Sigrok\PulseView\share\sigrok-firmware\saleae-logic16-fx2.fw' failed: No such file or directoryNotifying user of session error: "generic/unspecified error"There is such a directory path to the firmware files but the firmware it is looking for seems to be saleae-logic16-fx2.fw which is not in the sigrok-firmware folder. What is in the folder at the end of that directory path is a file named fx2lafw-sigrok-fx2-16ch.fwIf this is the only problem (I'm not sure if there might be others), there would seem to be a two possibilities: 1) I need to figure out how to tell the process (PulseView? or whatever manages the process) to look for fx2lafw-sigrok-fx2-16ch.fw instead of saleae-logic16-fx2.fw or 2) I need to figure out how to find and install a copy of saleae-logic16-fx2.fw in the sigrok-firmware folder.Thoughts? Thx!

author: abraxa
author_rank: Frequent Contributor
timestamp: April 14, 2020, 10:12:19 pm
content: fx2lafw-sigrok-fx2-16ch.fw won't work as that's for a completely different device, what you need to do is obtain the 3 firmware files by downloading a specific (!) version of Saleae Logic and extract the necessary firmware files from there, seehttps://sigrok.org/wiki/Saleae_Logic16#FirmwareThe sigrok project has no permission to distribute these files, which is why owners of these devices unfortunately have to jump through this hoop to make them work.

author: Electro Fan
author_rank: Super Contributor
timestamp: April 14, 2020, 11:59:20 pm
content: abraxa, thanks again.Ok, looks like at the end of the day it appears there is no real/full opensource software for making PulseView play with the 16 channel LA that I have (apparently it would require Saleae firmware to work with PulseView software).So, next up to bat is a new "high voltage tolerant" LA. One that looks pretty nice is the DSLogic Plus and it has some pretty good looking software that comes with the LA - apparently the software is a descendant of PulseView. But as good as the DSLogic software appears, I'd really like to stick with PulseView (although having the option to use DreamSource's software is not bad).I'd like to avoid a misfire on another LA. Any chance anyone can confirm that Sikgrok PulseView - without any software, firmware, etc. from DreamSource - will really work with the DSLogic analyzer? (Or is this just a path toward Round 2 of the same basic issue - that I got myself into - that started this thread?)Thanks very much for any help with this.

author: abraxa
author_rank: Frequent Contributor
timestamp: April 15, 2020, 07:34:17 am
content: Quote from: Electro Fan on April 14, 2020, 11:59:20 pmSure, but you already bought it, right? So once you have the firmware you're good to go. If I was in your place, this is what I'd do.Quote from: Electro Fan on April 14, 2020, 11:59:20 pmI have my own personal opinion about DSLogic as the people behind it do not play nice in the open source world because they lie, take what they can get and try to prevent others from taking from them. From a moral point of view, I would never recommend them. From a practical point of view, it's a decent LA and affordable for many, so I understand why people would buy them. They should be aware that the sigrok projects benefits from this in no way, though.Quote from: Electro Fan on April 14, 2020, 11:59:20 pmThe stance of the sigrok project is that we do not actively work on any part related to the DSLogic on our own time because we're not willing to kiss the hand that keeps slapping us across the face. However, we also don't reject efforts by the community, which is why sigrok has DSLogic support for certain models. So if you buy one, you may be able to use it with sigrok. However, their firmware is not open source if that matters to you, and you will not receive much support from the sigrok devs, if any - meaning that if you buy a U2 model, you're out of luck:https://sigrok.org/bugzilla/show_bug.cgi?id=1516Finding a high-speed true open source LA is tricky at this point and I'm not aware of any commercial efforts. With that, I'm afraid you'll have to settle.

author: Electro Fan
author_rank: Super Contributor
timestamp: April 15, 2020, 08:22:05 pm
content: Quote from: abraxa on April 15, 2020, 07:34:17 amabraxa, Roger all that.I'm a big fan of Sikgrok PulseView and I appreciate all the time and energy put in by you and all the people who have been contributing to and supporting the effort.I'm good with opensource and I also don't mind buying software and hardware - it's a way to keep society and the economy goingAs a both a regular person in the economy and as a person who has worked in IT I definitely support the concept of Intellectual Property. Based on my experience I'm generally inclined to go with the pay-for option for most things (you get what you pay for sometimes but not always) and I also cautiously try opensource (sometimes free is great but sometimes it comes with other costs - like extra time and effort). In the case of PulseView it's a no brainer - it's great product with a great community of developers and users behind it.At the end of the day, I'm not starting an electro-politico campaign to advocate or dis any particular product. I'm just trying to learn and do a few projects with some good tools. Sometimes things go smoothly, other times it's a bigger learning process than I anticipate. In any event, being able to learn from and share the experience with the many great EEVers here is a fantastic part of the overall experience.Thanks again for your help. I appreciate it. EFPS, watch for more threads on PulseView and LAs.... I'm still on the mission to find a way get a good "high voltage tolerant (RS232)" LA working, hopefully with PulseView

author: cb900
author_rank: Newbie
timestamp: October 05, 2021, 09:44:54 am
content: HiIn case someone is having problems with non detection here's how I fix it on mine.My biggest problem with Pulseview and my generic (Cypress Logic analyser) is if I use the SLEEP option to shut down windows! Then the 99% of the time it loses the LA (fx2lafw) after waking up. It will never find the LA and will never connect - No matter how many times you connect/disconnect device, reinstall WinUSB drivers etc.I'm lazy and have multiple windows of 'stuff' open and don't want to restart the PC so I can't comment on this route.The fix (for me) is to disconnected any development boards I am using which (I think) are on the same USB hub. I have USB mouse & keyboard plugged in the back and the LA, Xplained, Arduino and a memory stick plugged in the front. The keyboard and mouse I can leave in.When all the devices are unplugged connect the LA. Wait a sec and for a quick check, look in Device Manager you should see the fx2lafw listed under 'Universal Serial Bus Devices. AND no yellow explanation mark in USB controllers above it.That's it you're good to go - connect everything back up - run Pulseview whatever it doesn't matter it will work.However, just bare in mind that I was using a previously working setup that stopped working. Iwouldsuggest disconnecting all relevant USB device when doing an install anyway just in case if new install.As a gross generalisation, it does seem connection or identifying can be 'iffy' when playing with other devices when coming late to the party. Once working and connected it is fine. Unplugging device when Pulseview is running can also bring problems with subsequent connections.Hope this can be of help.

author: Renate
author_rank: Super Contributor
timestamp: October 05, 2021, 11:01:42 am
content: I just reinstalled the latest PulseView. With/without my FX2LP plugged in it crashes on startup.I had had a problem with the Intel Bluetooth adapter on my motherboard and had just updated the AMD drivers for my Asus X570. That includes the Aura LED controller. (Actually, I may have never used PulseView on this iteration of my PC?)In any case, the Aura USB hardware has two USB interfaces, Interface #0 & Interface #2!Interface numbers must be consecutive. This breaks some USB enumeration libraries. The fix is to manually select your interface:Code:C:\>pulseview.exe -D

author: willPowell
author_rank: Contributor
timestamp: April 29, 2022, 08:43:27 am
content: I had the same problem also. This was incredibly frustrating and spent far too much time debugging.Instead of pulseview I installed Salae Logic and it worked flawlessly -https://www.saleae.com/downloads/Hope this helps someone.

author: Iceage
author_rank: Newbie
timestamp: September 30, 2022, 04:00:16 pm
content: In case somebody else comes across this same issue on Windows 10 (as I did) please find a link below for useful instructions on how to get the clone Logic 16 working with Sigrok. I though it best to share on this thread as my searches for answers to the issue lead me hereHope you find it useful.https://github.com/anno73/Saleae-Logic16-Clone/wikiBest wishes.