• State Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 235 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

LP-AM243: How to firm ware update over EtherCAT

Tomoya Oyama
Intellectual 330 points
Part Number: LP-AM243


Tool/software:

Hi Team,

I'm developing EtherCAT application for LP-AM243x using "ethercat_slave_demo" 401_simple in the SDK ver.09_02_00_15.

I'd like to introduce firm ware update through FoE protocol. 

Therefore, could you provide firm ware update samples?  or please tell me the sequence of it.

Additionally, it migth be need to use EC_API_SLV_FoE_cbRegisterFwUpdate() when firm ware update over EtherCAT.

What's timing of called (or not called) function registered by  EC_API_SLV_FoE_cbRegisterFwUpdate().

it is important for firm ware update, the timing fixed bootstrap or not.

Best regards,

Oyama

  • +1
    TI__Expert 3020 points

    Hello Oyama,

    The EtherCAT Slave Stack supports file download and upload over FoE. The generic file download/upload functionality has been tested in TwinCAT and this implementation for APIs is available with EtherCAT Simple demo example in Industrial Communications SDK 09.02.00.15.

    These APIs EC_SLV_APP_FoE_fileOpen, EC_SLV_APP_FoE_fileWrite, EC_SLV_APP_FoE_fileRead and EC_SLV_APP_FoE_fileClose supports the file download/upload functionality via FoE. For further details please refer File access Over EtherCAT.

    For FoE Read request the sequence of the API call would be EC_SLV_APP_FoE_fileOpen() >>> EC_SLV_APP_FoE_fileRead().

    For FoE Write request the sequence of the API call would be EC_SLV_APP_FoE_fileOpen() >>> EC_SLV_APP_FoE_fileWrite() >>> EC_SLV_APP_FoE_fileClose().

    The above-mentioned APIs should also be triggered in 'Bootstrap' state during the firmware file download to support the firmware upgrade. The API implementation for firmware upgrade has not been provided as an example in Industrial Communications SDK. Customers can use these APIs to implement their own logic to achieve firmware upgrade over FoE. In EtherCAT stack provided with SDK 09.02.00.15, the API EC_API_SLV_FoE_cbRegisterFwUpdate is not used and also any registered API with EC_API_SLV_FoE_cbRegisterFwUpdate is not triggered.

    At present, there are no user APIs implemented, which trigger during the state transition from Init to Bootstrap and Bootstrap to Init state. We are working on these APIs and should be available in the upcoming Industrial Communications SDK releases.

    Kind Regards,