Hi, Not taken the wrong way. I've already used the gpmc to communicate with my fpga board. I have a servo system based on hostmot2 and a custom driver to go between hm2-servo and the gpmc which then 'talks' to the fpga. This all works fine This way way back in 2015 though. The method of accessing the gpmc connectivity has changed a lot since I last tried using the BBB with the old version of machinekit I was using. Now I'm trying to update what I have to newer machinekit software (with all the new overlays, etc.) and can no longer program the pins to allow me to access the gpmc. Jeff
On Friday, April 19, 2019 at 4:51:17 PM UTC-7, Charles Steinkuehler wrote: > > On 4/19/2019 6:39 PM, Jeff Pollard wrote: > > > > Hi, > > > > Thanks Robert and Charles. > > I've taken this: > > > https://github.com/RobertCNelson/bb.org-overlays/blob/master/src/arm/cape-universal-00A0.dts#L1551-L1562 > > > > > and added what would be necessary to get the gmpc pins usable > following > > the convention of the rest of the file. > > Hopefully this something I can test here... or is this something that > has > > to be in the "kernel" and out of my reach? > > If I can test here, can you tell me how to compile and deploy the new > dts > > file so I can test it out? > > Don't take this the wrong way, but if you have to ask about how to > compile a device tree (or overlay), you probably shouldn't be trying > to use the GPMC interface. > > Let's take a step back...exactly what are you trying to do? > > -- > Charles Steinkuehler > [email protected] <javascript:> > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
