Ok, so are these modules loaded ? william@beaglebone:~/dev$ lsmod | grep spi spidev 7523 0 spi_omap2_mcspi 11148 0
I show . . . william@beaglebone:~/dev$ ls /dev | grep spi spidev1.0 spidev1.1 spidev2.0 spidev2.1 I am however using Charles' universal IO, and loading univ-all at boot plus cape_universal=enabled in /boot/uEnv.txt. I am using a newer kernel version however . . . william@beaglebone:~/dev$ uname -r 4.4.14-ti-r34 One thing you can check in /boot/uEnv.txt though is to make sure that this line: cmdline=coherent_pool=1M quiet cape_universal=enable is commented out. Or at east remove the cape_universal=enable part is removed. On Wed, Jul 20, 2016 at 7:46 AM, William Hermans <[email protected]> wrote: > So, this is the file I remember seeing Robert talk about: > https://github.com/RobertCNelson/dtb-rebuilder/blob/4.4.x/src/arm/am33xx-overlay-edma-fix.dtsi > > Which if we look at this it's already loaded . . . > https://github.com/RobertCNelson/dtb-rebuilder/blob/4.4-ti/src/arm/am335x-boneblack-overlay.dts#L12 > > investigating further . . . > > On Wed, Jul 20, 2016 at 7:38 AM, William Hermans <[email protected]> > wrote: > >> Hello William, >>> >>> >>> do you mean to configure SPI in the am335x-boneblack-overlay.dts? >>> an set spi module to be set as built-in in the kernel? >>> >>> Can you explain a bit? Isn't clear for me >>> >> >> Yes, sorry I was not clearer, however I've not personal hands on, only >> remember Robert mentioning it before. However, if we search the board file >> for "SPI", and include for *something* SPI _ dtsi should stand out. Let me >> see if I can find something quicly. >> >> On Wed, Jul 20, 2016 at 7:35 AM, malkowki <[email protected]> >> wrote: >> >>> Hello William, >>> >>> >>> do you mean to configure SPI in the am335x-boneblack-overlay.dts? >>> an set spi module to be set as built-in in the kernel? >>> >>> Can you explain a bit? Isn't clear for me. >>> >>> Le mercredi 20 juillet 2016 15:45:31 UTC+2, William Hermans a écrit : >>>> >>>> >>>> I have also attached my Kernel Config file and the bootloog. >>>> Is Anyone to guide me how to solve this issue? >>>> >>>> >>>> I do believe that SPI has to be loaded earlier in the boot stage. I >>>> seem to recall this fix for this to be loading SPI from within the main >>>> board file. >>>> >>>> On Wed, Jul 20, 2016 at 5:33 AM, malkowki <[email protected]> wrote: >>>> >>>>> Hi everyone, >>>>> >>>>> I am runing Linux version 4.1.21-bone-rt-r20 from Robert Nelson >>>>> repository and I have the same issue. >>>>> The DTS seems ok but the SPI module does't appear under /dev/. >>>>> my uEnv.txt look like this: >>>>> uname_r=4.1.21-bone-rt-r20 >>>>> optargs=quiet drm.debug=7 capemgr.disable_partno=BB-BONELT-HDMI,BB- >>>>> BONELT-HDMIN >>>>> cape_enable=bone_capemgr.enable_partno=BB-SPI0-01 >>>>> If I do cat $SLOTS I have : >>>>> 0: PF---- -1 >>>>> 1: PF---- -1 >>>>> 2: PF---- -1 >>>>> 3: PF---- -1 >>>>> 4: P-O-L- 0 Override Board Name,00A0,Override Manuf,BB-SPI0-01 >>>>> >>>>> >>>>> I have also attached my Kernel Config file and the bootloog. >>>>> Is Anyone to guide me how to solve this issue? >>>>> >>>>> thanks, >>>>> >>>>> >>>>> Le samedi 27 juillet 2013 23:44:28 UTC+2, Nigel Magnay a écrit : >>>>>> >>>>>> >>>>>> I'm trying to activate SPI on a BBB. I think it's nearly there, save >>>>>> for a lack of anything in /dev, which is mysterious. >>>>>> >>>>>> I'm trying for SPI0 (I understand SPI1 requires HDMI deactivation). >>>>>> >>>>>> Brand new A5C board, uname -a is >>>>>> Linux beaglebone 3.8.13 #1 SMP Tue Jun 18 02:11:09 EDT 2013 armv7l >>>>>> GNU/Linux >>>>>> >>>>>> Followed http://elinux.org/BeagleBone_Black_Enable_SPIDEV, save for >>>>>> - my /lib/firmware already had BB-SPI0, so I used that >>>>>> - I didn't understand "Go to My Computer>BeagleBone Getting >>>>>> Started>". The mounted USB drive device is read-only. I modified the >>>>>> uEnv.txt in /boot, seems to work. >>>>>> >>>>>> Slots shows it there: >>>>>> root@beaglebone:~# cat /sys/devices/bone_capemgr.8/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-SPI0 >>>>>> >>>>>> root@beaglebone:~# cat >>>>>> /sys/kernel/debug/pinctrl/44e10800.pinmux/pingroups >>>>>> registered pin groups: >>>>>> >>>>>> .... >>>>>> group: pinmux_bb_spi0_pins >>>>>> pin 84 (44e10950) >>>>>> pin 85 (44e10954) >>>>>> pin 86 (44e10958) >>>>>> pin 87 (44e1095c) >>>>>> ... >>>>>> >>>>>> It appears in the dmesg output >>>>>> root@beaglebone:/dev# dmesg |grep SPI >>>>>> [ 0.000000] Kernel command line: console=ttyO0,115200n8 quiet >>>>>> drm.debug=7 capemgr.enable_partno=BB-SPI0 root=/dev/mmcblk0p2 ro >>>>>> rootfstype=ext4 rootwait >>>>>> [ 0.399220] bone-capemgr bone_capemgr.8: enabled_partno >>>>>> part_number 'BB-SPI0', version 'N/A' >>>>>> [ 0.399293] bone-capemgr bone_capemgr.8: slot #7: 'Override Board >>>>>> Name,00A0,Override Manuf,BB-SPI0' >>>>>> [ 0.404238] bone-capemgr bone_capemgr.8: loader: before slot-7 >>>>>> BB-SPI0:00A0 (prio 0) >>>>>> [ 0.404261] bone-capemgr bone_capemgr.8: loader: check slot-7 >>>>>> BB-SPI0:00A0 (prio 0) >>>>>> [ 0.404286] bone-capemgr bone_capemgr.8: loader: after slot-7 >>>>>> BB-SPI0:00A0 (prio 0) >>>>>> [ 0.404315] bone-capemgr bone_capemgr.8: slot #7: Requesting part >>>>>> number/version based 'BB-SPI0-00A0.dtbo >>>>>> [ 0.404345] bone-capemgr bone_capemgr.8: slot #7: Requesting >>>>>> firmware 'BB-SPI0-00A0.dtbo' for board-name 'Override Board Name', >>>>>> version >>>>>> '00A0' >>>>>> [ 0.404401] bone-capemgr bone_capemgr.8: slot #7: dtbo >>>>>> 'BB-SPI0-00A0.dtbo' loaded; converting to live tree >>>>>> [ 0.409351] bone-capemgr bone_capemgr.8: loader: done slot-7 >>>>>> BB-SPI0:00A0 (prio 0) >>>>>> >>>>>> >>>>>> But no /dev/spi*. Am I expected to mkdev for that? What am I missing ? >>>>>> >>>>> -- >>>>> 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]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/beagleboard/7e96f063-dbbd-4212-9911-855a6f2ff666%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/beagleboard/7e96f063-dbbd-4212-9911-855a6f2ff666%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> 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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/beagleboard/ea9fd8af-670a-4ad9-9c5e-49f9b37f20a4%40googlegroups.com >>> <https://groups.google.com/d/msgid/beagleboard/ea9fd8af-670a-4ad9-9c5e-49f9b37f20a4%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORqdYBrLshvh_SOKmVbv-TekwxAGAX6yD3Mzh70UKgHc%3Dw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
