gotitservices
2016-10-13, 19:18
So SPI isn't working for me, I've been searching and searching, and trying different things.
I have the spi_bcm2835 loaded, but if I load spidev, it doesn't show up with lsmod, and I don't have any /dev/spidev* devices.
I have spi under sys:
find /sys/ -iname 'spi*'
/sys/bus/spi
/sys/bus/spi/drivers/spidev
/sys/bus/platform/drivers/spi-bcm2835
/sys/class/spi_master
/sys/class/spidev
/sys/firmware/devicetree/base/soc/spi@7e204000
/sys/firmware/devicetree/base/soc/spi@7e204000/spidev@0
/sys/firmware/devicetree/base/soc/spi@7e204000/spidev@0/spi-max-frequency
/sys/firmware/devicetree/base/soc/spi@7e204000/spidev@1
/sys/firmware/devicetree/base/soc/spi@7e204000/spidev@1/spi-max-frequency
/sys/firmware/devicetree/base/soc/gpio@7e200000/spi0_pins
/sys/firmware/devicetree/base/__symbols__/spi0
/sys/firmware/devicetree/base/__symbols__/spi0_pins
/sys/firmware/devicetree/base/aliases/spi0
/sys/firmware/devicetree/base/__overrides__/spi
/sys/kernel/debug/tracing/events/spi
/sys/kernel/debug/tracing/events/spi/spi_master_idle
/sys/kernel/debug/tracing/events/spi/spi_master_busy
/sys/kernel/debug/tracing/events/spi/spi_message_submit
/sys/kernel/debug/tracing/events/spi/spi_message_start
/sys/kernel/debug/tracing/events/spi/spi_message_done
/sys/kernel/debug/tracing/events/spi/spi_transfer_start
/sys/kernel/debug/tracing/events/spi/spi_transfer_stop
/sys/module/spi_bcm2835
/sys/module/spidev
I did a bunch more searching and came up with an interesting post somewhere on the web that said he couldn't get SPI working unless spidev was compiled into the kernel.
Does anyone else have spi working? do I need to compile it into the kernel?
I noticed by default the config.txt file doesn't exist, and when I created it, it doesn't seem to make a difference. does Kali use this file? are there other ways to pass parameters to the kernel on boot?
I'm compiling on the device right now but running out of space so I'll probably setup an environment to cross compile it when I have time, if I have to.
Thanks for any help in advance.
I have the spi_bcm2835 loaded, but if I load spidev, it doesn't show up with lsmod, and I don't have any /dev/spidev* devices.
I have spi under sys:
find /sys/ -iname 'spi*'
/sys/bus/spi
/sys/bus/spi/drivers/spidev
/sys/bus/platform/drivers/spi-bcm2835
/sys/class/spi_master
/sys/class/spidev
/sys/firmware/devicetree/base/soc/spi@7e204000
/sys/firmware/devicetree/base/soc/spi@7e204000/spidev@0
/sys/firmware/devicetree/base/soc/spi@7e204000/spidev@0/spi-max-frequency
/sys/firmware/devicetree/base/soc/spi@7e204000/spidev@1
/sys/firmware/devicetree/base/soc/spi@7e204000/spidev@1/spi-max-frequency
/sys/firmware/devicetree/base/soc/gpio@7e200000/spi0_pins
/sys/firmware/devicetree/base/__symbols__/spi0
/sys/firmware/devicetree/base/__symbols__/spi0_pins
/sys/firmware/devicetree/base/aliases/spi0
/sys/firmware/devicetree/base/__overrides__/spi
/sys/kernel/debug/tracing/events/spi
/sys/kernel/debug/tracing/events/spi/spi_master_idle
/sys/kernel/debug/tracing/events/spi/spi_master_busy
/sys/kernel/debug/tracing/events/spi/spi_message_submit
/sys/kernel/debug/tracing/events/spi/spi_message_start
/sys/kernel/debug/tracing/events/spi/spi_message_done
/sys/kernel/debug/tracing/events/spi/spi_transfer_start
/sys/kernel/debug/tracing/events/spi/spi_transfer_stop
/sys/module/spi_bcm2835
/sys/module/spidev
I did a bunch more searching and came up with an interesting post somewhere on the web that said he couldn't get SPI working unless spidev was compiled into the kernel.
Does anyone else have spi working? do I need to compile it into the kernel?
I noticed by default the config.txt file doesn't exist, and when I created it, it doesn't seem to make a difference. does Kali use this file? are there other ways to pass parameters to the kernel on boot?
I'm compiling on the device right now but running out of space so I'll probably setup an environment to cross compile it when I have time, if I have to.
Thanks for any help in advance.