[etherlab-users] ethercat on BBB/Rasperry

[Raz]

let us start with step 1.

Why I need "own kernel" ?
you need a precompiled kernel headers. problem is that it is likely
that the signature of the kernel you build differs from the one you
already have in  your raspbian.

I saw on the etherlab site that not all kernel work with etherlab ?
For example I worked with kernel 3.8 on beaglebone. Is it possible to
use etherlab with kernel 3.8 ?

i will help you with that if needed. i fixed etherlLAB to work with
3.8.  but i would suggest you download an old raspbian kernel.
probably 3.2 or 3.0.






On Mon, Sep 22, 2014 at 4:29 PM, Jean-Philippe Pinget
<jp.pinget at yahoo.fr> wrote:
> Hi Raz,
>
> Thank you for your quick anwser !
>
> I have already worked on qt for beaglebone. I have successfully compiled qt with toolchain linaro.
> I did this with some tutorials.
> I think it's almost the same thing on rasperry pi b+.
>
> For ethercat... Etherlab.... Hmmm .... I think it will be harder.
>
> Let's try to begin :
>
> Step 1) compile and boot my own kernel.
>
> Why I need "own kernel" ?
> I saw on the etherlab site that not all kernel work with etherlab ?
> For example I worked with kernel 3.8 on beaglebone. Is it possible to use etherlab with kernel 3.8 ?
>
> Step 2) download the etherlab suite
>
> Ok, more precisely, what files ?
>
> Step 3) configure etherlab suite to use pi toolchain. Use the ec_generic driver.
>
> How can I configure etherlab suite ? What does it mean ?
> What is ec_generic driver ?
>
> Step 4) copy the etherlab output to pi.
>
> I think I will understand that at the end of procedure.
>
> Thank you very much for your help.
>
> Best regards.
>
>
>
>> Le 22 sept. 2014 à 13:15, Raz <raziebe at gmail.com> a écrit :
>>
>> Hey Jean
>>
>>
>> There are the steps you need to take:
>> 1.  compile and boot your own kernel.
>> 2.  download the etherlab suite .
>> 3.  configure the etherlab suite to use the pi toolchain. use the
>> ec_generic driver.
>> 4.  copy the ethelab output to pi. this includes
>> ec_master.ko,ec_generic.ko, ethercat util, libethercat.
>>
>> All of the above are for using etherlab ( ie, master ) on pi. to
>> launch qt on the pi you need to compile qt-embedded for pi. this is a
>> long task but it possible. take alook at:
>> http://qt-project.org/doc/qt-5/embedded-linux.html .
>>
>> if you have more questions, like , "how do i do step X" email me back.
>> i will help you.
>>
>> regards
>> raz
>>
>>
>>
>>
>>
>>
>>
>>
>> On Mon, Sep 22, 2014 at 1:32 PM, Jean-Philippe Pinget
>> <jp.pinget at yahoo.fr> wrote:
>>> Hi,
>>>
>>> Making research about Ethercat on embedded Linux, I found your website. It
>>> seems to be interesting for my project.
>>>
>>> But I'm not an expert on Ethercat.
>>>
>>> My goal is to drive an ETHERCAT MODULE (from BECKHOFF or others) with a
>>> RASPERRY PI or a BEAGLEBONEBLACK.
>>>
>>> More precisely, you can see below what I want to do :
>>>
>>>
>>>
>>> I have a Rasperry PI B+ and an Ethercat Terminal Beckhoff.
>>>
>>> On my rasperry PI B+, I want to launch an HMI (a Qt Application).
>>>
>>> On this HMI (drawn with Qt), there is a button (for example). From this
>>> button, I want to activate an output of the Beckhoff Ethercat Terminal
>>> (Sending an Ethercat command from the RASPERRY PI B+).
>>>
>>> Can I do this with Etherlab ?
>>> If yes, could you tell me what are the first steps ?
>>>
>>>
>>> Best Regards.
>>>
>>> _______________________________________________
>>> etherlab-users mailing list
>>> etherlab-users at etherlab.org
>>> http://lists.etherlab.org/mailman/listinfo/etherlab-users
>>
>>
>>
>> --
>> https://sites.google.com/site/ironspeedlinux/



-- 
https://sites.google.com/site/ironspeedlinux/