Enable audio in chromium container

[seasoned_geek]

What carrier board? I know you checked Verdin when applying tags, but it sounds like you might be using Dahlia.

The CODEC on the Dahlia has a lot of issues. To start with, if you are performing a straight EasyInstaller install of TorizonCore, the device drivers aren’t loaded. Only the device tree for the full sized Verdin carrier board is loaded.

You really need to build your own image and replace the device tree. See this message thread.

Where are the correct instructions for building a custom torizon-core-docker?

Greetings @seasoned_geek, Let’s see if we can clear this up. First of all, are you making U-Boot changes just to change the U-Boot environment variables so that system boots with the Dahlia device tree by default? Or are their other changes you wish to make? If it’s just the change for the device tree. You should be able to make this with TorizonCore Builder. See this section here: Device Tree Overlays on Torizon | Toradex Developer Center Basically you can use the dt apply command to set any…

You really need to read the Errata and pull some resistors off, especially if you are going to think about having any sound input.

Dahlia audio input magically broken - appears to be EasyInstaller issue

I think you need to stop focusing on the word “install.” EasyInstaller can pooch things if there are any “data values” or “settings” that don’t get reset via a standard image build and deploy. I don’t know about the Dahlia board, but you have such things on the Verdin big board. They are used to enable/disable various devices that share pins. No. 5.4.0+biuld.4 works 5.5.0+build6 screws the pooch Don’t know about versions and/or builds in between.

If you want non-static “good” sound coming in on the microphone there are other hardware modifications you will have to make and I’m not currently at liberty to share.

Once you jump through those hoops, you will find that there is a driver feature/bug/oddity where any WAV file you record will not be centered around zero. Your code will have to fix that. It helps if you copy the WAV files off to a Linux machine running Audacity so you can look a them.

Your first problem is that you don’t have the device tree loaded for your carrier board. You can verify this if you have a container with alsa-utils loaded. Just launch it interactively with a bash shell so you can tool around with aplay and arecord. Probably help if you copy some WAV files into your container while building as well.