That alone did not resolve the issue, but adding `dtoverlay=` directly above the `dtoverlay=draws,alsaname=udrc` line, then moving the entire DRAWS block to be above `dtparam=audio=on` seems to have

Place dtoverlay= directly above dtoverlay=draws,alsaname=udrc in /boot/config.txt -- *************************** Ryan Matthew Headley 1705 Granby Road Cayce, SC 29033 USA mobile - +1803-386-1799

Is there a guide for setting up the DRAWS hat with Buster? I started with a clean image, and tried to enable the DRAWS by adding `dtoverlay=draws` to the /boot/config.txt file, but when the pi starts,

Basil, You asked that I email you directly, but I do not have your email address. Everything I can find in forum only shows 'basil@...'

Jim, Yes that's exactly the problem! The chk_conflict.sh script was left over from when the DRAWS drivers were installed with DKMS (Dynamic Kernel Module Support). At that time the AutoSense-Pi

I think I have a repeatable set of steps that I can perform to make the DRAWS disappear. I’ve done it three times with the same results. Here they are. Please comment on changes to steps or

Ryan Matthew Headley <headley.ryan@...> writes: Thanks. With a little patience we will figure this out. I'm focusing on the drivers loading and enumerating the hardware sometimes and not

I will get all of that together tomorrow. I did check that the udrc was appearing is alsa. I will send you everything tomorrow.

What OS & program are you using to flash the microSD card? I'm trying to help you which is difficult if you don't do what I ask you to do. See previous post. Before you run any configuration scripts

Something is going wrong from the very beginning. I have done three straight flashes on the NW Digital image. I have followed the steps in 'Getting Started' to the letter. I have powered the hat

I see that, thanks Basil. I’ve got the 12v connector here too. I’ll power it up with that and verify the power and throttling. As I said, I needed to update to the bleeding edge kernel (Nov 29)

The DRAWS drivers are loaded & running fine. Your RPi is currently under voltage & running throttled. Either get a better 5V supply or think about powering the unit with DRAWS 12 V connector. Jim

Here’s my ./showudrc.sh output. pi@rpi4-draws:~/n7nix/bin $ ./showudrc.sh ==== Sound Card ==== udrc card number line: card 1: udrc [udrc], device 0: bcm2835-i2s-tlv320aic32x4-hifi

I actually have mine working now. I struggled last night with my RPi4 and Buster. It would get recognized immediately following these

A note on the Power Supply: DRAWS is designed for a nominal 12V Input. 9-15VDC is the recommended range. There is a 16V Tranzorb on the Input which provides over voltage and reverse protection (if

Jim Erickson <jim@...> writes: Please send me the output of showudrc.sh Also the make & model number of the power supply you are using to power your RPi. Thanks, /Basil

The driver modules not loading can only happen at boot time. Every time you make any change to your system & reboot run aplay -l to easily see if the DRAWS codec has been enumerated ie. the drivers

I feel like I suffer from a similar problem. Working image, then something happens, I wish I knew what, and then I can’t get my DRAWS recognized. This has happened on both a RPi4 and

I am running a fan external to the package which is blowing over the whole thing. /boot/config.txt is exactly as it was from the image with a single change. The on-board audio is commented out. I

Your hardware is fine. Your power supply is over voltage > +12V: +15.09 V You are running a Pi 4 with a very cool CPU core temp. Are running a fan? None of the required tlv320aic modules required by