Re: [beagleboard] debian: release candidate: 2014-12-11
Thanks! Does the cape-universaln overlay play nice with I2C? I'm having trouble with it being unable to read /dev/i2c-2 (which is created after loading cape-universaln). Trying to run the following fails, both by taking a long time to run (about 1 second per address) and also by not finding my devices at 0x27, 0x48, and 0x77: root@beaglebone:~# i2cdetect -y -r 2 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- The expected result (tested against the BB-I2C1 overlay) is the command returns quickly, and find a device at those three addresses. root@beaglebone:~# echo BB-I2C1 > /sys/devices/bone_capemgr.9/slots root@beaglebone:~# i2cdetect -y -r 2 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- 27 -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- 48 -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- 77 On Sunday, December 28, 2014 12:55:31 PM UTC-5, RobertCNelson wrote: > > On Sun, Dec 28, 2014 at 9:32 AM, Ian Woloschin > wrote: > > So where'd they go? Or, what's the naming convention of them? > > > > I've written a simple Python library to use for GPIO control on my > projects, > > and I want the whole thing to be automated. The sysfs part is easy, but > I > > couldn't find any overlays, and I'd rather not make my own overlay for > each > > GPIO pin. > > You can view the whole list in System-map > > cat /boot/System.map-`uname -r` | dtbo > > c0559bec r _fw_cape_bebopr_R2_dtbo_bin > c055c3ac r _fw_cape_bebopr_ena_R2_dtbo_bin > c055ead4 r _fw_cape_bebopr_brdg_R2_dtbo_bin > c0561020 r _fw_cape_bone_2g_emmc1_dtbo_bin > c0561514 r _fw_cape_bone_adafruit_lcd_00A0_dtbo_bin > c0562098 r _fw_cape_bone_dvi_00A0_dtbo_bin > c0562a14 r _fw_cape_bone_dvi_00A1_dtbo_bin > c0563918 r _fw_cape_bone_dvi_00A2_dtbo_bin > c056429c r _fw_cape_bone_hexy_00A0_dtbo_bin > c0565300 r _fw_cape_bone_lcd3_00A0_dtbo_bin > c05667d0 r _fw_cape_bone_lcd3_00A2_dtbo_bin > > > 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] debian: release candidate: 2014-12-11
Am Sonntag, 28. Dezember 2014 18:48:49 UTC+1 schrieb RobertCNelson: > > If your happy with your current "libpruio-00A0.dtbo" i can add it to > the default built.. > Meanwhile I made some adaptations for the next release (regarding QEP pins). I'd prefer to send you the latest version (of all related files). What about interferences? libpruio-00A0.dtbo claims the same header pins as the universal overlay (= all free pins)? BR -- 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] debian: release candidate: 2014-12-11
On Sun, Dec 28, 2014 at 9:32 AM, Ian Woloschin wrote: > So where'd they go? Or, what's the naming convention of them? > > I've written a simple Python library to use for GPIO control on my projects, > and I want the whole thing to be automated. The sysfs part is easy, but I > couldn't find any overlays, and I'd rather not make my own overlay for each > GPIO pin. You can view the whole list in System-map cat /boot/System.map-`uname -r` | dtbo c0559bec r _fw_cape_bebopr_R2_dtbo_bin c055c3ac r _fw_cape_bebopr_ena_R2_dtbo_bin c055ead4 r _fw_cape_bebopr_brdg_R2_dtbo_bin c0561020 r _fw_cape_bone_2g_emmc1_dtbo_bin c0561514 r _fw_cape_bone_adafruit_lcd_00A0_dtbo_bin c0562098 r _fw_cape_bone_dvi_00A0_dtbo_bin c0562a14 r _fw_cape_bone_dvi_00A1_dtbo_bin c0563918 r _fw_cape_bone_dvi_00A2_dtbo_bin c056429c r _fw_cape_bone_hexy_00A0_dtbo_bin c0565300 r _fw_cape_bone_lcd3_00A0_dtbo_bin c05667d0 r _fw_cape_bone_lcd3_00A2_dtbo_bin 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] debian: release candidate: 2014-12-11
On Sun, Dec 28, 2014 at 11:03 AM, TJF wrote: > > > Am Samstag, 27. Dezember 2014 23:22:26 UTC+1 schrieb Rick M: >> >> >> > On Dec 27, 2014, at 14:13 , Robert Nelson wrote: >> > >> > On Thu, Dec 25, 2014 at 4:24 PM, Rick Mann >> > wrote: >> >> >> >> On Friday, December 12, 2014 3:16:23 PM UTC-6, RobertCNelson wrote: >> >> >> >>> 2: This is open to more users, if you need something packaged and >> >>> distributed that is open source, ping us. >> >> >> >> How about libpruio? >> >> >> >>http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ >> >> >> >> Thanks for all the hard work! >> > >> > Thanks Rick, i'll look into this.. >> >> Thanks, Robert. It's a complicated project because it uses FreeBasic, and >> I'm not sure if that's needed to build it or use it. For those of us who >> want to just use it from C, maybe the basic package could install a built >> version and not install the FreeBasic compiler. > > > The first versions libpruio-0.0.x needed the FreeBASIC compiler installed, > to build and to use the library. > > That changed since libpruio-0.2. The binary libprussdrv.so and the C header > pruio.h are included in the package. To use the library from C code there's > only one further dependency named libprussdrv. (Only to [re-]build libpruio > itself, it needs a modified pasm assembler and the FreeBASIC compiler.) > > From my point of view the problem is the inbuild universal overlay, which > doesn't meet all needs of libpruio. It'd need the libpruio-00A0.dtbo > features in-build in the distro. (All current features can get retained, > when the config-pin tool from C. Steinkuehler gets adapted.) If your happy with your current "libpruio-00A0.dtbo" i can add it to the default built.. 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] debian: release candidate: 2014-12-11
Am Sonntag, 28. Dezember 2014 18:03:47 UTC+1 schrieb TJF: > > The binary libprussdrv.so and ... > A typo, sorry! The binary *libpruio.so* and ... -- 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] debian: release candidate: 2014-12-11
Am Samstag, 27. Dezember 2014 23:22:26 UTC+1 schrieb Rick M: > > > > On Dec 27, 2014, at 14:13 , Robert Nelson > wrote: > > > > On Thu, Dec 25, 2014 at 4:24 PM, Rick Mann > wrote: > >> > >> On Friday, December 12, 2014 3:16:23 PM UTC-6, RobertCNelson wrote: > >> > >>> 2: This is open to more users, if you need something packaged and > >>> distributed that is open source, ping us. > >> > >> How about libpruio? > >> > >>http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ > >> > >> Thanks for all the hard work! > > > > Thanks Rick, i'll look into this.. > > Thanks, Robert. It's a complicated project because it uses FreeBasic, and > I'm not sure if that's needed to build it or use it. For those of us who > want to just use it from C, maybe the basic package could install a built > version and not install the FreeBasic compiler. > The first versions libpruio-0.0.x needed the FreeBASIC compiler installed, to build and to use the library. That changed since libpruio-0.2. The binary libprussdrv.so and the C header pruio.h are included in the package. To use the library from C code there's only one further dependency named libprussdrv. (Only to [re-]build libpruio itself, it needs a modified pasm assembler and the FreeBASIC compiler.) >From my point of view the problem is the inbuild universal overlay, which doesn't meet all needs of libpruio. It'd need the libpruio-00A0.dtbo features in-build in the distro. (All current features can get retained, when the config-pin tool from C. Steinkuehler gets adapted.) BR -- 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] debian: release candidate: 2014-12-11
https://github.com/cdsteinkuehler/beaglebone-universal-io Next time try looking a little harder for *something* On Sun, Dec 28, 2014 at 8:32 AM, Ian Woloschin wrote: > So where'd they go? Or, what's the naming convention of them? > > I've written a simple Python library to use for GPIO control on my > projects, and I want the whole thing to be automated. The sysfs part is > easy, but I couldn't find any overlays, and I'd rather not make my own > overlay for each GPIO pin. > > -Ian > > On Saturday, December 27, 2014 5:13:10 PM UTC-5, RobertCNelson wrote: > >> On Sat, Dec 27, 2014 at 8:49 AM, Ian Woloschin >> wrote: >> > Does this image have pre-built overlays for GPIO control? I took a >> look in >> > /lib/firmware but couldn't find anything, and I'm wondering if that >> should >> > be included by default? >> >> They are "built-in" we removed them from /lib/firmware as users >> thought they could "change" them, which they couldn't (as they were >> "built-in") >> >> > Otherwise this is pretty nice! Went from a pile of parts to a working >> > project in a day or two without worrying about the OS at all, other >> than >> > figuring out how to enable the GPIO mux mode. >> >> 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] debian: release candidate: 2014-12-11
So where'd they go? Or, what's the naming convention of them? I've written a simple Python library to use for GPIO control on my projects, and I want the whole thing to be automated. The sysfs part is easy, but I couldn't find any overlays, and I'd rather not make my own overlay for each GPIO pin. -Ian On Saturday, December 27, 2014 5:13:10 PM UTC-5, RobertCNelson wrote: > > On Sat, Dec 27, 2014 at 8:49 AM, Ian Woloschin > wrote: > > Does this image have pre-built overlays for GPIO control? I took a look > in > > /lib/firmware but couldn't find anything, and I'm wondering if that > should > > be included by default? > > They are "built-in" we removed them from /lib/firmware as users > thought they could "change" them, which they couldn't (as they were > "built-in") > > > Otherwise this is pretty nice! Went from a pile of parts to a working > > project in a day or two without worrying about the OS at all, other than > > figuring out how to enable the GPIO mux mode. > > 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] debian: release candidate: 2014-12-11
On Sat, Dec 27, 2014 at 4:22 PM, Rick Mann wrote: > >> On Dec 27, 2014, at 14:13 , Robert Nelson wrote: >> >> On Thu, Dec 25, 2014 at 4:24 PM, Rick Mann wrote: >>> >>> On Friday, December 12, 2014 3:16:23 PM UTC-6, RobertCNelson wrote: >>> 2: This is open to more users, if you need something packaged and distributed that is open source, ping us. >>> >>> How about libpruio? >>> >>>http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ >>> >>> Thanks for all the hard work! >> >> Thanks Rick, i'll look into this.. > > Thanks, Robert. It's a complicated project because it uses FreeBasic, and I'm > not sure if that's needed to build it or use it. For those of us who want to > just use it from C, maybe the basic package could install a built version and > not install the FreeBasic compiler. > > Having said that, my project doesn't really need it currently, so I'd make it > a lower priority than other things. As long as freebasic is in debian's repo it should be pretty straight forward. ;) Just going thru the Christmas backlog. ;) But when Gerald get's back, thru the new user/spam queue they'll probally be lots and lots of questions. :) 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] debian: release candidate: 2014-12-11
> On Dec 27, 2014, at 14:13 , Robert Nelson wrote: > > On Thu, Dec 25, 2014 at 4:24 PM, Rick Mann wrote: >> >> On Friday, December 12, 2014 3:16:23 PM UTC-6, RobertCNelson wrote: >> >>> 2: This is open to more users, if you need something packaged and >>> distributed that is open source, ping us. >> >> How about libpruio? >> >>http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ >> >> Thanks for all the hard work! > > Thanks Rick, i'll look into this.. Thanks, Robert. It's a complicated project because it uses FreeBasic, and I'm not sure if that's needed to build it or use it. For those of us who want to just use it from C, maybe the basic package could install a built version and not install the FreeBasic compiler. Having said that, my project doesn't really need it currently, so I'd make it a lower priority than other things. -- Rick Mann rm...@latencyzero.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] debian: release candidate: 2014-12-11
On Thu, Dec 25, 2014 at 4:24 PM, Rick Mann wrote: > > On Friday, December 12, 2014 3:16:23 PM UTC-6, RobertCNelson wrote: > >> 2: This is open to more users, if you need something packaged and >> distributed that is open source, ping us. > > How about libpruio? > > http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ > > Thanks for all the hard work! Thanks Rick, i'll look into this.. 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] debian: release candidate: 2014-12-11
On Sat, Dec 27, 2014 at 8:49 AM, Ian Woloschin wrote: > Does this image have pre-built overlays for GPIO control? I took a look in > /lib/firmware but couldn't find anything, and I'm wondering if that should > be included by default? They are "built-in" we removed them from /lib/firmware as users thought they could "change" them, which they couldn't (as they were "built-in") > Otherwise this is pretty nice! Went from a pile of parts to a working > project in a day or two without worrying about the OS at all, other than > figuring out how to enable the GPIO mux mode. 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] debian: release candidate: 2014-12-11
What did you do to get GPIO mux working? I've got a working system and am terrified to change it to anything else right now, for fear of having to spend weeks re-learning how to do everything. > On Dec 27, 2014, at 06:49 , Ian Woloschin wrote: > > Does this image have pre-built overlays for GPIO control? I took a look in > /lib/firmware but couldn't find anything, and I'm wondering if that should be > included by default? > > Otherwise this is pretty nice! Went from a pile of parts to a working > project in a day or two without worrying about the OS at all, other than > figuring out how to enable the GPIO mux mode. > > On Thursday, December 25, 2014 5:25:09 PM UTC-5, Rick M wrote: > > On Friday, December 12, 2014 3:16:23 PM UTC-6, RobertCNelson wrote: > > > 2: This is open to more users, if you need something packaged and > > distributed that is open source, ping us. > > How about libpruio? > > http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ > > Thanks for all the hard work! > > -- > Rick Mann > rm...@latencyzero.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. -- Rick Mann rm...@latencyzero.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] debian: release candidate: 2014-12-11
Does this image have pre-built overlays for GPIO control? I took a look in /lib/firmware but couldn't find anything, and I'm wondering if that should be included by default? Otherwise this is pretty nice! Went from a pile of parts to a working project in a day or two without worrying about the OS at all, other than figuring out how to enable the GPIO mux mode. On Thursday, December 25, 2014 5:25:09 PM UTC-5, Rick M wrote: > > > On Friday, December 12, 2014 3:16:23 PM UTC-6, RobertCNelson wrote: > > > 2: This is open to more users, if you need something packaged and > > distributed that is open source, ping us. > > How about libpruio? > > http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ > > Thanks for all the hard work! > > -- > Rick Mann > rm...@latencyzero.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] debian: release candidate: 2014-12-11
On Friday, December 12, 2014 3:16:23 PM UTC-6, RobertCNelson wrote: > 2: This is open to more users, if you need something packaged and > distributed that is open source, ping us. How about libpruio? http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/ Thanks for all the hard work! -- Rick Mann rm...@latencyzero.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.
