I wanted to know which logic analyzer would actually show up in PulseView on a stock Linux box. The shopping lists I kept finding treat “works with sigrok” as a yes or no. It isn’t. The PulseView in Ubuntu’s archive is version 0.4.2 from 2020, and it can’t see several analyzers people recommend for it, including the Raspberry Pi Pico. A $13 clone needs nothing beyond the distro packages, while a $299 DSLogic needs DreamSourceLab’s own app, and the price tag tells you neither.
So this guide sorts the best logic analyzers for Linux by the software you’ll end up running: PulseView from the distro, the PulseView nightly, DSView or Saleae’s Logic 2. It covers the 24 MHz fx2lafw clones, the DSLogic Plus and U3Pro16, the Saleae Logic 8 and the Pico as a $5 analyzer, each with its sigrok driver name. I checked every driver claim in November 2026 on an Ubuntu 24.04 LTS VM called box1, against both the archive’s sigrok packages and the PulseView nightly AppImage, and the archive and nightly driver lists below come from that box.
Picking by the software you’ll open every day
Decide on the application first and the sample rate second. You will spend hours in the software and only seconds thinking about the hardware, and a fast analyzer that only one app understands locks you into that app for good:
- Best overall: DreamSourceLab DSLogic Plus (around $149): 16 channels, 400 MHz on 4, adjustable threshold, DSView on Linux and PulseView on older revisions
- Best under $20: HiLetgo 24 MHz 8-channel analyzer (around $13): fx2lafw clone, works in the distro PulseView
- Best DIY: Raspberry Pi Pico 2, pre-soldered (around $13): sigrok-pico firmware, 21 digital channels, nightly PulseView only
- Best for speed: DSLogic U3Pro16 (around $299): USB 3.0, 1 GHz on 8 channels, DSView only
- Best without sigrok: Saleae Logic 8 (around $499): analog on every channel, Logic 2 AppImage for Linux
Prices are what Amazon listed on 1 November 2026, so check the live price before you buy. If you’re new to this and debugging an Arduino or ESP32, buy the HiLetgo and stop there until 24 MHz feels slow. If you already know you’ll chase SPI at tens of megahertz, the DSLogic Plus is the one I’d put on my own bench, and the Saleae only makes sense when you want analog traces next to the digital ones.
Checking the drivers without owning the hardware
I do not own all five analyzers, so I didn’t capture anything with them and I will not pretend otherwise. What I could check for real is the Linux side: which driver each one needs, and whether the PulseView you’re likely to install has that driver at all. I cloned an Ubuntu 24.04.4 LTS VM, installed sigrok-cli and sigrok-firmware-fx2lafw from the archive, listed the drivers, then unpacked both sigrok nightly AppImages and read their libraries. What came back:
- Archive build: libsigrok 0.5.2, sigrok-cli 0.7.2, firmware package 0.1.7
- Missing from the archive build:
raspberrypi-picoandkingst-la2016 - DSLogic firmware: not packaged, the firmware package holds fx2lafw files only
- sigrok-cli nightly AppImage: still libsigrok 0.5.2, same driver list, no Pico
- Current PulseView nightly AppImage (its libsigrok built November 2025): both missing drivers present
Ubuntu’s own packages come first. Four drivers for the analyzers in this guide show up (fx2lafw, dreamsourcelab-dslogic, saleae-logic16 and saleae-logic-pro, next to a Hantek scope driver and the IPDBG FPGA core), and the firmware package installs thirteen fx2lafw images with nothing for DreamSourceLab:

My grep asked for kingst and pico too, and neither matched. Next I tried the sigrok-cli nightly AppImage, expecting the nightly command-line tool to carry the same library as the nightly GUI. It doesn’t:

That surprised me, because it means you can’t drive a Pico from sigrok-cli even with the nightly AppImage, so scripted captures are out for it. Which build does carry the driver, then? The PulseView nightly. Its AppImage won’t start a GUI on a headless VM, so I extracted it and searched the bundled library for each driver name and its version string:

