rubberduck203/stm32f3-discovery

Rust Board Support Package for the STM32F3DISCOVERY

stm32f3-discovery's Issues

Allow configuration of button interrupt trigger

Currently, the button interrupt is configured to only trigger on rising edge.
Allow other configurations.

stm32f3-discovery/src/button/interrupt.rs

Line 42 in 33db991

//TODO: take enum to specify trigger mode {rising, falling, both}

Change Leds to use a Compass like construction

Instead of taking ownership of the entire GPIOE port and returning a new struct that only has the pins that aren't owned by the Leds struct, just give the Leds ctor the pins it's needs.
Also, change init to new for consistency with the other periphs.

Create LED abstraction

There are 8 user leds on board, LD3-LD10, arranged in a "compass".
Provide

• A LED trait with on and off functions
• Allows users to access the leds via the names printed on the board rather than the GPIO they're connected to (i.e. PE13, etc.)
• Allow users to access the leds via their "direction" on the compass (N/S/E/W are printed on the board).
• Bonus points for being able to iterate through all 8 LEDs

Example for using SPI

Hello! I'm wondering if you have an example of how to setup SPI.

The feather_m0 board that I've used previously has a helper for setting up the master. Maybe something similar could be added here. https://docs.rs/feather_m0/0.6.1/feather_m0/fn.spi_master.html

Provide access to gyroscope

There is a L3GD20 gyroscope on board.
Provide access to this peripheral.

Not receiving any magnetometer data

Hi!

I'm learning embedded rust and currently trying to control the compass leds of the STM32F3 discovery board using the magnetometer data. I was able to setup everything and I get logs from the accelerometer, but not from the magnetometer.

I used the example code from examples/compass.rs and I'm running rust 1.53.0. Any ideas on what I might be overlooking?

Accel:I16x3 { x: -128, y: -896, z: 16512 }; Mag:I16x3 { x: 0, y: 0, z: 0 }
Accel:I16x3 { x: -320, y: -704, z: 16512 }; Mag:I16x3 { x: 0, y: 0, z: 0 }
Accel:I16x3 { x: -192, y: -576, z: 16448 }; Mag:I16x3 { x: 0, y: 0, z: 0 }
Accel:I16x3 { x: -128, y: -768, z: 16512 }; Mag:I16x3 { x: 0, y: 0, z: 0 }
Accel:I16x3 { x: -256, y: -704, z: 16384 }; Mag:I16x3 { x: 0, y: 0, z: 0 }
Accel:I16x3 { x: -320, y: -768, z: 16512 }; Mag:I16x3 { x: 0, y: 0, z: 0 }

Thanks!

Create Button abstraction

The board has one user button. Provide access and abstraction to this.
It's connected to PA0

Provide access to magometer & accelerometer

There is a LSM303DLHC e-compass on board.
Provide access to this peripheral.

This periph also has an accelerometer.
Consider implementing the accelerometer trait.

Info about cargo-flash/cargo-embed

How do you think would it be helpful for newcomers to note in this repo or may be in discovery book about easiest way to try examples with discovery board:

cargo install cargo-flash
cargo flash --chip stm32f3 --example leds --connect-under-reset

I think it can help newcomers to to start as quick as they type only 3 commands.

Create `ActiveHighLed` and `ActiveLowLed` implementations of LED trait

Much like was done for with the button::hal, allow users to create their own LEDs from externally wired sources.

stm32f3-discovery/src/button/hal.rs

Lines 1 to 46 in d68ba0b

	use stm32f3xx_hal::hal::digital::v2::InputPin;
	pub trait Button {
	type Error;
	fn is_pressed(&self) -> Result<bool, Self::Error>;
	}
	pub struct ActiveHighButton<T>
	where
	T: InputPin,
	{
	pin: T,
	}
	impl<T: InputPin> ActiveHighButton<T> {
	pub fn new(pin: T) -> Self {
	ActiveHighButton { pin: pin }
	}
	}
	impl<T: InputPin> Button for ActiveHighButton<T> {
	type Error = <T as stm32f3xx_hal::hal::digital::v2::InputPin>::Error;
	fn is_pressed(&self) -> Result<bool, Self::Error> {
	self.pin.is_high()
	}
	}
	pub struct ActiveLowButton<T>
	where
	T: InputPin,
	{
	pin: T,
	}
	impl<T: InputPin> ActiveLowButton<T> {
	pub fn new(pin: T) -> Self {
	ActiveLowButton { pin: pin }
	}
	}
	impl<T: InputPin> Button for ActiveLowButton<T> {
	type Error = <T as stm32f3xx_hal::hal::digital::v2::InputPin>::Error;
	fn is_pressed(&self) -> Result<bool, Self::Error> {
	self.pin.is_low()
	}
	}

stm32f3-discovery/src/leds.rs

Lines 5 to 9 in d68ba0b

	pub trait Led {
	fn on(&mut self);
	fn off(&mut self);
	fn toggle(&mut self);
	}

Allow LED access via compass direction

Currently, the led abstraction allows access via their names (ld3, etc).
The board is also labeled with directions.
Allow users to access the Leds via the direction, North, South, East, West, etc.

Related: #4, #8.

Release 0.6

PR #36 updated the stm32fx hal.
There were breaking changes and since we re-export the hal, we also have breaking changes.
Release new version with release notes documenting the breaking change.

Add warnings for 2 tricky problems I had.

I had 2 problems with the examples which required non-obvious fixes.

1. To make OpenOCD work under Windows 10, I had to use a USB 2.0 port, not a USB 3.1 port.
2. To make ITM output work ,I had to solder over the SB10 solder bridge on the Discovery board.

Add ability to use `interrupt::enable` and `interrupt::clear` on arbitrary GPIO/EXTI lines

interrupt::enable and interrupt::clear are currently hard coded to work only for the user button.
Allow these to work for any interrupt the user may want to use on the board.

Also, add UserButton.interrupt_enable() and UserButton.interrupt_clear() methods?