You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have implemented an example for the MAX 7219 Chip.
This chip uses 16Bit SPI which causes some problems on Raspberry Pi and possibly other devices because their SPI driver only supports 8/9 Bits.
To make this chip work I would like to implement an extended mraa_spi_bit_per_word function that takes a GPIO Pin as an additional parameter. This GPIO Pin then takes over the functionality of CS and makes it possible to have 16/32 Bit transfers on those limited devices.
I have also already implemented helper functions to send 16/32 Bit values via SPI, those functions and the mraa_spi_transfer_buf can get modified to support this extra CS seamlessly.
Any objections?
The text was updated successfully, but these errors were encountered:
I have implemented an example for the MAX 7219 Chip.
This chip uses 16Bit SPI which causes some problems on Raspberry Pi and possibly other devices because their SPI driver only supports 8/9 Bits.
To make this chip work I would like to implement an extended mraa_spi_bit_per_word function that takes a GPIO Pin as an additional parameter. This GPIO Pin then takes over the functionality of CS and makes it possible to have 16/32 Bit transfers on those limited devices.
I have also already implemented helper functions to send 16/32 Bit values via SPI, those functions and the mraa_spi_transfer_buf can get modified to support this extra CS seamlessly.
Any objections?
The text was updated successfully, but these errors were encountered: