Can not get Beocreate + Beovox CX100 to play any sound

Bart

June 16, 2019 14:49

None

Hi all,

I was very excited about this concept of repurposing vintage speakers to modern ones, so I ordered a Beocreate and Raspberry Pi, and I found a pair of CX100s I wanted to use.

Went through the whole upcycling guide with my dad who is more skilled when it comes to hardware than I am, then struggled a little as I never set up a Raspberry Pi before, but found out at the end and I was able to walk through the setup on my computer (Chrome on MacOS). The Beovox CX100 showed up in my bluetooth menu, but when I selected it and tried playing some music through Spotify, nothing happened. I also tried YouTube, and also tried playing from my smartphone and iPad, but still no sound. After the installation, I also didn't hear a tone, which should have played according to the set-up tool.

On this forum I read that the Beocreate should also play through Toslink, so I picked up a cable and tried playing sound through both my Chromecast Audio as well as my MacBook, but the Beocreate + Beovox remained stilent.

When looking at the internet use in my router app during setup, the Beocreate board isn't using any data at all (0 kb). Is this normal? Also during set-up, it is written that the system should announce its IP-address, but this didn't happen with mine either.

I hope somebody can help me to get sound from these speakers!

Kind regards,

— Bart.

Date Votes

21 comments

0

Tuomas June 18, 2019 21:21

Hi Bart,

sorry to hear about your issue. This sounds like an issue with the Beocreate board, because all of the things you mentioned depend on it.

The following steps should help us get closer to the solution. If the board "passes" a check, go to the next step, but if not, let me know and we'll figure out where to take it from there.

1. Is the "selfboot" jumper connected? This is a single jumper (two pins) near the optical audio jacks on the board and it should be seated, otherwise the DSP will not start up and thus you will get no sound. If not, power down the system, plug in the jumper and power up the system again.

2. Look at the "mute" jumper on the board. It's in a group of three jumpers (six pins), and it should not be connected – otherwise the board is muted all the time. Disconnect the jumper if it was in place.

3. When you look at the board, do you see two green LEDs illuminated? They are located at the edge of the board close to the Raspberry Pi HDMI connector. Additionally, is there a red light in the optical output jack? Under normal circumstances, the two green LEDs should be lit (but one of them will turn off when playing music) and there should be a red light in the optical output.

4. Connect to the Raspberry Pi via SSH (password is "raspberry" unless you have changed it) or hook it up to a keyboard and a monitor. Run the following:

dsptoolkit get-checksum

This will return the "fingerprint" of the DSP program that the board is currently running. For all default Beocreate installations this should be 18454E5C3033E17F5A11937BF90ED7E4. If you see something else, you should try going to the Sound Profile screen in the setup interface and reinstalling the sound profile for your CX 100 (just select it and choose Install). The board sometimes appears to be a bit stubborn in accepting a new DSP program, so doing this a couple of times may solve the issue.

As to your question about data usage, the board should be using some, but very minimal amounts of data. The only thing that is downloaded during the guided setup process is the sound profile, and this is about 100 KB in size.

Best,

Tuomas from Bang & Olufsen

Comment actions Permalink
0

Bart June 19, 2019 09:58

Hi Tuomas,

Thanks so much for your response, it was the mute jumper that was connected on the board!

Comment actions Permalink
0

Alexander May 20, 2020 08:03

Hi Tuomas,

I have had problems with my Beocreate board as well.
Retracing my steps, I booted up the RPi connected to the Beocreate board, flashed the DSP profile and tried to play via spotify connect (no sound), then i tried bluetooth (no sound).

I found your post and get as far as step 2. I had the mute jumper on.. removing it while powered off, but upon booting up the RPi the DSP said there was a problem and that profiles could not persist in memory. Tried to flash the DSP 5 times and rebooted 3 times. The same problem persisted. The webinterface says that music is playing but there is no sound.

I checked ALSA, sound was in line with the webinterface volumeslider

I tried to unmute the feature that mutes unknown profiles, still no sound.

I have only 1 green LED showing at all times. Never two even after a clean bootup where no external devices has initiated playback.

Any thoughts as to what is going on?
If i put the mute jumper on, I was able to flash the DSP as the manual states, but without it doesn't work.

Kind regards

Edited by Alexander May 20, 2020 08:04

Comment actions Permalink
0

HiFiBerry team May 21, 2020 17:40

What DSP profile did you install?

Comment actions Permalink
0

Alexander May 24, 2020 18:59

I have tried
Beocreate Universal
DAC+ DSP Universel

after flashing the DSP with either the web interface says Unknown Program

