Saleae Logic Analyser¶

This section describes how to download, install, and test the Saleae logic analyser.

Download¶

Download the application for your operating system from the official Saleae website.

Linux Installation¶

When downloading the Saleae Logic application for GNU/Linux, you receive an AppImage file. This file can be executed directly once execute permissions have been granted, as described in the official installation instructions. Alternatively, you can download the Logic 2 application using the curl command-line tool.

sudo apt install curl

curl -L <downloadLink> -o <downloadFileName>

curl -L "https://logic2api.saleae.com/download?os=linux&arch=x64" -o Logic-2.4.46-linux-x64.AppImage

Add AppImage to applications¶

To integrate the AppImage into your desktop environment and launch it like any standard application, some additional configuration is required. This procedure can be used for any AppImage application. Follow these steps to configure the application:

1. To simplify future updates, create a dedicated directory in a location of your choice:

   Command

   mkdir <newDirectory>
   

   Example

   mkdir ~/Documents/saleae
   

2. Move the downloaded AppImage file into the newly created directory, or download it directly into this directory using curl:

   Command

   mv <source> <target>
   

   Example

   mv ~/Downloads/Logic-2.4.46-linux-x64.AppImage ~/Documents/saleae/
   

3. Navigate to the new directory:

   Command

   cd <path/to/new/folder>
   

   Example

   cd ~/Documents/saleae/
   

4. Verify that the file is present using ls, then grant execution permissions:

   Command

   chmod +x <executable>
   

   Example

   chmod +x Logic-2.4.46-linux-x64.AppImage 
   

5. Install the required additional packages:

   Note

   This step is only required for the Saleae application. For other applications, install their respective dependencies.

   1. Install FUSE:

      Ubuntu (>= 24.04) | Debian 13:

      sudo add-apt-repository universe
      sudo apt update
      sudo apt install libfuse2t64
      

   2. Add the udev rules file:

      This rules file is required to grant non-root access to Saleae devices. Download the 99-SaleaeLogic.rules file and move it into the /etc/udev/rules.d directory:

      sudo mv ~/Downloads/99-SaleaeLogic.rules /etc/udev/rules.d/
      

   3. Launch the application to test the installation:

      Important

      Ubuntu (>= 24.04)
      When launching the application on Ubuntu 24.04 or later, you must append the --no-sandbox argument to the command, as described in Issues with Running AppImage file.

      Debian 13 in a Virtual Machine
      When launching the application on Debian 13 inside a virtual machine, you must append the --no-sandbox --disable-gpu arguments and run the command with superuser privileges (sudo ./<executable>).

      Command

      ./<executable>
      

      Example Ubuntu (>= 24.04)

      ./Logic-2.4.46-linux-x64.AppImage --no-sandbox
      

      Debian 13 in Virtual Machine

      sudo ./Logic-2.4.46-linux-x64.AppImage --no-sandbox --disable-gpu
      

      Warning

      If the application displays an information pop-up titled Install a udev rules file to allow non-root access to Saleae devices, run the command shown in the dialogue window or repeat step 5.2.

      Pop-up window

      

6. Create a symbolic link (symlink) to make your configuration modular and simplify future updates:

   Command

   ln -s <APPNAME> <LINKNAME>
   

   Example

   ln -s Logic-2.4.46-linux-x64.AppImage logic2.AppImage
   

7. Create a desktop launcher entry file to integrate the application into your desktop environment:

   Command

   touch ~/.local/share/applications/<appName>.desktop
   

   Example

   touch ~/.local/share/applications/logic2.desktop
   

