-
Notifications
You must be signed in to change notification settings - Fork 15
Getting Started
This page shows a minimal local setup to get Ripple running against a device on your network.
-
Rust Toolchain
- Stable channel (minimum version 1.82.0)
- Install via rustup
- Components needed:
rustc,cargo,rust-std
-
Build Tools
- Linux:
build-essential,pkg-config,libssl-dev - macOS: Xcode Command Line Tools
- Windows: Visual Studio Build Tools with C++ workload
- Linux:
-
Development Tools (Recommended)
- Visual Studio Code
- Rust Analyzer Extension
- LLDB Extension for debugging
- RDK device accessible on your network
- Network connectivity between development machine and device
- Device management access (e.g., SSH, Web UI)
For detailed requirements and troubleshooting, see the Ripple Repository.
git clone https://github.com/rdkcentral/Ripple.git
cd Ripple# Bootstrap Ripple configuration
./ripple initThis creates the ~/.ripple directory and sets up default manifests.
Ripple uses three key manifest types:
-
Device Manifest
- Defines device capabilities
- Platform settings
- Library references
- Located at
~/.ripple/firebolt-device-manifest.json
-
Extension Manifest
- Extension binary locations
- Contract definitions
- Located at
~/.ripple/firebolt-extn-manifest.json
-
App Library
- Application metadata
- Launch configurations
- Referenced in device manifest
See Manifests for detailed configuration options.p you set up Ripple in your development environment and get it running against an RDK device.
See Manifests for details and sample paths.
-
Extension Settings In
~/.ripple/firebolt-extn-manifest.json:{ "default_path": "target/debug/", "default_extension": "so" # or "dylib" (macOS), "dll" (Windows) } -
Device Configuration Verify in
~/.ripple/firebolt-device-manifest.json:{ "library": "path/to/your/app-library.json" } -
App Configuration Add Firebolt endpoint to your app's launch URL:
__firebolt_endpoint=ws%3A%2F%2F<RIPPLE_IP>%3A3473%3FappId%3D<app_id>%26session%3D<app_id>
ripple run <DEVICE_IP>Ensure your development machine and the target device have bidirectional network connectivity.
- Check Ripple logs for successful initialization
- Verify WebSocket server is listening
- Confirm device connection status
- Set up Debugging with VS Code and LLDB
- Explore the Brokers and Rules System
Common issues and solutions are documented in our Troubleshooting .
For additional support:
- Check the GitHub Issues
- Join our Developer Community
- Review the FAQ
© 2025 RDK Management, LLC (and contributors). Firebolt® is a registered mark of its owner.