Post Go back to editing

How do I route audio to the AD2428 A-port Upstream?

Thread Summary

The user is trying to configure an AD2428 to use its A-port as an upstream connection in an existing A2B network with a PocketBeagle 2 and McASP. The final answer confirms that the main node (AD2428) does not support an A-port for upstream connections due to internal state machine limitations. The user's reference to an OEM product using the A-port may indicate a separate, independent A2B network rather than a shared topology.
AI Generated Content
Category: Software
Product Number: AD2428
Software Version: SigmaStudio+ 2.3.0 (Update 4) with A2B 1.3.2 or SigmaStudio 4.7 with A2B 19.4.5

Hello,

I'm developing an automotive audio system using PocketBeagle 2 + AD2428W.

Current configuration

  • PocketBeagle 2 outputs audio through McASP
  • McASP is configured as 4-channel output
  • AD2428 receives:
    • DRX0 = TDM2 (2 channels)
    • DRX1 = TDM2 (2 channels)
  • This configuration works correctly.

Desired configuration

I would like add one more AD2428 to transmit audio to another AD2428 located elsewhere.

But, I have to keep my existing A2B network because hardware limitation.
(The easiest way is adding one pair McAsp and AD2428)

So, is there any way for an AD2428 to transmit using A-port as upstream?

Host (McASP)
            │
    AD2428 Main
            ├── B-port → Existing A2B speaker network (already working)
            │
             ── A-port (Upstream)
                              │
                        AD2428 Subordinate
                              │
                        ADAU1452
                              │
                        ADAU1761 DAC
                              │
                        Additional speakers

In SigmaStudio, I can enable Upstream, but I cannot find any A-port where the upstream audio channels are assigned or routed.

Thank you for always helping me.

Best Regards,

LocoField

Parents
  • The reason I'm asking is that I've come across an OEM product that appears to work use A port.
    I'm trying to understand what I'm may be missing.
    (My existing system I configured using B port is also imitating the OEM.)

    Could it actually be that the second module is operating as an independent A2B network with its own main node,
    rather than being part of the same network? In other words, are there cases where two separate A2B networks coexist without sharing a single network topology?
    (There is clearly only one audio generator, and it is outputting properly through port B.)

    Thank you
    LocoField

  • AD243x series A2B does offer running two parallel, i.e. two synchronized but independent  busses where all the sub nodes run off a common clock, to get 64 channels.  But both the main (root) nodes are still a B port only setup.

    It might be possible with some serious register hacking to make a main node have a functional A port but I kind of doubt it because of the way the clocking and data movement happen inside the part.  Best as I can tell that's all in internal state machines and you can't change it.  

  • I've been thinking about this for a few days, but I think I've been overthinking it.

    I think my board would be the sub node if I use a and b together.
    It is true that I send the audio from my board, but I just need to wait for it to be set up as a sub node, receive the bclk, and then send only the audio, right?

  • not quite sure I follow your question, but the general answer is you can only have the one main node, and main nodes do not have an A port.  So unless you change the main node to be whatever it is you're adding then whatever you're adding must be a sub node with and A and B port (unless last node, then no B needed).

    I think though I'm not answering your question.

  • Thank you, your answer was very helpful.

    The conclusion was that I initialized a subnode as the main node across the entire network without waiting for discovery from the OEM main node.
    I just left it alone, and eventually, a discovery request came from the main node...

    A2B_NODE (0x29) is 0x20 (Node Discovered (5:DISCVD))

Reply
  • Thank you, your answer was very helpful.

    The conclusion was that I initialized a subnode as the main node across the entire network without waiting for discovery from the OEM main node.
    I just left it alone, and eventually, a discovery request came from the main node...

    A2B_NODE (0x29) is 0x20 (Node Discovered (5:DISCVD))

Children
No Data

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.