Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
Forum Thread Details
  • Replies 180 replies
  • Subscribers 689 subscribers
  • Views 23082 views
  • Users 0 members are here
Related

Driver fixes and updates to kernel 3.18.16 and 4.0.5

hiassoft

Edit: Current kernel versions and install/config instructions are also available from my webpage http://www.horus.com/~hias/cirrus-driver.html

 

During the last few weeks I fixed various issues in the Wolfson/Cirrus driver and rebased it so it works with the current RPi kernel versions (3.18.16 and 4.0.5).

 

You can download the patches from my GitHub repository. The 3.18 kernel with Cirrus drivers is in the cirrus-3.18.y branch, the 4.0 kernel with Cirrus drivers is in the cirrus-4.0.y branch. I'll rebase and update these branches from time to time so that the Cirrus driver and my changes will stay on top of the commit list.

 

If you just want to have an updated 3.18.16 kernel you can download precompiled binaries from here. Just unpack the tarball in the root directory. Before you do that it might be a good idea to update the firmware files (bootcode.bin, start*.elf and fixup*.dat in the boot directory) to the latest version.

 

Here's a list of my changes:

- Added the FLL1 setup back so that switching between 44.1kHz and 48kHz (and other sample rates) works fine.

- Don't register Arizona IRQ if it's set to 0. The Cirrus driver uses polling here and if we register an interrupt handler for irq 0 we get lots of "spurious interrupt" messages spamming dmesg in kernel 3.19 and newer. IRQ 0 is wrong anyway.

- Include DCVDD patches from the Cirrus linux-drivers repository. These patches make sure the WM8804 chip is initialized properly. Without this patch I sometimes had SPDIF audio out only on the right channel.

- Disable spidev0 in Cirrus device tree overlay. That's mainly a safety precaution so that userspace programs trying to access spi0.0 won't interfere with the WM8804 reset line. I'm not 100% sure this is needed at all, so maybe I'll remove it some time later.

 

And some important notes:

I haven't included the mmap patch, this is already supported in the upstream kernels but currently disabled by default. To enable mmap support add the following line to config.txt:

dtoverlay=i2s-mmap

 

If you compile the kernel on your own please note that the devicetree overlays have now been moved to arch/arm/boot/dts/overlays.

 

Kernel 4.0 now uses spi_bcm2835 by default (the older spi_bcm2708 module is available via a devicetree overlay) so you have to extend your /etc/modprobe.d conf file and add a pre-depend for spi_bcm2835 as well. It's safe to have both the old and the new module in here, so just use this configuration:

softdep arizona-spi pre: arizona-ldo1
softdep spi-bcm2708 pre: fixed
softdep spi-bcm2835 pre: fixed

 

so long,

 

Hias

