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

spidev module doesn't load; no /dev/spi* in core/linux-raspberrypi-latest 3.13.1-1 #526

Closed
hugoferreira opened this issue Feb 8, 2014 · 7 comments

Comments

@hugoferreira
Copy link

SPI support, present in core/linux-raspberrypi 3.10.29-1, hasn't been working at least since 3.12.

@ghost
Copy link

ghost commented Apr 18, 2014

Might be the same issue I'm having. SPI (/dev/spi) using spidev only works when spidev is not a module but is statically built into the kernel. the spi-bcm2708 can be used as a module though.

#ifdef CONFIG_BCM2708_SPIDEV

@P33M
Copy link
Contributor

P33M commented Jul 14, 2015

spidev is working on recent firmware, but not enabled by default. The recommended method to enable this by default is to add the module name to /etc/modules.

@P33M P33M closed this as completed Jul 14, 2015
@pelwell
Copy link
Contributor

pelwell commented Jul 14, 2015

With a DT-enabled kernel, enable the spi interface by adding dtparam=spi=on to config.txt. This will also cause the spidev module to be loaded (but see #1054 ...)

@xevilmaxx
Copy link

xevilmaxx commented Jul 28, 2021

Hi,
Recently had some issues with SPI module too.
OS used: Debian10 arm64
Soc: Raspberry Pi 3 B v1.2

As many sugested, i added dtparam=spi=on to config.txt in: /boot/firmware/
but after several tries (including adding more specific dtparams) and kernel changes, nothing worked.

Solution:

  1. Backup/Move *.dtb from /boot/firmware/ into /boot/firmware/oldDtbs
  2. Clone this repo: https://github.com/raspberrypi/firmware/tree/master/boot
  3. Copy *.dtb and overlays folder into: /boot/firmware/
  4. sudo shutdown -r now
  5. Check if SPI si ok: ls /dev/spi*

@transplier
Copy link

I had the same issue with my old B Rev. 2. Attempting the above suggestions did not fix it. Copying over the official firmware as per the previous comment unfortunately crashes the board on boot.

@pelwell
Copy link
Contributor

pelwell commented Jan 5, 2022

Install a fresh RPiOS to a spare card and verify that it works as expected. If it does (and it will), your issue must be the result of some unknown combination of kernel + firmware + Device Tree files, and an issue from 2015 is not the right venue for getting some help - try the Raspberry Pi Forums.

@transplier
Copy link

OK. This is a fresh install of Debian 10, but I'll take this elsewhere.

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