Post Go back to editing

No data output on sub node (AD2428)

Thread Summary

The user is troubleshooting an issue where no audio data is output from the sub-node in a TDM4 setup with a BeagleBone Black and AD2428WD1BZ. The final answer suggests starting with a simple 2-node setup, using known hardware, and verifying A2B routing and I2S settings. The user should also check the A2B bus signals with a scope to ensure data is being transmitted correctly. The accompanying answers highlight the importance of proper A2B routing and stream definitions, and suggest using sine wave generators for debugging.
AI Generated Content
Category: Software
Product Number: AD2428
Software Version: SigmaStudio+ 2.3.0 (Update 4) with A2B 1.3.2

My system is as follows: Main node - 1 sub-node (it will become 2 sub-nodes later)

The main node generates TDM4 data with speaker-test (-c4 -r48000 -FS16_LE)
(Only one of the 4 channels is activated.)

The subnode generates 50% duty cycles and intends to play them through TAS6422.

However, no data comes out of the sub node, and only some noise is generated.

Which setting might be wrong?

Thank you.
Eunsang Ko

Edit Notes

add images2 (main node setting)
[edited by: LocoField at 3:28 AM (GMT -4) on 15 Mar 2026]
Parents
  • TLDR:

    • Start with a simple 2 node setup transporting stereo audio in one direction
    • Use the ADAU1452 to generate known data to eliminate trying to get some ADC/external I2S thing involved
    • Only change one thing at a time - like generate 4 channels instead of 2 put leave everything else the same, then transport the 4, etc
    • If really stuck look at the A2B bus itself to make sure the data is making it on to the bus

    Not sure if you're still stuck, but since you have the WDZ boards I would drop back and run one of the examples that's available so you can see how it's set up.  Sometimes when I'm chasing the "where did the signal go" problems - particularly for lots of channels - I'll put some sinewave generators at different frequencies on the ADAU1452.  Then I can confirm routing is doing what I think as well as it will expose clock edge problems.  The AD2428 settings don't mean much on their own - you have to get both ends to agree.  Also remember the word size on the i2S port is not the same as what A2B will transport so that's another place to make a mistake.

    When I get really stuck I put a scope probe on the A2B signals as you an see what it's transporting and is the data changing or not (see TRM for details).



  • Hi.

    I finally got it working. Thank you so much for your help!

    Now I understand why you recommended using SigmaStudio 4.7.
    After going through this process, I found that it is much more intuitive when working with manual configurations.

    I really appreciate your support, and I look forward to your help again in the future.

    Best regards,
    LocoField

  • Hey that's great.  Now you've got something you can build off of it will get easier.  A2B is definitely one of those things where you only learn from mistakes Confounded

Reply Children
No Data