TLV320AIC3104 Audio Device Not Detected on BeagleY-AI

General Discussion
, ,
1

We are making a new custom hat for the BeagleY-AI for a university course on embedded systems at Simon Fraser University. The hat has a TLV320AIC3104 audio device which we cannot get to recognize as an audio device. We wired the TLV32 to the BeagleY-AI and added a 12MHz crystal oscillator for the MCLK. It detects on I2C (i2cdetect -y -r 1 shows it correctly at address 0x18). We created a custom device tree overlay, but are unable to have it recognized as an audio device:

beagle@beagleyai:~$ aplay -l
aplay: device_list:274: no soundcards found...

We suspect the problem is with our device tree overlay: embedded-starter-example/audio-devicetree at master · jarell-santella/embedded-starter-example · GitHub (See k3-am67a-beaglemod-audio.dts ; the README contains some more information about the issue and what we have tried.) Any help in finding our bug is appreciated! We are looking forward to teaching ~100 students all about the BeagleY-AI and embedded systems!

2

in the first part of the boot log, when k3-am67a-beagley-ai.dtb is loaded, are there any errors or warnings

in extlinux.conf, remove “quiet” from the “append console” being used
can you post your boot log (serial console output)

3

You need a debug probe on the linux port. The dtbo will either load and not work, not load, load and break the system. GTK term works the best and capture the entire boot sequence, look around FTD that will indicate if its loaded or not.

Also, how did you compile it. If it has #includes you will have to build it using the RCN tree. No includes dtc will be fine.

I did not see your .dts on the github page. Did notice your are preprocessing that using cpp, the ti device tree has a rats nests of stuff to link to and it makes a mess. It would be best to drop it in the .dts files of the RCN overlay tree and use the make file to build it. Not sure if cpp generates all the errors for missing the deep links.

It is assumed you modified the .dts file that is posted.

// #include <dt-bindings/leds/common.h>
// #include <dt-bindings/net/ti-dp83867.h>
// #include "k3-j722s.dtsi"

That cannot be done, you have some macros that must be expanded for the mux. If memory is correct they are in the k3-j722s.dtsi file. You must be able to do a clean build with those existing includes.

What I would do is revert back to the original file and make sure it is in the as provided state. Create an overlay my-custom-audio-project.dts and load it on top of the existing overlay. FYI, you will not get error codes on this, so it is important to leave what is working alone and add your own specific overlay file, this will help prevent you from chasing your tail all day.

1 Like