AM2631: IEEE 1722 AVTP SDK Support Roadmap

Hi Luke,

ACF traffic support is available in the SDK. There is an example in AM263x SDK where ACF packet traffic is demonstrated. In this example, CAN packets are encapsulated as ACF packets.

Please see the below SDK documentation regarding the example:

https://software-dl.ti.com/mcu-plus-sdk/esd/AM263X/11_01_00_19/exports/docs/api_guide_am263x/EXAMPLES_ENET_CPSW_ETHERRING_CAN.html

Thanks & Regards,

Aswin

Hi Aswin,

I had seen this example before, however I noticed that the example implements the ACF packet encapsulation, not some functions within the SDK, then interfaces directly with the Ethernet LLD driver or EtherRing driver. Is there a plan to move this encapsulation to the SDK and add support for time-sensitive variants of the ACF packet protocol in the future?

Best,

Luke

Hi Luke, 
Let me check the Software team regarding this. So, basically the ask is regarding an SDK API that will do the ACF packet encapsulation instead of the application as demonstrated in the example, right?

Thank & Regards,

Aswin

Luke said:

time-sensitive variants of the ACF packet protocol in the future?

Can you please elaborate of time sensitive variants for ACF packet protocol?

Hi Aswin,

Yes, I would like to know if the ACF support will be rolled into the SDK itself, rather than need to be implemented in the application.

The ACF protocol encompasses NTSCF (non-time-synchronous control) and TSCF (time-synchronous control) messages. The example seems to use the non-time-synchronous format (based on the frame header), which doesn’t require gPTP to run. Making these messages time-synchronous would require interfacing with the TSN modules that the SDK provides, so I am curious about whether this support would get rolled into the SDK for convenience.

Best,
Luke

I investigated further and it seems that the TSN stack is being used by the example to send time-synchronous control messages. This is implemented by the example code, not the SDK.

Best,
Luke