• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 81 subscribers
  • Views 992 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.

TMS320F28388D: Using Etercat I2C Eeprom for General Data Storage Also?

Erhan(engineerhan)
Intellectual 505 points
Part Number: TMS320F28388D


Hi all!

TMDSCNCD28388D has 16kbit i2c eeprom which is connected to the ethercat i2c pins. What i got is that this eeprom for data storing for ecat slaves and it is configured by Twincat app.

1- Can i use a larger eeprom(like 32kbit) and store extra data?

2- If yes what are the lib functions to read/write from/to  this eeprom?

3- Can use driverlib to read/write from/to this eeprom?

4- Are they open source?

5- how often is this eeprom used by ecat controller or twincat?

thanks in advance.

  • 0
    TI__Guru 55700 points

    Erhan,

    Thanks for reaching out to us.

    I need to follow-up with fellow engineers to get answers to your question. Please expect atleast 2 - 3 business days to expect a reply from me.

    Regards,

    Manoj

  • 0 in reply to Manoj Santha Mohan
    Intellectual 505 points

    Hi Manoj!

    Thanks a lot. All good. I am waiting here.

    cheers,

  • 0 in reply to Erhan(engineerhan)
    TI__Guru 55700 points

    Which ethercat i2c pins are connected to EEPROM? Are you sure they are connected to ethercat i2c pins or just i2c peripheral pins?

  • 0 in reply to Erhan(engineerhan)
    TI__Guru 55700 points

    Please provide which pins on the device is connected to EEPROM?

  • 0 in reply to Manoj Santha Mohan
    TI__Mastermind 45606 points

    Hi Erhan,

    EtherCAT EEPROM sizes are from 1 Kbit up to 4 Mbit. Are you wanting to store more EtherCAT data or some other unrelated data in the unused memory space? I'm not certain if the latter is supported, the Beckhoff / ETG documentation may give a clue if this is allowed.

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Intellectual 505 points

    Hi Manoj and Kevin!

    Thanks for answers,

    We are designing the hardware of our product now. There is no software/firmware at the moment. And we have some (<1kB) info which should be stored in a non volatile external memory such i2c serial eeprom. However, I noticed that ecat slave controller peripheral also has an i2c interface. That means, we have to connect there another i2c serial eeprom also. So we don't want to connect 2 eeproms for one product. Because it increases the BOM cost.

    Therefore, I want to know if it is possible to store an extra information to the eeprom which is connected to that ECAT i2pins?

    Probably we will use TWINCAT. In the example of ti TWINCAT app, it is just loading a binary file to this eeprom. Actually I want to know how does the TWINCAT app communicate with this eeprom? Does it erase it before write flash? etc. I want to use one eeprom for my product and i dont want my data to be erased by TWINCAT during ECAT communication.

    I hope I explained it clearly. :)

    cheers,

  • +1 in reply to Erhan(engineerhan)
    TI__Mastermind 45606 points

    Hi Erhan,

    Erhan(engineerhan) said:

    However, I noticed that ecat slave controller peripheral also has an i2c interface. That means, we have to connect there another i2c serial eeprom also. So we don't want to connect 2 eeproms for one product. Because it increases the BOM cost.

    Therefore, I want to know if it is possible to store an extra information to the eeprom which is connected to that ECAT i2pins?

    OK understand, however I'm not sure if EtherCAT functionality would be affected if you split the EEPROM space for both ECAT related data (ESI file) and other application specific data. I can ask some others on the team if they know, but it may be a question better suited for Beckhoff or ETG.

    Also, the ESC_I2C is not a regular C2000 device I2C. It's only connected to the ESCSS for EtherCAT EEPROM data handling. Another regular F2838x I2C instance can be connected to the EEPROM as well for the application specific data handling. The register below can be used for switching between the two on ESCSS side at least.

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    TI__Mastermind 45606 points

    Hi Erhan,

    I asked a colleague about this and learned the below. Reaching out to Beckhoff or ETG would still be a good idea, as they're the dedicated experts.

    Only the first 16-bytes of the EEPROM space are mandatory for EtherCAT / ESC usage. If you are flashing an XML, then you should know the size of that too (so the rest is purely up to the user to utilize).

    Best,

    Kevin

  • 0 in reply to Kevin Allen18
    Intellectual 505 points

    Hi Kevin!

    Thanks a lot for your effort.

    Actually it is not necessary to know it. I just wanted to know it if it was already clear. It seems eventual I will reach out Beckhoff guys. Or I will figure it out later during ECAT app development.

    cheers,