Problem using ShushEngine alongside other SPI devices #5
Description
Hi,
I've been able to successfully try out the ShushEngine library to control a motor with a TMC5160-BOB. Separately I can also run a small OLED screen on a RPi, but I'm not able to run both on the RPi at the same time. I'm aiming to have the motor running and an RPM readout alongside, which I'll control from the same python script.
It seems, however, that this library is locking up the SPI (and I2C) busses from being used by other devices (I tested with Adafruit PiOLED and another SPI OLED screen, both based on ssd1306). I am running the two devices on separate SPI busses on RPi e.g SPI0.0 (motor) ad SPI1.0 (display).
I wonder if the library is keeping the driver/bus open and not releasing it for other use? I find that just enabling the single line 'include shush' is enough to stop the previously working display. I'm seeing error messages like unable to find device when trying with I2C. For example 'sudo i2cdetect -y 1' no longer can find the device and I have to reboot the pi to release the resources again.
I guess a workaround might be to try software SPI/I2C to get the display working, but I think this is something to look into so that it can be used alongside other devices on the RPi.
Thanks,