Skip to content
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

Issues with the latest version of Raspbian jessie #29

Open
danbuntu opened this issue Jun 27, 2016 · 4 comments
Open

Issues with the latest version of Raspbian jessie #29

danbuntu opened this issue Jun 27, 2016 · 4 comments

Comments

@danbuntu
Copy link

The newer version of Raspbian have switched to using dttree when enabling SPI. When you do this upgrade this library stops working. Running the Read.py example just sits there.

@EECSdude
Copy link

Activity here: raspberrypi/linux#1547

but no solution yet.

@Jbithell
Copy link

+1 - Having huge issues with the latest release and SPI

@mab5vot9us9a
Copy link

If you take a look at Issue #1547, there is a workaround now!

When cloning the SPI-Py library, changing '.cs_change = 1' to '.cs_change = 0' (line 189 in spi.c) before running sudo python setup.py install fixes the issues I had. Alternatively you can also clone my fork of this library https://github.com/mab5vot9us9a/SPI-Py, so you don't have to make the changes yourself.

Also make sure you have the latest kernel (>= 4.4.14), because it fixes a bug in earlier versions (see Issue #1547).
You can check your version using:

uname -a | sed -E "s/.*([0-9]+\.[0-9]+\.[0-9]+)-v.*/\1/"

If you need to update your kernel, use sudo rpi-update. If it's not yet installed, do so using sudo apt-get install rpi-update.

@thijstriemstra
Copy link

thijstriemstra commented Sep 9, 2016

@mab5vot9us9a's change was also fixed in SPI-Py master so that fork isn't necessary anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants