Hi, One of the reasons I'm trying to update is the uSD card I was using stopped working(booting). I can access some of the files, but I don't remember exactly the process I used to enable the pins (it was 4 to 5 years ago!). So, I'm not actually "running" it any more.
In any case I think what I did was modify your old config-pin to a different version called config-pins: http://xylotex.com/config-pins.txt and the overlay file here: http://xylotex.com/cape-univ-gpmc-00A0.dts.txt I would program the fpga with a general I/O bit-bang and then had a simple batch file that would call config-pins for each gpmc pin I wanted to switch modes on: *sudo ./config-pins P8.14 gpmc* I just did similar for all 20 pins I wanted to use for gpmc, and I was able to use the bus. I could then call the linuxcnc script (before the scripts was changed to machinekit), and the hm2-servo code would be able to access the fpga through the gpmc bus. Now when I try the same thing I end up with errors, which I'm now trying to solve. Thanks, Jeff On Friday, April 19, 2019 at 6:32:57 PM UTC-7, Charles Steinkuehler wrote: > > OK, so for that I would definitely recommend crafting your own overlay > that enables the GPMC pins you need. Again, most "casual" users will > not be able to do anything with GPMC, which is why it isn't part of > the "universal" cape to begin with. > > It shouldn't be too hard to migrate your existing device tree (or > overlay) to work on modern kernels. Do you have a link to the source > for what you're currently running? > > On 4/19/2019 7:40 PM, Jeff Pollard wrote: > > > > 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 > >> cha...@steinkuehler.net <javascript:> > >> > > > > > -- > Charles Steinkuehler > cha...@steinkuehler.net <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 machinekit+unsubscr...@googlegroups.com. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
