Hi Miero,
is the I2C connection a hardware problem? So, did I solder the jumpers/resistors on the Cronus wrong? http://www.diyaudio.com/forums/atta...452944-bbb-botic-cape-play-problem-cronus.jpg
is the I2C connection a hardware problem? So, did I solder the jumpers/resistors on the Cronus wrong? http://www.diyaudio.com/forums/atta...452944-bbb-botic-cape-play-problem-cronus.jpg
I do not see whole picture, but ISO_I2C connector is not connected to B3. So I'd say you did it wrong. And also IC must be removed from B3 then.
Whenever I try to use mpc, all I get is:
Code:
root@botic:~# mpc status
error: Timeout
root@botic:~# root😡
Hi Miero.
Here the link to the other pictures: http://www.diyaudio.com/forums/twisted-pear/274476-bbb-botic-cape-play-problem-2.html#post4491110
Which IC?
Many thanks for your help, I appreciate it very much!
Do I have to wire Hermes' 4-pin ISO-I2C to Buffalo's I2C? Is this not connected directly with the board connectors? Ah, I wish I could look it up in the documentation... 😉
Here the link to the other pictures: http://www.diyaudio.com/forums/twisted-pear/274476-bbb-botic-cape-play-problem-2.html#post4491110
Which IC?
Many thanks for your help, I appreciate it very much!
Do I have to wire Hermes' 4-pin ISO-I2C to Buffalo's I2C? Is this not connected directly with the board connectors? Ah, I wish I could look it up in the documentation... 😉
Murdoc: you need to have 4 wire cable from ISO_I2C socket on Hermes-BBB to the I2C socket on the B3. And you have to also remove IC from B3 (see the missing socket).
Only then I2C control of DAC from BBB will work.
But I suggest to wait for botic6. It will work better than botic5 with helper script.
See image of my setup: https://drive.google.com/file/d/0B72OZ4isAcAQVktYalJYVTBDRXc/view?usp=sharing
Only then I2C control of DAC from BBB will work.
But I suggest to wait for botic6. It will work better than botic5 with helper script.
See image of my setup: https://drive.google.com/file/d/0B72OZ4isAcAQVktYalJYVTBDRXc/view?usp=sharing
I get:
Code:
speaker-test 1.0.27.2
Playback device is hw:0,0
Stream parameters are 48000Hz, S16_LE, 2 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 128 to 32768
Period size range from 8 to 2048
Using max buffer size 32768
Periods = 4
was set period_size = 2048
was set buffer_size = 32768
0 - Front Left
1 - Front Right
Time per period = 5.296016
0 - Front Left
1 - Front Rightand it continues. The DACs lock but I hear nothing from the headphones (which I checked in case there was a fault).
Oddly, I'm now seeing:
Code:
ERROR: Failed to open audio output
Last edited:
So all of your BBB, Hermes-BBB, Cronus and input part of DAC are alive and probably well! 🙂
Are you using some form I2C control of DAC or does it have standard firmware/configuration?
Are you using some form I2C control of DAC or does it have standard firmware/configuration?
Well that's some relief anyway 🙂
I have reconnected Volumite (which used to work but now it doesn't).
What about botic driver configuration?
Are there default parameters, or did you have something non-standard? E.g. what is printed by these commands?
aplay -l
cat /sys/module/snd_soc_botic/parameters/serconfig
Are there default parameters, or did you have something non-standard? E.g. what is printed by these commands?
aplay -l
cat /sys/module/snd_soc_botic/parameters/serconfig
Code:
root@botic:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Botic [Botic], device 0: external dac-hifi-0 []
Subdevices: 0/1
Subdevice #0: subdevice #0
Code:
root@botic:~# cat /sys/module/snd_soc_botic/parameters/serconfig
MMMMERROR: Failed to open audio output
Probably some other player mpd/squeezelite/... has opened device.
I'd try to carefully measure DC voltage on the DCK, D1, D2 pins on the Cronus output. None of them should be 0V during playback of speaker-test.
Probably some other player mpd/squeezelite/... has opened device.
I'd try to carefully measure DC voltage on the DCK, D1, D2 pins on the Cronus output. None of them should be 0V during playback of speaker-test.
That is strange, during playback of speaker-test there should be ~1.6V between GND and DCK/D1 and ~0.4V between GND and D2.
Try to stop mpd first by executing:
systemctl stop mpd
These are clock signals. The values you see with a multi-meter will vary depending on the meter you use.
Last edited:
They're hooked up to IVY III balanced outputs, which has always worked nicely.
Regards, Duffy. I am not an expert but I am learning slowly by trial and error.
Show us the result of 'ps -A'
This is every process your software is running. If I try to run speaker-test while squeezelite is also running, I get 'device or resource busy'. ...though MPD is usually not a problem when it runs unneeded. ...still, perhaps there will be a clue, like a duplication, etc.
Show us the result of 'ps -A'
This is every process your software is running. If I try to run speaker-test while squeezelite is also running, I get 'device or resource busy'. ...though MPD is usually not a problem when it runs unneeded. ...still, perhaps there will be a clue, like a duplication, etc.