• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 2379 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.

AVB IEEE 1722a support or compliance on TDA2x Vision SDK

K Md Feroz Irfan
Expert 7225 points

Dear All,

Could you all please let me know if the AVB demo on Vision SDK 2.50 has IEEE 1722a compliance. Or is it handled by the AVB stack vendor?

If not compliant, please brief on the deliverable AVB test code...

Thanks 

Best Regards

Feroz

  • 0
    TI__Mastermind 29520 points

    Hello Feroz,

    TDA2x' AVB is compatible with IEEE1722. See section IEEE 1722: "Layer 2 Transport Protocol for Time-Sensitive Streams" - in device TRM.
    AVBTP or 1722 sits above the IEEE 802.1 AVB plumbing and below the application layer. It acts as the conduit between an Ethernet MAC and a streaming application. AVBTP abstracts the underlying network transmission channel to enable the virtual connection of distributed audio and video CODECs over reliable Ethernet networks.

    Based on the information in VisionSDK_Manifest.pdf the version of AVBTP in VisionSDK is 0_09_00_01.
    This version of The AVBTP (Audio/Video Bridging Transport Protocol) library provides support to extract JPEG data from an ethernet stream conformant to the IEEE 1722 standard.

    Best regards,

    Yanko

  • 0 in reply to Yanko Todorov-XID
    TI__Expert 7225 points

    Thank you Yanko!

    Actualy 1722A is a new extension over 1722. So can you we confirm of this support as well on our SoC and over the AVB software that TI provides?

    Key question will also be our partners who provide their AVB stack in complaince here.

    Could you please check and let us know?

    Thanks & Best Regards

    Feroz

  • 0 in reply to K Md Feroz Irfan
    TI__Mastermind 29520 points

    Hello Feroz,

    I will make some clarifications about IEEE standards:

    - IEEE 1722: "Layer 2 Transport Protocol for Time-Sensitive Streams"
    - IEEE Std 1722.1-2013 = P1722.1 - IEEE Standard Device Discovery, Connection Management and Control Protocol for P1722 based devices.

    Applications using IEC 61883 and other formats can use procedures defined in IEEE Std 1722-2011 to sample the 802.1AS clock relevant for an A/V data block and then add the worst case transport delay to the sample time to get a presentation time which is inserted into the 1722 packet.

    IEEE Std 1722.1-2013 is a standard which allows AVB Discovery, Enumeration, Connection management and Control (AVDECC) of devices using IEEE Std 1722-2011.

    I have checked in some AVB specifications and I found that there are references only to IEEE 1722.

    I forwarded your question to AVB expert to provide more information.

    Best regards,

    Yanko

  • 0 in reply to Yanko Todorov-XID
    TI__Expert 7225 points

    Thank you Yanko!

    Will look forward to the clarification. As i understood it is an exension of the 1722 std...So wondering if there are any limitations in our hardware...

    Best REgards

    Feroz

  • 0 in reply to K Md Feroz Irfan
    TI__Genius 17355 points

    The AVBTP software component is not compliant to 1722 nor 1722a. The layer 2 packet format used is basically standard IEEE 1722, but we don't support a number of things described in the standards (IEC 61883 support, MAAP, etc.). It really is only an raw Motion JPEG video depacketizer, but the formats of the headers are as defined in the 1722 standard (though not all of the fields of the headers are in use). 

    In any case, 1722  or 1722a are simply software stacks - there isn't any hardware dependencies for these. So either one could be implemented with no issues.

    Regards, Daniel