I've just downloaded the latest test iot image (BeagleBoard.org Debian Image 2017-11-26) and tried config-pin on the BeagleBone Black
bone$ *config-pin -l P9_31 spi_sclk* default gpio gpio_pu gpio_pd spi_sclk pwm pruout pruin So far so good, but I want to use SPI, so bone$ *sudo config-pin P9_31 spi_sclk* P9_31 pinmux file not found! bash: /sys/devices/platform/ocp/ocp*P9_31_pinmux/state: No such file or directory Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P9_31_pinmux/state Oops, what am I missing? --Mark On Tuesday, November 28, 2017 at 12:33:35 PM UTC-5, RobertCNelson wrote: > > On Tue, Nov 28, 2017 at 12:45 AM, Ken Shirriff <[email protected] > <javascript:>> wrote: > > I'm trying to understand the current state of device tree overlays. Is > it > > correct that the cape manager is now obsolete, and device tree overlays > > should be set up through /boot/uEnv.txt? What about config-pin? Is that > an > > alternative to device tree overlays, or something orthogonal? > > > > The system I'm using is a PocketBeagle with 4.4.91-ti-r133. Before that > I > > was using the 3.8 kernel on a BeagleBone and everything seems to have > > changed. (Is there a summary somewhere of the new world?) > > Kernel Overlays is obsolete. > > We now use U-Boot Overlays: > > https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays > > config-pin is enabled by default, it allows you to easily change pin's > to different functions. > > 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/c7fa05fc-cbdd-468a-a295-a29a3a1d0f92%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
