Troubleshooting

When encountering issues while using the Ameba extension, you can follow these troubleshooting steps:

Plugin Malfunction

Issue: Plugin buttons appear grayed out, or terminal commands fail with script not found errors

Solution:

• Uninstall the current plugin

• Press Ctrl+Shift+P > Developer: Reload Window to reload the window

• Search and install the latest version of the plugin from the extension marketplace

Extension Installation Failure

Issue: Extension cannot be installed properly or fails to start after installation

Solution: Check system environment version requirements and ensure the following minimum versions are met:

• VS Code version ≥ 1.84.0

• Node.js version ≥ 18.16.0

You can check version information through the following methods:

• Menu bar Help → About to view version number

If the versions do not meet the requirements, please upgrade to the corresponding versions first and then reinstall the extension.

Terminal-Related Issues

Issue: Terminal command execution fails, or the interface is unresponsive

Solution: The extension’s core functions are executed through a dedicated terminal named Ameba. When abnormalities occur:

• If you find that the Ameba terminal has errors or is unresponsive, manually close it

• The extension will automatically detect and recreate the Ameba terminal when executing functions next time

• After closing the abnormal terminal, click the corresponding function button again to use it normally

Toolchain Path Modification Issues

Issue: After modifying the toolchain installation path, the extension cannot properly recognize the development environment or functions abnormally

Solution: If you have modified the toolchain installation path (refer to Installing Toolchain ), you need to perform the following steps:

• Completely close VS Code (ensure all VS Code windows are closed, simply reloading the window is not sufficient)

• Restart VS Code and open the Ameba SDK project

• The extension will automatically re-detect the development environment configuration and update the relevant path information

External Project SDK Not Recognized

Issue: After opening an external project, the status bar shows ⚠ Not Ready and the feature buttons are grayed out

Solution:

• Confirm that ameba.rootSDKPath in .vscode/settings.json points to a valid ameba-rtos SDK root directory

• Run Ameba: Set Root SDK Path from the Command Palette to select the SDK path again and regenerate the configuration files

• If the SDK has not been downloaded yet, download and configure it through the Setup Wizard

Code Navigation Not Working

Issue: Go to definition, completion and similar features do not work, or VS Code shows a clangd error in the bottom-right corner

Solution:

• Confirm that the llvm-vs-code-extensions.vscode-clangd or ms-vscode.cpptools extension is installed from the VS Code Marketplace. See Code Navigation

• If the clangd extension was installed after the .vscode configuration was generated, run Ameba: Set Root SDK Path from the Command Palette to regenerate the configuration

• When using clangd, confirm that Build has been run at least once so that compile_commands.json is generated

• If you have switched the target chip, rebuild to update compile_commands.json; the extension automatically synchronizes the clangd configuration path

• If clangd is still unresponsive, run clangd: Restart Language Server from the Command Palette to restart the language server