Accessing the Linux Console on Tachyon
Tachyon provides multiple ways to access the Linux console, depending on your build type and available connectivity options.
Two Types of Builds
Tachyon currently ships with two software builds:
- Desktop Build
- Access the Linux console by clicking the terminal application and using the shell normally.
- Headless Build & Desktop Build (Alternative Methods)
- Additional non-graphical access methods are available for both builds, as outlined below.
1. Root Console via Debug Port (Serial Connection)
The root console is configured to output logs over the debug port, including:
- Bootloader logs
- UEFI logs
- Kernel logs
- Combined root shell access
To use this, connect a debug adapter to your Tachyon device and access the serial console.
➡️ See the Debug Adapter page for setup instructions.
Note:
- This console auto-logs in for development builds.
- Kernel logs are merged with the console output.
- If you want to disable kernel logs in the console, see Tips & Tricks.
- Primarily used for debugging.
2. ADB (Android Debug Bridge) over USB
ADB allows direct access to the Linux shell via USB.
Steps to Use ADB:
- Install Android Debug Tools on your host machine. ADB Install
- Connect your host computer to the Tachyon device via USB.
- Open a terminal and type:
adb devices
- This will list all connected devices.
- To start a shell session:
adb shell
- This opens a direct Linux shell over USB.
Why use ADB?
- Allows pushing/pulling files.
- Supports rebooting the device.
- No network required.
3. SSH Over Local Network
If your Tachyon device is connected to Wi-Fi or Ethernet, you can SSH into it.
How to Connect via SSH:
- Find the device’s IP address (check your router or use
ifconfig
on the device). - Run:
ssh root@<DEVICE_IP>
- Enter the password (set during the setup process).
Why use SSH?
- Secure and encrypted.
- Works over Wi-Fi & Ethernet.
- Recommended for general remote access.
4. Particle Console Remote Access
Tachyon integrates with the Particle Console, allowing remote SSH access even if the device is not on the same network.
How to Access via Particle Console:
- Log into Particle Console.
- Navigate to your device page.
- Click on "Open Remote Console".
🚀 Why use Particle Console?
- Works even if the device is in the field.
- Uses a secure reverse shell for access.
- No need for local network connectivity.
5. Tailscale VPN Access
Tachyon ships with Tailscale VPN pre-installed for alpha testers and EVT units.
Tailscale is a VPN infrastructure that we are somewhat fond of at Castle Particle. It provides a simple method to login to a single board computer from a standard laptop by using the Tailscale server to redirect traffic from without exposing SSH ports to the internet (which is bad!).
We have pre-installed Tailscale on the Linux image and authenticate this on EVT units directly into the Particle Tailscale so its easy to observe any errors occuring in the field. This won't be part of DVT and we'll find an alternative VPN solution our customers can use.
You can switch the device to your own Tailscale account if you wish! Its a great tool.
How to Set Up Tailscale on Your Own Account:
- Open any console method above.
- Run:
tailscale up
- Click the authentication link and log into your own Tailscale account.
🚀 Why use Tailscale?
- Secure overlay networking.
- Access your device even behind firewalls.
- Works with any internet connection.
Which Access Method Should You Use?
Method | Requires Local USB Access? | Requires Local Network Access? | Best For |
---|---|---|---|
Debug Port (Serial Console) | ✅ Yes | ❌ No | Low-level debugging (Bootloader, UEFI, Kernel Logs) |
ADB over USB | ✅ Yes | ❌ No | Local device management via USB |
SSH Over Network | ❌ No | ✅ Yes | General remote access |
Particle Console | ❌ No | ✅ Yes (Cellular or Wi-Fi) | Remote field access (even if no open SSH port) |
Tailscale VPN | ❌ No | ✅ Yes | Secure, private network access across all your devices |
Summary
Tachyon supports multiple ways to access the Linux console, ensuring flexibility for different use cases.
Choose the method that best fits your setup and needs!
Stay tuned for further documentation on advanced console management and remote access workflows.