Austin Glaser
Austin Glaser
It's unfortunate that there's no nonblocking variant of the `i2c` HAL traits -- but that could easily change. My first impression is that it should look something like: ```Rust //!...
# Signed count It's unclear from the documentation whether the intended use is an unsigned result from `count()`, with `direction()` indicating which way the system has moved from its zero...
Many MCUs (the STM32s especially) implement a plethora of different output options for their GPIO pins. A driver generally has specific output requirements for its pins -- but enforcing these...
The CLI usage message doesn't give an overview of the available flags, nor does it provide a way (that I could discover) to pass a help flag. Furthermore, [the documentation](https://docs.rs/cargo-lock/4.0.1/cargo_lock/)...
Closes #13 This implements the first option (automatic clearing errors on detection) discussed in the above issue. It hasn't yet been tested on actual hardware -- I likely won't be...
Depending on fpclk, there are only a few selectable SPI frequencies. However, the SPI init function allows selection of an arbitrary frequency, and then rounds to the closest available. This...
My reading of the current error detection code in the SPI module seems to suggest that if an error occurs it will never be cleared. The [code in question](https://github.com/japaric/stm32f30x-hal/blob/d51a39b0ad1665c04ecead9ab148a5520dca139b/src/spi.rs#L158): ```Rust...
When using parametrized tests with Ceedling, I often run into situations something like the following: ```C //error.h typedef enum { NO_ERROR = 0, ERROR_FOO, ERROR_BAR, } error_t; ``` ```C //...