JC
JC
Updating my project today and get this warning ``` (HOST) WARN (BUG) location info is incomplete; it will be omitted from the output ``` Debug build works fine, release build...
Uses probe-run / defmt as the runner/logger combo for all examples. I see (after making all the changes...) probe-run now supports rtt-target so if that would be preferred I can...
Any remaining warnings lints should be in `examples/` and resolved by #297
Examples currently use a mix of logging methods (semi-hosting / RTT / ...?). it would make sense to standardise on one here. My past experience with semi-hosting has been "unpleasant"...
current master branch asserts that the buffer length for I2C::read and I2C::write is at least 1 and less than 256 (1..=255) write: https://github.com/stm32-rs/stm32l4xx-hal/blob/master/src/i2c.rs#L254 read: https://github.com/stm32-rs/stm32l4xx-hal/blob/master/src/i2c.rs#L308 A fairly common I2C operation...
closes #277 This uses a build script to generate internal conditional compilation gates. This allows keeping the cargo features clean, while internally being able to use readable checks like ```Rust...
As it currently stands, detection of device specific features is rather unwieldy (prone to repetition, potential errors, verbosity, ...). NOTE: for simplicity, I will use detection of ADC2 peripheral in...
Was just looking at adding ADC2/ADC3, but adc's are a fairly big target feature wise so a full list of features and implmentation status seems like a good starting point...
The const-ness of parent objects is being ignored Expected behaviour: https://godbolt.org/g/huR6Kg A const collection can't be modified through naive iteration, compiler error if this is attempted Current behaviour: ``` xlnt::workbook...
Should be a thing, but mode UI is right out of space. Not sure what I'm going to do here