• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 104 subscribers
  • Views 848 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

66AK2G12: EtherCAT firmware update

Hiroyasu Tazawa1
Guru 12350 points
Part Number: 66AK2G12
Other Parts Discussed in Thread: AMIC110

Hi,

Let me talk about EtherCAT of 66AK2G12.

My cusotmer think Firmware update using FoE of EtherCAT.
We guess 66AK2G need reset after Firmware update.

In this case, 66AK2G12 can not communicate with Node of latter EtherCAT module,
while it is reset.

ET1100 is hardware module and I guess it does not need this update.

I thought they should update only CA15 and DSP and so on  without PRU-ICSS.
But Actually CA15 execute EtherCAT stack.

My customer worry about this.
Do you have any solutions to avoid this reset time?

Best Regards
Hiroyasu

  • 0
    TI__Guru 65405 points
    The team is notified. They will post their feedback directly here.

    BR
    Tsvetolin Shulev
  • 0 in reply to Cvetolin Shulev-XID
    TI__Mastermind 43296 points
    Hiroyasu,

    During the 'Firmware update' through FoE, actually it's the app update, the PRU-ICSS is still functional. Only after the app is downloaded and reloaded, the PRU-ICSS is reset and its firmware is updated and restarted. User may be able to customize the app by removing PRU-ICSS firmware load, and flash firmware into SPI flash memory and load into PRU memory using customize SBL similar as what we implement for AMIC110 DDR-less EtherCAT processors.wiki.ti.com/.../PRU_ICSS_EtherCAT

    Regards,
    Garrett
  • 0 in reply to Garrett Ding
    Guru 12350 points

    Hi, Garrett

    Thank you for your reply.

    and I'm sorry, It was late.

    So Customer does not worry about K2G firmware update.

    But They are concerned that reset will cause a loss of communication

    at the back of the daisy chain.

    Because System of their end customer may run 24 hours.

    We need a mechanism to reset and update the firmware without loss of the communication.

    Actually Is there a mechanism to reset other function(ARM and DSP and Peripheral and so on)

    and firmware update while running PRU-ICSS (while communicating EtherCAT)?

    Could you tell me your opinion ?

    Best regards

    Hiroyasu

  • 0 in reply to Hiroyasu Tazawa1
    TI__Mastermind 43296 points
    Hiroyasu,

    The customer might be able to develop a mechanism to check if PRU-ICSS is out of reset then no longer update firmware. however some concerns:
    1. intc mappings. Not sure what will happen if arm is in reset state and intc interrupt triggered from PRU side.
    2. not sure how the firmware will behave if we just reset the arm core i.e. restart the stack. Changing the initial state of PRU for the stack might have some unexpected results.

    Regards,
    Garrett
  • 0 in reply to Garrett Ding
    Intellectual 930 points

    Hello Garrett-san,

     

    Thank you very much for your strong support as usual.  And Sorry for my jump-in/interrupt.  I’d like to have confirmation back in the first place, whether  the customer requirement are far from making sense/reasonable.

    Do you have any customer information who want to use PRU-ICSS/ARM like this customer?

    In other words, the customer requirement “ARM reset”, “EtherCAT communication don’t reset” with FoE in application update are reasonable requirement if we compared with other customer.

     

    1. 24-hours working system (reasonable I think).

    2. Only ARM core will be updated (reasonable I think).

    3. When above #2., EtherCAT communication don’t stop (I’m not sure whether this requirement are reasonable..)

    I think your answer are reasonable, but my customer may think it feel troublesome unfortunately..

    Best regards,

    Gou

  • 0 in reply to Okayama Gou
    TI__Mastermind 43296 points

    Gou,

    We didn't have any request for the feature - 'ARM rest' AND 'EtherCAT communication don't reset' except this thread.

    There are many unpredictable result may happen with the 'feature' as I explained in last post.

    Regards, Garrett

  • 0 in reply to Garrett Ding
    TI__Mastermind 32710 points
    Gou, let me close this E2E thread, as this issue is currently discussed directly.
    thank you,
    Paula
  • 0 in reply to Paula Carrillo
    Intellectual 930 points
    Paula-san,
    Thank you for your support.
    Hiroyasu-san who start this thread will close soon this thread. Because I jump in this thread, I cannot close this thread.
    Best regards,
    Gou