Interesting, thanks Charles... FWIW, I've been working with the eQEP hardware from within the PRU and that also lacks a header file, however, some example TI code (which I am using in my project) shows:
/* Non-CT register defines */ #define CM_PER_EPWMSS1 (*((volatile unsigned int *)0x44E000CC)) Coupled with: #include <sys_pwmss.h> As being good enough to allow subsequent access and control of the PWMSS from within the PRU... I have added a #define for the base address of I2C2 but I now need to find if there is a header file to go with. I'll do some searching. On Wednesday, 15 August 2018 03:30:01 UTC+1, Charles Steinkuehler wrote: > > On 8/14/2018 6:29 AM, 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... > > AFAIK, there are no "standard" headers for accessing physical hardware > like the i2c buses from the PRU. Even the Linux kernel generally > mixes this sort of thing between header files (for the bit definitions > and "structure" of the control registers) and the device tree (for > base addresses, IRQ values, etc). > > Probably the closest you'll find is something from the TI bare-metal code: > > http://processors.wiki.ti.com/index.php/StarterWare > > -- > Charles Steinkuehler > cha...@steinkuehler.net <javascript:> > -- 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/c2ed5676-e76b-4227-8e87-f249db3eeed1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
