The Role of Embedded Firmware and Software in Performance-Critical Design

What’s important when developing firmware for a new embedded system?

Firstly, understanding the use case, i.e. how it’s being used and what it’s being used for. Requirements derived from examples of real customer systems, which can then be broken down into functional domains, mean that a system can be meaningfully validated to ensure it’s fit for purpose.

We start with a good framework, a layered structure, and we continually improve our process, striving for better quality code. Part of this comes from the aim to be able to directly address the needs of the avionics and safety critical business sectors.

All of our software is embedded, i.e. it is designed to run optimally and produce the best result for a combined hardware, firmware, and software solution. We develop all of these in parallel to ensure that we’re providing efficient, performant functionality. Although our solutions are inherently versatile, we ensure that they meet the exact needs of targeted use cases.

We test everything at multiple levels, using simulation, emulation, and real hardware testing to properly exercise functionality, and do so in functional blocks, and varying levels of system integration.

How do we ensure our modules integrate with a wider system?

We share goals and form deep, meaningful relationships with our customers so that we understand what is needed now, and how we can help build the next generation of capability.

Internally, we love iterative development – seeking to integrate at the earliest possible opportunity, and building on that functionality over successive sprints and product releases.

Our approach to ASTRO, our own wideband adaptive radio processor ecosystem, has been to make something that can directly address system problems that our customers face, and to enable them to build on a flexible, performant platform framework, adding their own functionality and digital signal processing (DSP) capabilities.

This year, we’re focusing on open standards, such as VITA specifications, Open CPI, and STICS, and what that means for supporting system integration and operability.

What makes high-performance embedded code?

It all comes back to a detailed knowledge of the platform, such that the function can be achieved efficiently.

Embedded code is typically optimised for power, though embedded systems are always resource constrained, and even fast, capacious FPGAs will struggle if there is not good knowledge and implementation in the areas of Performance and Area (PPA) Power.

The ability to build up a library of high-level functionality, and make this to be portable across related platforms also helps.

What does the future of [high-performance] code look like?

Although increasingly complex code-abstraction reduces the barrier to entry, good embedded code will always come from a marriage of slim, efficient software making best use of hardware to deliver functionality.

Speedy reconfigurability within nanoseconds is crucial for the system to be responsive. This goes hand in hand with code being testable, maintainable, and expandable.

Ultimately, though, the best code will always come from a team with detailed understanding of the full system, with a multi-disciplinary engineering approach, and shared goals.

What are you looking for in the future of Slipstream Design’s code?

We’re in the early stages of exploring a Continuous Integration pipeline, testing realistic and representative scenarios more accurately, and traceability from customer system requirements.

What excites you most about the future of embedded RF systems?

So many things! To name a few: new hardware capabilities coming to the fore in the form of chiplets, plus the increasing integration of processing, FPGA, and RF capability, and the increasing demands on good firmware to be able to capitalise on this.

We’re enjoying exploring the possibilities of using AI to increase functionality at the edge, and monitoring its growing ability to make decisions and operate autonomously, which seems promising in improving the resilience of sensing and communication systems.

Conclusion 

We hope you’ve found this conversation with Stuart insightful. If it’s sparked any further questions, we can put you in touch with the Digital team via info@slipstream-design.co.uk