Cirrus Logic Audio Card working on the Raspberry Pi 2

I tried the patched kernel with Ubuntu MATE Beta 15.04 and it worked.

But with the new stable release of Ubuntu the kernel breaks all network connections and input devices even bluetooth keyboard

Hello,

thank you for the provided image. The audio works fine.

However, I am trying to compile the kernel with cirrus driver and RT patch without success. I assume it already fails with the cirrus part.

I followed the cirrus instructions from here: https://github.com/CirrusLogic/rpi-linux/wiki/Building-the-code

and added the RT patch from https://www.kernel.org/pub/linux/kernel/projects/rt/3.18/older/patch-3.18.9-rt5.patch.gz

How did you build your image, Ragnar?

Martin

No need to recompile, Jack2 from the Raspbian repositories works on the RPi (contrary to Jack1 which needs a patch to work around the bus error). You need to tell it where the dbus session bus is though:

export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/dbus/system_bus_socket

Then it probably still won't start because Jack2 can not acquire the sound card, you can fix that by adding the following lines to /etc/dbus-1/system.conf:

  <policy user="pi">
        <allow own="org.freedesktop.ReserveDevice1.Audio1"/>
  </policy>

More info here: http://wiki.linuxaudio.org/wiki/raspberrypi#running_jack

I patched the kernel in my image to add mmap support for I2S cards. The stock Raspbian kernel doesn't have it, but the old Wolfson 3.10 kernel does.

Could you please provide me with the entire patch file, I'm getting a malformation error.

That's why I built my own, without dbus. Almost all of my Pis are headless, thus no X server running and consequently no dbus service.

Since mine are headless too, this might be interesting. Where did you disable the dbus service?

After inserting this in /etc/dbus-1/system.conf and adding export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/dbus/system_bus_socket

  <policy user="pi">
        <allow own="org.freedesktop.ReserveDevice1.Audio0"/>
        <allow own="org.freedesktop.ReserveDevice1.Audio1"/>
  </policy>

I was able to start jack2 via jackd -v -P70 -p16 -t2000 -d alsa -dplughw:0,0 -p 1024 -n 3 -r 44100 -s but only with the increased buffer size and -dplughw:0,0

which might not start in RT and does not make a stable impression.

Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackPosixThread::ThreadHandler : start
Jack: JackThreadedDriver::Init real-time
Jack: JackPosixThread::AcquireRealTimeImp priority = 70
Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackPosixThread::ThreadHandler : start

Jack: JackAlsaDriver::Read warning fBufferSize = 1024 nframes = 2048
Jack: JackAlsaDriver::Read warning fBufferSize = 1024 nframes = 2048
Jack: JackAlsaDriver::Read warning fBufferSize = 1024 nframes = 2048
Jack: JackAlsaDriver::Read warning fBufferSize = 1024 nframes = 2048
Jack: JackAlsaDriver::Read warning fBufferSize = 1024 nframes = 2048
Jack: JackAlsaDriver::Read warning fBufferSize = 1024 nframes = 2048
Jack: JackAlsaDriver::Read warning fBufferSize = 1024 nframes = 2048

