Part Number: PROCESSOR-SDK-AM64X
Other Parts Discussed in Thread: TMDS64EVM
Tool/software:
Hi TI Team,
we already had an issue where we mentioned that the Ti and To times did not correlate with callbacks for sending/receiving cyclic data: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1463428/processor-sdk-am64x-understanding-isochronous-profinet-api-4-0-3-irt---timing-pins/5774931?tisearch=e2e-sitesearch&keymatch=profinet%2525252520irt#5774931
The setup is the same as in the original issue. We have 4 PINs we connect to a logic analyzer to see the timing. We have the
2 PINs triggered from stack:
PRG1_IEP0_EDC_SYNC_OUT2
PRG1_IEP0_EDC_SYNC_OUT0
2 PINs manually added:
MCU_SPI0_D1/B6 --> PN_APP_IOD_cbDataWrite
MCU_SPI0_D0/E7 --> PN_APP_IOD_cbDataRead
PLC setup:
Ti @ 250 us interval 125 us
To @ 375 us interval 125 us
Application Cycle: 1 ms
Send clock: 1 ms
We have now tested again with 11.00.00.08 Industrial Communication SDK on our board (TMDS64EVM) and data callbacks PN_APP_IOD_cbDataWrite() and PN_APP_IOD_cbDataRead() are still not in sync with IRT sync signals.
We have defined PN_APP_IOD_TI_TO_MEASURE in example profinet_device_demo_am64x-evm_r5fss0-0_freertos_ti-arm-clang to get meaningful values ti/to cycle times from PLC.

We expect callbacks cbDataWrite and cbDataRead to be executed within SYNC_OUT0 (TO) and SYNC_OUT2 (TI) interval.
What behaviour is expected here from your side?
Thanks in advance!
Kind Regards
Alex