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 noticed in the README that you reference both SPI and HSPI (spi_no: SPI or HSPI) but in your blog you recommended against SPI use and indicated no further information would be forthcoming due to the complexities of SPI usage. I was wondering if the existence of options for spi_no indicates that your library works without issue with SPI given the constraint that it is shared?
I ask because my use case for SPI requires very infrequent use and PWM usage so I would like to free up the GPIO12-GPIO15 pins on an ESP-12F module.
Thanks,
Jason
The text was updated successfully, but these errors were encountered:
Hi,
I noticed in the README that you reference both SPI and HSPI (spi_no: SPI or HSPI) but in your blog you recommended against SPI use and indicated no further information would be forthcoming due to the complexities of SPI usage. I was wondering if the existence of options for spi_no indicates that your library works without issue with SPI given the constraint that it is shared?
I ask because my use case for SPI requires very infrequent use and PWM usage so I would like to free up the GPIO12-GPIO15 pins on an ESP-12F module.
Thanks,
Jason
The text was updated successfully, but these errors were encountered: