• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 440 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.

ICE AM3359, XML and EEPROM

Bindu Ganesh
Expert 2220 points
Other Parts Discussed in Thread: SYSBIOS

Hi,

I have gone through the document "AM335x SYSBIOS Industrial SDK 01.00.00.04 User Guide.pdf" patch to extract the stack code.

In Page 13, there is a procedure mentioned to "Generating ESI Header file From ESI xml" , here as it is mentioned If the application needs to work with some other ESI xml file, user need to generate curresponding ESI header file  ( tiesc_eeprom.h ) and built " ecat_appl " with newly generated "tiesc_eeprom.h"

In the link it is mentioned, how to create a .bin file equivalnt to XML http://processors.wiki.ti.com/index.php/Configuring_TwinCAT_For_AM335x

Now i need certain clarification.

1) Using TwinCAT system Manager, Hex editor can i edit the EEPROM data, if Yes then i want to know what all the parameters that i can edit along with format

2) If i have edited the parameter of EEPROM, for Device description as per my understanding the XML file is read by Master TwinCAT for Device description

Now should i generate the New XML, if yes what is the procedure else Master TwinCAT, will no longer use the XML file, but instead directly read it from the EEPROM.

Regards,

Bindu

 

  • 0
    TI__Prodigy 520 points

    1) There is some information which should be directly edited in the XML itself. For example, the FMMUs and SMs you want to configure for the slave.

    The parameters that can be conveniently edited in the Hex window include the EtherCAT Slave Controller Configuration Area (where configured station alias, SYNC signal pulse length, and other such parameters are configured). Note that whenever modifying these, the EEPROM checksum should also be modified to correspond to the new data. Also, some parameters need a reset to take effect.

    2) The XML is used by TwinCAT to configure mailboxes and process data before going to operational state. In case of SYNC signal pulse length, configured station alias, etc., the setting which will take effect will be what is present in the register (e.g., 0x12:0x13 for configured station alias).

    We cannot directly create XMLs from modified EEPROM data on TwinCAT.