the trait bound (avr_hal_generic::spi::Spi<Atmega, SPI, PB5, PB3, PB4, PB2>, ChipSelectPin<PB2>): embedded_hal::blocking::spi::write::Default<u8> is not satisfied

[sudokit]

the trait bound `(avr_hal_generic::spi::Spi<Atmega, SPI, PB5, PB3, PB4, PB2>, ChipSelectPin<PB2>): embedded_hal::blocking::spi::write::Default<u8>` is not satisfied the trait `embedded_hal::blocking::spi::write::Default<u8>` is implemented for `avr_hal_generic::spi::Spi<H, SPI, SCLKPIN, MOSIPIN, MISOPIN, CSPIN>` required because of the requirements on the impl of `_embedded_hal_blocking_spi_Write<u8>` for `(avr_hal_generic::spi::Spi<Atmega, SPI, PB5, PB3, PB4, PB2>, ChipSelectPin<PB2>)

Its kind of similar to #63, but it doesn't say that it is not implemented.

[Rahix]

Hello,

please provide your code to reproduce the error you got. It is impossible to provide proper help from this little information. You'll find that people are much more willing to help when you spend a bit more effort on your bug/issue reports :)

That said, the error complains that spi::write::Default is not implemented for a tuple type (Spi, ChipSelectPin). I assume you didn't destructure the return value from Spi::new(). It should look like this:

avr-hal/examples/arduino-uno/src/bin/uno-spi-feedback.rs

Lines 31 to 38 in 533159f

	let (mut spi, _) = arduino_hal::Spi::new(
	dp.SPI,
	pins.d13.into_output(),
	pins.d11.into_output(),
	pins.d12.into_pull_up_input(),
	pins.d10.into_output(),
	spi::Settings::default(),
	);

(The _ could also be a name like cs, so let (mut spi, mut cs) = ...;. It's the chip select pin, but not used in the example)

[Rahix]

Hm, maybe to make it more clear: Spi::new() doesn't return a Spi instance, but instead a tuple of Spi and the ChipSelectPin. See https://rahix.github.io/avr-hal/avr_hal_generic/spi/struct.Spi.html#method.new

What you're after is just the Spi instance, so you need to destructure the tuple.

[sudokit]

Hey,
Yeah sorry i got a little lazy writingt this issue. Destructuring it fixed the error. I was trying to get it to work with the ssd1306 driver and just thought that maybe it didn't work because of that destructuring.
Thanks!