>> >> root@beaglebone:~# config-pin -l P9.24 >> default gpio gpio_pu gpio_pd uart can i2c pruin >> >> root@beaglebone:~# config-pin -l P9.26 >> default gpio gpio_pu gpio_pd uart can i2c pruin >> >> root@beaglebone:~# config-pin P9.24 uart >> >> root@beaglebone:~# config-pin P9.26 uart >> >> and now /dev/ttyS1 should be working as a usart ;) > > > Bingo the minicom loopback test now works along with my application, almost > too easy, I was reading up on config-pin yesterday but got confused and > thought it couldn't be that simple :) > I"m not sure I'll need rts/ctr but I see uart1 rts/cts on P9 19&20 are "not > modifyable", guess they are now hardwired to /dev/i2c-2 in the kernel which > I'm sure many people buying Beaglebones would prefer over a default > interface to obsolete serial port equipment needing rts/cts hardware > handshaking. > > Y'all have been making really great progress behind the scenes, but the > details aren't getting out to where they can be easily found. > While config-pin may not be the most efficient way, it takes a lot less > effort than trying to learn how to write or modify an overlay! > > One, hopefully last, question about the boot up timing, if I wrote a script > with a list of config-pin commands to setup what I need, could I run it with > a root crontab @reboot? or would it be safer to run it via system() when my > code is initializing the gpio via /sys/class/ file writes?
I'd watch the slots file and wait for the cape-universal to be loaded. (within 10-15-ish seconds after power on).. Then your script can use config-pin and modify away.. 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.
