It seems that i failed to clearify enough that eclave may work as a user space exe, not just as driver. The driver is for performance matters. i suggest you boot some linux, like fedora or ubunto and: $ git clone git://git.code.sf.net/p/ecslave/code ecslave $ cd ecslave $ autoreconf $ automake --add-missing $ sh ./configure $ make the output would be ecslave binary that can executed on you pc. $ ./ec_slave< rx interface> < tx interface> now cross-wire an ethercat master to your pc and then execute: $ ./ec_slave eth1 --> if eth1 is the interface you connected .
you can also piggy back another pc/pi with eclave so that you have several ecslaves. to compile for pi i would suggest you compile in pi itself, as you pcap.h and this file is part of libcap-dev and it would easier to apt-get it in pi then add it to the build environment ( aka toolchain ) of pi. Also, if you guys want , i can upload to a dropbox the binaries to pi. you can also compile ecslave for arduino if you want. regards raz On Wed, Oct 1, 2014 at 4:59 AM, Stijn Goossens <[email protected]> wrote: > Dear Raz, > > I've found this thread about etherlab and BBB or raspberry: > https://www.mail-archive.com/[email protected]/msg02330.html > > Is there a chance you could explain (or publish) in more detail the steps > you need to take to make a raspberry or BBB working? > > I'm a control engineer so I'm quite deeply into simulink and rapid > prototyping, but compiling kernels etc. is not really something I'm very > used to :). So I'm quite curious to know what kind of hassle it is to get > etherlab operational. > > Thanks in advance! > Stijn -- https://sites.google.com/site/ironspeedlinux/ _______________________________________________ etherlab-users mailing list [email protected] http://lists.etherlab.org/mailman/listinfo/etherlab-users
