Driver fixes and updates to kernel 3.18.16 and 4.0.5

Somewhere along the line, /boot/config.txt was overwritten and had default settings which had i2c turned OFF.  I found this by running i2cdetect.  Once I corrected the settings in /boot/config.txt, it worked and I was able to use mplayer to play an MP3 file.

That is great new. I am glad the i2cdetect led to the discovery what happened. Also for experts like hiassoft

Clem

Hi Matthias!

Thank you for the amazing work here and for keeping the kernels updated.

I wish what you are doing could replace the manual (or at least a big part of it) and the software download on the Cirrus Logic Audio Card page. I wasted quite a bit of time trying to get the outdated Wolfson / Cirrus Logic code to work. I'm pretty new to Element 14 so I don't know how to suggest it, but if there are any moderators here, this work should be linked to as the official version of how to get the card to work. I have a feeling people are wasting a lot of time (and maybe giving up) just because they don't realize the original manual is no longer correct.

I wish what you are doing could replace the manual (or at least a big part of it) and the software download on the Cirrus Logic Audio Card page. I wasted quite a bit of time trying to get the outdated Wolfson / Cirrus Logic code to work. I'm pretty new to Element 14 so I don't know how to suggest it, but if there are any moderators here, this work should be linked to as the official version of how to get the card to work.

spannerspencer What do you think?

Hi, I've been trying to get the 4.1x Kernel that you provide with the RPI 2 and cirrus audio card from the link : RPi Linux driver for Wolfson / Cirrus Logic Audio Card

I am trying to incorporate this into a buildroot built pi2 image. I am using the rpi-linux/arch/arm/configs/bcm2709_defconfig configuration for the kernel and 4.1.19 kernel headers

The rpi firmware which contains the config.txt and dtb overlays come from official rpi git ( 046effa13ebc4cc7601df4f06f4834bd0eebb0f8 which is think is latest ).

my config.txt is :-

arm_freq=900

core_freq=250

sdram_freq=450

over_voltage=2

dtoverlay=rpi-cirrus-wm5102-overlay

dtoverlay=i2s-mmap

I took the overlays for rpi-cirrus-wm5102-overlay.dtb , i2s-mmap-overlay.dtb from your 4.1 prebuilt kernel gz image

( a question about the overlays , does the reference in the contig.txt have to match exact file name . i.e. I've seen : dtoverlay=rpi-cirrus-wm5102  & dtoverlay=rpi-cirrus-wm5102 does the file name have to correspond exactly to the overlay dtb file name or does it automatically remove the -overlay part? )

Also i've seen both raspi-blacklist.config and cirrus.config in different instructions up the page. Which is correct? why?

Mine is cirrus.config and it contains

softdep arizona-spi pre: arizona-ldo1

softdep spi-bcm2708 pre: fixed

softdep spi-bcm2835 pre: fixed

softdep snd-soc-wm8804-i2c pre: snd-soc-rpi-wsp-preinit

softdep snd-soc-rpi-wsp pre: snd-soc-wm8804-i2c

is this correct?

Am I missing something?

here is extract of my dmesg where the audio card is attempted to be initialised. Could you tell me what is wrong here?

Hi Rob!

The problem you're running into probably come from mixing dtbs/overlays. The dtbs/overlays are tied to the kernel, so always use the ones generated from "make dtbs / make dtbs_install".

Use the GPU firmware (bootcode.bin, start_x.elf, fixup_x.elf) from the rpi-firmware repo and config.txt from there as a template. Compile the kernel from my github tree, using bcm2709_defconfig from that tree, and use kernel(7).img, modules and dtbs from there.

As for overlays: better use "dtoverlay=rpi-cirrus-wm5102", without the "-overlay". With kernel 4.1 both versions will work but with kernel 4.4 that'll change - the overlay files are named "rpi-cirrus-wm5102.dtbo" there (instead of previously rpi-cirrus-wm5102-overlay.dtb) and the "-overlay" variants will no longer work.

As for the modprobe file: Use cirrus.conf - putting the config into blacklist.conf as described in the original instructions is rather counter-intuitive IMO. Also you don't need the 2 last softdep lines with wm8804-i2c when using my 4.1.19 kernel, that was only needed for older kernels where I tried a different approach to fix wm8804 initialization issues (which I've now replaced by a better fix).

so long,

Hias

Hi there, tried downloading some of the images, however, on extraction there are quite a few files that are already written, and asks if I want to overwrite them, some have different kb sizes, not sure what is going on there, any pointers?

I have just received my first raspi3 with the cirrus logic card, works great on the piB with other images, but those "other" images do not work on the raspi3.

Regards

Hi Alan!

What exactly to you mean by "other" images? How did you extract the files, when did you get the "overwrite" messages?

For the RPi3 you need the very latest kernel, currently 4.1.19. Also follow the instructions on my website:

RPi Linux driver for Wolfson / Cirrus Logic Audio Card

The precompiled kernel overwrites quite some files (kernel.img, dtb/overlay files, modules if you have kernel 4.1.19 already installed), but normally extracting with tar will silently overwrite them. Unless you forgot to extract as root or use sudo, then it can't overwrite these files and will complain loudly.

so long,

Hias

Hello Hias,

When I extract the file cirrus-linux-4.1.19.tgz (using windows PC) extract to a new folder, as the image is being extracted, the files being written from the folder "lib" - there are quite a few files (9) with the same name, but different files sizes, I get prompted to either overwrite or skip them. Not sure why there are already files written as they should all be unique. Quite confused about that!

The first two are shown below.

Anyway I was hoping they would be extracted so that I could then copy them to the Pi3's SD card.

I'm a bit of a noob, but have several Pi's, but not had any experience with Pi2's or Pi3's though.

I'm just playing with a NOOBS image that can boot the Pi3, and seeing if I can manage to get darkice to install.

But any help in the mean time would be welcomed.

Regards

Alan

Hi Alan!

Ah, now I understand :-)

You shouldn't extract the .tar.gz file on your PC, download it on your RPi and then extract it there using the commands from my webpage.

sudo tar zxf cirrus-linux-4.1.19.tgz -C /

sudo ensures the the command is run as root (and can overwrite the files / access the directories owned by root) and the -C / at the end ensures the files are extracted into the correct directories (/boot, /lib/modules etc).

You also have to create the /etc/modprobe.d/cirrus.conf file as root, using an editor on the raspberry pi, for example using nano (that's one of the less-confusing editors on the RPi)

sudo nano /etc/modprobe.d/cirrus.conf

Ah, and don't forget to edit /boot/config.txt as described on my webpage.

so long,

Hias

Thank you for that - I actually managed (only just before your email arrived) to do that very thing.

I am slowly getting there, just trying to remember where the scripts were to test darkice!

Not sure if any sound can be heard or recorded as yet, I've basically done it, with a reboot all seems fine (thanks to your work), just about to find the elusive scripts now, ha...

Thank you so much for the work you do, though Cirrus should be doing that on OUR behalf eh..

Thanks again!

Alan