Hello, I'm using PuleView on ArchLinux. It's compiled from source code using AUR system, the package version is 0.5.0-git-9a0e130 (previously I've tested binary package version 0.4.0-3 and the behavior is the same so I've decided to upgrade to the latest one). BusPirate v4 has a firmware version v6.3-r2151. Since it's listed as an officially supported device I've decided to test it and discovered that it doesn't work with PulseView at all. First of all PulseView is not always capable to find the device during "Step 3. Scan for devices using driver above". I choose "ols" driver on step 1 and select a serial port that corresponds to BusPirate on step 2. When I press "Scan for devices using driver above" sometimes PulseView find no devices, sometimes it finds a device with an empty name and sometimes it finds "PBv4" as expected. It been my observation that usually search succeed if you <!> double click </!> the button. Successful search - https://afiskon.ru/s/17/667625ca28_temp.png Empty name bug - https://afiskon.ru/s/13/5b9bc9fe7c_temp.png BTW knowing that BusPirate has only 5 channels "BPv4 with 8 channels" looks like another bug. Afterwards if I press "Run" sometimes PulseView hangs with no obvious error until I unplug BusPirate. Afterwards the program displays the following error: https://afiskon.ru/s/a2/35499de41d_temp.png Another behavior - PulseView displays some data immediately, but the data is garbage (always the same BTW): https://afiskon.ru/s/1f/c970662598_temp.png Here for instance I know for sure CS and CLK don't change. I'm pretty confident that the problem is not with BusPirate since if I use it over UART in screen everything works just fine. Scripts like spi-sniffer work well too.
HydraBus uses OLS protocol as well and is broken too https://github.com/hydrabus/hydrafw/issues/82
> HydraBus uses OLS protocol as well and is broken too Sorry, I was wrong. Unlike Bus Pirate, HydraBus works fine with Sigrok and PulseView. You can find all the details here: https://github.com/hydrabus/hydrafw/issues/82
Removed HydraBus from the title since it was reported to work.
I can confirm that the BusPirate v4 which I checked briefly for an hour had some of the issues as well: * scanning only worked every second time * measured data was gibberish Things which were different for me: * It said "BPv4 with 5 channels" * capturing never crashed For the latter two, I could imagine a firmware update is the reason. I sadly didn't check the BPv4 firmware version on that device. My gut feeling is that the scanning problem is also a firmware problem. Definately needs more research