Comment actions Permalink
0

brandon October 17, 2020 16:52

mute jumper came installed on mine as well. frustrating.

Comment actions Permalink
0
Alexander February 20, 2021 13:40
Hi HiFiBerry team,

I never got board to work, so for this vacation, I thought at have another go at it.

What I have done so far, starting from scratch and redoing as many steps as possible:
1. Downloaded the latest HiFiBerryOS for Raspberry Pi 3 (I have the 3B+) from your website.
2. Flashed the balenaEtcher onto a SanDisk 64GB MicroSD
3. With the beo speaker disassembled I attached the wires to the board as shown is this github guide on the CX100 and REMOVED THE MUTE JUMPER :)
4. With the Pi attached with LAN cable and power directly connected to the barrel plug on the beoboard I power it up and navigate my browser towards the DHCP assigned IP.
5. Following the setup process, all went well.
6. Without fiddling with any settings, I bring up my phone and try out Spotify Connect, but no sound comes out.
7. Attaching my NAS test folder with only two albums in it, to the music daemon for indexing. Indexing without a problem and the interface showing no errors playing the FLAC music, but no sound comes from the speaker.
I found the following comment from you HiFiBerry team:

Ok, login via SSH and run the following command

dsptoolkit get-checksum

aplay -l

amixer

play -n synth sine 100

And post the output of these commands.

Output:
```
# dsptoolkit get-checksum
40FB6C92F57ABB70177CE053C73F54DC

# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dac], device 0: HifiBerry DAC HiFi pcm5102a-hifi-0 [HifiBerry DAC HiFi pcm5102a-hifi-0]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

# amixer
Simple mixer control 'DSPVolume',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 255
  Front Left: 56 [22%]
  Front Right: 56 [22%]
Simple mixer control 'Softvol',0
  Capabilities: volume
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: 0 - 255
  Front Left: 255 [100%]
  Front Right: 255 [100%]
```
```
# play -n synth sine 100
play WARN alsa: can't encode 0-bit Unknown or not applicable

 File Size: 0
  Encoding: n/a
  Channels: 1 @ 32-bit
Samplerate: 48000Hz
Replaygain: off
  Duration: unknown

In:0.00% 00:00:32.94 [00:00:00.00] Out:1.58M [!=====|=====!] Hd:0.0 Clip:0
```
The sine test tone did not produce any sounds I could hear.
Comment actions Permalink

Alexander February 20, 2021 13:42

Forgot about this command:

# dsptoolkit get-xml | head -20
<?xml version="1.0" encoding="utf-8"?>
<ROM IC="ADAU1451" IC_Address="1" Address_byte_length="2">
        <beometa>
                <metadata type="sampleRate">48000</metadata>
                <metadata type="profileName">Beocreate Universal</metadata>
                <metadata type="profileVersion">10</metadata>
                <metadata type="programID">beocreate-universal</metadata>
                <metadata type="modelName" modelID="beocreate-4ca-mk1">Beocreate 4-Channel Amplifier</metadata>
                <metadata type="checksum">40FB6C92F57ABB70177CE053C73F54DC</metadata>
                <metadata type="balanceRegister" storable="yes">799</metadata>
                <metadata type="readIsDaisyChainSlaveRegister">98</metadata>
                <metadata type="canBecomeDaisyChainSlaveRegister">4833</metadata>
                <metadata type="muteRegister">4834</metadata>
                <metadata type="muteInvertRegister" storable="yes">4855</metadata>
                <metadata type="enableSPDIFTransmitterRegister">4835</metadata>
                <metadata type="sensitivitySPDIFRegister">86</metadata>
                <metadata type="enableSPDIFRegister" storable="yes">4840</metadata>
                <metadata type="readSPDIFOnRegister">93</metadata>
                <metadata type="tuningForkPitchRegister">29</metadata>
                <metadata type="tuningForkOnRegister">25</metadata>
Traceback (most recent call last):
  File "/bin/dsptoolkit", line 29, in <module>
    cmdline.main()
  File "/usr/lib/python3.9/site-packages/hifiberrydsp/dsptoolkit.py", line 1017, in main
  File "/usr/lib/python3.9/site-packages/hifiberrydsp/dsptoolkit.py", line 701, in cmd_get_xml
BrokenPipeError: [Errno 32] Broken pipe

0

HiFiBerry team February 20, 2021 17:16

Did you remove the "MUTE" jumper from the Beocreate? It is set on some boards.

Comment actions Permalink
0

Alexander February 21, 2021 14:26

Hi,

