[etherlab-dev] foe_write for copley firmware update

[Gavin Lambert]

They are not the same.  The "p/etherlabmaster" repository is the mainline repository, while the "u/uecasm/etherlab-patches" repository contains unofficial patches not yet in mainline.

However, that particular patch is included in the mainline default branch, just not in the stable-1.5 branch.

The unofficial patchset does contain some additional FoE patches but they are new features rather than bugfixes; at least in this regard you should be fine using the mainline default branch alone.
             
> -----Original Message-----
> From: Lingjie_Kong at amat.com
> Sent: Tuesday, 31 October 2017 06:23
> To: ricardo.ribalda at gmail.com
> Cc: etherlab-dev at etherlab.org
> Subject: Re: [etherlab-dev] foe_write for copley firmware update
> 
> Hi Ricardo,
> 
> Thanks for the information. Meanwhile, I just want to double check that is
> the patchset version that you are talking about the same as the EtherLAB
> EtherCAT Master code in mercurial repository.
> https://sourceforge.net/p/etherlabmaster/code/ci/default/tree/
> 
> Because I see the document in NEWS file.
> 
> Changes since 1.5.2:
> 
> * Fixed FoE timeout calculation bug.
> 
> Best regards,
> 
> Lingjie (Kimi) Kong
> Software Engineer – Servo Control Engineering || Common Solution Group
> || Applied Materials lingjie_kong at amat.com || Office: (408)563-4400
> 
> The content of this message is Applied Materials Confidential. If you are not
> the intended recipient and have received this message in error, any use or
> distribution is prohibited. Please notify me immediately by reply e-mail and
> delete this message from your computer system. Thank you.
> 
> ** Save a tree. Please don't print this e-mail unless needed.
> 
> -----Original Message-----
> From: Ricardo Ribalda Delgado [mailto:ricardo.ribalda at gmail.com]
> Sent: Monday, October 30, 2017 5:37 AM
> To: Lingjie Kong --TR <Lingjie_Kong at amat.com>
> Cc: etherlab-dev at etherlab.org
> Subject: Re: [etherlab-dev] foe_write for copley firmware update
> 
> Have you tried the unofficial patchset? It solves an issue with the foe timeout
> calculation
> 
> https://sourceforge.net/u/uecasm/etherlab-patches/ci/default/tree/
> 
> 
> regards!
> 
> On Wed, Oct 25, 2017 at 6:33 PM,  <Lingjie_Kong at amat.com> wrote:
> > Hi,
> >
> >
> >
> > I am just wondering that does anybody notice the following issue when
> > downloading the firmware for Copley Drive through foe_write command.
> >
> >
> >
> > First, I put the Copley drive into BOOT mode.
> >
> > ethercat -m0 states -p0 BOOT
> >
> >
> >
> > Then, I send the Copley .cff to download firmware
> >
> > ethercat -m0 foe_write -p0 /var/ftp/gather/BE2_2.99.cff
> >
> >
> >
> > However, I consistently get FOE_TIMEOUT_ERROR and FOE_WC_ERROR
> >
> >
> >
> > Based on what Copley told me that,
> >
> >
> >
> > “It looks like your EtherCAT FoE command timed out during the firmware
> > download.  Can you increase the timeout that it uses? At the start of
> > the firmware download the drive needs to erase the old firmware before
> > it can start writing the new file.  This can take several seconds.
> > During that time the drive will indicate that it's busy and the master
> > should keep trying.  It's possible that the master program you're
> > using quit before the drive finished erasing the flash.”
> >
> >
> >
> > Therefore, I am just wondering that does anybody has problem on
> > downloading firmware through foe_write like above and how to resolve
> > it. Any suggestion will be really appreciated.
> >
> >
> >
> > Best regards,
> >
> >
> >
> > Lingjie (Kimi) Kong
> >
> > Software Engineer – Servo Control Engineering || Common Solution Group
> > || Applied Materials
> >
> > lingjie_kong at amat.com || Office: (408)563-4400
> >
> > The content of this message is Applied Materials Confidential. If you
> > are not the intended recipient and have received this message in
> > error, any use or distribution is prohibited. Please notify me
> > immediately by reply e-mail and delete this message from your computer
> system. Thank you.
> >
> > ** Save a tree. Please don't print this e-mail unless needed.
> >
> >
> >
> >
> > ________________________________
> >
> >
> > _______________________________________________
> > etherlab-dev mailing list
> > etherlab-dev at etherlab.org
> > http://lists.etherlab.org/mailman/listinfo/etherlab-dev
> >
> 
> 
> 
> --
> Ricardo Ribalda
> 
> ________________________________
> 
> _______________________________________________
> etherlab-dev mailing list
> etherlab-dev at etherlab.org
> http://lists.etherlab.org/mailman/listinfo/etherlab-dev