FreeRTOS Instrument SDK: Hardware Integration Checklist
Define your CPU, OS, connectivity, display and vehicle interfaces to scope SDK delivery and integration.
Define the hardware before the feature set
Infinite Ride provides a shared Android/iOS APP and a C99 terminal SDK for FreeRTOS. Manufacturers can reuse the phone-side connection flows and business protocol while implementing their own transport, display and vehicle interfaces. Complete hardware details help separate reusable capabilities from firmware work early in the project.
A checklist for platform assessment
- Processor and toolchain: CPU architecture, chip, compiler and ABI. Static libraries are built for the target platform and cannot be reused across architectures.
- System and resources: FreeRTOS version and configuration, available RAM and storage. Include existing clock, randomness and persistence interfaces.
- Connectivity: BLE stack and data interfaces. Navigation video also requires Wi-Fi and a network receiving path.
- Display: resolution, UI framework and display driver. For video, specify decoding resources and the required refresh behavior.
- Vehicle interfaces: available state and controls, plus the readiness of CAN, serial or other interfaces.
If a prototype exists, identify the drivers already working. If board selection is still open, share candidate processors and required features before committing to a platform.
Keep the first integration small
Begin with discovery, authenticated pairing, capability exchange and one real state update. Then add navigation, notifications or vehicle controls. Large-screen navigation needs both video and HUD; use HUD alone only when the screen is too small to mirror.
Vehicle commands require an actual execution result. Video requires a working receive, decode and display pipeline. Successful pairing alone does not establish either capability.
Agree on delivery and validation
SDK delivery includes a target-platform static library, public headers and integration documentation. You retain the UI, drivers and vehicle interfaces. Validate target phones, reconnection, revoked permissions and failed operations before choosing the features each model exposes to riders.