Yes, I wrote that as well in my comment. Attaching picture to make sure that the hardware configuration looks correct in your eyes.

Comment actions Permalink
0

HiFiBerry team February 22, 2021 09:45

This looks good so far. It might be a hardware problem. While defective Pi's are rare, we regularly see these. Do you have another Pi to test with?

Comment actions Permalink

Alexander February 28, 2021 14:29

So I switched out the RPi B+ for a different B+, with no change, just moving the SD card - still no sound.
I also reinstalled the SD card to make sure it was a clean installation. I noticed I got a different checksum and that one of the volumes in amixer - DSPVolume = 0, should that match Softvol?

# dsptoolkit get-checksum
30F8E2E60F9359A7862E69CCFE9A2FD6

# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dac], device 0: HifiBerry DAC HiFi pcm5102a-hifi-0 [HifiBerry DAC HiFi pcm5102a-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0

# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: sndrpihifiberry [snd_rpi_hifiberry_dac], device 0: HifiBerry DAC HiFi pcm5102a-hifi-0 [HifiBerry DAC HiFi pcm5102a-hifi-0]
Subdevices: 1/1
Subdevice #0: subdevice #0
# amixer
Simple mixer control 'DSPVolume',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 255
Front Left: 0 [0%]
Front Right: 0 [0%]
Simple mixer control 'Softvol',0
Capabilities: volume
Playback channels: Front Left - Front Right
Capture channels: Front Left - Front Right
Limits: 0 - 255
Front Left: 217 [85%]
Front Right: 217 [85%]

# play -n synth sine 100
play WARN alsa: can't encode 0-bit Unknown or not applicable

File Size: 0
Encoding: n/a
Channels: 1 @ 32-bit
Samplerate: 48000Hz
Replaygain: off
Duration: unknown

In:0.00% 00:00:08.19 [00:00:00.00] Out:393k [!=====|=====!] Hd:0.0 Clip:0
Aborted.

0

HiFiBerry team March 01, 2021 09:56

Looking at the checksum of your DSP profile, this seems to be an unknown DSP program. What did you install?

Comment actions Permalink
0

Alexander March 01, 2021 10:00

CX100 with a no errors in the webui animation of DSP flashing using the installation wizard. I tried to reflashing again yesterday, because it said Unknown DSP Program in the sound settings, but same result. It still says Unknown Program but the animation prompts me with no errors in flashing the DSP.

Comment actions Permalink
0

HiFiBerry team March 01, 2021 10:01

CX100 is NOT a DSP profile. You need to deploy the DSP profile first from the advanced settings.

Comment actions Permalink
0

Alexander March 01, 2021 10:12

I guess today, it is having a worse day. As mentioned, yesterday it stated Unknown Program or something like that... Today:

Comment actions Permalink
0

HiFiBerry team March 01, 2021 14:49

Did you try rebooting? We have seen this error in some older HBOS releases. Check if you're really running the latest version.

Comment actions Permalink
0

Alexander March 01, 2021 15:55

Tried rebooting 3 times. Also let the machine warm up a couple of hours and then rebooted. Here in the afternoon I booted it up again to check the version. There is still a problem accessing the sound processor and I am running version: 20210203

Comment actions Permalink
0

HiFiBerry team March 02, 2021 07:24

Ok, let's try from command line. What's the output of

dsptoolkit get-checksum

Comment actions Permalink
0
Alexander March 02, 2021 13:49
The board seems flaky... FYI I tried to flash the Beocreate Universal. The result is the screenshot below where it still says Unknown Program. The command before and after trying to flash the DSP:
```
# dsptoolkit get-checksum
30F8E2E60F9359A7862E69CCFE9A2FD6
# dsptoolkit get-checksum
30F8E2E60F9359A7862E69CCFE9A2FD6
```
Comment actions Permalink
0
daniel November 02, 2024 18:08
Did this every find a resolution?

I am also getting the same error for my CX100 (PI5). Unknown DSP program despite trying multiple reinstalls. I have the most relevant beocreate.

1. Mute jumper not connected.
2. I noticed that there are 2 holes where the 2 pins should be for the self-boot jumper (perhaps a change with the new beocreate - mine looks a little different than the product page)
3. Led light shown on board near USB-C port. No optical audio jack (likely because I disabled this with dsptoolkit write-mem 426 0 when troubleshooting).
4. I tried installing the CX100 presets (3-4x). I even tried using the CX50 preset. I always get (see below)
```
# dsptoolkit get-checksum
30F8E2E60F9359A7862E69CCFE9A2FD6
```
Comment actions Permalink

Please sign in to leave a comment.