• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 207 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.

Original question:

AM2434: Request to reset R5FSS independently, excluding PRU_ICSSG reset

AM2434: AM2434 industrial communication SDK for EtherCAT, is it possible to do software update without disconnecting EtherCAT network after update?

Rich Chen
Intellectual 2775 points
Part Number: AM2434

Dear Sir, 

Below two e2e post all lead to same target which is implementing software update which can update AM2434 software on R5F side but not affecting PRU-ICSS because EtherCAT slave device need to stay connecting while doing software update from EtherCAT master side.  

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1308891/am2434-request-to-reset-r5fss-independently-excluding-pru_icssg-reset

https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1310783/am2434-arm-based-microcontrollers-forum

1. Is there limitation rule software/firmware update on EtherCAT slave need to keep connecting during and after software/ firmware update?

2. Now customer has implement reset isolation for PRU-ICSS and complete software update on R5F side. However, EtherCAT will not operate normally after software update. Customer supposes it is just skip the PRU-ICSS firmware download procedure. Is there any other check point like SYSFW Resource management need to be updated for this "reset isolation"? 

BR, Rich

  • 0
    TI__Mastermind 21500 points

    Hello Rich,

    For the 1st question, we should get help from an Industrial Protocol expert.

    For the second query, whatever code is shared by Nilabh is not full code and you still face some issues while integrating Ethercat code.

    Actually, in the Nilabh Shared code there are different issues, like for every Reset we are configuring the clock  of PRU core this step should not happen for every Reset to SOC and we should do initialization of PRU core clock initializations only once  .

    And, SYSFW is initializing PRU clock to default to the irrespective of user clock configuration for every Reset . For this we need to add patch to SYSFW.

    I heard from the Networking Team that after adding above changes still Ethercat stack is corrupting after resetting the core.

    So, in future release this Isolation code is properly integrated into MCU+SDK until please don't integrate these steps into customer code.

    Regards,

    S.Anil.

  • 0
    TI__Intellectual 2775 points

    Anil, 

    For 1, Yes, we really need Industrial Protocol expert to answer this. 

    For 2, customer uses code from Nilabh and it does do reset without reseting PRU-ICSS and system still work which achieves the original target. 

    However, the ultimate goal is to do software update then reset and reboot but keep connection on EtherCAT because customer used to use BechOff solution on FPGA and it is what they experienced (Slave device will keep online and EtherCAT Master doesn't get disconnect on this device). 

    In your last comments, do you recommend customer to wait for next Industrial Communication SDK (say 9.2?)?

    Which will integrate reset isolation code and make EtherCAT will not disconnect after reset/reboot?

    BR, Rich

  • 0 in reply to Rich Chen
    TI__Genius 15700 points
    Rich Chen said:
    do you recommend customer to wait for next Industrial Communication SDK (say 9.2?)?

    The tentative plan is to add an example in 10.0.

    Please allow some more time to discuss this issue internally and get back to you.

    Regards

    Ashwani