wheezy is a bit long in the tooth now - and I don't know what state the kernel is in for Wheezy. I'd strongly recommend upgrading (or starting from scratch) with Raspbian. It's still wheezy, but compiled to match the Pi's ARM architecture and it kept up to date kernel wise, etc.bass0324 wrote:I am trying to use the spi port on the Raspbian OS for the Pi but I am unable to see spidev in /dev/. Is there anything I can do to get this to show up? I tried a modprobe spidev, also rpi-update and neither worked. I know everything I have found online about the spi bus was using the Debian weezy version which I am assuming is different, but i figure it shouldn't matter. Any help would be greatly appreciated.
It certianly should do. Very odd!bass0324 wrote:When I do "sudo modprobe spidev" it returns nothing so I assume it goes through just fine. I have also tried lsmod in /dev/ and also ls -l /dev/spi* and neither of them could find anything spi related in the /dev folder. I am not seeing I2C or SPI at all. Also, I just redid my Raspbian image based off the most recent one released by eben on the 28th. So I am not sure why this is happening at all since the newest kernel should have support for it built in.
Code: Select all
gordon @ pi2: ls -l /dev/spi* ls: cannot access /dev/spi*: No such file or directory gordon @ pi2: gpio load spi gordon @ pi2: ls -l /dev/spi* crw------- 1 gordon gordon 153, 0 Nov 2 14:59 /dev/spidev0.0 crw------- 1 gordon gordon 153, 1 Nov 2 14:59 /dev/spidev0.1 gordon @ pi2: lsmod | grep spi spidev 5136 0 spi_bcm2708 4401 0
Sorry, no record for digging up long deceased topicsdotgreg wrote:To help, I solved this issue with Rpi-config,
Thanks @dotgreg for that usefull hint!by dotgreg » Thu Jul 31, 2014 8:50 am
To help, I solved this issue with Rpi-config,
-> do "sudo raspi-config"
-> Go to "Advanced Options"
-> Go to "A5 SPI" option
-> Click on yes when asked if you wanted to load the SPI kernel by default
-> reboot and you are done