Additional information: I seem to recall there was an issue with SPI loading at boot. This had something to do with having to enable the spi software module in main board overlay file. Of which there has been several posts over the last few months. So see those for the exact details. So basically . . .
*root@beaglebone:~#* dmesg |grep SPI [ 47.792110] bone_capemgr bone_capemgr: part_number 'BB-SPIDEV0', version 'N/A' [ 47.802326] bone_capemgr bone_capemgr: slot #4: 'Override Board Name,00A0,Override Manuf,BB-SPIDEV0' [ 47.826377] bone_capemgr bone_capemgr: slot #4: dtbo 'BB-SPIDEV0-00A0.dtbo' loaded; overlay id #0 There two modules must be loaded at boot, through the main board overlay file: *root@beaglebone:~#* lsmod |grep spi spidev 7564 0 spi_omap2_mcspi 11588 0 Here is the include file: https://github.com/RobertCNelson/dtb-rebuilder/blob/4.4-ti/src/arm/am33xx-overlay-edma-fix.dtsi Which you'll see is commented out by default in at least this one board overlay file. Which I'm fairly certain it's commented out in all the stock board files. https://github.com/RobertCNelson/dtb-rebuilder/blob/4.4-ti/src/arm/am335x-boneblack-emmc-overlay.dts#L12-Lundefined Additionally, if you simply upgraded your kernel from an older image( e.g. an image that started with kernel 3.8.x ). You'll need to git pull that whole git repo, rebuild the board files, then install the ones you need. But you did not mention how you've managed to update your kernels from one test to the next. The best way to test would actually be to use two different flasher or stand alone images to test properly. Wheezy(debian 7 ) for 3.8.x, and Jessie(debian 8 ) for 4.x kernels. As some important changes have been made which may conflict between different kernels. 3.8.x may actually work fine on Jessie images, but I did personally run into troubles trying to update to a 4.x kernel on Wheezy images. On Wed, Jan 18, 2017 at 3:33 AM, William Hermans <[email protected]> wrote: > *root@beaglebone:~#* cat /etc/dogtag > BeagleBoard.org Debian Image 2016-06-19 > > *root@beaglebone:~#* uname -r > 4.4.43-bone-rt-r16 > > *root@beaglebone:~#* ls /lib/firmware/ |grep SPI > BB-SPI0-MCP3008-00A0.dtbo > BB-SPIDEV0-00A0.dtbo > BB-SPIDEV1-00A0.dtbo > BB-SPIDEV1A1-00A0.dtbo > > *root@beaglebone:~#* ls /dev |grep spi > > *root@beaglebone:~# *echo 'BB-SPIDEV0' > /sys/devices/platform/bone_ > capemgr/slots > > *root@beaglebone:~#* ls /dev |grep spi > spidev1.0 > spidev1.1 > > > > On Wed, Jan 18, 2017 at 3:22 AM, Thomas Hoppe <[email protected]> > wrote: > >> Hi, >> >> I have a board attached via SPI0 to a BBB (also tested with Green). >> I'm activating SPI0 via uEnv.txt entries which I read is the best >> practice. >> Now I can use the board with its user space software (no kernel driver >> whatsoever involved). >> The setup *works* with 3.8 and 4.1 kernels but *not* with 4.4 and 4.9. >> Below I have the output of >> >> cat /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins | grep spi >> >> and the actual device name for each version. >> I cannot spot any relevant difference. So what has changed in the SPI >> code between those kernels >> or has anyone an idea what could be the issue here? >> >> BG, Thomas >> >> >> 3.8.13 >> >> /dev/spidev1.0 >> >> pin 84 (44e10950): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> pin 85 (44e10954): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> pin 86 (44e10958): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> pin 87 (44e1095c): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> >> 4.1.x >> >> /dev/spidev1.0 >> >> pin 84 (44e10950.0): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> pin 85 (44e10954.0): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> pin 86 (44e10958.0): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> pin 87 (44e1095c.0): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> >> >> 4.4.x >> >> /dev/spidev1.0 >> >> pin 84 (44e10950.0): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> pin 85 (44e10954.0): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> pin 86 (44e10958.0): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> pin 87 (44e1095c.0): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> >> >> 4.9.x >> >> /dev/spidev0.0 >> >> pin 84 (44e10950.0): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> pin 85 (44e10954.0): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> pin 86 (44e10958.0): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> pin 87 (44e1095c.0): 48030000.spi (GPIO UNCLAIMED) function >> pinmux_bb_spi0_pins group pinmux_bb_spi0_pins >> >> >> >> >> >> -- >> 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/ms >> gid/beagleboard/e1a2e7ae-1e6e-406b-be64-7efb1cbfe8f6%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/e1a2e7ae-1e6e-406b-be64-7efb1cbfe8f6%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/CALHSORr_D2CDF8Nu4HBsse_rhTncW5-Jz0qx5t8MYScLegctLQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
