[etherlab-users] Looking for Slave firmware update example

[Gavin Lambert]

The change to OP seems wrong, but otherwise the procedure below looks about
right.

 

One thing to note is that the foe_write command takes two filenames – the
other you’ve left unspecified (and so will default to the .efw filename) is
the internal name sent to the device.  You’ll have to check with the vendor
whether they require a particular name or whether they’ll accept any name.
(If there’s upgrade instructions in the docs, it probably shows how the
upgrade is done via TwinCAT – you can see what filename is used there, or if
it doesn’t appear to be relevant.)

 

A quick glance at the docs myself suggests that the device doesn’t
particularly care what filename is used.  But to be sure, you will need to
try it.

 

From: etherlab-users-bounces at etherlab.org
[mailto:etherlab-users-bounces at etherlab.org] On Behalf Of Graeme Foot
Sent: Wednesday, 6 November 2013 11:17
To: etherlab-users at etherlab.org
Subject: [etherlab-users] Looking for Slave firmware update example

 

Hi,

 

I want to update the firmware on an EtherCAT slave (an EL6021 module).  I'm
using the latest 1.5.2 master.

 

I take it that I need to use the "ethercat foe_write" command but I haven't
been able to find what "output-file" name I should be using.  Should it be
the name of the .efw file (or not used so it automatically picks up the name
of the .efw file)?

 

 

Is this general procedure correct? :

- ethercat states -p1 INIT

- ethercat states -p1 BOOT

à check current state is BOOT

- ethercat foe_write -p1 /tmp/EL6021_FW06.efw

- ethercat states -p1 INIT

- ethercat states -p1 OP

à repower the slave and check new firmware is active

 

 

Thanks,

Graeme Foot

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20131106/8afef44b/attachment-0003.htm>