Skip to content

Troubleshooting

This page collects fixes for every area. Task pages have their own short lists: Build, Debug a program, Activate a licence and Probe drivers.

Logs

Most messages from the extension have a Show Log button that opens the right log. To open a log yourself, select View → Output (Ctrl+Shift+U), then pick the channel in the drop-down at the top right of the panel.

Where What it shows
Output → Ashling vcpkg Checking for updates, downloading, removing and activating SDKs
Output → Ashling Drivers Probe driver checks and installs (Windows)
Output → CMake/Build CMake configure and build output (from CMake Tools)
Terminal panel Make build output, and Clean for Make projects
Debug Console panel GDB, Ashling GDB server and QEMU output during a debug session

SDK Manager and downloads

A new SDK or version isn't listed

Select Check for updates in the SDK Manager. After the first download, the list is only refreshed when you select Check for updates. The SDK Manager also only offers SDKs built for your operating system; the Ashling SDK for VSD is Windows only.

Could not load the SDK registry

The extension couldn't reach GitHub and has no saved list to fall back on. Check your internet connection and proxy settings, then select Check for updates.

A download fails

The message gives the cause and what to do. The common causes are:

  • No connection, or a proxy or firewall blocks it. Ask IT to allow access to GitHub and Amazon S3, where SDKs are downloaded from. Behind a proxy, set HTTPS_PROXY before you start VS Code; SDK downloads don't use http.proxy.
  • TLS or certificate errors. Often caused by a company proxy or antivirus that inspects HTTPS traffic, or a wrong system clock. Ask IT to let GitHub and Amazon S3 traffic through without HTTPS inspection.
  • Low disk space. Free at least 1 GB plus the size of the SDK, or change the SDK root folder to a larger drive.
  • Path too long (Windows). Change the SDK root folder to a short path such as C:\sdk, or enable Windows long paths.

Select Show Log for the full details.

An SDK shows incomplete, warning or failed

Select Verify to check it again. Verify doesn't download anything; to fix the SDK, see Repair an SDK. For a warning, select a component marked to see the issue.

An antivirus program that quarantines SDK tools can cause this. Exclude the SDK root folder from scanning, then repair the SDK.

Projects and builds

No SDK installed. Samples are provided by an SDK.

Install an SDK first. Select Open SDK Manager in the message.

No SDK is selected for project

Building, adding a debug configuration and starting a debug session all need the project's SDK. The message ends Select an SDK for this project to build it or …to debug it. Select Select SDK in the message, or select an SDK on the project's SDK Selection row.

The project doesn't appear in the Ashling Project View

Select the Ashling icon in the Activity Bar, then under Quick Operations select Add folder(s) to workspace and pick the project's root folder. If the folder is already in the workspace but isn't recognised, see How the project type is detected.

The project's files are shown instead of Build Actions and Debug Configurations

The Ashling Project View is showing the project's files. Select the icon in the view's title bar (Show Build and Debug Actions) to switch back.

The build uses the wrong tools, or the wrong toolchain is used in a terminal

Check the project's SDK Selection row and select the SDK again. Only terminals opened after the SDK was selected get its tools, so close the terminal and open a new one.

CMake Tools asks for a kit

CMake Tools asks for a kit when you open your own CMake project before an SDK is selected for it, or when you build with CMake Tools' own commands. Cancel it, select an SDK for the project, then build from Build Actions.

Invalid CMake path configured

The extension sets the project's cmake.cmakePath to the SDK's CMake when you select the SDK and on every build. This message means the selected SDK doesn't include CMake. Select an SDK that includes the build tools.

Compiler or make not found

The SDK may be incomplete. Check its status in the SDK Manager, and repair it if needed.

My Make project builds as CMake, or not at all

A CMakeLists.txt in the project root always takes priority, and the Makefile must be in the root of the workspace folder. Remove or rename the root CMakeLists.txt if the project isn't a CMake project, or add the folder that holds the Makefile to the workspace on its own. See How the project type is detected.

Debugging

The probe isn't listed, or No debug probes found
  • Windows: install the probe drivers, then reconnect the probe.
  • Linux: check the udev rules are installed, then reconnect the probe.
  • Select the refresh icon next to Debug probe in the Debug Configuration panel. A configuration with a saved probe doesn't scan for probes when it opens.
No .elf files found in project. Build the project first.

Build the project, then select Search Project.. on the Main tab again.

The debug session doesn't start, or can't connect to the target

Open the Debug Console: the GDB server's output there usually names the problem. Then check the probe connection, power and target settings as in The target doesn't respond.

A QEMU session doesn't start while another one is running

All QEMU configurations use GDB port 1234, so only one QEMU session can run at a time. Stop the other session first, and close any other program that uses port 1234.

The GDB server reports a licence error
  • Check that the licence is activated for the SDK the project uses.
  • A key locked to another computer doesn't work on this one; send this computer's fingerprint to Ashling for a new key.
  • If the key has expired, or the error persists, contact support@ashling.com with the message from the Debug Console.
tool (the \"gdb\" or \"server\" of configuration) is not in the SDK sdk version of project

The configuration needs a GDB or GDB server that the project's SDK doesn't have. Select the matching SDK, or create a new configuration of the right type.

Report a bug or get support

To report a bug or request a feature, open an issue on GitHub. Issues are public, so don't include licence keys or confidential details.

For technical support, licensing, or anything you'd rather not post in public, email support@ashling.com with:

  • The extension version (Extensions view → RiscFree™ for Embedded Software Development → Installation panel)
  • The SDK name and version (SDK Manager)
  • Your operating system and version
  • Your probe and target device, if debugging on hardware
  • What you did, and the message you saw
  • The relevant log for the area that failed (see Logs): the output channel, the Terminal output for Make builds, or the Debug Console output for debug sessions