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 (Audio Video Bridging)/TSN (Time Sensitive Networking) support?

Other Parts Discussed in Thread: DP83640, AM3359

I'm trying to figure out what the right combination of stuff to do AVB is, and I see answers all over the map in the forums.

It looks like a DP83640 would be a good choice of PHY(although I'd prefer a gigabit one), but what *processor* do I need to drive that for full AVB support.  Do I need to connect the PHY to the PRU's?  Is there documentation about this that I'm missing?

Thanks.

  • Hi,

    Which processor are you asking about?
  • Um, well, as low as I can get, if possible.

    How about the AM3359? It lists 1588 as supported, so that there is at least a possibility. In addition, it's available on the Beaglebone Black, so I have a cheap way of verifying any answers I am given.
  • I have asked the factory team for comments. They will post directly here when feedback is available.
  • 1588 is just the beginning of the requirements for an AVB network. A full AVB stack is typically arranged through a 3rd party. It also really depends on what you want to do. What features of AVB are you looking for?

    The Linux Processor SDK for the AM335x does not use a PHY with 1588 support, but 1588 can still be tested on the beagle bone black. I do not know if there is open source AVB stack but you can start evaluation with the ptpd2 daemon that allows clock synchronization between a clock master node and client nodes. The cpsw hardware is used, not the PRUs. Linux Ethernet support for the PRUs is coming in a future release. To get a working ptpd2 daemon please use the 1.0.0.3 release of the processor linux SDK. When downloading you can navigate backwards through releases to get to 1.0.0.3. The ptpd2 daemon is an open source package that is pulled in as a convenience for users, we are looking at why the later versions of this package are not working on the latest SDK.

    What kind of requirements do you have for this network? I am not so much asking the actual use as what is timing requirement and network throughput expected.
  • Multiple streams of 48K/24-bit audio. Multiple being around a dozen or less. Even 100Meg Ethernet should be way more than sufficient. Gigabit Ethernet is overkill.

    I'm currently looking at a set of products that already are digitizing audio and communicating over USB 2.0. This is, as you would expect, suboptimal.

    Currently, for upgrade, I'm standing in the middle of two camps yelling at one another--USB 3.0 and Thunderbolt.

    The problem is that I *ALREADY* have had bad experiences with Thunderbolt and audio. 4K monitors create large transactions that cause low-latency audio to hiccup, even though there is plenty of bandwidth overall. I have no reason to believe that the USB 3.0 guys were any smarter about this. Sure *at some point* both camps will fix this, but I'd rather not wait for 5 years for everybody in the Thunderbolt/USB 3.0 standards committees to execute a cranio-rectal extraction.

    AVB, on the other hand, *did* tackle this stuff and forces reservations and timeliness. This stuff is already addressed on Ethernet, today. Big audio manufacturers are already using it in their high-end equipment, and it's starting to move down into the sub $1000 audio market. So, while AVB is still probably "beta", it's not vapor. And, it's probably the correct decision.

    Unfortunately, *proving* that is turning out to be difficult. Nobody seems to have an eval kit that has a PHY that enables me to use 1588 properly. Without 1588, I can't even really start on AVB proper. Until I can at least start down that path, I can't in good conscience allocate a junior guy on what could very well be a wild goose chase.