Parents Reply Children
  • in reply to clem57

    The RPi is connected to my router with a cable. The routers webinterface shows all connected devices so I can determine the Pi's IP.

    But now it doesn't show up there anymore so I guess it doesn't even get an IP which makes it hard to ping.

  • in reply to Former Member

    Check the cable for kinks or if you have another cable, try it. Also ports get loose and ned to be reseated. Clicks indicate good connection.

    C

  • in reply to clem57

    The cable is fine. I reinstalled Volumio 2 and made sure everything worked as it should. The RPi boots up and I can reach it with a web browser or ssh.

    While logged in over ssh I download the tarball and ran `sudo tar zxf cirrus-linux-4.4.14.tgz -C /`

    Then I added `dtoverlay=rpi-cirrus-wm5102` and `dtoverlay=i2s-mmap` to `/boot/config.txt`

    After a `reboot` I can no longer connect through browser or ssh and the RPi no longer shows up in the overview of connected devices in my router. In the meantime the cable was never disconnected so that connection should be fine.

  • in reply to Former Member

    I just had a look at volumio 2 (RC2 hotfix):

     

    It's setup is a quite different to Raspbian, it uses an initrd which sets up squashfs+overlayfs for the root partition. If you update the kernel, the modules in the initrd no longer match the kernel version, so it can't load them and setup the root filesystem which results in a nice kernel crash (visible if you connect a monitor or a serial console cable).

     

    I'm not sure if there's an official way to update the initrd from within a running volumio installation (there's a "volumio-init-updater" in /root, but it doesn't have the executable bits set and I'm not sure how to use it), but by looking at the buildscripts of the volumio system I figured out a way how to do it.

     

    After a fresh installation you first have to extract the existing initrd, there's one file we need from it, "init", which must be placed in the /root folder. Best do everything as root (use "sudo -s")

    root@volumio:~# mkdir initrd
root@volumio:~# cd initrd/
root@volumio:~/initrd# gzip -c -d /boot/volumio.initrd | cpio -i
root@volumio:~/initrd# cp -a init /root/

    Then extract the cirrus kernel, setup the modprobe.d and config.txt files etc as usual (I also commented out "dtparam=audio=on" and "force_turbo=1" in config.txt - we don't want the onboard audio and I'm not sure force_turbo is a good idea on a RPi3 without a heatsink).

     

    Next better remove the old modules, (check version with "uname -r") - 4.4.9 in case of current Volumio 2. The script to create the initramfs might pick up the wrong modules (it just uses the first 2 directories). ATM this works fine, because alphabetical sorting puts 4.4.14 before 4.4.9, but it might fail in the future when volumio ships a different kernel version. Also we don't really need the old modules.

    root@volumio:~# rm -rf /lib/modules/4.4.9*

     

    Now you can create an updated initrd:

    root@volumio:~# /usr/local/sbin/mkinitramfs-custom.sh -o /boot/volumio.initrd

     

    Then reboot (which should now work), ssh into the RPi and check with "aplay -l" that the soundcard is there.

     

    Now the only thing left to do is run the appropriate usecase scripts like "Playback_to_Lineout.sh" etc. You only need to do that once, the settings are preserved via the alsa mixer settings accross reboots.

     

    so long,

     

    Hias

  • in reply to hiassoft

    Many many thanks for your investigation and solution!

     

    While typing this message I am enjoying music playing through the Cirrus DAC on my RPi running Volumio image.

    The only other option would have been to buy a new (better supported) DAC and I'm really glad that is not necessary.

  • in reply to hiassoft

    @Matthias,

    you are right about volumio's initrd but you found a nice workaround. The volumio-init-updater does something else, it replaces the squash file on the second partition (as an alternative to doing this online).

    We have not finished the kernel & initrd update part, yet. Getting the first version of Volumio 2 had our priority.

    Gé

  • in reply to Former Member

    Hi Gé!

    you are right about volumio's initrd but you found a nice workaround. The volumio-init-updater does something else, it replaces the squash file on the second partition (as an alternative to doing this online).

    We have not finished the kernel & initrd update part, yet. Getting the first version of Volumio 2 had our priority.

    Thanks a lot for the info! A already thought this part might still be WIP (also maybe I missed some bits and pieces). No need to hurry, take your time, and good luck finishing the release!

     

    so long,

     

    Hias

  • in reply to hiassoft

    Thank you Hias for you help.

    I can try Volumio, it's working.

    FYI: I also can try RuneAudio by using ARCH linux kernel based on you patches:

    ArchLinux ARM kernel packages with driver for Cirrus Logic/Wolfson Audio Card

    Raspberry Pi2/3 with Cirrus Logic Audio Card : Raspberry Pi • RuneAudio Forum

    Vladimir

  • in reply to hiassoft

    Hi

     

    I tried this (July 18, 2016) post along with your site instructions RPi Linux driver for Wolfson / Cirrus Logic Audio Card

    Unfortunately failed, tried it a couple times to be sure I didn't miss anything.

     

    Using pi B+ , cirrus logic board , latest volumio 2.031

     

    I've tried multiple guides and images. The errors:

    mounting devices failing:

    /dev/loop0

    mounting overlay on /mnt/ext/union failed no such device

    mounting /mnt/static on /mnt/ext/union/static failed invalid argument

    ...

    finish initramfs, continue booting volumio

    switch_root: error moving root: invalid argument

     

    then kernel panic - not syncing: attempted to kill init!

    then gives stack info

    entering kdb dur to keyboard entry

    kdb>

     

    I'm lost here, I'm totally new to pi

    anyone help? thanks

  • in reply to vv111y

    Just tested current volumio (2.041) with the steps outlined in my post and it worked fine. Triple-check that you didn't miss anything.

     

    so long,

     

    Hias