Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
Hey Robert, I know this thread is getting long in the tooth. Originally I had asked for help on enabling the SPI devices on the 3.14 kernel. You got me past that with some patches. However, I just did a merge from the latest upstream and now my SPI devices are not enabled any more when I boot the kernel. This is what I have on the command line: capemgr.enable_partno=BB-SPIDEV0,BB-SPIDEV1 Do these parts have different names now? Thanks, Dallas On Fri, Sep 5, 2014 at 1:10 PM, Jason Lange j.b.la...@gmail.com wrote: On Friday, 29 August 2014 10:37:09 UTC-7, RobertCNelson wrote: 2nd thought, the uart conflicts.. so disable: #include am335x-bone-basic-proto-cape.dtsi - /* #include am335x-bone-basic-proto-cape.dtsi */ Then add spi0: #include am335x-bone-spi0-spidev.dtsi Then spi1: #include am335x-bone-spi1-spidev.dtsi or #include am335x-bone-spi1a-spidev.dtsi then make/sudo make install/sudo reboot ..I think I should add this for completion Also do: #include am335x-boneblack-nxp-hdmi-audio.dtsi to: /*#include am335x-boneblack-nxp-hdmi-audio.dtsi*/ and if you want hdmi do: /* #include am335x-boneblack-nxp-hdmi-no-audio.dtsi*/ to: #include am335x-boneblack-nxp-hdmi-no-audio.dtsi -- 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/_qhb4wumgpU/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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
I got it figured out. The SPI dev include dtsi were commented out after my merge. I guess the default state is SPI devices disabled. On Sun, Oct 5, 2014 at 1:27 PM, Dallas Clement dallas.a.clem...@gmail.com wrote: Hey Robert, I know this thread is getting long in the tooth. Originally I had asked for help on enabling the SPI devices on the 3.14 kernel. You got me past that with some patches. However, I just did a merge from the latest upstream and now my SPI devices are not enabled any more when I boot the kernel. This is what I have on the command line: capemgr.enable_partno=BB-SPIDEV0,BB-SPIDEV1 Do these parts have different names now? Thanks, Dallas On Fri, Sep 5, 2014 at 1:10 PM, Jason Lange j.b.la...@gmail.com wrote: On Friday, 29 August 2014 10:37:09 UTC-7, RobertCNelson wrote: 2nd thought, the uart conflicts.. so disable: #include am335x-bone-basic-proto-cape.dtsi - /* #include am335x-bone-basic-proto-cape.dtsi */ Then add spi0: #include am335x-bone-spi0-spidev.dtsi Then spi1: #include am335x-bone-spi1-spidev.dtsi or #include am335x-bone-spi1a-spidev.dtsi then make/sudo make install/sudo reboot ..I think I should add this for completion Also do: #include am335x-boneblack-nxp-hdmi-audio.dtsi to: /*#include am335x-boneblack-nxp-hdmi-audio.dtsi*/ and if you want hdmi do: /* #include am335x-boneblack-nxp-hdmi-no-audio.dtsi*/ to: #include am335x-boneblack-nxp-hdmi-no-audio.dtsi -- 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/_qhb4wumgpU/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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Friday, 29 August 2014 10:37:09 UTC-7, RobertCNelson wrote: 2nd thought, the uart conflicts.. so disable: #include am335x-bone-basic-proto-cape.dtsi - /* #include am335x-bone-basic-proto-cape.dtsi */ Then add spi0: #include am335x-bone-spi0-spidev.dtsi Then spi1: #include am335x-bone-spi1-spidev.dtsi or #include am335x-bone-spi1a-spidev.dtsi then make/sudo make install/sudo reboot ..I think I should add this for completion Also do: #include am335x-boneblack-nxp-hdmi-audio.dtsi to: /*#include am335x-boneblack-nxp-hdmi-audio.dtsi*/ and if you want hdmi do: /* #include am335x-boneblack-nxp-hdmi-no-audio.dtsi*/ to: #include am335x-boneblack-nxp-hdmi-no-audio.dtsi -- 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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Tuesday, 2 September 2014 16:15:58 UTC-7, William Hermans wrote: Jason, /boot/uboot should have been nothing more than a mount point for /dev/mmcblk0p1. Which is the fat16 formatted partition that u-boot.img, MLO, and uEnv.txt reside. For a while the fat16 partition was mounted at /boot/uboot so that the kinds of things that frequently go in boot like different kernel images could be kept there without filling up the tiny FAT16 partition (similar to /boot/efi). The factory images from May which are labeled BeagleBoard.org Latest Firmware Images are that way. From /etc/fstab: /dev/mmcblk0p1 /boot/uboot auto defaults0 0. Scripts that manipulate /boot should take this possibility into account. -- 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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
heh whatever you like Jason. Simply using lsblk, and mount should make things crystal clear. On Wed, Sep 3, 2014 at 2:57 PM, Jason Lange j.b.la...@gmail.com wrote: On Tuesday, 2 September 2014 16:15:58 UTC-7, William Hermans wrote: Jason, /boot/uboot should have been nothing more than a mount point for /dev/mmcblk0p1. Which is the fat16 formatted partition that u-boot.img, MLO, and uEnv.txt reside. For a while the fat16 partition was mounted at /boot/uboot so that the kinds of things that frequently go in boot like different kernel images could be kept there without filling up the tiny FAT16 partition (similar to /boot/efi). The factory images from May which are labeled BeagleBoard.org Latest Firmware Images are that way. From /etc/fstab: /dev/mmcblk0p1 /boot/uboot auto defaults0 0. Scripts that manipulate /boot should take this possibility into account. -- 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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
Hello Robert, I had done just as you've described, but the system I started with had uboot and company installed in /boot/uboot rather than /boot and your 'make install' in ../dtb-rebuilder.git didn't seem to be touching /boot/uboot. I guessed that that was why I wasn't seeing the changes I was hoping for ( that is: /dev/spidev2.[0/1] ) so i tried completing the install for my setup by moving files into /boot/uboot/dtbs and bricked my board. This morning I began with: https://rcn-ee.net/deb/testing/2014-08-19/lxde/BBB-eMMC-flasher-debian-7.6-lxde-armhf-2014-08-19-2gb.img.xz flashed my bone... did: apt-get install linux-image-3.14.17-ti-r16 then: git clone -b 3.14-ti https://github.com/RobertCNelson/dtb-rebuilder.git then changed ../dtb-rebuilder.git/src/arm/am335x-boneblack.dts following your guidelines below: 2nd thought, the uart conflicts.. so disable: #include am335x-bone-basic-proto-cape.dtsi - /* #include am335x-bone-basic-proto-cape.dtsi */ Then add spi0: #include am335x-bone-spi0-spidev.dtsi Then spi1: #include am335x-bone-spi1-spidev.dtsi or #include am335x-bone-spi1a-spidev.dtsi then make/sudo make install/sudo reboot The system this gives me has everything in /boot and nothing in /boot/uboot and 'make install' does what it is supposed to, and sure enough after reboot: ls /dev/spidev* gives me: /dev/spidev1.0 /dev/spidev1.1 /dev/spidev2.0 /dev/spidev2.1 Thanks for the time and the tools. -- 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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
Jason, /boot/uboot should have been nothing more than a mount point for /dev/mmcblk0p1. Which is the fat16 formatted partition that u-boot.img, MLO, and uEnv.txt reside. /boot/uEnv.txt should be nothing more than . .. *root@arm:~# cat /boot/uEnv.txt* *uname_r=3.8.13-bone64.1* *cmdline=quiet init=/lib/systemd/systemd* *cape_disable=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN* Or something similar. On Tue, Sep 2, 2014 at 3:33 PM, Jason Lange j.b.la...@gmail.com wrote: Hello Robert, I had done just as you've described, but the system I started with had uboot and company installed in /boot/uboot rather than /boot and your 'make install' in ../dtb-rebuilder.git didn't seem to be touching /boot/uboot. I guessed that that was why I wasn't seeing the changes I was hoping for ( that is: /dev/spidev2.[0/1] ) so i tried completing the install for my setup by moving files into /boot/uboot/dtbs and bricked my board. This morning I began with: https://rcn-ee.net/deb/testing/2014-08-19/lxde/BBB-eMMC-flasher-debian-7.6-lxde-armhf-2014-08-19-2gb.img.xz flashed my bone... did: apt-get install linux-image-3.14.17-ti-r16 then: git clone -b 3.14-ti https://github.com/RobertCNelson/dtb-rebuilder.git then changed ../dtb-rebuilder.git/src/arm/am335x-boneblack.dts following your guidelines below: 2nd thought, the uart conflicts.. so disable: #include am335x-bone-basic-proto-cape.dtsi - /* #include am335x-bone-basic-proto-cape.dtsi */ Then add spi0: #include am335x-bone-spi0-spidev.dtsi Then spi1: #include am335x-bone-spi1-spidev.dtsi or #include am335x-bone-spi1a-spidev.dtsi then make/sudo make install/sudo reboot The system this gives me has everything in /boot and nothing in /boot/uboot and 'make install' does what it is supposed to, and sure enough after reboot: ls /dev/spidev* gives me: /dev/spidev1.0 /dev/spidev1.1 /dev/spidev2.0 /dev/spidev2.1 Thanks for the time and the tools. -- 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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Tue, Sep 2, 2014 at 6:15 PM, William Hermans yyrk...@gmail.com wrote: Jason, /boot/uboot should have been nothing more than a mount point for /dev/mmcblk0p1. Which is the fat16 formatted partition that u-boot.img, MLO, and uEnv.txt reside. How would you guys feel about nuking that fat16 boot partition. ;) Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
*How would you guys feel about nuking that fat16 boot partition. ;)* Quite honestly Robert. It's been around since I first got my A5A last year, so I'm used to it. But I suppose having one partition formatted as ext2/3/4 would be more convenient On Tue, Sep 2, 2014 at 4:40 PM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Sep 2, 2014 at 6:15 PM, William Hermans yyrk...@gmail.com wrote: Jason, /boot/uboot should have been nothing more than a mount point for /dev/mmcblk0p1. Which is the fat16 formatted partition that u-boot.img, MLO, and uEnv.txt reside. How would you guys feel about nuking that fat16 boot partition. ;) Regards, -- Robert Nelson http://www.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 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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Tue, Sep 2, 2014 at 5:33 PM, Jason Lange j.b.la...@gmail.com wrote: Hello Robert, I had done just as you've described, but the system I started with had uboot and company installed in /boot/uboot rather than /boot and your 'make install' in ../dtb-rebuilder.git didn't seem to be touching /boot/uboot. I guessed that that was why I wasn't seeing the changes I was hoping for ( that is: /dev/spidev2.[0/1] ) so i tried completing the install for my setup by moving files into /boot/uboot/dtbs and bricked my board. Sorry about that, i need to add backwards compatibility to that script. I promise i only have one more earth shaking change coming down the pipe. Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Tue, Sep 2, 2014 at 6:45 PM, William Hermans yyrk...@gmail.com wrote: How would you guys feel about nuking that fat16 boot partition. ;) Quite honestly Robert. It's been around since I first got my A5A last year, so I'm used to it. But I suppose having one partition formatted as ext2/3/4 would be more convenient done ;) dd if=MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k dd if=u-boot.img of=/dev/sdX count=2 seek=1 conv=notrunc bs=384k only works on omap4+ bootrom's (so the old omap34xx/omap36xx family is out) I'm close to rolling out a new testing image that uses this feature.. The flasher gets more interesting as i need to remember to include the MLO/u-boot.img somewhere in the ext4 partition for later flashing.. Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
*done ;)* * dd if=MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k* * dd if=u-boot.img of=/dev/sdX count=2 seek=1 conv=notrunc bs=384k* * only works on omap4+ bootrom's (so the old omap34xx/omap36xx family is out)* * I'm close to rolling out a new testing image that uses this feature..* * The flasher gets more interesting as i need to remember to include the* * MLO/u-boot.img somewhere in the ext4 partition for later flashing..* Wait a minute, is this creating two partitions that are raw contents of each file ? Not sure what this is doing actually seems more like you're dumping the raw content of each file onto the same partition. But I've actually never seen dd used this way. On Tue, Sep 2, 2014 at 4:47 PM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Sep 2, 2014 at 6:45 PM, William Hermans yyrk...@gmail.com wrote: How would you guys feel about nuking that fat16 boot partition. ;) Quite honestly Robert. It's been around since I first got my A5A last year, so I'm used to it. But I suppose having one partition formatted as ext2/3/4 would be more convenient done ;) dd if=MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k dd if=u-boot.img of=/dev/sdX count=2 seek=1 conv=notrunc bs=384k only works on omap4+ bootrom's (so the old omap34xx/omap36xx family is out) I'm close to rolling out a new testing image that uses this feature.. The flasher gets more interesting as i need to remember to include the MLO/u-boot.img somewhere in the ext4 partition for later flashing.. Regards, -- Robert Nelson http://www.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 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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
OK, so I think I got that figured out. Was not familiar with seek, but am now. So what about uEnv.txt ? On Tue, Sep 2, 2014 at 4:52 PM, William Hermans yyrk...@gmail.com wrote: *done ;)* * dd if=MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k* * dd if=u-boot.img of=/dev/sdX count=2 seek=1 conv=notrunc bs=384k* * only works on omap4+ bootrom's (so the old omap34xx/omap36xx family is out)* * I'm close to rolling out a new testing image that uses this feature..* * The flasher gets more interesting as i need to remember to include the* * MLO/u-boot.img somewhere in the ext4 partition for later flashing..* Wait a minute, is this creating two partitions that are raw contents of each file ? Not sure what this is doing actually seems more like you're dumping the raw content of each file onto the same partition. But I've actually never seen dd used this way. On Tue, Sep 2, 2014 at 4:47 PM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Sep 2, 2014 at 6:45 PM, William Hermans yyrk...@gmail.com wrote: How would you guys feel about nuking that fat16 boot partition. ;) Quite honestly Robert. It's been around since I first got my A5A last year, so I'm used to it. But I suppose having one partition formatted as ext2/3/4 would be more convenient done ;) dd if=MLO of=/dev/sdX count=1 seek=1 conv=notrunc bs=128k dd if=u-boot.img of=/dev/sdX count=2 seek=1 conv=notrunc bs=384k only works on omap4+ bootrom's (so the old omap34xx/omap36xx family is out) I'm close to rolling out a new testing image that uses this feature.. The flasher gets more interesting as i need to remember to include the MLO/u-boot.img somewhere in the ext4 partition for later flashing.. Regards, -- Robert Nelson http://www.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 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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Tue, Sep 2, 2014 at 6:57 PM, William Hermans yyrk...@gmail.com wrote: OK, so I think I got that figured out. Was not familiar with seek, but am now. So what about uEnv.txt ? /boot/uEnv.txt can be in any partition ( /dev/mmcblkXp1 - /dev/mmcblkXp7* ) 7: is the usual max enabled by default for most normal mmc host controllers in linux. Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
*/boot/uEnv.txt can be in any partition ( /dev/mmcblkXp1 - /dev/mmcblkXp7* )* *7: is the usual max enabled by default for most normal mmc host controllers in linux.* *Regards,* Right, I get that, but in the case of NFS rootfs, how is uboot supposed to know to look over an NFS share ? Right now, we have the main uEnv.txt file that resides where uboot.img, and MLO reside. This points to yet another( optional ? ) uEnv.txt for loading possibly common setenv variables. Will this just be hard coded to search /boot, no matter it's location ? On Tue, Sep 2, 2014 at 5:25 PM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Sep 2, 2014 at 6:57 PM, William Hermans yyrk...@gmail.com wrote: OK, so I think I got that figured out. Was not familiar with seek, but am now. So what about uEnv.txt ? /boot/uEnv.txt can be in any partition ( /dev/mmcblkXp1 - /dev/mmcblkXp7* ) 7: is the usual max enabled by default for most normal mmc host controllers in linux. Regards, -- Robert Nelson http://www.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 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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
Oh, and nearly forgot for the fifth time heh. What about g_multi file share ? The one that gets auto mounted on Windows machines. I do not use this myself, but I'm sure there are people out there who do use it. On Tue, Sep 2, 2014 at 6:22 PM, William Hermans yyrk...@gmail.com wrote: */boot/uEnv.txt can be in any partition ( /dev/mmcblkXp1 - /dev/mmcblkXp7* )* *7: is the usual max enabled by default for most normal mmc host controllers in linux.* *Regards,* Right, I get that, but in the case of NFS rootfs, how is uboot supposed to know to look over an NFS share ? Right now, we have the main uEnv.txt file that resides where uboot.img, and MLO reside. This points to yet another( optional ? ) uEnv.txt for loading possibly common setenv variables. Will this just be hard coded to search /boot, no matter it's location ? On Tue, Sep 2, 2014 at 5:25 PM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Sep 2, 2014 at 6:57 PM, William Hermans yyrk...@gmail.com wrote: OK, so I think I got that figured out. Was not familiar with seek, but am now. So what about uEnv.txt ? /boot/uEnv.txt can be in any partition ( /dev/mmcblkXp1 - /dev/mmcblkXp7* ) 7: is the usual max enabled by default for most normal mmc host controllers in linux. Regards, -- Robert Nelson http://www.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 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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Tue, Sep 2, 2014 at 8:22 PM, William Hermans yyrk...@gmail.com wrote: /boot/uEnv.txt can be in any partition ( /dev/mmcblkXp1 - /dev/mmcblkXp7* ) 7: is the usual max enabled by default for most normal mmc host controllers in linux. Regards, Right, I get that, but in the case of NFS rootfs, how is uboot supposed to know to look over an NFS share ? Right now, we have the main uEnv.txt file that resides where uboot.img, and MLO reside. This points to yet another( optional ? ) uEnv.txt for loading possibly common setenv variables. Will this just be hard coded to search /boot, no matter it's location ? So as of right now, it'll search for these files in this order: (microSD) Partition: 1 (fat/extX) /uEnv.txt /boot.scr /boot/boot.scr Then it'll loop thru partition's: 1 - 7: /boot/uEnv.txt (eMMC) Partition: 1 (fat/extX) /uEnv.txt /boot.scr /boot/boot.scr Then it'll loop thru partition's: 1 - 7: /boot/uEnv.txt I've left the logic for the first partition for compatibility sake. Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Tue, Sep 2, 2014 at 8:23 PM, William Hermans yyrk...@gmail.com wrote: Oh, and nearly forgot for the fifth time heh. What about g_multi file share ? The one that gets auto mounted on Windows machines. I do not use this myself, but I'm sure there are people out there who do use it. That's why we've been moving every critical file out of that partition. For the official lxde image, the fat partition will still be there, but NO critical boot files will exist in. (a windows user can add a 'uEnv.txt/boot.scr/boot/boot.scr' and it will change the boot.. In theory, windows users should be able to re-format the drive too, when it's shown in windows over the usb-gadget connection. Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
*That's why we've been moving every critical file out of that partition.* * For the official lxde image, the fat partition will still be there,* * but NO critical boot files will exist in. (a windows user can add a* * 'uEnv.txt/boot.scr/boot/boot.* *scr' and it will change the boot..* * In theory, windows users should be able to re-format the drive too,* * when it's shown in windows over the usb-gadget connection.* It is kind of sad that this is even necessary. In the context that the BBB is a dev board, and as such *some* knowledge / common sense should be implied. On Tue, Sep 2, 2014 at 6:45 PM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Sep 2, 2014 at 8:23 PM, William Hermans yyrk...@gmail.com wrote: Oh, and nearly forgot for the fifth time heh. What about g_multi file share ? The one that gets auto mounted on Windows machines. I do not use this myself, but I'm sure there are people out there who do use it. That's why we've been moving every critical file out of that partition. For the official lxde image, the fat partition will still be there, but NO critical boot files will exist in. (a windows user can add a 'uEnv.txt/boot.scr/boot/boot.scr' and it will change the boot.. In theory, windows users should be able to re-format the drive too, when it's shown in windows over the usb-gadget connection. Regards, -- Robert Nelson http://www.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 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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Tue, Sep 2, 2014 at 8:58 PM, William Hermans yyrk...@gmail.com wrote: *That's why we've been moving every critical file out of that partition.* * For the official lxde image, the fat partition will still be there,* * but NO critical boot files will exist in. (a windows user can add a* * 'uEnv.txt/boot.scr/boot/boot.* *scr' and it will change the boot..* * In theory, windows users should be able to re-format the drive too,* * when it's shown in windows over the usb-gadget connection.* It is kind of sad that this is even necessary. In the context that the BBB is a dev board, and as such *some* knowledge / common sense should be implied. It keeps things interesting. ;) It Feels like bullet proofing the perfect mouse trap! Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
Hello Robert, I've just tried to duplicate your instructions here to get both spidev 0 and 1 using your dts from the pastebin link above and I am only getting /dev/spidev1.0 and /dev/spidev1.1 -- no spidev0.N or spidev2.N uname -a: Linux SQR-3 3.14.17-ti-r16 #1 SMP Thu Aug 28 23:18:48 UTC 2014 armv7l GNU/Linux I just updated from 3.8 using your latest install-me.sh from rcn-ee.org and did: git clone -b 3.14-ti https://github.com/RobertCNelson/dtb-rebuilder.git *make* and *make install *did not complain but no joy. On Wednesday, 27 August 2014 19:59:11 UTC-7, Dallas Clement wrote: You're my hero! :) Working like a champ now! Thanks a million. On Wed, Aug 27, 2014 at 9:42 PM, Robert Nelson robert...@gmail.com javascript: wrote: On Wed, Aug 27, 2014 at 9:41 PM, Dallas Clement dallas.a...@gmail.com javascript: wrote: I just pasted my am335x-boneblack.dts to http://pastebin.com/PwccRatb Here you go: http://pastebin.com/rSg1h46h (just disabled the last line, proto-cape, as it'll inerfear) Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Fri, Aug 29, 2014 at 12:20 PM, Jason Lange j.b.la...@gmail.com wrote: Hello Robert, I've just tried to duplicate your instructions here to get both spidev 0 and 1 using your dts from the pastebin link above and I am only getting /dev/spidev1.0 and /dev/spidev1.1 -- no spidev0.N or spidev2.N uname -a: Linux SQR-3 3.14.17-ti-r16 #1 SMP Thu Aug 28 23:18:48 UTC 2014 armv7l GNU/Linux I just updated from 3.8 using your latest install-me.sh from rcn-ee.org and did: git clone -b 3.14-ti https://github.com/RobertCNelson/dtb-rebuilder.git make and make install did not complain but no joy. /dev/spidev1.[0/1] is enabled by: https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-boneblack.dts#L102 as that enables: #include am335x-bone-spi0-spidev.dtsi For /dev/spidev2.[0/1] you have two choices: Uncomment: https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-boneblack.dts#L43 or https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-boneblack.dts#L50 then make/sudo make install/sudo reboot Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Fri, Aug 29, 2014 at 12:35 PM, Robert Nelson robertcnel...@gmail.com wrote: On Fri, Aug 29, 2014 at 12:20 PM, Jason Lange j.b.la...@gmail.com wrote: Hello Robert, I've just tried to duplicate your instructions here to get both spidev 0 and 1 using your dts from the pastebin link above and I am only getting /dev/spidev1.0 and /dev/spidev1.1 -- no spidev0.N or spidev2.N uname -a: Linux SQR-3 3.14.17-ti-r16 #1 SMP Thu Aug 28 23:18:48 UTC 2014 armv7l GNU/Linux I just updated from 3.8 using your latest install-me.sh from rcn-ee.org and did: git clone -b 3.14-ti https://github.com/RobertCNelson/dtb-rebuilder.git make and make install did not complain but no joy. /dev/spidev1.[0/1] is enabled by: https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-boneblack.dts#L102 as that enables: #include am335x-bone-spi0-spidev.dtsi For /dev/spidev2.[0/1] you have two choices: Uncomment: https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-boneblack.dts#L43 or https://github.com/RobertCNelson/dtb-rebuilder/blob/3.14-ti/src/arm/am335x-boneblack.dts#L50 then make/sudo make install/sudo reboot 2nd thought, the uart conflicts.. so disable: #include am335x-bone-basic-proto-cape.dtsi - /* #include am335x-bone-basic-proto-cape.dtsi */ Then add spi0: #include am335x-bone-spi0-spidev.dtsi Then spi1: #include am335x-bone-spi1-spidev.dtsi or #include am335x-bone-spi1a-spidev.dtsi then make/sudo make install/sudo reboot Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Tue, Aug 26, 2014 at 10:56 PM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Aug 26, 2014 at 10:25 PM, Dallas Clement dallas.a.clem...@gmail.com wrote: Hi Robert, many thanks for this. How dost one actually enable the spi devices in 3.14? I'm used to working with the overlays and capemgr, i.e. echoing to capemgr slots etc. Well it's still in it's infancy. Here's what works today: http://elinux.org/Beagleboard:Capes_3.8_to_3.14 Take a look at the main am335x-boneblack.dts file: https://github.com/beagleboard/linux/blob/3.14.17-ti-r15/arch/arm/boot/dts/am335x-boneblack.dts#L31 If you need usart1: Just change: /* #include am335x-bone-ttyO1.dtsi */ to: #include am335x-bone-ttyO1.dtsi and rebuild. I'm working on a second repo, so that you don't have to rebuild the kernel, just for dts changes: https://github.com/RobertCNelson/dtb-rebuilder/tree/3.14-ti Just issue make all and all *.dtb's will be rebuilt (these match the full kernel tree (3.14.17-ti-r15)) above. Haven't finished the make install so you still have to manually copy the *.dtb's. So, just make the *.dts change, rebuild, copy *.dtb, reboot, new device enabled.. Okay just added the make install Follow: http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb edit ./src/arm/am335x-boneblack.dts To rebuild/install: make sudo make install Then, reboot.. Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
Wow! Thanks for the quick response. Will give it a shot. On Wed, Aug 27, 2014 at 9:50 AM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Aug 26, 2014 at 10:56 PM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Aug 26, 2014 at 10:25 PM, Dallas Clement dallas.a.clem...@gmail.com wrote: Hi Robert, many thanks for this. How dost one actually enable the spi devices in 3.14? I'm used to working with the overlays and capemgr, i.e. echoing to capemgr slots etc. Well it's still in it's infancy. Here's what works today: http://elinux.org/Beagleboard:Capes_3.8_to_3.14 Take a look at the main am335x-boneblack.dts file: https://github.com/beagleboard/linux/blob/3.14.17-ti-r15/arch/arm/boot/dts/am335x-boneblack.dts#L31 If you need usart1: Just change: /* #include am335x-bone-ttyO1.dtsi */ to: #include am335x-bone-ttyO1.dtsi and rebuild. I'm working on a second repo, so that you don't have to rebuild the kernel, just for dts changes: https://github.com/RobertCNelson/dtb-rebuilder/tree/3.14-ti Just issue make all and all *.dtb's will be rebuilt (these match the full kernel tree (3.14.17-ti-r15)) above. Haven't finished the make install so you still have to manually copy the *.dtb's. So, just make the *.dts change, rebuild, copy *.dtb, reboot, new device enabled.. Okay just added the make install Follow: http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb edit ./src/arm/am335x-boneblack.dts To rebuild/install: make sudo make install Then, reboot.. Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
Hi Robert, everything builds clean and I can see SPI0 after booting. The devices are spi1.0 and spi1.1. However, I'm not able to see any SPI1 devices. Suspecting HDMI conflict, I set the status for the HDMI device to disabled in am335x-base0033.dts. But that didn't seem to help. Anything else you can think of that I should check? Thanks, Dallas On Wed, Aug 27, 2014 at 10:07 AM, Dallas Clement dallas.a.clem...@gmail.com wrote: Wow! Thanks for the quick response. Will give it a shot. On Wed, Aug 27, 2014 at 9:50 AM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Aug 26, 2014 at 10:56 PM, Robert Nelson robertcnel...@gmail.com wrote: On Tue, Aug 26, 2014 at 10:25 PM, Dallas Clement dallas.a.clem...@gmail.com wrote: Hi Robert, many thanks for this. How dost one actually enable the spi devices in 3.14? I'm used to working with the overlays and capemgr, i.e. echoing to capemgr slots etc. Well it's still in it's infancy. Here's what works today: http://elinux.org/Beagleboard:Capes_3.8_to_3.14 Take a look at the main am335x-boneblack.dts file: https://github.com/beagleboard/linux/blob/3.14.17-ti-r15/arch/arm/boot/dts/am335x-boneblack.dts#L31 If you need usart1: Just change: /* #include am335x-bone-ttyO1.dtsi */ to: #include am335x-bone-ttyO1.dtsi and rebuild. I'm working on a second repo, so that you don't have to rebuild the kernel, just for dts changes: https://github.com/RobertCNelson/dtb-rebuilder/tree/3.14-ti Just issue make all and all *.dtb's will be rebuilt (these match the full kernel tree (3.14.17-ti-r15)) above. Haven't finished the make install so you still have to manually copy the *.dtb's. So, just make the *.dts change, rebuild, copy *.dtb, reboot, new device enabled.. Okay just added the make install Follow: http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb edit ./src/arm/am335x-boneblack.dts To rebuild/install: make sudo make install Then, reboot.. Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Wed, Aug 27, 2014 at 8:59 PM, Dallas Clement dallas.a.clem...@gmail.com wrote: Hi Robert, everything builds clean and I can see SPI0 after booting. The devices are spi1.0 and spi1.1. However, I'm not able to see any SPI1 devices. Suspecting HDMI conflict, I set the status for the HDMI device to disabled in am335x-base0033.dts. But that didn't seem to help. Anything else you can think of that I should check? Okay, i should probally remove all non bb.org boards.. am335x-base0033.dts am335x-base0033.dts - Device Tree file for IGEP AQUILA EXPANSION The only two you should touch: am335x-bone.dts (BeagleBone White) am335x-boneblack.dts (BeagleBone Black) If you want to pastebin.com your current *.dts I'll look at it.. Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Wed, Aug 27, 2014 at 9:23 PM, Robert Nelson robertcnel...@gmail.com wrote: On Wed, Aug 27, 2014 at 8:59 PM, Dallas Clement dallas.a.clem...@gmail.com wrote: Hi Robert, everything builds clean and I can see SPI0 after booting. The devices are spi1.0 and spi1.1. However, I'm not able to see any SPI1 devices. Suspecting HDMI conflict, I set the status for the HDMI device to disabled in am335x-base0033.dts. But that didn't seem to help. Anything else you can think of that I should check? Okay, i should probally remove all non bb.org boards.. am335x-base0033.dts am335x-base0033.dts - Device Tree file for IGEP AQUILA EXPANSION The only two you should touch: am335x-bone.dts (BeagleBone White) am335x-boneblack.dts (BeagleBone Black) If you want to pastebin.com your current *.dts I'll look at it.. btw, i added some more notes to: http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb This feedback always helps us tune the wiki for the next new user.. Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
I just pasted my am335x-boneblack.dts to http://pastebin.com/PwccRatb On Wed, Aug 27, 2014 at 9:33 PM, Robert Nelson robertcnel...@gmail.com wrote: On Wed, Aug 27, 2014 at 9:23 PM, Robert Nelson robertcnel...@gmail.com wrote: On Wed, Aug 27, 2014 at 8:59 PM, Dallas Clement dallas.a.clem...@gmail.com wrote: Hi Robert, everything builds clean and I can see SPI0 after booting. The devices are spi1.0 and spi1.1. However, I'm not able to see any SPI1 devices. Suspecting HDMI conflict, I set the status for the HDMI device to disabled in am335x-base0033.dts. But that didn't seem to help. Anything else you can think of that I should check? Okay, i should probally remove all non bb.org boards.. am335x-base0033.dts am335x-base0033.dts - Device Tree file for IGEP AQUILA EXPANSION The only two you should touch: am335x-bone.dts (BeagleBone White) am335x-boneblack.dts (BeagleBone Black) If you want to pastebin.com your current *.dts I'll look at it.. btw, i added some more notes to: http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Custom_dtb This feedback always helps us tune the wiki for the next new user.. Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Wed, Aug 27, 2014 at 9:41 PM, Dallas Clement dallas.a.clem...@gmail.com wrote: I just pasted my am335x-boneblack.dts to http://pastebin.com/PwccRatb Here you go: http://pastebin.com/rSg1h46h (just disabled the last line, proto-cape, as it'll inerfear) Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
You're my hero! :) Working like a champ now! Thanks a million. On Wed, Aug 27, 2014 at 9:42 PM, Robert Nelson robertcnel...@gmail.com wrote: On Wed, Aug 27, 2014 at 9:41 PM, Dallas Clement dallas.a.clem...@gmail.com wrote: I just pasted my am335x-boneblack.dts to http://pastebin.com/PwccRatb Here you go: http://pastebin.com/rSg1h46h (just disabled the last line, proto-cape, as it'll inerfear) Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] How to enable SPI devices on 3.14 kernel?
Hi All, I am trying to enable both SPI devices in the 3.14 kernel for a beaglebone black. I understand that the capemgr support is no longer there. I need some tips on how to enable these devices in the kernel. I don't care if it is done statically at kernel build time. My application has no need to runtime enabling/disabling as is possible with capemgr and device tree overlays. I see device tree source for spi0 but not spi1 in the 3.14 kernel source. ./arch/arm/boot/dts/am335x-bone-spi0-spidev.dtsi Looks like SPI support is half-baked. I am pulling my source from here: https://github.com/beagleboard/linux.git Am I going down the wrong path with 3.14? Building from the 3.8 branch in this repo has compilation errors. Thanks, Dallas -- 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.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Tue, Aug 26, 2014 at 8:05 PM, Dallas Clement
dallas.a.clem...@gmail.com wrote:
Hi All,
I am trying to enable both SPI devices in the 3.14 kernel for a beaglebone
black. I understand that the capemgr support is no longer there. I need
some tips on how to enable these devices in the kernel. I don't care if it
is done statically at kernel build time. My application has no need to
runtime enabling/disabling as is possible with capemgr and device tree
overlays.
I see device tree source for spi0 but not spi1 in the 3.14 kernel source.
./arch/arm/boot/dts/am335x-bone-spi0-spidev.dtsi
Looks like SPI support is half-baked. I am pulling my source from here:
https://github.com/beagleboard/linux.git
Am I going down the wrong path with 3.14? Building from the 3.8 branch in
this repo has compilation errors.
Well, looks we have a volunteer.. Apply this on top of the latest 3.14
branch (i force pushed out an update about an hour ago)
Just enable either spi1/spi1a via:
#include am335x-bone-spi1-spidev.dtsi
(or)
#include am335x-bone-spi1a-spidev.dtsi
Regards,
--
Robert Nelson
http://www.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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
From c9835cb84fa92fced9b0b26e556fb15861d5257c Mon Sep 17 00:00:00 2001
From: Robert Nelson robertcnel...@gmail.com
Date: Tue, 26 Aug 2014 20:26:40 -0500
Subject: [PATCH] testing: add spi1/spi1a
Signed-off-by: Robert Nelson robertcnel...@gmail.com
---
arch/arm/boot/dts/am335x-bone-common-pinmux.dtsi | 21 +++
arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi | 26
arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi | 26
arch/arm/boot/dts/am335x-boneblack.dts | 14 +
4 files changed, 87 insertions(+)
create mode 100644 arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi
create mode 100644 arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi
diff --git a/arch/arm/boot/dts/am335x-bone-common-pinmux.dtsi b/arch/arm/boot/dts/am335x-bone-common-pinmux.dtsi
index 7519b71..4cef01c 100644
--- a/arch/arm/boot/dts/am335x-bone-common-pinmux.dtsi
+++ b/arch/arm/boot/dts/am335x-bone-common-pinmux.dtsi
@@ -303,6 +303,27 @@
;
};
+ spi1_pins: pinmux_spi1_pins {
+ pinctrl-single,pins =
+ 0x190 0x33 /* mcasp0_aclkx.spi1_sclk, INPUT_PULLUP | MODE3 */
+ 0x194 0x33 /* mcasp0_fsx.spi1_d0, INPUT_PULLUP | MODE3 */
+ 0x198 0x13 /* mcasp0_axr0.spi1_d1, OUTPUT_PULLUP | MODE3 */
+ 0x19c 0x13 /* mcasp0_ahclkr.spi1_cs0, OUTPUT_PULLUP | MODE3 */
+ // 0x164 0x12 /* eCAP0_in_PWM0_out.spi1_cs1 OUTPUT_PULLUP | MODE2 */
+ ;
+ };
+
+ spi1a_pins: pinmux_spi1a_pins {
+ pinctrl-single,pins =
+ 0x164 0x34 /* eCAP0_in_PWM0_out.spi1_sclk, INPUT_PULLUP | MODE4 */
+ /* NOTE: P9.42 is connected to two pads */
+ // 0x1A0 0x27 /* set the other pad to gpio input */
+ 0x194 0x33 /* mcasp0_fsx.spi1_d0, INPUT_PULLUP | MODE3 */
+ 0x198 0x13 /* mcasp0_axr0.spi1_d1, OUTPUT_PULLUP | MODE3 */
+ 0x178 0x14 /* uart1_ctsn.spi1_cs0, OUTPUT_PULLUP | MODE4 */
+ ;
+ };
+
uart0_pins: pinmux_uart0_pins {
pinctrl-single,pins =
0x170 (PIN_INPUT_PULLUP | MUX_MODE0) /* uart0_rxd.uart0_rxd */
diff --git a/arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi b/arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi
new file mode 100644
index 000..24013d8a6b
--- /dev/null
+++ b/arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi
@@ -0,0 +1,26 @@
+/*
+ * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+spi1 {
+ pinctrl-names = default;
+ pinctrl-0 = spi1_pins;
+ status = okay;
+
+ spidev0: spi@0 {
+ compatible = spidev;
+ reg = 0;
+ spi-max-frequency = 1600;
+ spi-cpha;
+ };
+
+ spidev1: spi@1 {
+ compatible = spidev;
+ reg = 1;
+ spi-max-frequency = 1600;
+ };
+};
diff --git a/arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi b/arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi
new file mode 100644
index 000..b2185dd
--- /dev/null
+++ b/arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi
@@ -0,0 +1,26 @@
+/*
+ * Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public License version 2 as
+ * published by the Free Software Foundation.
+ */
+
+spi1 {
+ pinctrl-names = default;
+ pinctrl-0 = spi1a_pins;
+ status = okay;
+
+ spidev0: spi@0 {
+ compatible = spidev;
+ reg = 0;
+ spi-max-frequency = 1600;
+ spi-cpha;
+ };
+
+ spidev1: spi@1 {
+
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Tue, Aug 26, 2014 at 8:28 PM, Robert Nelson robertcnel...@gmail.com wrote:
On Tue, Aug 26, 2014 at 8:05 PM, Dallas Clement
dallas.a.clem...@gmail.com wrote:
Hi All,
I am trying to enable both SPI devices in the 3.14 kernel for a beaglebone
black. I understand that the capemgr support is no longer there. I need
some tips on how to enable these devices in the kernel. I don't care if it
is done statically at kernel build time. My application has no need to
runtime enabling/disabling as is possible with capemgr and device tree
overlays.
I see device tree source for spi0 but not spi1 in the 3.14 kernel source.
./arch/arm/boot/dts/am335x-bone-spi0-spidev.dtsi
Looks like SPI support is half-baked. I am pulling my source from here:
https://github.com/beagleboard/linux.git
Am I going down the wrong path with 3.14? Building from the 3.8 branch in
this repo has compilation errors.
Well, looks we have a volunteer.. Apply this on top of the latest 3.14
branch (i force pushed out an update about an hour ago)
Just enable either spi1/spi1a via:
#include am335x-bone-spi1-spidev.dtsi
(or)
#include am335x-bone-spi1a-spidev.dtsi
btw:
crap, forgot to update the spidev node names: if you have spi0-spidev
or the bottom am335x-bone-basic-proto-cape.dtsi enabled, you'll get
this error:
ERROR (duplicate_label): Duplicate label 'spidev0' on
/ocp/spi@481a/spi@0 and /ocp/spi@4803/spi@0
ERROR (duplicate_label): Duplicate label 'spidev1' on
/ocp/spi@481a/spi@1 and /ocp/spi@4803/spi@1
ERROR: Input tree has errors, aborting (use -f to force output)
Makefile:121: recipe for target 'src/arm/am335x-boneblack.dtb' failed
make[1]: *** [src/arm/am335x-boneblack.dtb] Error 2
This fixes that..
diff --git a/arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi
b/arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi
index 24013d8a6b..5bc03e8 100644
--- a/arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi
+++ b/arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi
@@ -11,14 +11,14 @@
pinctrl-0 = spi1_pins;
status = okay;
- spidev0: spi@0 {
+ spidev2: spi@0 {
compatible = spidev;
reg = 0;
spi-max-frequency = 1600;
spi-cpha;
};
- spidev1: spi@1 {
+ spidev3: spi@1 {
compatible = spidev;
reg = 1;
spi-max-frequency = 1600;
diff --git a/arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi
b/arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi
index b2185dd..3aded7b 100644
--- a/arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi
+++ b/arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi
@@ -11,14 +11,14 @@
pinctrl-0 = spi1a_pins;
status = okay;
- spidev0: spi@0 {
+ spidev2: spi@0 {
compatible = spidev;
reg = 0;
spi-max-frequency = 1600;
spi-cpha;
};
- spidev1: spi@1 {
+ spidev3: spi@1 {
compatible = spidev;
reg = 1;
spi-max-frequency = 1600;
you know.. half baked.. ;) Just got all the lcd's working today, spi1
hasn't been a priorty as i don't have a cape that uses it...
Regards,
--
Robert Nelson
http://www.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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
Hi Robert, many thanks for this. How dost one actually enable the spi
devices in 3.14? I'm used to working with the overlays and capemgr, i.e.
echoing to capemgr slots etc.
On Tue, Aug 26, 2014 at 8:39 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, Aug 26, 2014 at 8:28 PM, Robert Nelson robertcnel...@gmail.com
wrote:
On Tue, Aug 26, 2014 at 8:05 PM, Dallas Clement
dallas.a.clem...@gmail.com wrote:
Hi All,
I am trying to enable both SPI devices in the 3.14 kernel for a
beaglebone
black. I understand that the capemgr support is no longer there. I
need
some tips on how to enable these devices in the kernel. I don't care
if it
is done statically at kernel build time. My application has no need to
runtime enabling/disabling as is possible with capemgr and device tree
overlays.
I see device tree source for spi0 but not spi1 in the 3.14 kernel
source.
./arch/arm/boot/dts/am335x-bone-spi0-spidev.dtsi
Looks like SPI support is half-baked. I am pulling my source from here:
https://github.com/beagleboard/linux.git
Am I going down the wrong path with 3.14? Building from the 3.8 branch
in
this repo has compilation errors.
Well, looks we have a volunteer.. Apply this on top of the latest 3.14
branch (i force pushed out an update about an hour ago)
Just enable either spi1/spi1a via:
#include am335x-bone-spi1-spidev.dtsi
(or)
#include am335x-bone-spi1a-spidev.dtsi
btw:
crap, forgot to update the spidev node names: if you have spi0-spidev
or the bottom am335x-bone-basic-proto-cape.dtsi enabled, you'll get
this error:
ERROR (duplicate_label): Duplicate label 'spidev0' on
/ocp/spi@481a/spi@0 and /ocp/spi@4803/spi@0
ERROR (duplicate_label): Duplicate label 'spidev1' on
/ocp/spi@481a/spi@1 and /ocp/spi@4803/spi@1
ERROR: Input tree has errors, aborting (use -f to force output)
Makefile:121: recipe for target 'src/arm/am335x-boneblack.dtb' failed
make[1]: *** [src/arm/am335x-boneblack.dtb] Error 2
This fixes that..
diff --git a/arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi
b/arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi
index 24013d8a6b..5bc03e8 100644
--- a/arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi
+++ b/arch/arm/boot/dts/am335x-bone-spi1-spidev.dtsi
@@ -11,14 +11,14 @@
pinctrl-0 = spi1_pins;
status = okay;
- spidev0: spi@0 {
+ spidev2: spi@0 {
compatible = spidev;
reg = 0;
spi-max-frequency = 1600;
spi-cpha;
};
- spidev1: spi@1 {
+ spidev3: spi@1 {
compatible = spidev;
reg = 1;
spi-max-frequency = 1600;
diff --git a/arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi
b/arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi
index b2185dd..3aded7b 100644
--- a/arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi
+++ b/arch/arm/boot/dts/am335x-bone-spi1a-spidev.dtsi
@@ -11,14 +11,14 @@
pinctrl-0 = spi1a_pins;
status = okay;
- spidev0: spi@0 {
+ spidev2: spi@0 {
compatible = spidev;
reg = 0;
spi-max-frequency = 1600;
spi-cpha;
};
- spidev1: spi@1 {
+ spidev3: spi@1 {
compatible = spidev;
reg = 1;
spi-max-frequency = 1600;
you know.. half baked.. ;) Just got all the lcd's working today, spi1
hasn't been a priorty as i don't have a cape that uses it...
Regards,
--
Robert Nelson
http://www.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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] How to enable SPI devices on 3.14 kernel?
On Tue, Aug 26, 2014 at 10:25 PM, Dallas Clement dallas.a.clem...@gmail.com wrote: Hi Robert, many thanks for this. How dost one actually enable the spi devices in 3.14? I'm used to working with the overlays and capemgr, i.e. echoing to capemgr slots etc. Well it's still in it's infancy. Here's what works today: http://elinux.org/Beagleboard:Capes_3.8_to_3.14 Take a look at the main am335x-boneblack.dts file: https://github.com/beagleboard/linux/blob/3.14.17-ti-r15/arch/arm/boot/dts/am335x-boneblack.dts#L31 If you need usart1: Just change: /* #include am335x-bone-ttyO1.dtsi */ to: #include am335x-bone-ttyO1.dtsi and rebuild. I'm working on a second repo, so that you don't have to rebuild the kernel, just for dts changes: https://github.com/RobertCNelson/dtb-rebuilder/tree/3.14-ti Just issue make all and all *.dtb's will be rebuilt (these match the full kernel tree (3.14.17-ti-r15)) above. Haven't finished the make install so you still have to manually copy the *.dtb's. So, just make the *.dts change, rebuild, copy *.dtb, reboot, new device enabled.. Regards, -- Robert Nelson http://www.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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
