Replies: 1 comment 7 replies
-
Yes (it won't work) for output pins, no for input pins like MISO.
The proper way would be to drop the spi driver. |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm developing on a device with a limited number of GPIO's available.
I'm left with single GPIO free and the rest are used by a SPI device.
I want to add another device which requires two GPIO's and there are two ways to use it, either just using GPIO 'bit banging', or some hack to use another SPI with those pins (it's not really a SPI device but that technique seem to work).
I don't need both devices together, and I know when to switch between them.
I assume that when the SPI device takes over the GPIO, even if I unsafely get access to the GPIO, setting it to high/low, won't work, right? Because the ESP32 internally gave the control over the GPIO to the SPI.
If my assumption is correct, what's the proper way to give the SPI a GPIO, take it away, then give back?
Unsafe options are also acceptable in this case, since I'm just out of GPIO's.
Maybe control the esp32 behind the 'Rust scenes' in such case?
Beta Was this translation helpful? Give feedback.
All reactions