Bridging the Gap Between Firmware, Software and Product

Hardware development is notoriously challenging. Unlike software development for front or backend, which can be swiftly iterated upon, debugged, and benefits from ample resources, embedded firmware usually runs on very limited memory (Flash and RAM). It requires a deep understanding of low-level hardware intricacies, including architecture, peripherals, and even electrical requirements. In this article, I’ll share some behind-the-scenes insights into the solutions we developed at Roadie Music to bridge the gap between firmware and software development.

The Difference Between Firmware and Software Development

Firmware development differs from traditional software development in several key ways:

1. Hardware Dependency: Firmware is intrinsically tied to the hardware it operates on. This dependency means that developing and testing firmware often requires physical hardware, which can be limited and costly. For instance, early-stage hand-soldered prototypes in a small startup can be delicate; one burnt component can delay development work for weeks.
2. Resource Constraints: Firmware typically runs on devices with limited memory and processing power. This constraint demands highly optimized code, which can be more complex to develop and maintain.
3. Deployment and Updates: Unlike software, which can be updated frequently and easily, firmware updates are more challenging due to the need for secure and reliable update mechanisms. While this is changing with more connected devices, traditionally, most consumer electronics products were not designed for easy updates.

Tools to Streamline Firmware Development

At Roadie Music by Band Industries , we've developed several tools and approaches to make firmware development as seamless as possible, akin to traditional software development.

• Building a Cross-Platform Emulator One of the critical needs in development is separating concerns, particularly between the business logic layer and the tech stack. For example, we don’t want our graphic interface code to be sending SPI commands; instead, it should be decoupled from the hardware it’s running on. To achieve this, we developed a cross-platform emulator that mimics our hardware's behavior, allowing our engineers to develop and test firmware without needing physical devices. The benefits include: Development Without Hardware: Engineers can write and test firmware code without waiting for hardware availability, accelerating the development cycle. Automated Testing: The emulator integrates with our CI/CD pipeline, enabling automated testing of firmware, which helps catch bugs early and ensures code quality. Enforcing Clean Firmware Design Patterns: By separating the code into drivers and a Hardware Access Layer, we ensure it can run on all platforms. Here's a sneak peek into Roadie Coach's emulator:

• Custom Database for Hardware We generally build our own custom file system or relational database from scratch to optimize memory usage and speed. This database is hosted in non-volatile memory (flash or other), and in one instance, we implemented it over an external eMMC. These were tailored specifically to our needs and hardware constraints. This database is generally integrated into our emulator, so we can easily use it for automated testing.
• Embedding Analytics in Firmware Understanding how our devices are used in the field is vital for continuous improvement and for product management. We embedded analytics capabilities directly into our firmware, allowing us to collect and analyze data efficiently: Offline Analytics: Data is stored in the device’s database and transmitted once a connection is available, ensuring we don't miss critical usage information. BLE and WiFi Transmission: For devices with BLE capabilities, data is transmitted to a central device, while with WiFi, it’s transmitted in real-time to our microservices, enabling us to actively monitor performance and user behavior.

Conclusion: Bridging the Gap

By implementing these tools and approaches, we've managed to bridge the gap between hardware and software development. These innovations not only streamline our development process but also ensure we can deliver high-quality, reliable products to our customers. My journey in making firmware development as seamless as possible continues to evolve, and I am excited about the future possibilities in this space.