Automotive Session

Automotive devices in QDC are accessed through ADB (Android Debug Bridge) over an SSH tunnel, with optional QNX shell access. This guide walks you through the full connection process.

Prerequisites

Before you begin, make sure you have:

  • An SSH key imported or generated in QDC. See SSH Keys for setup instructions.
  • A running Interactive Session with an Automotive device.

Step 1: Set up SSH tunneling

The SSH tunnel creates a secure connection between your local machine and the remote device. This tunnel must stay running for the entire session.

Open a PowerShell or Terminal window and run the SSH command shown in the Connect dialog.

The command follows this format:

ssh -i {path_to_private_key} -L {adb_port}:sa{session_id}.sa.svc.cluster.local:5037 -L {qnx_port}:sa{session_id}.sa.svc.cluster.local:9022 -N sshtunnel@ssh.qdc.qualcomm.com
ValueDescriptionWhere to find it
{path_to_private_key}Path to your SSH private key fileThe file you created/uploaded when setting up SSH keys
{adb_port}Local port for ADB access to the deviceShown in the Connect dialog
{qnx_port}Local port for QNX shell accessShown in the Connect dialog
{session_id}Your session execution IDShown in the Connect dialog

Keep this window open

The SSH tunnel must remain active for the duration of your session. Do not close the terminal window running this command.

Step 2: Run ADB commands

Once the tunnel is running, open a new terminal window and run ADB commands to interact with the device:

adb devices — Verify the device is connected

adb shell — Open a remote shell on the device

adb push / adb pull — Copy files to and from the device

For a full list of commands and examples, see the ADB Commands reference.

Step 3: Connect to QNX (Optional)

If your Automotive device supports QNX, you can connect to the QNX interface. Open a new terminal window and run:

ssh -p {qnx_port} root@localhost

Replace {qnx_port} with the QNX port you specified in the Connect dialog.

Troubleshooting

Having trouble connecting? See SSH Troubleshooting for solutions to common issues including host authenticity warnings, permission denied errors, and connecting to additional ports.