0

CX100 SCREAMING on power up

Viktor Perselli

August 03, 2019 11:14

None

Follow

Hi

I've been using my beocreate board inside a CX100. It had a really scary laud pop at start, so I tended not to use it at all for a while. But this summer I saw that there was a new profile that should fix this, so I flashed a new sd-card with the new img. 

Now the speaker is instead screaming a laud beep until I pull the plug. Sounds like maximum output and I'm afraid the speaker will damage. At least my ears hurt! So while trying to reinstalling the image and trying to reapply the soundprofile for CX100 I've been holding my ears and been ready to pull the plug. 

No sound comes out with the mute jumper installed, but then I don't get any sound when streaming from Roon via shareport either. I haven't tried the optical input, but then I'm not interested in using it with the speaker closed up. 

I noticed today that when first changing to the CX50 profile and then back to CX100, there was no more screaming without the mute jumper. Hurray! But, also no sound at all when playing over shareport... So I checked the recreate/setup page and tried to change the master volume there, but I got a message that the sound profile wasn't recognized. So I reinstalled the CX100 profile, and was able to play some music. Though after a reboot it started screaming again. 

I checked the checksum from dsptoolkit and it is 18454E5C3033E17F5A11937BF90ED7E4. Is that correct? I tought that it was for the sound profile, but in this thread they are talking about the CX50 with the same checksum: https://support.hifiberry.com/hc/en-us/community/posts/360005436518-Beocreate-Loud-pops-on-start-up

I'm about to give up. Do you have any suggestions?

Oh, besides, if important, I've connected the beocreate board to a raspberry pi 3b+.

 

Best regards

Viktor

• Facebook
• Twitter
• LinkedIn

31 comments

• 0
  
  HiFiBerry team August 05, 2019 06:30

  Hi,

  please install the profile again and then run the command

  dsptoolkit check-eeprom

  and post the output.

  Best regards,
  Daniel

• 0
  
  Viktor Perselli August 05, 2019 11:56

  Hi

  Double checked the cableing since that would be rather embarrasing if that would be the problem, eventhough it's the same as before when it worked better. Noticed that in the CX100 guide that the cables in the photoes on page 15 and 20 are not the same as in the diagram of the amplifier outputs on page 16. I've followed page 16.

  Reflashed the sd with the same downloaded img (beocreate-181228.img)

  Added wireless network
  applied the soundprofile CX100

  logged in via ssh

  got messege about not being able to connect to wireless due to country settings (I belive)

  dsptoolkit check-eeprom
  EEPROM content matches running profile, checksum 18454E5C3033E17F5A11937BF90ED7E4

  used rasp-config to set country

  did a shutdown
  removed mute

  booted with only a short pop, same pitch as before, but not quite as loud.

  installed shair-port via setup webbpage

  still without the mute-jumper it rebooted without loud noice. I had hearing protection on, and didn't hear if there was a short pop.

  Music through Roon via airplay works.

  Changing sound adjustments from stereo to mono

  Still music from Roon.

  Sudo reboot with ssh - only got a little "plupp" at bootup.

  Sudo shutdown and removing power cable.
  Screams again at bootup! Pulled the powercord.

  Booting with mutejumper.
  dsptoolkit check-eeprom still outputs:
  EEPROM content matches running profile, checksum 18454E5C3033E17F5A11937BF90ED7E4

  changed sound adjustment from mono to stereo.
  Sudo shutdown - pulling the power cord

  Booting without mute-jumper - still loud screaming.

   

• 0
  
  HiFiBerry team August 05, 2019 15:10

  Ok, let's check the version of dsptoolkit

  What's the output of

  dsptoolkit version

  Best regards,
  Daniel

• 0
  
  Viktor Perselli August 05, 2019 18:21

  Thank you for helping me out.

  The dsptoolkit version is 0.13

   

  Best regards

  Viktor

• 0
  
  HiFiBerry team August 06, 2019 05:37

  Ok, let's try updating it to the latest version. Try the following:

  sudo pip3 install --upgrade hifiberrydsp

  Then reboot and apply the profile again.

  Best regards,
  Daniel

• 0
  
  Viktor Perselli August 06, 2019 06:10

  Now the dsptoolkit version is version 0.17
  Rebooted and the dsptoolkit check-eeprom outputs:
  EEPROM content matches running profile, checksum 18454E5C3033E17F5A11937BF90ED7E4
  made a shutdown, removed power cable, removed mute jumper, still screaming

   

  Best regards
  Viktor