8. Add the desktop entry content:

   Download logic2Icon.png for the official application icon. Move the icon into your Saleae directory so that all related files are stored together. Add the following configuration to the previously created file:

   Template

   [Desktop Entry]
   Version=x.x.x
   Type=Application
   Name=appName
   Comment=Application Description
   TryExec=<Path/to/App>
   Exec=<Path/to/App>
   Icon=<Path/to/AppIconImage>
   Actions=Editor
   Keywords=<keyword1>;<keyword2><...>
   StartupWMClass=<executable>
   X-AppImage-Version=<Version>
   

   Example

   [Desktop Entry]
   Version=1.0
   Type=Application
   Name=logic2
   Comment=Saleae Logic 2
   TryExec=/home/user/Documents/saleae/logic2.AppImage
   Exec=/home/user/Documents/saleae/logic2.AppImage --no-sandbox
   Icon=/home/user/Documents/saleae/logic2Icon.png
   Actions=Editor
   Keywords=logic2;2;saleae;
   StartupWMClass=Logic
   X-AppImage-Version=2.4.46
   

   Note

   If the application does not appear in your desktop menu, verify that all file paths in the .desktop file are correct.

Add a terminal command¶

To launch the application from the terminal, you must specify the correct path to the executable. To run it conveniently like a standard shell command, several options are available. One convenient approach is to add an alias to the .bashrc file located in your home directory. Pointing the alias to the same symlink used in the .desktop file ensures that both always reference the same executable. This promotes maintainability and makes future application updates straightforward. To make the alias more robust, the if condition verifies whether the target directory exists before creating the alias. Alternatively, you can reference the *.AppImage file directly without using the symlink.

1. Add the following block to the .bashrc file in your home directory:

   Template

   <_APP_DIR>=<path/to/your/application>
   
   if [ -d ${<_APP_DIR>} ]; then
      alias <newName>=${<_APP_DIR>}/<commandSubstitute>
   fi
   

   Example

   _LOGIC2_DIR=/home/user/Documents/saleae
   
   if [ -d ${_LOGIC2_DIR} ]; then
      alias logic2='${_LOGIC2_DIR}/logic2.AppImage --no-sandbox'
   fi
   

2. Because changes to .bashrc do not take effect automatically in your current session, reload the configuration using one of the following methods:

   • Reload the configuration in the current terminal using source:

     source ~/.bashrc 
     

   • Close the terminal (exit) and open a new one (Shift+Alt+T). The new terminal session loads the updated .bashrc file automatically.

Update Logic 2 application¶

When prompted to update the application, download the new version and repeat steps 2 to 6 in Add AppImage to applications. Use the same LINKNAME to redirect the symlink to the new application version. Once you have verified that the new version works correctly, you can safely delete the older AppImage file.

Route Saleae to a Virtual Machine¶

Using the Saleae device inside a virtual machine requires two USB filters. Initially, before connecting to the Logic 2 application, the device is identified as Cypress WestBridge. Once initialised and recognised by the application, its name changes to Saleae Logic (Pro). Add both USB filters permanently to your virtual machine configuration by following the instructions in How do I connect a USB port permanently to the virtual machine?.

USB Settings

Logic 2 Tutorials¶

Saleae provides short tutorial videos to help you get started with the Logic 2 application.

Capturing Data¶

This tutorial video demonstrates how to capture data using your Saleae logic analyser.

Organising the Workspace¶

Tips and techniques for customising your workspace and working efficiently with the Logic 2 application.

Triggers¶

Learn how to use triggers with the Saleae to start and stop measurements based on external signals.

Protocol Analysers¶

Serial communication protocols can be difficult to debug using a microcontroller alone. A logic analyser can decode and display serial communication data in real time. The tutorial video below demonstrates how to configure and use protocol analysers:

Tips and Tricks¶

Voltage Level Settings¶

If you observe unexpected digital voltage levels, such as short glitches or spurious spikes, the issue may be caused by the threshold voltage settings on Saleae Logic Pro models, which feature configurable logic threshold levels.

Example Error Situation

Set the appropriate voltage level for your hardware in the channel settings menu:

Setting Threshold Voltage

1. Open the channel settings menu.

2. Adjust the threshold voltage to match your target system’s operating voltage.

The available threshold levels determine how digital signal transitions are detected:

As a result, the logic analyser correctly interprets the signal levels and decodes the SPI communication without requiring any changes to the MCU firmware.

Correct Measurement Result