shared-bus-rtic

Provides macros and type definitions for using a shared peripheral bus in an RTIC application

Description

Note that all of the drivers that use the same underlying bus must be stored within a single resource (e.g. as one larger struct) within the RTIC resources. This ensures that RTIC will prevent one driver from interrupting another while they are using the same underlying bus. The crate provides a detection mechanism that will panic if the shared bus is used in multiple task priorities without proper locking.

Features

This crate is compatible with thumbv6 architectures. To enable support for thumbv6 devices, enable the thumbv6 feature in your Cargo.toml: [dependencies.shared-bus-rtic] features = ["thumbv6"]

Usage Example

```rust use sharedbusrtic::SharedBus;

struct SharedBusResources { device: Device>, other_device: OtherDevice>, }

// ...

// Replace this type with the type of your bus (e.g. hal::i2c::I2c<...>). type BusType = ();

struct Resources { sharedbusresources: SharedBusResources, }

[init]

fn init(c: init::Context) -> init::LateResources { let manager = sharedbusrtic::new!(bus, BusType); let device = Device::new(manager.acquire()); let other_device = OtherDevice::new(manager.acquire());

init::LateResources {
    shared_bus_resources: SharedBusResources { device, other_device },
}

} ```

Valid Example

```rust struct SharedBusResources { deviceonsharedbus: Device, otherdeviceonshared_bus: OtherDevice, }

// ...

struct Resources { sharedbusresources: SharedBusResources, }

[task(resources=[sharedbusresources], priority=5)

pub fn highprioritytask(c: highprioritytask::Context) { // Good - This task cannot interrupt the lower priority task that is using the bus because of a // resource lock. c.resources.sharedbusresources.deviceonshared_bus.read(); }

[task(resources=[sharedbusresources], priority=0)

pub fn lowprioritytask(c: lowprioritytask::Context) { // Good - RTIC properly locks the entire shared bus from concurrent access. c.resources.sharedbusresources.lock(|bus| bus.otherdeviceonsharedbus.read()); } ```

In the above example, it can be seen that both devices on the bus are stored as a single resource (in a shared struct). Because of this, RTIC properly locks the resource when either the high or low priority task is using the bus.

Unsound Example

The following example is unsound and should not be repeated. When a resource is interrupted, the crate will panic.

```rust struct Resources { // INVALID - DO NOT DO THIS. deviceonsharedbus: Device, otherdeviceonshared_bus: OtherDevice, }

[task(resources=[deviceonshared_bus], priority=5)

pub fn highprioritytask(c: highprioritytask::Context) { // ERROR: This task might interrupt the read on the other device! // If it does interrupt the low priority task, the shared bus manager will panic. c.resources.deviceonshared_bus.read(); }

[task(resources=[otherdeviceonsharedbus], priority=0)

pub fn lowprioritytask(c: lowprioritytask::Context) { // Attempt to read data from the device. c.resources.otherdeviceonsharedbus.read(); } ```

In the above incorrect example, RTIC may interrupt the low priority task to complete the high priority task. However, the low priority task may be using the shared bus. In this case, the communication may be corrupted by multiple devices using the bus at the same time. To detect this, shared-bus-rtic will detect any bus contention and panic if the bus is already in use.