• 0
  
  HiFiBerry team August 06, 2019 06:11

  You have to install the DSP profile again

  Best regards,
  Daniel

• 0
  
  Viktor Perselli August 06, 2019 06:42

  yes, did so as well, after the reboot and before I made the shutdown

  /Viktor

• 0
  
  HiFiBerry team August 06, 2019 07:24

  You installed the CX100 profile? Do you have anything connected to the TOSLink input?

  Best regards,
  Daniel

• 0
  
  Viktor Perselli August 06, 2019 07:31

  Yes, installed the CX100 profile again. Have nothing connected to the TOSLink input. The light there is on. 

  Now changed to mono in adjustments again, rebooted, logged in and shutdown. Pulled power cable, removed jumper. Replugged and instantly loud tone screaming. 

  Should I test with a chromecast audio in the TOSLink input?

  best regards

  Viktor

• 0
  
  Viktor Perselli August 06, 2019 08:00

  Out of curiosity I've now tried with the tweeter plugged in as in the picture on page 20 in the guide, that is in the other tweeter output. The loud sound was gone. So, I shutdown, plugged and unplugged the power once again, and it was back. So, plugged the tweeter back to the first output and the loud sound was gone again. Shutdown, pulled the power cord and back in, and the loud sound was back. Also tried without the tweeter connected, still that loud sound. 

  So, it's not about the tweeter output, although I find it a rather high pitch. And it's not anymore everytime I put the power back in. 

  best regards
  Viktor

• 0
  
  Viktor Perselli August 06, 2019 08:16

  So, tried with a CCaudio plugged in (not playing anything). There was a long loud sound so that I pulled the power out. Unplugged the CCaudio and put the power cable back in, same loud result and I again pulled the power. 

  best regards
  Viktor

• 0
  
  dr.mike August 06, 2019 17:35

  Sharing my experience:

  I had exactly the same issue at the beginning at initial setup - the board was screaming at me directly after plugging in power. The vendor exchanged it for me, defective hardware.

  With the replacement board almost all is fine and the CX100s sound fantastic, apart from a smaller glitch with pops switching streams, currently the last post here: https://support.hifiberry.com/hc/en-us/community/posts/360005436518-Beocreate-Loud-pops-on-start-up?page=2#comments

   

• 0
  
  HiFiBerry team August 12, 2019 09:42

  @Viktor: Sorry I missed your replay. I don't think this is a hardware issue.
  
  Please try the following:
  dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/beocreate-default.xml
  dsptoolkit check-eeprom

  
  This is NOT the correct profile, but it will help us debugging this.

   

  Best regards,
  Daniel

• 0
  
  Gerard Levels August 13, 2019 11:43

  Hello,

  I have amongst others the same issue.

  I am following this forum for quite some time now to hopefully find an appropriate solution. Please find below some findings from my side which might help to resolve the issue.

  I have used various B&O XML profiles i.e. Basic, CX50 and S35 all having the same issue.

  Multiple installations of the SD card did not resolve the issue as well (Full B&O image).

  I even changed the S35 profile i.e. deleted the input selection section and passed the SPDif input directly to the filter section, however without success so far.

  Hooking up a CD player (SPDIF) give NO loud beep (1kHz) ONLY when already set to playback before powering up the Beocreate board  i.e. the light guide is showing the "red light"!

  I have bought an AD converter from Oehlbach which apparently always has its output active .... resulting in NO bleep at all!

  I will closely follow this post to hopefully have a solution for me as well.

   

  Best regards,

  Gerard

  P.s. One other thing that I have noticed. When there is this loud beep at power up and I have the SPDIF cable of the AD converter close to the SPDIF input (not plugged in!) the bleep stops immediately.

• 0
  
  HiFiBerry team August 13, 2019 13:38

  Hi Gerard,

  thanks for this information. This is something I didn't think about. The DSP sometimes behaves a bit strange with noting connected to the SPDIF input. 
  What profile are you using at the moment? Can you try the following:

  Have a look at the XML file for the line

  <metadata type="enableSPDIFRegister">xxx</metadata>

  Then run the following command:
  

  dsptoolkit write-mem XXX 0

  where XXX is the number you find in the DSP profile.

  Make sure you use the correct XML file, otherwise it might get much worse. Writing to an incorrect memory cell can result in all kinds of crazy behaviour - depending on the DSP profile.
  
  Then remove the SPDIF cable. Does this stop the beeping sound?

  Best regards,
  Daniel

