I'm working with a Raspberry Pi5, and while connecting to another device, I may have shorted something.
I can still get reasonable signals out of my other spi outputs (Clock/ chip select), but when I run the Spidev test tool from the Linux kernel, I get a constant high on MOSI when CS is activated. Before CS turns on, MOSI is at zero. I am verifying this with my logic analyzer, scope, and by just doing a loopback using a jumper wire between MOSI and MISO.
Are there any alternative explanations, such as SD card memory corruption or some other debugging steps I can do?
I can still get reasonable signals out of my other spi outputs (Clock/ chip select), but when I run the Spidev test tool from the Linux kernel, I get a constant high on MOSI when CS is activated. Before CS turns on, MOSI is at zero. I am verifying this with my logic analyzer, scope, and by just doing a loopback using a jumper wire between MOSI and MISO.
Are there any alternative explanations, such as SD card memory corruption or some other debugging steps I can do?
Statistics: Posted by Randomusernames — Wed Jul 03, 2024 11:22 pm — Replies 0 — Views 15