• State TI Thinks Resolved
  • Locked Locked
  • Replies 11 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 772 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.

TMDS64EVM: Cannot see EtherCAT SYNC0 signal on oscilloscope

Jonas Ens
Prodigy 140 points
Part Number: TMDS64EVM
Other Parts Discussed in Thread: SYSCONFIG,

Dear TI-Team,

I am running the 'Simple EtherCAT Slave'-demo on the evaluation board mentioned above. It runs among other EtherCAT-Slaves and an EtherCAT-Master with Distributed Clocks configured. The master indicates, that all the slaves are successfully operating in DC-mode. I tried to measure the SYNC-signal with an oscilloscope, but I am not able to see it from the TMDS64EVM-slave. I can only see the SYNC-signals generated by the other slaves within the EtherCAT-network.

I am using the header 'J18 SYNC OUT0' (page 6 in AM64x / AM243x Evaluation Module User's Guide (Rev. A)) to measure. Do I have to configure this header in SYSCONFIG? If yes, please let me know how to do this.

I am happy to hear from you and thanks in advance,
Jonas

  • 0
    TI__Expert 8995 points

    Hi Jonas,

    Thank you for reaching out to us.

    Jonas Ens said:
    Do I have to configure this header in SYSCONFIG?
    • No header configuration is to be done in SYSCONFIG.

    The issue you are facing is a known issue with EVMs. We are trying for a workaround to capture the signals from a different pin. Will update with you once we have the workaround.

    Regards,

    Aaron 

  • 0 in reply to Aaron Thomas
    Prodigy 140 points

    Hi Aaron,

    thanks for your immediate reply.

    Could you give an approximate date of when I can expect the workaround? We carry out first experiments in order potentially to use the AM64x in our product.

    My other questions regarding this topic would be, whether the interrupt triggers in the software, even though the hardware signal cannot be measured.

    I tried to adapt the 'Simple EtherCAT Slave'-demo in order to implement a task that is triggered by the SYNC-interrupt. Do you have any example or documentation on this? I could not find anything online.

    Thanks and have a nice weekend,
    Jonas

  • 0 in reply to Jonas Ens
    TI__Expert 8995 points

    Hi Jonas,

    Jonas Ens said:
    Could you give an approximate date of when I can expect the workaround?
    • I'll come with an update by Wednesday. Hope that is fine with you.
    Jonas Ens said:
    whether the interrupt triggers in the software, even though the hardware signal cannot be measured.
    • Yes, the interrupt will trigger in the software even if the hardware signal is not measurable.
    Jonas Ens said:
    Do you have any example or documentation on this?
    • I will look into this and get back to you by EOD.

    Thanks and Regards,

    Aaron

  • 0 in reply to Aaron Thomas
    Prodigy 140 points

    Hi Aaron,

    short update on the measurement of the SYNC-signal: The problem was on my side. I made a mistake in my measurement setup, i'm sorry for your inconvenience. I can assure that the SYNC-header works perfectly fine ;-).

    Aaron Thomas said:
    Jonas Ens said:
    Do you have any example or documentation on this?
    • I will look into this and get back to you by EOD.

    When you have news on this, I would be happy to hear from you.

    Regards,

    Jonas

  • 0 in reply to Jonas Ens
    TI__Expert 8995 points

    Hi Jonas,

    So are you saying now you're able to measure the SYNC0 signal from TMDS64EVM. Also can I know what was the mistake on your measurement setup ?

    Regards,

    Aaron

  • 0 in reply to Aaron Thomas
    Prodigy 140 points

    Hi Aaron,

    yes exactly, I'm able to measure SYNC0 signal from TMDS64EVM as can bee seen in the screenshot.

    My mistake was that I took the arrow printed on the board next to the header for the GND-symbol and therefore mixed up the polarity.

    Regards,
    Jonas

  • 0 in reply to Jonas Ens
    TI__Expert 8995 points

    Hi Jonas,

    Just wanted to clarify, so are you connecting only a single EtherCAT device to the EtherCAT master and probing the SYNC0 signal from that device?

    Regards,

    Aaron 

  • 0 in reply to Aaron Thomas
    Prodigy 140 points

    Hi Aaron,

    the screenshot above was taken with the following setup: EtherCAT-master connected to Non-TI-slave, TMDS64EVM-slave and Non-TI-slave (--> 3 slaves in total, connected in this order). But the measurement also works if only the TMDS64EVM-slave is connected to a EtherCAT-master.

    Regards,
    Jonas

  • 0 in reply to Jonas Ens
    TI__Expert 8995 points

    Thank you for the details Jonas.

    Regards,

    Aaron

  • 0 in reply to Jonas Ens
    TI__Expert 8995 points

    Jonas,

    Jonas Ens said:
    When you have news on this, I would be happy to hear from you.
    • Regarding this, wanted to update you that we are still waiting for a reply from the corresponding stack provider. Thank you for your patience.

    Regards,

    Aaron

  • 0 in reply to Jonas Ens
    TI__Expert 8995 points

    Hi Jonas,

    The function you are looking for is EC_API_SLV_cbRegisterUserApplicationRun

    You can find it as part of the simple demo:

    EC_API_SLV_cbRegisterUserApplicationRun(
        pAppInstance_p->ptEcSlvApi,
        EC_SLV_APP_SS_applicationRun,
        pAppInstance_p);

    You need to register the application, so the function is called then either by the PDI task or the Sync task when the PRU triggers the interrupts.

    Regards,

    Aaron