Hello I had a similar issue as noted here : https://groups.google.com/forum/#!topic/beagleboard/gOynYr8fgns
I found I could not mux the pins by loading the overlay from the command line *BUT* it did work when I loaded the overlay via boot/uEnv.txt I still don't know why !!! On Friday, 25 March 2016 18:12:02 UTC+1, Le Costaouec Vincent wrote: > > I'm confused because I recheck the wired configuration. I also tried on a > second beagleboneblack with the same configuration. > So I'm lost. For me it still look like that the problem came from the pin > mux. > In fact > # cat $PINS | grep '990\|998\|994\|99c' > pin 100 (44e10990.0) 00000027 pinctrl-single > pin 101 (44e10994.0) 00000027 pinctrl-single > pin 102 (44e10998.0) 00000027 pinctrl-single > pin 103 (44e1099c.0) 00000027 pinctrl-single > This mean that the pins are not correctly configure, in fact they should > be configure at 0x33 0x33 0x13 and 0x13, isn't it ? > And since I started configuring caps and pinmux it is the only time It > doesn't correspond with the dts. > > # dmesg | grep bone > [ 0.000000] Linux version 4.1.18-bone20 (lecostaouec@mppdev) (gcc > version 4.9.3 20150413 (prerelease) (Linaro GCC 4.9-2015.05) ) #4 Fri Mar > 18 15:16:19 CET 2016 > [ 0.000000] Kernel command line: console=ttyO0,115200n8 > bone_capemgr.enable_partno=BB-SPIDEV1 root=/dev/mmcblk0p1 ro > rootfstype=ext4 rootwait > [ 3.998684] usb usb1: Manufacturer: Linux 4.1.18-bone20 musb-hcd > [ 4.349285] bone_capemgr bone_capemgr: Baseboard: > 'A335BNLT,00C0,4414BBBK9699' > [ 4.356616] bone_capemgr bone_capemgr: > compatible-baseboard=ti,beaglebone-black - #slots=4 > [ 4.422658] bone_capemgr bone_capemgr: slot #0: No cape found > [ 4.482655] bone_capemgr bone_capemgr: slot #1: No cape found > [ 4.542654] bone_capemgr bone_capemgr: slot #2: No cape found > [ 4.602654] bone_capemgr bone_capemgr: slot #3: No cape found > [ 4.608439] bone_capemgr bone_capemgr: enabled_partno PARTNO > 'BB-SPIDEV1' VER 'N/A' PR '0' > [ 4.616751] bone_capemgr bone_capemgr: slot #4: override > [ 4.622088] bone_capemgr bone_capemgr: Using override eeprom data at > slot 4 > [ 4.629091] bone_capemgr bone_capemgr: slot #4: 'Override Board > Name,00A0,Override Manuf,BB-SPIDEV1' > [ 4.638497] bone_capemgr bone_capemgr: initialized OK. > [ 4.645406] bone_capemgr bone_capemgr: slot #4: dtbo > 'BB-SPIDEV1-00A0.dtbo' loaded; overlay id #0 > > # cat /proc/cmdline > console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-SPIDEV1 > root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait > > > The other issue could be that we are not using exatly the same version of > the kernel > # uname -ar > Linux beagle01 4.1.18-bone20 #4 Fri Mar 18 15:16:19 CET 2016 armv7l > GNU/Linux > > Or I'm I wrong and 4.1.18-ti-r55 is the same as 4.1.18-bone20 ? > Thanks for your time > > > Le vendredi 25 mars 2016 16:49:55 UTC+1, RobertCNelson a écrit : >> >> On Fri, Mar 25, 2016 at 10:01 AM, Le Costaouec Vincent >> <[email protected]> wrote: >> > I tried directly by copying and past this one, and I had still the same >> > answer. In addition I have tried to monitor the different signal on the >> > scope, nothing. >> > Moreover, nothing new appears on the dmesg. >> >> Yeah, double check your wires, it works as-is... >> >> root@beaglebone:~# ./spidev_test -D /dev/spidev2.1 >> spi mode: 0 >> bits per word: 8 >> max speed: 500000 Hz (500 KHz) >> >> FF FF FF FF FF FF >> 40 00 00 00 00 95 >> FF FF FF FF FF FF >> FF FF FF FF FF FF >> FF FF FF FF FF FF >> DE AD BE EF BA AD >> F0 0D >> root@beaglebone:~# ./spidev_test -D /dev/spidev2.0 >> spi mode: 0 >> bits per word: 8 >> max speed: 500000 Hz (500 KHz) >> >> FF FF FF FF FF FF >> 40 00 00 00 00 95 >> FF FF FF FF FF FF >> FF FF FF FF FF FF >> FF FF FF FF FF FF >> DE AD BE EF BA AD >> F0 0D >> >> root@beaglebone:~# cat /proc/cmdline >> console=tty0 console=ttyO0,115200n8 >> bone_capemgr.enable_partno=BB-SPIDEV1 root=/dev/mmcblk0p1 >> rootfstype=ext4 rootwait coherent_pool=1M quiet cape_universal=enable >> root@beaglebone:~# uname -r >> 4.1.18-ti-r55 >> >> root@beaglebone:~# dmesg | grep bone >> [ 0.000000] Kernel command line: console=tty0 >> console=ttyO0,115200n8 bone_capemgr.enable_partno=BB-SPIDEV1 >> root=/dev/mmcblk0p1 rootfstype=ext4 rootwait coherent_pool=1M quiet >> cape_universal=enable >> [ 3.426727] bone_capemgr bone_capemgr: Baseboard: 'A335BNLT, >> ,BBG115096609' >> [ 3.426755] bone_capemgr bone_capemgr: >> compatible-baseboard=ti,beaglebone-black - #slots=4 >> [ 3.477193] bone_capemgr bone_capemgr: slot #0: No cape found >> [ 3.537209] bone_capemgr bone_capemgr: slot #1: No cape found >> [ 3.597174] bone_capemgr bone_capemgr: slot #2: No cape found >> [ 3.657179] bone_capemgr bone_capemgr: slot #3: No cape found >> [ 3.662979] bone_capemgr bone_capemgr: enabled_partno PARTNO >> 'BB-SPIDEV1' VER 'N/A' PR '0' >> [ 3.662991] bone_capemgr bone_capemgr: slot #4: override >> [ 3.663006] bone_capemgr bone_capemgr: Using override eeprom data at >> slot 4 >> [ 3.663021] bone_capemgr bone_capemgr: slot #4: 'Override Board >> Name,00A0,Override Manuf,BB-SPIDEV1' >> [ 3.663322] bone_capemgr bone_capemgr: initialized OK. >> [ 3.671575] bone_capemgr bone_capemgr: slot #4: dtbo >> 'BB-SPIDEV1-00A0.dtbo' loaded; overlay id #0 >> [ 11.231817] LUN: removable file: >> /var/cache/doc-beaglebone-getting-started/beaglebone-getting-started-2015-12-04.img >> >> >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> > -- 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/d/optout.