• 0
  
  HiFiBerry team August 14, 2019 06:25

  @Victor: Can you try the same?

• 0
  
  Gerard Levels August 14, 2019 07:02

  Hello Daniel,

  Thanks for the feedback.

  I am using a Modiefied S35 profile (uploaded via Sigma Studio) and are able to switch between SPDIF and Pi as well as switch on/off Mute via dsptoolkit and the appropriate register. 

  I have not tried your suggestion yet, but I will. Please give me some time as I would like to run various scenarios to have a full picture on when it is happening and when not.

  And am very interested in the results from Victor.

  Regards,

  Sjra

   

• 0
  
  Gerard Levels August 14, 2019 08:28

  Hello Daniel,

   

  Please find attached a screenshot of the modified (simplified) S35 profile for testing purposes.

   

  Regards,

  Gerard

• 0
  
  HiFiBerry team August 14, 2019 11:26

  Looks good.

• 0
  
  Gerard Levels August 15, 2019 13:52

  Hello Daniel,

  Finally I have gone through some test scenarios with the profile as shown above (SPDIF selected and Muted). Results are shown in the second  table.

  I have done the same with another profile where per default PI was selected and NOT Muted. Results are shown in the first table.

  Please find below the test scenarios and results:

  

  I have noticed that when SPDIF is selected per default the appropriate address does have the value 2! Although I expected it to be 1. Switching between SPDIF/PI however works fine with thew values 1 and 0. The appropriate PARAMS file does provide in the value 2 as well.

  Beeps occur at power-on as long as there is nothing connected or a toslink connected being not active (i.e. no red light seen).

  As soon as toslink is active (red light seen) there is no beep either stops ar not even there at power-on. 

  Both a beep at full volume level is heard or an increasing level from low to full in time. I have not found any indication when the full beep is there or the increasing one.

  When PI is selected per default no beep is noticed and any toggling of SPDIF and/or Mute doesn't chage this.

   

  Hope this helps a bit in trying to find for a solution.

  Regards,

  Gerard

• 0
  
  Gerard Levels August 15, 2019 13:57

  Hello Daniel,

   

  I have done a small test with a straight forward profile i.e. no input selection or mute at all:

  

  At power-on a beep is heard however stops as soon as the Raspberry-Pi has finished booting i.e. as soon as username/password is requested for!  Also here as soon as a Toslink is connected being active (red light seen) the beep stops or is not even there in case of power-on. Tried this several times.

   

  Regards,

  Gerard

• 0
  
  HiFiBerry team August 15, 2019 13:57

  Hi Gerard,
  
  Thank you for this extensive tests. That's what I expected. On the software side there is not really something we can do here. The DSP's SPDIF input sometimes behaves a bit strange if nothing is connected. Therefore I recommend to switch it off on startup and only activate it when you want to use it.

  Best regards,
  Daniel

• 0
  
  Gerard Levels August 15, 2019 14:19

  Hello Daniel,

   

  Thanks for the fast response. 

  As the problem als occurs by the profiles made available by B&O I wonder how you and/or B&O are going to tackle the problem!

  I could think of forcing the input select to PI at power-on (or even an extra input with input 'null') and as soon as the Becreate is up and running let the input select part do the job as currently done.

  At least some work for me anyway to figure out a solution that fits my needs.

   

  Regards,

  Gerard

   