Both raspberrypi-pico and kingst-la2016 are in there, in libsigrok 0.6.0-git-883c2ac. The last libsigrok release is 0.5.2 from December 2019, and Ubuntu 26.04 still packages that same version. For the specs, I read each maker’s product page and the device’s page on the sigrok supported hardware list, and took prices and stock from Amazon’s catalog API on the day I wrote this.
Comparing the five analyzers
Read the “Linux software” column before the sample rate column. One of the five is sure to run in the PulseView your distro ships, one more does only on older hardware revisions, one needs the nightly, and two never touch sigrok at all:
| Analyzer | Channels | Top sample rate | Memory | Input threshold | Linux software | sigrok driver |
|---|---|---|---|---|---|---|
| HiLetgo 24 MHz clone | 8 | 24 MHz | None, streams over USB 2.0 | Fixed, 0.8 V low / 2.0 V high | PulseView (distro) | fx2lafw |
| Raspberry Pi Pico 2 | 21 digital + 3 analog | 120 MHz on 1 to 4 channels | Up to 400K samples | 3.3 V GPIO | PulseView nightly | raspberrypi-pico |
| DSLogic Plus | 16 | 400 MHz on 4 channels | 256 Mbit | Adjustable 0 to 5 V | DSView (PulseView on older revisions only) | dreamsourcelab-dslogic |
| DSLogic U3Pro16 | 16 | 1 GHz on 8 channels | 2 Gbit | Adjustable 0 to 5 V | DSView | None (planned) |
| Saleae Logic 8 | 8, each digital or analog | 100 MS/s digital | Streams to the PC | Set in Logic 2 | Logic 2 | None (planned) |
Memory matters more than its column suggests. An analyzer with no onboard memory, like the fx2lafw clones, pushes every sample over USB as it’s taken, so a busy hub or a slow laptop drops the capture at high rates. The DSLogic boards fill their own buffer first and then upload, which is why they hold 400 MHz and 1 GHz where a streaming device can’t. Saleae streams too, but over a link and driver built for it.
1. DreamSourceLab DSLogic Plus: best overall
I’d buy the DSLogic Plus for a Linux bench, because it pairs a fast buffer and an adjustable threshold with a vendor app that runs on Linux, and older units also open in sigrok’s release driver.
DreamSourceLab rates it at 400 MHz on 4 channels, 200 MHz on 8 and 100 MHz on all 16 in buffer mode, backed by 256 Mbit of memory. In stream mode it drops to between 100 MHz on 3 channels and 20 MHz on 16, which is still close to the clones’ 24 MHz with twice the channels. The input threshold is adjustable from 0 to 5 V in 0.1 V steps, inputs work from -0.9 to 6 V, and the supplied fly wires protect them to ±30 V. That threshold control is what you need for 1.8 V logic, which a fixed-threshold clone reads badly.
In PulseView it uses the dreamsourcelab-dslogic driver, but my Ubuntu VM had no DSLogic firmware installed, because the archive does not package it. sigrok’s DSLogic page points you to sigrok-fwextract-dreamsourcelab-dslogic to fetch the firmware and FPGA bitstreams first. There’s a second catch. The same page lists newer hardware revisions (USB IDs 2a0e:0030 and 2a0e:0034) as not supported. The listing does not say which revision a new unit is, so I’d treat DSView (v1.3.2, with Linux builds) as the guaranteed path and PulseView as the bonus.
Don’t buy it if all your buses run at 5 V and under a few megahertz, since the HiLetgo does that job for a tenth of the price. The DSLogic Plus on Amazon (around $149) showed only six left, and DreamSourceLab’s own shop had it at $149 on 1 November, down from $199.
2. HiLetgo 24 MHz 8-channel analyzer: best under $20
Everyone starts with this “Saleae clone”, and on Linux it is the least fuss of anything here. It works in the PulseView from your package manager with no firmware hunting.
Inside is a Cypress CY7C68013A (FX2) microcontroller, and libsigrok uploads the open fx2lafw firmware to it each time you plug it in. That firmware comes from the sigrok-firmware-fx2lafw package, and on my VM it installed fx2lafw-saleae-logic.fw along with a dozen other variants. You get 8 channels at up to 24 MHz, no onboard memory and only software triggers, so a long capture at full rate depends on how quiet your USB bus is.
Voltage is where people break these. sigrok’s page for the no-name clones gives an absolute maximum of -0.5 to 5.25 V with fixed thresholds of 0.8 V low and 2.0 V high. On paper that covers 2.5 V, 3.3 V and 5 V logic and nothing higher. Clip it onto a 12 V line or an RS-232 port and it is dead. HiLetgo doesn’t name the chip on this listing, so its support is by class, the same way our USB serial console cable guide treats unnamed FTDI clones.
Stock was thin when I priced it. The HiLetgo analyzer on Amazon (around $13) was down to 13 units. If it sells out, the Comidox 24 MHz analyzer (around $13) is the same class of board and was in stock.
3. Raspberry Pi Pico 2 with sigrok-pico: best DIY analyzer
A Pico costs less than the clone and has more channels, so why isn’t it the default budget pick? Because the PulseView you install with apt cannot talk to it.
The sigrok-pico project turns a Pico or Pico 2 into a 21-channel digital plus 3-channel analog analyzer. It reaches 120 MHz on 1 to 4 channels with at most 400K samples, and its guide recommends staying at 60 MHz or below once you use 8 or more channels. You flash a UF2 file built for your board, then pick the raspberrypi-pico driver in PulseView. The README says plainly that PulseView 0.4.2 and sigrok-cli 0.7.2 don’t support it, and my VM agreed: the driver was only in the PulseView nightly AppImage.
The Pico’s pins are 3.3 V logic, so put a divider or level shifter in front of anything 5 V. If you’d rather skip sigrok entirely, gusmanb’s LogicAnalyzer firmware gives the same board 24 channels at 100 MHz with its own Linux app, and release 6.0 added Pico 2 support and sigrok’s protocol decoders. A spare Pico from a Raspberry Pi build is a fine place to start.
Don’t pick it if you want a tool that runs straight from apt. Raspberry Pi lists the bare Pico 2 from $5, and the pre-soldered Pico 2 on Amazon (around $13) saves soldering 40 pins before the first probe goes on.
4. DSLogic U3Pro16: best for raw speed
Nothing under $400 I found beats the U3Pro16 for speed, and it is also the one where reading sigrok’s model table before buying saves you a surprise.
On paper it runs 1 GHz on 8 channels and 500 MHz on all 16 in buffer mode, with 2 Gbit of memory and a 2 ns minimum pulse width. Over USB 3.0 it can stream at 125 MHz on 16 channels, about six times what the Plus streams on 16. The input side matches the Plus, with a 0 to 5 V adjustable threshold and a -0.9 to 6 V working range. As a spec sheet, it is the obvious upgrade.
sigrok marks it “planned”, and the driver’s model table says no, so PulseView won’t open it on any build. That leaves DSView, DreamSourceLab’s own app, which is built on the sigrok code. DSView is fine, but its download page lists v1.3.2 from April 2024 while GitHub’s Releases page still shows v1.3.0, which tells you how often it moves. The 32-channel U3Pro32 (around $399) is in the same position.
If sigrok-cli scripting is part of your workflow, look elsewhere. The U3Pro16 on Amazon (around $299) was in stock.
5. Saleae Logic 8: best if you’d rather skip sigrok
The Logic 8 is the one pick over $400, and it’s here because plenty of you will ask whether to just buy the Saleae.
Each of its 8 inputs records digital at up to 100 MS/s or analog at 10 MS/s with 10-bit resolution, so you can watch a slow edge ring while the decoder reads the bytes on it. Saleae ships Logic 2 for Linux as an x64 AppImage, version 2.4.48 when I checked, built for Ubuntu 20.04 and newer, with a Python automation API and a 3-year warranty on the hardware.
sigrok is a different story. Its saleae-logic-pro driver only registers the Logic Pro 16, and only its digital side, as experimental. The Logic 8 and Logic Pro 8 sit at “planned”. If you want sigrok decoders, the Logic 8 is the wrong purchase. The step up, the Logic Pro 8, listed at $999 on Saleae’s store, with 500 MS/s digital over USB 3.0, is far past this guide’s budget.
For digital-only work it’s the wrong buy, since the DSLogic Plus out-samples it in buffer mode for less than a third of the price. The Logic 8 on Amazon (around $499) is sold by Saleae itself, at the same price as Saleae’s store.
Choosing the specs that matter for your bus
Sample rate is the number on every box, but it’s rarely the first thing that goes wrong. When a capture looks like garbage, one of these is usually why:
- Sampling too slow: I aim for at least four samples per bit of the fastest signal, so 24 MHz covers I2C, UART and slow SPI
- Wrong threshold: fixed 0.8/2.0 V inputs misread 1.8 V logic, adjustable ones don’t
- Overvoltage: 5.25 V on the clones, 3.3 V on the Pico, 6 V on the DSLogic boards
- Streaming drops: no onboard memory means USB decides how long you can capture
- Missing firmware: DSLogic and Kingst need an extraction script first, fx2lafw doesn’t
- Missing driver: Pico and Kingst need the PulseView nightly, not the distro package
Missing firmware and missing drivers cost the most time, because the error looks like broken hardware when it’s a software gap. If you program boards with the Arduino IDE on Linux, the same udev permission habits apply here, since PulseView opens the USB device as your normal user. Our programmable bench power supply guide covers the other half of the bench that Linux can script, and our guide to multimeters with Linux logging covers the meter beside it. For ESP32 radio boards like the ones in our Meshtastic device roundup, a 16-channel analyzer earns its keep on the SPI bus between the MCU and the LoRa chip.
Leaving out Kingst and the rest
A few analyzers came close, and each missed for a reason that matters if one turns up cheaper somewhere else:
- Kingst LA2016: 16 channels at 200 MHz, listed at $138 direct on Kingst’s site, but no genuine listing on Amazon
- Kingst LA1010: listed at $68, with no onboard memory, same Amazon problem
- Saleae Logic Pro 16: the only current Saleae model sigrok drives, but listed at $1,499
- Hantek 6022BL: a 20 MHz USB scope with an 8-channel fx2lafw mode, a scope first (it anchors the mid tier of our electronics workbench builds)
The Kingst LA2016 hurt to drop. Kingst’s own table gives it 1 Gbit of memory and a -4 to +4 V threshold, and sigrok lists the kingst-la2016 driver as supported. On Linux, though, you need the PulseView nightly and you have to extract the FPGA bitstreams from Kingst’s own software with sigrok-fwextract-kingst-la2016. sigrok’s page also notes that only one edge trigger works. Amazon’s catalog returned no genuine Kingst, only third-party LA1010 listings I couldn’t tie to Kingst, so it’s an AliExpress order from Kingst’s store or nothing.
Buying the first one, then the second
If I were starting a Linux bench from nothing today, using one of our three budget workbench builds, I’d buy the HiLetgo first, learn PulseView’s decoders on a real UART, and only then decide whether I need speed or analog. That second purchase is where the software question bites. The DSLogic Plus is my pick for it, because it’s fast, cheap for what it does and runs in DSView today, with PulseView as a bonus if your unit is an older revision. Buy the U3Pro16 only if you’re happy living in DSView, and the Logic 8 only if analog traces matter more than sigrok’s decoder library.
Matched to the work on the bench, my short version reads like this:
- Arduino, ESP32 and I2C sensors, like the boards in an Arduino starter kit: HiLetgo clone
- 1.8 V logic or SPI past 6 MHz: DSLogic Plus
- Spare Pico and happy on nightly builds: sigrok-pico
- Long captures of fast buses on 16 channels: U3Pro16
- Analog edges next to decoded bytes: Saleae Logic 8
Whichever you buy, run the PulseView nightly AppImage next to the distro package. It cost me one download to find that the driver list I’d assumed from the sigrok wiki only exists in a build most tutorials never mention.




