On 3/17/14 11:55 , Paul S. wrote: > > Are you adding your comp's write function to a running thread? > As I was told, I did the following things: > > halrun -V > loadrt threads > loadrt imx6gpiofix > start > setp imx6gpiofix.0.pin-00-out 1 > setp imx6gpiofix.0.pin-00-out 0
Ah, that's a problem. After your loadrt calls but before your start, addf your functions to your threads. > Oscilloscope shows no change on any pin on a board. > > >> Does your read function successfully read the gpios? > Haven't tried that yet, only tried to make gpios work as an output. > >> Are you basing your work on the unified-build-candidate-3 branch or >> something else? ubc3 has very different logging. In master and 2.5, >> look in dmesg, ~/linuxcnc_print.txt, and ~/linuxcnc_debug.txt. In ubc3, >> look in dmesg and /var/log/linuxcnc.log. > Yep, I've been working with unified-build-candidate-3 branch, though I > haven't git pushed for a couple of month or so. There is no > ~/linuxcnc_print.txt, or ~/linuxcnc_debug.txt, or /var/log/linuxcnc.log, > though I've given 777 rights to /var/log just to make sure that linuxcnc is > able to create logs there. There are some other steps you need to do to get logging working in ubc3. It might be in the documentation, or maybe one of the ubc folks can help you with it. -- Sebastian Kuzminsky ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
