Hugh, Thanks for sharing your research. Any chance you could also include a reference (ie where did you find this info)?
Thanks On Friday, August 17, 2018 at 9:43:47 AM UTC-5, Hugh Frater wrote: > > I forgot this from my previous post: > > /* I2C2 register offsets */ > > #define I2C2_STATUSRAW (*((volatile unsigned int*)0x4819C024)) > #define I2C2_CNT (*((volatile unsigned int*)0x4819C098)) > #define I2C2_SA (*((volatile unsigned int*)0x4819C0AC)) > #define I2C2_DATA (*((volatile unsigned int*)0x4819C09C)) > #define I2C2_CON (*((volatile unsigned int*)0x4819C0A4)) > #define I2C2_SCLL (*((volatile unsigned int*)0x4819C0B4)) > #define I2C2_SCLH (*((volatile unsigned int*)0x4819C0B8)) > #define I2C2_PSC (*((volatile unsigned int*)0x4819C0B0)) > > I couldn't be bothered to setup a header file for this lot, so just > stuffed it in the top of my PRU code... Registers for other I2C modules are > in the memory map from the am335X_trm > > On Tuesday, 14 August 2018 12:29:12 UTC+1, Hugh Frater wrote: >> >> Does anyone know the header file I need to include to get access to the >> i2c2 control registers from within the PRU subsystem? Having a hard time >> getting any info and my google-foo is usually pretty decent... >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/ec0bcc70-1d82-4877-b074-c762337ff4bd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
