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 <[email protected] 
> <javascript:>> 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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to