Post Go back to editing

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

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

  • I thought I threw an answer in here but the dog must have eaten it.

    By definition the main node does not have an A (upstream) port.  It is the first node in the daisy chain. you can not do what you've shown.  You could hang your 'new' things on the end of your existing chain as that should require minimal modifications.  Though you have to be cognizant of how the system is going to assign slots and the I2S mapping that results.

  • 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