Skip to main content
All CollectionsGetting Started
Connect to Your Virtual Devices
Connect to Your Virtual Devices

You can connect to your virtual devices via a few methods.

avhsupport avatar
Written by avhsupport
Updated over a year ago

You can connect to your virtual devices via a few methods.

Connect via VPN

For security, some connections require that you first connect to the virtual device via VPN. Just download the provided configuration file, install it, and you’re ready to go.

To connect to VPN, you will need to have a VPN client installed. If you don't already have a VPN client, we recommend an OpenVPN client. Once your VPN client is installed, you can simply download the OpenVPN configuration file from the Connect tab and install it to configure your VPN.

Please note: if you are using macOS, you will need to use either Viscosity (paid) or TunnelBlick (free) OpenVPN clients. The popular client OpenVPN Connect for macOS will fail since it does not support TAP mode.

Important Notes

  • VPN will only establish connection if you have at least one device in your project that is in the on state. If all your devices are off, or if you have no devices, the VPN will not establish connection.

  • Running other VPNs may interfere with your VPN connection. If you are having trouble connecting to the VPN and are already running your own VPN, you may need to disable the other VPN and then reconnect to the VPN.

Troubleshooting Tips

  • If you're having trouble connecting, try re-installing your VPN Profile.

  • Make sure you're connecting to the right profile for your project, and that at least one device in your project is On.

  • Close any other VPNs.

  • Check that your network doesn't have a firewall preventing your connection. Learn more about configuring Windows Defender Firewall.

Please also reference our Connect to the VPN article.

Connect via GDB

You can connect to the stub via GDB with the address and port for your particular virtual device, located at the bottom of the virtual device page.

Make sure to use the correct version of GDB for your device. 32-bit devices, including Cortex-M based ones, require 32-bit Arm GDB, and 64-bit devices require a 64-bit one.

You can also use other debuggers compatible with the GDB protocol, for instance lldb and IDA debugger.

Connect via Serial Console

If you prefer to view the device's serial console input / output in your local console program, such as Terminal, you can copy and paste the Console link from the Connect tab to your local console app. This can be convenient for enabling advanced console features, such as search.

Connect via other methods

Some virtual devices also support connect methods such as Iris and Cadi.

Did this answer your question?