English · 简体中文
A cross-platform serial port debugging assistant built with Flutter and Rust
Connect devices, send and receive text or Hex data, inspect ANSI-colored logs, and export debugging records.
Download · Quick start · Release notes · Build from source · Report an issue
Windows / Linux / Android · Text / Hex transfer · English / Chinese interface
- Serial connections: discover available ports, configure baud rate, data bits, stop bits, parity, and flow control, and remember your settings.
- Text and Hex transfer: switch transmission and receive-display modes; optionally append LF, CR, or CRLF to text transmissions.
- Log viewing and export: display ANSI colors, timestamps, and separate sent and received records; adjust the log buffer and export debugging records.
- Repeatable debugging: reduce repetitive input with send history and automatic sending at a configurable interval.
- Connection status and statistics: view connection state, byte counts, and receive rate, with optional automatic reconnection after a device disconnects.
- Desktop experience: English and Chinese interfaces, light, dark, and system themes, and remembered window size and position.
Download from the latest release. Previous versions and release notes are available on Releases.
| Platform | Packages | How to choose |
|---|---|---|
| Windows | Installer -setup.exe / portable -portable.zip |
Follow the installer, or fully extract the portable archive and run skyport.exe |
| Linux | .deb / .rpm / .AppImage |
Prefer .deb on Debian / Ubuntu, .rpm on RPM-based distributions such as Fedora, or make the AppImage executable and run it |
| Android | -android-arm64.apk |
Android 8.0+ (API 26), ARM64; USB Host / OTG support required for serial devices |
Windows and Linux provide amd64 (x64 / x86_64) and arm64 (ARM64 / aarch64) packages. Choose amd64 for Intel / AMD x64 computers and arm64 for ARM devices. Check your system's processor architecture if unsure.
Keep the entire desktop portable directory intact. Do not copy only the executable or remove bundled libraries and resources. Windows, Linux, and Android are supported; macOS is not. The macOS project files in this repository do not imply a supported release.
Android: install the APK, connect a USB serial device via OTG, and grant USB access. Leaving the app disconnects USB and stops automatic sending; reconnect manually after returning.
- Connect your device: plug the serial device into your computer, launch SkyPort, and select a port under "Port Settings".
- Match the parameters: set baud rate, data bits, stop bits, parity, and flow control to match your device. Click "Connect" and confirm that the status becomes "Connected".
- Send data: enter a command supported by your device. In text mode, configure newline handling to match its protocol. For binary data, enable "Hex Send" and enter complete bytes.
- Inspect the response: view sent and received records in the log area. Enable Hex display, timestamps, or ANSI rendering as needed. Whether the device echoes or responds depends on its protocol.
- Save your records: use "Export Logs" to save debugging records. To send the same content repeatedly, configure an automatic-send interval.
Automatic reconnection restores the connection; it does not mean failed data has been resent. If sending fails, inspect the error and the number of bytes written before deciding what to do next.
No serial port found, or unable to connect?
Check that the operating system recognizes the device, the required drivers are installed, and no other program is using the port. On Linux, also check your user's permissions for the serial device. Do not bypass permission setup by routinely running the application as root.
Garbled received data, or no response after sending?
Check the communication parameters, text / Hex mode, and newline requirements. Inspect binary data using Hex display. ANSI rendering is for text logs containing escape sequences; it does not turn binary data into readable text.
Can exported logs recover lost data?
No. Exports contain only the records currently retained. Data evicted from the buffer or lost in a data gap cannot be recovered by exporting. Export important debugging records promptly.
-
Flutter / Dart: satisfy the SDK constraints in
app/pubspec.yaml. See the CI configuration for the toolchain versions used in CI. -
Rust stable, with the appropriate platform compilation target installed through rustup.
-
Windows: Visual Studio with the "Desktop development with C++" workload.
-
Linux: Clang, CMake, Ninja,
pkg-config, and GTK3 and libudev development packages. On Debian / Ubuntu:sudo apt-get install clang cmake ninja-build pkg-config libgtk-3-dev libudev-dev
Running only the Rust core tests does not require Flutter. On Linux, pkg-config and the libudev development package are still required.
git clone https://github.com/StarSphere-1024/SkyPort.git
cd SkyPort
cd app
flutter pub getRun the following commands from app/, choosing the group for your host system:
Windows
flutter run -d windows
flutter build windows --releaseLinux
flutter run -d linux
flutter build linux --releaseFlutter's Windows / Linux CMake build invokes Cargo and bundles the Rust bridge library. Distribute the complete bundle: skyport_flutter_bridge.dll sits next to the Windows .exe, while Linux uses lib/libskyport_flutter_bridge.so.
SkyPort uses Rust + Flutter. The independent Rust core owns serial lifecycle, data transfer, configuration persistence, logs, statistics, and scheduling. Flutter handles the desktop interface and interaction, accessing the core through flutter_rust_bridge.
See the Rust core design (in Chinese) for architecture and data, queue, and configuration migration contracts. Dependency versions are defined in the Flutter manifest, Cargo manifest, and their respective lockfiles.
When opening a pull request, describe the use case, behavior changes, and verification results. Include reproduction steps for bug fixes. When changing cross-layer interfaces, update Rust, the bridge, and Dart consumers together.
Local checks and real serial-path verification
Run the Rust core tests and Flutter unit / widget tests from the repository root:
cargo test --locked -p skyport_core
tool/test_quiet.shOn systems without Bash, such as Windows, run dart ../tool/quiet_flutter_test.dart from app/. Run static analysis from app/ as well:
flutter analyzeRun the following commands from the repository root:
python3 scripts/pty_ui_smoke.py
python3 scripts/package_smoke.py <bundle-or-package-path>pty_ui_smoke.py: Linux only; exercises data transfer and lifecycle with the real UI, bridge, and pseudo-terminals.package_smoke.py: checks loading and lifecycle for a complete bundle, deb, rpm, AppImage, or Windows portable zip on the corresponding platform. Install Windows installers into an isolated directory first, then check that directory.- Linux checks require a display. Prefix commands with
xvfb-run -ain headless environments. - RPM package checks require
bsdtar; installlibarchive-toolson Debian / Ubuntu. - On Windows, replace
python3with your local Python command, usuallypython.
Pseudo-terminal verification does not replace acceptance testing with physical serial ports, other architectures, or actual hardware.
Generate bindings after changing the bridge API
Regenerate bindings only after relevant API / type changes. Do not edit generated files manually. Keep the generator version aligned with the bridge manifest.
Run from the repository root:
cargo install flutter_rust_bridge_codegen --version 2.13.0 --locked
cd app
flutter_rust_bridge_codegen generate --config-file flutter_rust_bridge.yamlReport bugs or suggest features through GitHub Issues. Search existing issues first, and include where possible:
- Application version, operating system version, and processor architecture.
- Reproduction steps, expected behavior, and actual results.
- Relevant serial parameters, text / Hex mode, and newline configuration.
- Error messages, diagnostic details, relevant logs, or screenshots.
Remove keys, device identifiers, and other sensitive data before sharing logs. For feature requests, describe the debugging scenario and the problem you want to solve.
SkyPort is licensed under the GNU Affero General Public License v3.0.
Maintained by StarSphere-1024.
