Don't know, I don't have the hardware to connect to yet On Fri, Mar 6, 2015, 16:00 Matt Graham <matti...@gmail.com> wrote:
> It's been a while since I was tinkering with this, but as I recall, the > pin designations were as expected. > > Is your SPI not working? > > On Fri, Mar 6, 2015 at 4:55 AM, <axo...@gmail.com> wrote: > >> I see the same problems. Guys, will it work though using the pins >> described for spi0? >> >> 2015. február 22., vasárnap 5:18:34 UTC+1 időpontban Steve French a >> következőt írta: >> >>> Matt, >>> I agree!!! It is very confusing, especially when you are trying to >>> figure out which pin to probe!! >>> -frenchy >>> >>> On Thursday, January 23, 2014 at 12:18:57 PM UTC-5, Matt Graham wrote: >>>> >>>> >>>> I think I posted to the wrong section of the group. Apologies for this >>>> repost. >>>> >>>> Running the latest angstrom image, with update, upgrade. >>>> Installing BB-SPIDEV0 seems to produce /dev/spidev1 which doesn't seem >>>> right. >>>> I was expecting /dev/spidev0 based on this http://elinux.org/ >>>> BeagleBone_Black_Enable_SPIDEV#SPI0 >>>> >>>> Any ideas on this problem? >>>> >>>> root@beaglebone:~# find /dev -iname *spi* >>>> root@beaglebone:~# cat /sys/devices/bone_capemgr.*/slots >>>> 0: 54:PF--- >>>> 1: 55:PF--- >>>> 2: 56:PF--- >>>> 3: 57:PF--- >>>> 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G >>>> 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI >>>> root@beaglebone:~# echo BB-SPIDEV0 > /sys/devices/bone_capemgr.*/slots >>>> root@beaglebone:~# cat /sys/devices/bone_capemgr.*/slots >>>> 0: 54:PF--- >>>> 1: 55:PF--- >>>> 2: 56:PF--- >>>> 3: 57:PF--- >>>> 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G >>>> 5: ff:P-O-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI >>>> 7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-SPIDEV0 >>>> root@beaglebone:~# find /dev -iname *spi* >>>> /dev/spidev1.0 >>>> /dev/spidev1.1 >>>> root@beaglebone:~# >>>> >>> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to a topic in the >> Google Groups "BeagleBoard" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/beagleboard/4IeImY8I4-g/unsubscribe. >> To unsubscribe from this group and all its topics, 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 a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/4IeImY8I4-g/unsubscribe. > To unsubscribe from this group and all its topics, 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.
