I think its because of this, the Adafruit Python GPIO library broke. Is there anyway to fix this? I fixed the I2C probably by changing the python file, but unsure how for the SPI.
On Friday, March 21, 2014 11:41:06 AM UTC-5, David wrote: > > Robert, > It appears that the GPIO label numbering scheme has been changed > from the device tree overlay's "1 to n+1", to the more con-formant 0 to > n; I fell into this trap :-[ . I will send you my consolidated patch > directly, once I had time to check it out further. > > Sorry for the confusion. Regards, > > Dave. > > > On 03/20/2014 12:33 PM, David Lambert wrote: > > Robert, > > It looks like I spoke too soon. Although my device tree appears to > > get loaded and my driver entry point is called with correct > > parameters, the pinmux does not appear to get set up correctly. Where > > do I look in 3.13 kernel based systems to debug the pinmux settings? > > > > Best regards, > > > > Dave. > > > > > > On 03/06/2014 03:11 PM, Robert Nelson wrote: > >> On Thu, Mar 6, 2014 at 3:03 PM, David Lambert > >> <da...@lambsys.com<javascript:>> > wrote: > >>> Just a suggestion. If the dtb for the cape does not exist or is > >>> corrupted, > >>> could the device tree default to the base, for example > >>> am335x-boneblack.dtb? > >> You read my mind, there is a new file test function, i'd like to > >> backport to v2014.01 > >> > >> > http://git.denx.de/?p=u-boot.git;a=commit;h=e5e897c01b1cd496187ca56a38ff5559d27f951c > > >> > >> > >> Then yes, we can set it to use the default *.dtb. > >> > >> Regards, > >> > > > > -- 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.
