I got I2C1, I2C2 and I2C3 working by editing the default am335x-bone-common.dts file. Then use uEnv to load this tree. devtree=/boot/am335x-bone.dtb
Op vrijdag 16 augustus 2013 23:04:58 UTC+2 schreef [email protected]: > > > For my robot project I would like to create a virtual cape that includes 3 > UARTs, the SPI interface, and both I2C devices (I2c0) is used on the board > and not accessible as I remember it. I need 2 buses for my project. I > got all those items working by hard-coding them into the bone-common device > tree source and replacing the /boot/am335x-boneblack.dtb with it but that > really doesn't seem like the way to go. Arch updates appear to replace > that file at times. > > I'm lost though in the weeds of the syntax for the fragment sections and > how that applies to the I2C devices. I think I understand that the first > fragment sets the correct mux modes and claims certain pins and the second > section connects the kernel device to the hardware but I'm not sure how to > convert from the working entries I have in am335x-bone-common.dtsi to an > overlay fragment. Lots of the stuff in there seems to be incantations and > the incantations vary from the SPI overlay I have and the others that > activate serial ports so I'm not sure what proper incantations are needed > for the I2C device. > > Has anyone setup the other I2C port using an overlay? > -- 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/groups/opt_out.
