https://scottgibb.github.io/Gibbiverse/tags/no-std/Recent content in No-Std on GibbiverseHugoen-ukTue, 07 Oct 2025 00:00:00 +0000https://scottgibb.github.io/Gibbiverse/posts/creating_a_multi_platform_rust_driver/part_3/Tue, 07 Oct 2025 00:00:00 +0000https://scottgibb.github.io/Gibbiverse/posts/creating_a_multi_platform_rust_driver/part_3/<p>In the previous part of the series, we discussed the FT232H breakout board and how we can use it with Rust to interact with our I2C devices from a desktop environment. In this part, we will explore how we we can use our I2C driver on multiple platforms without changing any of the driver code, thanks to the <code>embedded-hal</code> and <code>embedded-hal-async</code> traits.</p> <h2 id="the-platforms">The Platforms</h2> <figure class="tc"><img src="https://scottgibb.github.io/Gibbiverse/images/posts/creating_a_multi_platform_rust_driver/vendors.drawio.svg" alt="Chip Vendors"> </figure> <p>The beauty of using the <code>embedded-hal</code> traits is that we can write our driver code once and then use it on multiple platforms without any modifications. This is because the <code>embedded-hal</code> traits provide a common interface for interacting with hardware peripherals, regardless of the underlying platform. This means our vendors are responsible for implementing these traits in their HALs.</p>