The two devices that show up are associated with the same clock and data lines, they just have different chip select lines to allow you to multiplex two devices -- they cannot be used simultaneously.
On Mon, Nov 10, 2014 at 3:54 PM, <janszymanski12...@gmail.com> wrote: > Hi, > > Following the links: http://elinux.org/BeagleBone_Black_Enable_SPIDEV > and > http://www.nagavenkat.adurthi.com/2014/02/spi-communication-beaglebone-black-as-master-to-arduino-as-slave/ > I was able to make it work, but I have a SS too long (1.4ms) for my need. > For easy test connect MOSI and MISO with a wire (loopback) to eliminate > connection problem with you SPI slave. > Hope this will help. When you done, can you measure the timing a let me > know? > I can post you my code if you need it. > > Jan > > > On Tuesday, November 11, 2014 5:03:38 AM UTC+11, lambert...@gmail.com > wrote: >> >> Hi, >> >> I am trying to communicate with a device (ADS1299à by using the >> Beaglebone black but without success. First I have to enable spi dev >> entries in /dev. There are plenty of blog/tuto which are giving dtc file to >> generate our own dtbo. But dtc files seems to not be always the same. >> >> In fact I can see that there are already some dtbo files in /lib/firmware >> : >> root@beaglebone:~# ls /lib/firmware/ | grep SPI >> ADAFRUIT-SPI0-00A0.dtbo >> ADAFRUIT-SPI1-00A0.dtbo >> BB-SPIDEV0-00A0.dtbo >> BB-SPIDEV1-00A0.dtbo >> BB-SPIDEV1A1-00A0.dtbo >> >> So I want to use only SPI0 because I know that SPI1 is already used by >> HDMI. Can I used theses dtbo files ? Is it better to write my own ? It is >> quite strange, when I enable one of theses dtbo files, I get not only one >> but two entries in /dev ?? >> >> Currently I want to validate my wiring between the two boards. I found a >> piece of code to read the device id in register of the device though SPI. >> But when I try to read this register, I can only get 1 or only get 0 >> (depends of the dtbo files) >> >> Any advice of the good way to process here ? >> >> Thanks & Regards, >> Arthur. >> >> >> >> >> -- > 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 beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
