<font color='black' size='2' face='arial'><font color="black" face="arial" size="2"><br>
<div> <br>
</div>
<div style="font-family: arial,helvetica; font-size: 10pt; color: black;">>-----Original Message-----<br>
>From: Jeff Krasky <jeff.krasky@dspcg.com><br>
>To: etherlab-users <etherlab-users@etherlab.org><br>
>Sent: Tue, Nov 1, 2011 1:08 pm<br>
>Subject: [etherlab-users] install on non-PC<br>
<br>
<div id="AOLMsgPart_2_54fc710b-e7a9-4453-a339-5b53fa43d8d2">
<style>#AOLMsgPart_2_54fc710b-e7a9-4453-a339-5b53fa43d8d2 td{color: black;} @font-face {font-family:"MS Mincho"; panose-1:2 2 6 9 4 2 5 8 3 4;} @font-face {font-family:"@MS Mincho"; panose-1:0 0 0 0 0 0 0 0 0 0;} #AOLMsgPart_2_54fc710b-e7a9-4453-a339-5b53fa43d8d2 p.MsoNormal,#AOLMsgPart_2_54fc710b-e7a9-4453-a339-5b53fa43d8d2 li.MsoNormal,#AOLMsgPart_2_54fc710b-e7a9-4453-a339-5b53fa43d8d2 div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman";} #AOLMsgPart_2_54fc710b-e7a9-4453-a339-5b53fa43d8d2 a:link,#AOLMsgPart_2_54fc710b-e7a9-4453-a339-5b53fa43d8d2 span.MsoHyperlink {color:blue; text-decoration:underline;} #AOLMsgPart_2_54fc710b-e7a9-4453-a339-5b53fa43d8d2 a:visited,#AOLMsgPart_2_54fc710b-e7a9-4453-a339-5b53fa43d8d2 span.MsoHyperlinkFollowed {color:purple; text-decoration:underline;} #AOLMsgPart_2_54fc710b-e7a9-4453-a339-5b53fa43d8d2 span.EmailStyle17 {mso-style-type:personal-compose; font-family:"Times New Roman"; color:black; font-weight:normal; font-style:normal; text-decoration:none none;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in;} #AOLMsgPart_2_54fc710b-e7a9-4453-a339-5b53fa43d8d2 div.Section1 {page:Section1;} </style>
<div class="Section1"><font face="Times New Roman"> >...<br>
<br>
</font>
<div class="MsoNormal"><font color="black" face="Times New Roman" size="2"><span style="font-size: 11pt; color: black;">>2) I don’t think I can build
EtherCAT this way. The build machine is Windows to begin with, and even if I
managed to compile everything, >the default scripts wouldn’t work –
they’d want to install on the machine they are running on, the paths
wouldn’t be correct, etc.<br>
<br>
Here's how I recently cross built on x86 Ubuntu 10.04LTS for an ARM system with kernel sources and toolchain provided my the chip vendor:<br>
<br>
</span></font></div>
On host:<br>
<br>
TARG_KERNEL is path to kernel sources for target system<br>
TARG_FS is path to filesystem of target system<br>
<br>
In Etherlab source dir:<br>
<br>
./configure --prefix=$TARG_FS/opt --with-linux-dir=$TARG_KERNEL \<br>
--enable-generic --host=arm-none-linux-gnueabi-<br>
<br>
make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- # ARCH and CROSS_COMPILE redundant here?<br>
<br>
# I may have run make install as root here?<br>
<br>
<br>
On target as su (I haven't automated these steps yet):<br>
<br>
mknod /dev/EtherCAT0 c 252 0<br>
<br>
vi /etc/sysconfig/ethercat to include generic driver and set MAC addr<br>
<br>
cd /lib/modules/<kernel_being_run><br>
<br>
<br>
<br>
<font face="Times New Roman">>...</font><br>
<div class="MsoNormal"><font color="black" face="Times New Roman" size="2"><span style="font-size: 11pt; color: black;"> <br>
Thanks,<br>
Bruno<br>
</span></font></div>
<!-- end of AOLMsgPart_3_54fc710b-e7a9-4453-a339-5b53fa43d8d2 -->
</div>
</div>
</div>
</font></font>