px4flow_bsp

Rust no_std embedded hal board support package for the PX4FLOW optical flow sensor hardware.

Usage

See the example to an example that has been tested with the PX4FLOW hardware.

Interrupt Handling

Currently you need to configure your application to forward interrupts from app-level interrupt handlers, ie:

/// should be called whenever DMA2 completes a transfer
#[interrupt]
fn DMA2_STREAM1() {
    dcmi::dma2_stream1_irqhandler();
}

/// should be called whenever DCMI completes a frame
#[interrupt]
fn DCMI() {
    dcmi::dcmi_irqhandler();
}

This assumes you are using the cortex-m-rt crate to construct your embedded application, and using its #[interrupt] to handle interrupts.

Status

Work in progress

• Does not overwrite the default PX4FLOW bootloader that typically ships with the board
• Example that sets up DCMI to read from the camera
• Support for spi2 (l3gd20 gyro)
• Support for i2c1 (offboard i2c communication)
• Support for i2c2 (MT9V034 configuration port, and eeprom)
• Support for USART2, USART3, and UART4 (sonar)
• Support for serial eeprom on i2c2
• Initial setup of DCMI peripheral
• Initial setup of DMA2
• Fully working DCMI->DMA2-> image buffer pipeline

Notes

• The only supported mode for debugging is RTT with the rttdebug feature. This is because the PX4FLOW v2.3 only makes the SWD interface available (no easy ITM solution).
• The breakout feature is intended for library development and debugging purposes. Currently it's setup to work with the "DevEBox STM32F4XX_M Ver:3.0" board, which does not include a l3gd20 gyro or eeprom, and eg the Arducam MT9V034 breakout board ("UC-396 RevA")
• This has been tested with the CUAV PX4FLOW v2.3. On this particular board, the SWD and SWCLK pads noted on the bottom of the board appear to be swapped

MCU Pin Map