• 0
  
  Viktor Perselli August 18, 2019 09:05

  Hello again

  it's been a long and busy week, but now I've had a bit time for myself again.

  Removed mute jumper and plugged in the power cable.
  Loud beep for about 5 seconds, I think, then it stopped.
  Plugged in cromecast in optical and played some music. Very loud. Can adjust volume from the app streaming (Plex), but the Master volume at bang-olufsen.com/recreate/setup/ has no effect.

  I'm wondering about the jumper 5, for the output voltage. I have it connected now, because it doesn't seem to do any difference if it's connected or not. Is that ok?

  Some thoughts: I've previously mixed up the optical in and out. Silly. Well, The plug has until now been connected to the optical in, but playing music from the chromecast made me notice my mistake. Sigh. Last time I just connected it without playing anything, which is whyI didn't notice that I connected it to the output.

  Logged in with putty and did:
  pi@beovox:~ $ sudo dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/beocreate-default.xml
  DSP profile https://raw.githubusercontent.com/hifiberry/hifiberry-dsp/master/sample_files/xml/beocreate-default.xml installed
  pi@beovox:~ $ dsptoolkit check-eeprom
  EEPROM content matches running profile, checksum 16EA9EE2C6A296BDBF4C2C3A55246729

  sudo poweroff

  Pulled power cable. Put it back in (no mute jumper, nothing in optical in, not even plug). No screaming. Just two tiny klicks after 15-20 seconds.
  Trying to play music from Roon, but there is no sound. In Roon I've limited the volume to 35. When trying to adjust the master volume at https://www.bang-olufsen.com/recreate/setup/, there is a message saying "Adjustments disabled. Sound adjustments are disabled, because an unknown sound profile was installed. To enable them again, you can reinstall one of the preset sound profiles from Sound Profiles screen."

  With putty I do a sudo poweroff
  pull the power cable. Put it back in as before with no mute jumper nor optical connected. No screaming, but again two tiny clicks. The https://www.bang-olufsen.com/recreate/setup/ still says "Adjustments disabled" and no music to hear.

  From https://www.bang-olufsen.com/recreate/setup/ I again installed the Beovox CX 100 profile.
  dsptoolkit check-eeprom
  EEPROM content matches running profile, checksum 18454E5C3033E17F5A11937BF90ED7E4

  With putty a sudo poweroff. Pulled the power cable, put it back (still no mute jumper etc). LOUD! But I waited, maybe around 30 seconds then it stopped, and again two tiny clicks.
  Music from Roon now works again.

  power off again with putty. Pull the power and connect the chromecast to the optical IN (this time). Start playing music on low level and then connect the power to the beocreate. No loud beep, but instead music! Now the master volume has effect too.
  Putty power off. Music still playing, but raspberry is off.

  Pulled the power cord. Disconnected the optical. Connected the power cord again. LOUD beep again, about 30 seconds, then it's almost gone. A tiny beep started after a few seconds and increased in strenght. It dissapears as soon as I press play in Roon, but comes back when I press pause!

  I don't understand how to have a look at the xml file to do the mem-write thing. I don't know where to download/open it from the bang-olufsen.com/recreate/setup page, or fromsomewhere else?

  It seems to me like the culprit is the optical in. Is it possible to disable it? I will anyway not be able to use it when the speaker is closed up.

   

• 0
  
  Jan Chroback August 21, 2019 12:33

  Same problem here on the CX50. I assured I connected everything right. To be quiet honest I am scared of starting this without the mute jumper, since this beep hurts.

• 0
  
  HiFiBerry team August 21, 2019 12:36

  @Victor @Jan:
  
  Try the following:
  
  dsptoolkit write-mem 469 0

  Does this work?

• 0
  
  Jan Chroback August 21, 2019 13:49

  Will try this, when I get my hearing protection, because this is really heavy on my ears.

   

• 0
  
  Gerard Levels August 22, 2019 14:26

  Hello Daniel,

  As I was not that satisfied with your answer I have been looking in more detail in the S35 profile.

  The automatic input detection circuit is ofcourse a nice feature. However has also some backdraws. On of them switching between 2 active inputs as soon as one input has a pause between 2 songs!

  The other one having a SPDIF input that can give a spurious signal at power-on this disabling mute and pass through the SPDIF input to the output.

  One of the solutions would be to disable the SPDIF input i.e. advice people when they setup a Beocreate from the webside NOT to select for the Optical Input, when they are not going to use it (anyway problematic when the source has no volume control).

  One other would be, and that is the one I have tried to include a power-on delay in the profile that ensures that PI is selected and Mute enabled for a certain time at power-on (I believe in my example delays for some 40s).

  I have noticed that there is still a beep with increasing level when the power-on delay is not long enough (at least the time it takes PI to boot!).

  Please find attached the link to the profile: https://drive.google.com/open?id=1_RPrxOcfLP06aLcezlU44DNaY6dO5dMS

  For your information I have created a second version with a simplified (using simple logic) input detection circuit.

  I have tested both versions and work fine (at least for me). Maybe these can help to think of a Beocreate solution in general.

  This is the last post from my side on this topic as I have come up with a workaround.

   

  Regards,

  Gerard

   

  P.s. Next step from my side is to try a hw solution i.e. use the free MP6 GPIO of the DSP for switching between PI and SPDIF.

   

• 0
  
  HiFiBerry team August 23, 2019 07:05

  Hi Gerards,
  
  wow, thank you for this great work. We'll look into this. As the B&O developer is a bit busy with the new Beocreate software, it might take a bit. 

  Best regards,
  Daniel