pi@raspberrypi2 ~ $ jackd -v -P70 -p16 -t2000 -d alsa -dhw:0,0 -p 128 -n 3 -r 44100 -s
jackdmp 1.9.9
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2012 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 70
Jack: JackPosixThread::StartImp : create non RT thread
Jack: JackPosixThread::ThreadHandler : start
Jack: playback device hw:0,0
Jack: capture device hw:0,0
Jack: frames per period = 128
Jack: apparent rate = 44100
Jack: JackDriver::Open capture_driver_name = hw:0,0
Jack: JackDriver::Open playback_driver_name = hw:0,0
Jack: Check protocol client = 8 server = 8
Jack: JackEngine::ClientInternalOpen: name = system
Jack: JackEngine::AllocateRefNum ref = 0
Jack: JackPosixSemaphore::Allocate name = jack_sem.1000_default_system val = 0
Jack: JackEngine::NotifyAddClient: name = system
Jack: JackGraphManager::SetBufferSize size = 128
Jack: JackConnectionManager::DirectConnect first: ref1 = 0 ref2 = 0
Jack: JackGraphManager::ConnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Jack: JackDriver::SetupDriverSync driver sem in flush mode
control device hw:0
control device hw:0
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0,0|hw:0,0|128|3|44100|0|0|nomon|swmeter|soft-mode|32bit
control device hw:0
configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 3 periods
ALSA: mmap-based access is not possible for the capture stream of this audio interface
ALSA: cannot configure capture channel
Jack: JackDriver::Close
Jack: JackConnectionManager::DirectDisconnect last: ref1 = 0 ref2 = 0
Jack: JackGraphManager::DisconnectRefNum cur_index = 0 ref1 = 0 ref2 = 0
Jack: JackEngine::ClientInternalClose ref = 0
Jack: JackEngine::ClientCloseAux ref = 0
Jack: JackGraphManager::RemoveAllPorts ref = 0
Jack: JackPosixSemaphore::Destroy name = jack_sem.1000_default_system
Jack: ~JackDriver
Cannot initialize driver
Jack: no message buffer overruns
Jack: JackPosixThread::Stop
Jack: JackPosixThread::ThreadHandler : exit
JackServer::Open failed with -1
Jack: Succeeded in unlocking 13589216 byte memory area
Jack: JackShmMem::delete size = 0 index = 0
Jack: ~JackDriver
Jack: Succeeded in unlocking 1040 byte memory area
Jack: JackShmMem::delete size = 0 index = 1
Jack: Cleaning up shared memory
Jack: Cleaning up files
Jack: Unregistering server `default'
Failed to open server

I have noticed that you can get invisible junk characters if you copy-paste from this web site, especially from the "view plain" window.

While you're at it, you might be interested in a patch supplied by hiassoft that solves some problems when switching sampling rates, described here Issues with samplerates below 44.1kHz

Building jack with its default compilation mode produces a dbus-less version. You have to explicitly give it a --dbus flag at configure time to enable it.

--

Ragnar

Try using -hw:sndrpiwsp instead of -hw:0,0 and use the appropriate Wolfson amixer scripts to enable the inputs and outputs you want to to use with JACK before starting JACK.

I applied the mmap patch. The fll patch had to be applied manually to ~/code/rpi-linux/sound/soc/bcm/rpi-cirrus-sound-pi.c since the patch was looking for a rpi-cirrus-sound-pi.c.orig

Recompiled the kernel but JACK seems to miss the alsa driver I should have inclueded with ./waf configure --alsa but it requires version 1.0.18

What kind of package of alsa is that?

I was under the impression of this being the alsa version:

pi@raspberrypi2 ~/jack2 $ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version k3.18.9-v7+.

Jeremy, I used the Playback_to_Lineout.sh script but I got sound from the headset port aswell.

And the jack errors with missing alsa driver:

pi@raspberrypi2 ~/jack2 $ jack_control start
Traceback (most recent call last):
  File "/usr/local/bin/jack_control", line 399, in <module>
    main()
  File "/usr/local/bin/jack_control", line 158, in main
    bus = dbus.SessionBus()
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 211, in __new__
    mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 122, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

pi@raspberrypi2 ~/jack2 $ jackd  -P70 -p16 -t2000 -d alsa -dhw:sndrpiwsp -p 1024 -n 3 -r 44100 -s
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
Unknown driver "alsa"

Recompiled the kernel but JACK seems to miss the alsa driver I should have inclueded with ./waf configure --alsa but it requires version 1.0.18

What kind of package of alsa is that?

It's the ALSA developer files and libraries.

sudo apt-get install libasound2-dev

I used the Playback_to_Lineout.sh script but I got sound from the headset port aswell.

The scripts are cumulative, switching an output on does not switch the others off. That's why Reset_paths.sh exists, it switches everything off.

--

Ragnar

I see, Jeremy just meant it is not advisable to configure the soundcard after starting JACK.

It's getting closer: JACK2 compiled successfully and I can start the daemon. Although the build had many warnings (http://pastebin.com/Q22hQBV6) and not everything works as expected. It is still looking for the dbus.

pi@raspberrypi2 ~ $ jack_control start
Traceback (most recent call last):
  File "/usr/local/bin/jack_control", line 399, in <module>
    main()
  File "/usr/local/bin/jack_control", line 158, in main
    bus = dbus.SessionBus()
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 211, in __new__
    mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 122, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

pi@raspberrypi2 ~ $ export DBUS_SESSION_BUS_ADDRESS=unix:path=/run/dbus/system_bus_socket
pi@raspberrypi2 ~ $ jack_control start
Traceback (most recent call last):
  File "/usr/local/bin/jack_control", line 399, in <module>
    main()
  File "/usr/local/bin/jack_control", line 160, in main
    controller = bus.get_object(service_name, "/org/jackaudio/Controller")
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 248, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 180, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 278, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking
    message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.jackaudio.service was not provided by any .service files

The daemon starts but clients are not able to connect

pi@raspberrypi2 ~ $ jack_simple_client 
Cannot open jack_simple_client client
jack_client_open() failed, status =

pi@raspberrypi2 ~/jack2 $ jackd -P70 -p16 -t2000 -d alsa -dhw:0,0 -p 128 -n 3 -r 44100 -s
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 70
self-connect-mode is "Don't restrict self connect requests"
creating alsa driver ... hw:0,0|hw:0,0|128|3|44100|0|0|nomon|swmeter|soft-mode|32bit
configuring for 44100Hz, period = 128 frames (2.9 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 3 periods for playback
JackPosixSemaphore::Signal name = jack_sem.1000_default_system already deallocated!!
JackAudioDriver::ProcessGraphAsyncMaster: ResumeRefNum error
JackPosixSemaphore::Signal name = jack_sem.1000_default_system already deallocated!!
JackAudioDriver::ProcessGraphAsyncMaster: ResumeRefNum error
JackPosixSemaphore::Signal name = jack_sem.1000_default_system already deallocated!!
JackAudioDriver::ProcessGraphAsyncMaster: ResumeRefNum error
JackPosixSemaphore::Signal name = jack_sem.1000_default_system already deallocated!!
JackAudioDriver::ProcessGraphAsyncMaster: ResumeRefNum error
JackPosixSemaphore::Signal name = jack_sem.1000_default_system already deallocated!!
JackAudioDriver::ProcessGraphAsyncMaster: ResumeRefNum error
JackPosixSemaphore::Signal name = jack_sem.1000_default_system already deallocated!!
JackAudioDriver::ProcessGraphAsyncMaster: ResumeRefNum error
JackPosixSemaphore::Signal name = jack_sem.1000_default_system already deallocated!!
JackAudioDriver::ProcessGraphAsyncMaster: ResumeRefNum error
status error: Bad file descriptor
ALSA: prepare error for playback on "hw:0,0" (File descriptor in bad state)
JackAudioDriver::ProcessAsync: read error, stopping...
JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Driver is not running
Cannot create new client
JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Driver is not running
Cannot create new client
JackPosixProcessSync::LockedTimedWait error usec = 5000000 err = Connection timed out
Driver is not running
Cannot create new client
^CJack main caught signal 2
Segmentation fault

It is still looking for the dbus

Where have you installed your self-compiled jackd? Mine lives in /usr/local/bin and I've put a symlink to it in /usr/bin because that's where some of the jack_* utilities look for it.

It's jack_control and jack_simple_client that's trying to use dbus to start a jack daemon.

If they actually manage to start a jack daemon, it might be because they have found the old dbus-enabled jackd in /usr/bin

--

Ragnar

I used the default path when executing sudo ./waf install

I also deinstalled and removed all jack related binaries to make sure only the newly compiled dbus-less version gets used.

Maybe I checked out a different JACK2 version than you did?

pi@raspberrypi2 ~ $ ll /usr/local/bin/
total 520
drwxrwsr-x 2 root indiecity  4096 Feb 16 13:29 indiecity
-rwxr-xr-x 1 root staff      8918 May 10 17:41 jack_alias
-rwxr-xr-x 1 root staff      9393 May 10 17:41 jack_bufsize
-rwxr-xr-x 1 root staff     12033 May 10 17:41 jack_connect
-rwxr-xr-x 1 root staff     15725 May 10 13:14 jack_control
-rwxr-xr-x 1 root staff     12738 May 10 17:41 jack_cpu
-rwxr-xr-x 1 root staff      7747 May 10 17:41 jack_cpu_load
lrwxrwxrwx 1 root staff        12 May 10 13:24 jack_disconnect -> jack_connect
-rwxr-xr-x 1 root staff      9344 May 10 17:41 jack_evmon
-rwxr-xr-x 1 root staff      7778 May 10 17:41 jack_freewheel
-rwxr-xr-x 1 root staff     13053 May 10 17:41 jack_iodelay
-rwxr-xr-x 1 root staff     12159 May 10 17:41 jack_latent_client
-rwxr-xr-x 1 root staff     10665 May 10 17:41 jack_load
-rwxr-xr-x 1 root staff     13849 May 10 17:41 jack_lsp
-rwxr-xr-x 1 root staff     14799 May 10 17:41 jack_metro
-rwxr-xr-x 1 root staff     12954 May 10 17:41 jack_midi_dump
-rwxr-xr-x 1 root staff     31878 May 10 17:41 jack_midi_latency_test
-rwxr-xr-x 1 root staff      9933 May 10 17:41 jack_midiseq
-rwxr-xr-x 1 root staff     10275 May 10 17:41 jack_midisine
-rwxr-xr-x 1 root staff      7325 May 10 17:41 jack_monitor_client
-rwxr-xr-x 1 root staff     14606 May 10 17:41 jack_multiple_metro
-rwxr-xr-x 1 root staff     38948 May 10 17:41 jack_netsource
-rwxr-xr-x 1 root staff      7864 May 10 17:41 jack_samplerate
-rwxr-xr-x 1 root staff     12988 May 10 17:41 jack_server_control
-rwxr-xr-x 1 root staff     11743 May 10 17:41 jack_session_notify
-rwxr-xr-x 1 root staff      8316 May 10 17:41 jack_showtime
-rwxr-xr-x 1 root staff     10132 May 10 17:41 jack_simple_client
-rwxr-xr-x 1 root staff     10913 May 10 17:41 jack_simple_session_client
-rwxr-xr-x 1 root staff     66387 May 10 17:41 jack_test
-rwxr-xr-x 1 root staff     10479 May 10 17:41 jack_thru
-rwxr-xr-x 1 root staff      7682 May 10 17:41 jack_unload
-rwxr-xr-x 1 root staff      9667 May 10 17:41 jack_wait
-rwxr-xr-x 1 root staff      8064 May 10 17:41 jack_zombie
-rwxr-xr-x 1 root staff     28881 May 10 17:41 jackd

pi@raspberrypi2 ~ $ ll /usr/bin/jack*
lrwxrwxrwx 1 root root 27 May 11 08:52 /usr/bin/jack_control -> /usr/local/bin/jack_control
lrwxrwxrwx 1 root root 33 May 11 08:59 /usr/bin/jack_simple_client -> /usr/local/bin/jack_simple_client
lrwxrwxrwx 1 root root 20 May 11 08:50 /usr/bin/jackd -> /usr/local/bin/jackd
pi@raspberrypi2 ~ $ jack_control start
Traceback (most recent call last):
  File "/usr/local/bin/jack_control", line 399, in <module>
    main()
  File "/usr/local/bin/jack_control", line 158, in main
    bus = dbus.SessionBus()
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 211, in __new__
    mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/_dbus.py", line 100, in __new__
    bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 122, in __new__
    bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

PS: The fll patch worked, I can now play my wave testfile with aplay!

Maybe I checked out a different JACK2 version than you did?

Mine is older than yours (1.9.9.5) but otherwise  the same.

But, jack_control has only one purpose; to control jack-dbus. It's a python script, it isn't configured or built, just copied.

The fll patch worked, I can now play my wave testfile with aplay!

--

Ragnar

Maybe I checked out a different JACK2 version than you did?

Mine is older than yours (1.9.9.5) but otherwise  the same.

But, jack_control has only one purpose; to control jack-dbus. It's a python script, it isn't configured or built, just copied.

The fll patch worked, I can now play my wave testfile with aplay!

--

Ragnar

But, jack_control has only one purpose; to control jack-dbus. It's a python script, it isn't configured or built, just copied.

So there is no need for jack_control if I want to run it headless anyway?

I removed all jack files and started over, this time I used a prefix to install it directly into /usr/bin

./waf configure --alsa --prefix /usr/

The jackd executes fine, but I did not find a client who was able to connect. This was working at least partially with the JACK1 version from the raspbian repository.

pi@raspberrypi2 ~/jack2 $ jackd  -P70 -p16 -t2000 -d alsa -dhw:sndrpiwsp -p 1024 -n 3 -r 44100 -s
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 70
self-connect-mode is "Don't restrict self connect requests"
creating alsa driver ... hw:sndrpiwsp|hw:sndrpiwsp|1024|3|44100|0|0|nomon|swmeter|soft-mode|32bit
configuring for 44100Hz, period = 1024 frames (23.2 ms), buffer = 3 periods
ALSA: final selected sample format for capture: 32bit integer little-endian
ALSA: use 3 periods for capture
ALSA: final selected sample format for playback: 32bit integer little-endian
ALSA: use 3 periods for playback

pi@raspberrypi2 ~/jack2 $ jack_simple_client 
unknown option character l
connect(2) call to jackdmp 1.9.11/jack-1000/default/jack_0 failed (err=No such file or directory)
jackdmp 1.9.11
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2014 Grame.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
`default' server already active
Failed to open server
connect(2) call to jackdmp 1.9.11/jack-1000/default/jack_0 failed (err=No such file or directory)
connect(2) call to jackdmp 1.9.11/jack-1000/default/jack_0 failed (err=No such file or directory)
connect(2) call to jackdmp 1.9.11/jack-1000/default/jack_0 failed (err=No such file or directory)
connect(2) call to jackdmp 1.9.11/jack-1000/default/jack_0 failed (err=No such file or directory)

Hello Martin, what are your plans with the RPi?

Hi Jeremy, I am trying to setup a low latency audio system for filtering etc. I might even get into AMP with some RTOS but getting the cirrus board to work in bare metal might take to long.

So for now it is just the RT kernel JACK and maybe Supercollider or pure C.