[SOLVED] Justboom Digi zero

[Tantor]

Hello, I have an issue with my Raspberry Zero W and a Justboom Zero Digi Hat. When I try to open Moode Player 7.3 I have a message saying that Moode cannot open the ALSA device "_audio out".
Can you help me?

Whoa! where did that monumentally long link come from ???

[Tantor]

I don't know, I did a copy paste of the screen and I got this "link" instead.

[Tim Curtis]

Reboot and post the Moode log.

Code:

moodeutl -l

[Tantor]

That's what I got.


/boot$ moodeutl -l
20210903 092743 worker: -- Start
20210903 092743 worker: Successfully daemonized
20210903 092744 worker: Integrity check (passed)
20210903 092748 worker: File check (OK)
20210903 092750 worker: Session vacuumed
20210903 092750 worker: Session loaded
20210903 092750 worker: Debug logging (ON)
20210903 092750 worker: -- Audio debug
20210903 092750 worker: ALSA cards: (0:empty | 1:empty | 2:empty | 3:empty
20210903 092750 worker: MPD config: (0:JustBoom Digi HAT(Zero) | mixerDigital) | card:0)
20210903 092750 worker: ALSA mixer actual (Digital)
20210903 092751 worker: ALSA Digital volume set to (Invalid card number.)
20210903 092751 worker: -- System
20210903 092755 worker: Host (moode)
20210903 092755 worker: moOde (7.3.0 2021-06-25)
20210903 092755 worker: RaspiOS (10.6)
20210903 092755 worker: Kernel (5.4.77+ #1371)
20210903 092755 worker: Platform (Pi-Zero W 1.1 512MB)
20210903 092755 worker: ARM arch (armv6l, 32-bit kernel)
20210903 092755 worker: MPD ver (0.22.8_p0x3)
20210903 092755 worker: CPU gov (ondemand)
20210903 092755 worker: USB boot not available
20210903 092755 worker: File system not expanded yet
20210903 092755 worker: HDMI port on
20210903 092755 worker: -- Network
20210903 092755 worker: eth0 does not exist
20210903 092755 worker: eth0 address not assigned
20210903 092756 worker: wlan0 exists
20210903 092756 worker: wifi country (US)
20210903 092756 worker: wlan0 trying SSID
20210903 092756 worker: IP addr (192.168.0.116)
20210903 092756 worker: Netmask (255.255.255.0)
20210903 092756 worker: Gateway (192.168.0.1)
20210903 092756 worker: Pri DNS (192.168.0.1)
20210903 092756 worker: Domain (None)
20210903 092756 worker: Pi integrated wlan0 power save disabled
20210903 092756 worker: -- Audio config
20210903 092758 worker: MPD conf updated
20210903 092758 worker: ALSA card number (0)
20210903 092758 worker: MPD audio output (JustBoom Digi HAT(Zero))
20210903 092758 worker: WARNING: No device found at MPD configured card 0
20210903 092758 worker: ALSA mixer name (Digital)
20210903 092758 worker: MPD volume control (software)
20210903 092758 worker: Hdwr volume controller exists
20210903 092758 worker: Max ALSA volume (100%)
20210903 092758 worker: ALSA output mode (Default: plughw)
20210903 092758 worker: ALSA loopback (Off)
20210903 092758 worker: Reset renderer active flags
20210906 212008 worker: CamillaDSP (__quick_convolution__.yml)
20210906 212008 worker: -- MPD startup
20210906 212009 worker: MPD started
20210906 212009 openMpdSocket(): error: connection failed (1) 111, Connection refused
20210906 212010 openMpdSocket(): error: connection failed (2) 111, Connection refused
20210906 212010 openMpdSocket(): error: connection failed (3) 111, Connection refused
20210906 212011 openMpdSocket(): error: connection failed (4) 111, Connection refused
20210906 212011 openMpdSocket(): error: connection failed (5) 111, Connection refused
20210906 212012 openMpdSocket(): error: connection failed (6) 111, Connection refused
20210906 212012 worker: MPD connection refused
20210906 212014 readMpdResponse(): error: fgets failure ()
20210906 212014 worker: MPD crossfade (off)
20210906 212014 readMpdResponse(): error: fgets failure ()
20210906 212014 worker: MPD ignore CUE files (yes)
20210906 212014 worker: -- Feature availability
20210906 212014 worker: Source select (available)
20210906 212014 worker: Source select (source: MPD)
20210906 212014 worker: Source select (output: JustBoom Digi HAT(Zero))
20210906 212014 worker: Bluetooth (available)
20210906 212014 worker: Airplay renderer (available)
20210906 212014 worker: Spotify renderer (available)
20210906 212014 worker: Squeezelite (available)
20210906 212014 worker: RoonBridge renderer (not installed)
20210906 212014 worker: UPnP renderer (available)
20210906 212014 worker: DLNA server (available)
20210906 212014 worker: UPnP browser (available)
20210906 212014 worker: GPIO button handler (available)
20210906 212014 worker: Stream recorder (n/a)
20210906 212014 worker: -- Music sources
20210906 212015 worker: USB sources (none attached)

20210906 212023 worker: NAS and UPnP sources (mountall initiated)
20210906 212023 worker: -- Other
20210906 212023 worker: USB volume knob (Off)
20210906 212023 worker: USB auto-mounter (udisks-glue)
20210906 212023 worker: LED0 (On)
20210906 212023 worker: LED1 (sysclass does not exist)
20210906 212023 worker: Saved MPD vol level (0)
20210906 212023 worker: Preamp volume level (0)
20210906 212024 worker: MPD volume level (0) restored
20210906 212024 worker: ALSA Digital volume (Invalid card number.)
20210906 212024 worker: Auto-play (Off)
20210906 212024 readMpdResponse(): error: fgets failure ()
20210906 212024 worker: Maintenance interval (3 hours)
20210906 212024 worker: Screen saver activation (Never)
20210906 212024 worker: Session permissions (OK)
20210906 212024 worker: Watchdog started
20210906 212024 worker: Ready

[Tim Curtis]

The log messages below suggest breakage in the image. Try a fresh image, re-seat the DAC board, select it in Audio Config and reboot. The log should look clean at that point and show the device assigned to ALSA card 0. If not then it would suggest some sort of hardware issue.

These messages indicates Linux / ALSA does not see any audio device connected.

Code:

20210903 092750 worker: ALSA cards: (0:empty | 1:empty | 2:empty | 3:empty

20210903 092751 worker: ALSA Digital volume set to (Invalid card number.)

20210903 092758 worker: ALSA card number (0)
20210903 092758 worker: WARNING: No device found at MPD configured card 0

20210906 212024 worker: ALSA Digital volume (Invalid card number.)

These messages indicate MPD internal communication is broken.

Code:

20210906 212009 worker: MPD started
20210906 212009 openMpdSocket(): error: connection failed (1) 111, Connection refused
20210906 212012 worker: MPD connection refused
20210906 212014 readMpdResponse(): error: fgets failure ()

[Tantor]

Hello Tim, thank you very much for the advice. Actually, I already tried to reboot with a fresh image and I still have the issue. I also connected the hat to another PI and still the ALSA mixer doesn't detect it : I am afraid the Justboom digi zero hat is fried... ?

[Tim Curtis]

Possibly.

Most audio boards have an LED that lights up to indicate power and operation. You could also verify that the driver for the board is configured. You would see the line below in /boot/config.txt

Code:

dtoverlay=justboom-digi

If the driver is correctly specified then reboot and look in dmesg log for i2s success line or i2s error lines. Below is an example from my Allo Boss2 DAC.

Code:

pi@rp2:~ $ dmesg | grep i2s
[    6.858213] asoc-audio-graph-card soc:sound: allo-cs43130 <-> fe203000.i2s mapping ok

[Tantor]

Possibly.

Most audio boards have an LED that lights up to indicate power and operation. You could also verify that the driver for the board is configured. You would see the line below in /boot/config.txt

Code:

dtoverlay=justboom-digi

If the driver is correctly specified then reboot and look in dmesg log for i2s success line or i2s error lines. Below is an example from my Allo Boss2 DAC.

Code:

pi@rp2:~ $ dmesg | grep i2s
[    6.858213] asoc-audio-graph-card soc:sound: allo-cs43130 <-> fe203000.i2s mapping ok

[Tantor]

Possibly.

Most audio boards have an LED that lights up to indicate power and operation. You could also verify that the driver for the board is configured. You would see the line below in /boot/config.txt

Code:

dtoverlay=justboom-digi

If the driver is correctly specified then reboot and look in dmesg log for i2s success line or i2s error lines. Below is an example from my Allo Boss2 DAC.

Code:

pi@rp2:~ $ dmesg | grep i2s
[    6.858213] asoc-audio-graph-card soc:sound: allo-cs43130 <-> fe203000.i2s mapping ok

 
Hello Tim, I checked the point you mentioned :the driver is correctly specified in the file config.txt and the hat is OK (initially I thought it was fried). Would you mind having a look at the driver justboom-digi.dtbo (maybe an issue with the compile?, the chip seems to be Wolfson WM8804G)

15.111737] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[   15.124964] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[   15.125069] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[   15.137480] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[   15.137557] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[   15.887508] snd-rpi-wm8804 socound: ASoC: failed to init link JustBoom Digi: -517
[   17.011145] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   17.327255] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   17.816559] snd-rpi-wm8804 socound: ASoC: failed to init link JustBoom Digi: -517
[   17.831079] brcmfmac: F1 signature read @0x18000000=0x1541a9a6
[   17.854351] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   17.854821] usbcore: registered new interface driver brcmfmac
[   17.857452] snd-rpi-wm8804 socound: ASoC: failed to init link JustBoom Digi: -517
[   17.884950] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43430-sdio.raspberrypi,model-zero-w.txt failed with error -2
[   18.152831] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1
[   18.153063] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available
[   18.163910] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 22 2019 01:59:28 version 7.45.98.94 (r723000 CY) FWID 01-3b33decd
[   26.036292] wm8804 1-003b: Failed to read device ID: -121
[   26.098311] wm8804: probe of 1-003b failed with error -121
[   29.307331] random: crng init done

[Tim Curtis]

The manufacturer creates and maintains the driver overlays for their boards. You would need to contact them for support.