• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 1442 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.

SDK 1.1.0.3 Ethercat EEPROM

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

Hi,

We are using ICE AM3359 SDK 1.1.0.3 EtherCAT Application

1) We changed few data in file "tiesc_eeprom.h" the changes did not allow to connect with EtherCAT Master

2)Later we commented "EEPROM_SPI" in file "tiescbsp.c", then we were able to connect to EtherCAT master

Can any one let me know what is the importance of "EEPROM_SPI" ?

Do we need to comment  EEPROM_SPI if any changes are made to ties_eeprom.h ?

Do we need to uncomment again once EEPROM data is updated ?

Regrads,

Bindu

  • 0
    TI__Mastermind 47531 points

    Hi,

    Its explained here, http://processors.wiki.ti.com/index.php/AM335x_EtherCAT_firmware_API_guide#ESI_EEPROM_emulation_support

    EEPROM_SPI indicates EEPROM is in SPI flash (non-volatile storage). You can update EEPROM from TwinCAT or equivalent EtherCAT master or manually using CCS SPI flash writer

    But for debug purposes, you can use the EEPROM header (tiesc_eeprom.h) by commenting out EEPROM_SPI. This is volatile mode, changes are not saved back to EEPROM , so power reset will restore the default EEPROM again

  • 0 in reply to PratheeshGangadhar
    Expert 2220 points

    Hi,

    1) Now we have modified ESI File ( XML ) for PDO objects,

    But when we check Hex Editor (EtherCAT -> Advance setting->ESC Access->EEPROM->Hex Editor) the new created object are seen, but we have not yet updated the EEPROM Data (how can we update the TWINCAT EEPROM Data)

    2) Now we have generated the EEPROM bin file from Twincat. converted binary to header ( using ti bin2header) and replaced tiesc_eeprom.h with these data

    a) now commented the EEPROM_SPI -> twincat connectivity with TI Slave successful

    b)Now uncommented after step a, It is observed that -> twincat connectivity with TI Slave is again successful

     why is the above behaviour (step b), It is so that when we have commented EEPROM_SPI the eeprom data is stored in SPI Flash ( Non volatile)

    Please comment on this above behavior

    Regards,

    Bindu

  • 0 in reply to Bindu Ganesh
    TI__Mastermind 47531 points

    Hi,

    > how can we update the TWINCAT EEPROM Data


    I think you meant ESI EEPROM data in flash, just download from TwinCAT after updating ESI XML. EEPROM will be synced with updated XML. For this step to work,  of course you need a non-volatile storage as EEPROM i.e. EEPROM_SPI shall be enabled while building the slave


    Regarding b. I am not sure. Did you rescan the boxes after step a?