This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AMIC110: Support Availability for ” .efw ” File

Guru 10235 points

Part Number: AMIC110

Hi Support Team,

I have a question regarding the required specifications for FoE updates on the AMIC110.
Regarding the “.efw” file format used to combine the Slave Unit Firmware updater with SII information,
is there an official procedure for directly handling .efw files on the AMIC110?

If not supported on the AMIC110, please share any official procedures or
documented results for directly handling .efw files on the AM243x.

Best Regards,
Kanae

 

  • Hello Kanae,

    Please provide additional context. What are these .efw files?

    It seems like FoE has to do with downloading files over the EtherCAT protocol?

    Regards,

    Nick


  • Hi Nick,

    Thank you for your reply.

    The .efw file is the extension for the ETHC Firmware File, which combines the controller's firmware
    and ESI information into a single file. This enables updating both components with a single transfer.
    This is the default extension used when downloading TwinCAT.

    Our customer's intended implementation is as follows:
    Combine the ESI (EtherCAT SubDevice Information) binary file and
    the other SoC update file (in ZIP format) into a single file andsend it with the “.efw” extension.
    On AMIC110 side, after receiving this, they wish to simultaneously use the ESI to update
    the EEPROM and send the ZIP file to the other SoCs.

    The goal of this method is to simultaneously update the AMIC110's SII version information
    and the firmware with a single FoE file transfer.

    Please let us know if it supports FoE updates using the “.efw” extension,
    or if modifications are possible to enable future support.

    For detailed specifications, please refer to the following site:
    https://infosys.beckhoff.com/english.php?content=../content/1033/el20xx_el2124/402909835.html&id=4429606895834499921

    Best Regards,
    Kanae

  • Hello Kanae,

    To set expectations, we can no longer provide software design support on AMIC110, as per  Notice regarding Processor SDK TI-RTOS for AM335x, AM437x, OMAP-L13x, C674x, K2G, AMIC110, AMIC120 devices 

    I am sending your thread over to our team who support EtherCAT on AM243x, just in case they have any input. But keep in mind that AM243x uses MCU+ SDK with FreeRTOS instead of TI-RTOS, so they may be unable to offer any additional assistance.

    Regards,

    Nick

  • Hi Kanae

    We do not support this but demonstration of binary file transfer for flashing the application firmware, the same can be extended by customers to file format of their choice.

    On AMIC110 side, after receiving this, they wish to simultaneously use the ESI to update
    the EEPROM and send the ZIP file to the other SoCs.

    The goal of this method is to simultaneously update the AMIC110's SII version information
    and the firmware with a single FoE file transfer.

    This approach is ok; AFAIK this is not part of any ETG standard and Beckhoff SSC does not support this format by default either.

    Please let us know if it supports FoE updates using the “.efw” extension,
    or if modifications are possible to enable future support.

    Unfortunately, as of now there is no plan to support this as part of our roadmap.

    Regards

    Pratheesh

  • Hi Pratheesh,

    Thank you for your reply.
    I will share this with my customer.

    Best Regards,
    Kanae

  • I had a typo in my response - corrected above - specifically: the same can be extended by customers to file format of their choice.

  • Hi Pratheesh,

    Thank you for the correction.
    I understand that customers can extend it to any file format.

    Best Regards,
    Kanae