Scopy troubleshooting guide [Analog Devices Wiki] (2025)

This version (13 Feb 2025 10:35) was approved by Adrian Suciu.The Previously approved version (13 Feb 2025 10:34) is available.

Table of Contents

Make sure you install the latest driver -

• Windows Drivers

• Linux Drivers

• macOS Drivers

Scopy.ini and Preferences.ini contain the user-settings that are saved in-between sessions. Sometimes these can get messed up and can cause problems. In order to reset them, go to:These file are located in:

• Windows: C:\Users\<your_username>\AppData\Roaming\ADI Sometimes this is a hidden directory, and you unhide it.

• Linux: /home/<your_username>/.config/ADI

• Mac: /Users/<your_username>/.config/analog.com

and delete (or rename) Scopy.ini, Scopy.ini.bak, Preferences.ini, Preferences.ini.bak. The preference is to rename things with a different suffix, so if you need to report a bug, the file still exists.

Scopy configuration can sometimes get messed up when updating as opposed to uninstall/reinstall. If you are facing this issue, you can try uninstalling Scopy and then reinstall.

Make sure that after uninstall Scopy's folder is clear

Make sure you install Scopy in a location that doesn't require any write privileges since Scopy needs to write to it's installation folder.

Visit the ADALM2000 firmware page https://github.com/analogdevicesinc/m2k-fw/releases.

Compare the latest firmware version on this page with the one you have installed. Follow these steps to update the firmware.

• Run a clean uninstall

• Delete the ini files

• Run a clean reinstall

• Restart your computer after the clean install can fix your problems.

Some laptops limit the amount of current that can be delivered via an USB port (either native or from a docking station/usb hub). In order to workaround this issue you can try the following:

1. Go to Device Manager tool in Windows OS

2. Go to Universal Serial Bus Controllers

3. Select ASMedia USB Root hub(or which USB root hub the board is connected to), Right click on its properties

4. uncheck the “Allow the computer to turn off this device to save power” in the Power management tab

5. Reboot.

Download latest version of https://github.com/analogdevicesinc/libiio/releases .

Open a command prompt and run

iio_info -a 

or

iio_info -u "ip:192.168.2.1"

Scopy displaying a white screen on startup (combined with hangs or crashes) is an issue that indicates OpenGL incompatibility with your system due to a missing or outdated graphics driver/DirectX/OpenGl Driver.

• Disable OpenGL usage in favor software rendering by setting the general_use_opengl preference in preferences.ini to false.

• On Windows Virtual Machine, enable 3d hardware acceleration.

In recent Scopy versions, a pop-up will appear when this issue is detected, the preference will be automatically disabled and Scopy will try to restart. For older Scopy versions, please do this manually.

Download the debug files associated with your release. From the same place you downloaded the release, download the “debug-64.zip” file. If you can't remember where you downloaded the release from, a safe bet would be to redownload and reinstall Scopy and the appropriate debug archive.

It is critical that the debug file and Scopy is the same version for this to work

• Unzip debug-64.zip to a location.

• Copy the .pdb files to Scopy.exe's location. The installation folder should look like this:

• Open WinDbg (x64)

• File → Open Executable (CTRL+E) → Navigate to Scopy.exe → Select Scopy.exe

• File → Symbol File Path → Navigate to Scopy.exe folder → Select Scopy folder (Make sure you select “Reload” checkbox in the bottom left of the Dialog Box)

• File → Source File Path → Navigate to debug-64.zip folder → Select “scopy” folder (this file should contain the sources from github)

• You can save this workspace if you plan to do this multiple times to save time (File → Save workspace to file)

• Debug → Run (or F5)

• Profit

You can now reproduce bug/crash/hang

• If scopy crashes, WinDbg will stop after crash so you can investigate.

• If scopy hangs, you can debug→break (CTRL+Brk) to see where it's hanging

• View → Call Stack (ALT+6) (to check out call stack when crash/hang occurs) (opens window like 2 in screenshot)

• View → Processes & Threads (ALT+9) (so you can cycle through different threads) (opens window like 4 in screenshot)

• Call Stack → Source (to enable source mapping) (button 1 in screenshot)

• Command → run: “.dump <file_name.dmp>” to create crash dump that can be sent to the developers (Command window input - 5 in screenshot)

• You can look around to figure out where it crashed/why (3 in screenshot shows source mapping - where the hang occurs)