-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can I set MOSI default HIGH, and set CS low separately for ~1ms? #59
Comments
Hi, Thank you very much, |
I'm having similar issues. Any solution? |
You may be able to get the same effect as MOSI default HIGH (also called "active low") by inverting the data you're sending (i.e. flipping each bit before transmission, e.g. converting 0b00110011 to 0b11001100). You can do this easily; if |
As far as setting the CS pin to wake up the chip, will it work if you just send a byte (or a few bytes) of non-data (e.g. 0x00 or 0xFF etc.) first? My cursory inspection of the datasheet implies that for the LTC6804, that should work, although I haven't taken the time to fully understand the function of the device. |
I can confirm that I got this working with help of additional IO line witch will force MOSI line rest to HIGH. Simple solution with 2 shotky diodes was enough to achieve this. |
Hello,
I am doing a project using RPi to talk with Linear LTC6804 (battery monitoring chip) in SPI. I am using Python with spidev module to control SPI communication. However, it looks like the default MOSI pin signal is LOW, while the LTC6804 requests MOSI default HIGH.
See below in good communication the LTC6804 requests MOSI default HIGH. Also before sending request on MOSI, the CS needs to be set LOW for 0.3ms for waking up the chip.
See below in bad communication with LTC6804 using functions from spidev with MOSI default LOW. I cannot find how to set MOSI pin default HIGH with spidev.
So see someone can help out:
I want to get exactly the same output from RPi as the first attached screenshot.
Thank you!
The text was updated successfully, but these errors were encountered: