Alan: Not sure if you got it to work, but the following worked for me. I am using a BBB with Linux beaglebone 3.8.13 #1 SMP Wed Sep 4 09:09:32 CEST 2013 armv7l GNU/Linux I compiled your spi-test.c program and connected d0 to d1 and it ran perfectly.
root@beaglebone:~# ./BB-SPiTest cmd: 0x02 0x12 0x34 0x56 rsp: 0x02 0x12 0x34 0x56 The main difference is that I used SPI0 instead of SPI1. I used the device tree overlay shown here: http://elinux.org/BeagleBone_Black_Enable_SPIDEV This web page shows how to use SPI1 first, and towards the end of the page shows the dts file for SPI0 (the one I tried). My guess is that you may still having some problems with the HDMI using those pins. Martin On Monday, May 6, 2013 7:40:38 AM UTC-6, Alan Backlund wrote: > > I have been trying to get SPI1 working on my new BB-Black, the output > works but the input always reads 0. > > The first thing I discovered is that SPI1 is used by the HDMI interface. I > created a modified am335x-bone-common.dtsi with the hdmi sections removed. > Putting the new am335x-boneblack.dtb into /boot and rebooting got rid of > the SPI1 signals. I then loaded a new device tree that enables spidev (See > bone-test.dts below). /dev/spidev1.0 appeared. > > I tried running a test program that transferred a few bytes with spi1_d0 > connected to spi_d1. The output of this program on my old BB White loaded > with > Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.05-beaglebone-2012.11.22.img, > using /dev/spidev2.0 was: > cmd: 0x02 0x12 0x34 0x56 > rsp: 0x02 0x12 0x34 0x56 > > with > Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.04.13.img on > my BB Black it's always: > cmd: 0x02 0x12 0x34 0x56 > rsp: 0x00 0x00 0x00 0x00 > > Looking at the signals with a logic analyser showed that the output > (SPI1_D0) is correct. > > I then moved the micro SD card from my BB Black to my BB White and > discovered that it does the same thing, so the problem is not the Black but > in the 2012.11.22 image (the only one that supports the Black). The problem > seems to me be in the spidev driver or in the underlying hardware driver. > > Any ideas? > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
