Logo
ScienceStack
Table of Contents
Fetching ...
Sign In

Rust for Embedded Systems: Current State, Challenges and Open Problems (Extended Report)

Ayushi Sharma, Shashank Sharma, Santiago Torres-Arias, Aravind Machiry

TL;DR

It is found that existing RUST software support is inadequate, SAST tools cannot handle certain features of RUST embedded software, resulting in failures, and the prevalence of advanced types in existing RUST software makes it challenging to engineer interoperable code.

Abstract

Embedded software is used in safety-critical systems such as medical devices and autonomous vehicles, where software defects, including security vulnerabilities, have severe consequences. Most embedded codebases are developed in unsafe languages, specifically C/C++, and are riddled with memory safety vulnerabilities. To prevent such vulnerabilities, RUST, a performant memory-safe systems language, provides an optimal choice for developing embedded software. RUST interoperability enables developing RUST applications on top of existing C codebases. Despite this, even the most resourceful organizations continue to develop embedded software in C/C++. This paper performs the first systematic study to holistically understand the current state and challenges of using RUST for embedded systems. Our study is organized across three research questions. We collected a dataset of 2,836 RUST embedded software spanning various categories and 5 Static Application Security Testing ( SAST) tools. We performed a systematic analysis of our dataset and surveys with 225 developers to investigate our research questions. We found that existing RUST software support is inadequate, SAST tools cannot handle certain features of RUST embedded software, resulting in failures, and the prevalence of advanced types in existing RUST software makes it challenging to engineer interoperable code. In addition, we found various challenges faced by developers in using RUST for embedded systems development.

Rust for Embedded Systems: Current State, Challenges and Open Problems (Extended Report)

TL;DR

It is found that existing RUST software support is inadequate, SAST tools cannot handle certain features of RUST embedded software, resulting in failures, and the prevalence of advanced types in existing RUST software makes it challenging to engineer interoperable code.

Abstract

Embedded software is used in safety-critical systems such as medical devices and autonomous vehicles, where software defects, including security vulnerabilities, have severe consequences. Most embedded codebases are developed in unsafe languages, specifically C/C++, and are riddled with memory safety vulnerabilities. To prevent such vulnerabilities, RUST, a performant memory-safe systems language, provides an optimal choice for developing embedded software. RUST interoperability enables developing RUST applications on top of existing C codebases. Despite this, even the most resourceful organizations continue to develop embedded software in C/C++. This paper performs the first systematic study to holistically understand the current state and challenges of using RUST for embedded systems. Our study is organized across three research questions. We collected a dataset of 2,836 RUST embedded software spanning various categories and 5 Static Application Security Testing ( SAST) tools. We performed a systematic analysis of our dataset and surveys with 225 developers to investigate our research questions. We found that existing RUST software support is inadequate, SAST tools cannot handle certain features of RUST embedded software, resulting in failures, and the prevalence of advanced types in existing RUST software makes it challenging to engineer interoperable code. In addition, we found various challenges faced by developers in using RUST for embedded systems development.
Paper Structure (72 sections, 13 figures, 19 tables)

This paper contains 72 sections, 13 figures, 19 tables.

Table of Contents

  1. Introduction
  2. Background
  3. Embedded Systems
  4. Rust
  5. Study Methodology
  6. Embedded Software Dataset
  7. Crates collection
  8. Identifying Stable Crates
  9. Compilation Validation
  10. Embedded Targets Filtering
  11. Categorization
  12. RQ1: Software Support
  13. Libraries and Support Software
  14. Hardware Support Crates
  15. Utility Crates
  16. ...and 57 more sections

Figures (13)

  • Figure 1: Response summary of Developers not using Rust.
  • Figure 2: Required Improvements to Rust Documentation.
  • Figure 3: Response summary of Developers on ease of adopting Rust toolchain.
  • Figure 4: Response summary of Developers perspectives on Rust's Interoperability.
  • Figure 5: Ease of Adopting Rust for Embedded Systems Development
  • ...and 8 more figures