Support for Botic Linux driver

ichiban · 2015-05-12 10:27 pm

Russ White said:
1:2

Dumb question, can jumper be switched while powered up?

Russ White · 2015-05-12 10:29 pm

Yes but it is safer to do it powered down. Only one jumper may be present in 1:1,1:2,1:4

ichiban · 2015-05-12 11:21 pm

Well, progress has been made, I get hiss out of the speaker test.

But, when trying to play a track via play ....

root@botic:~# play /data/remote/MUSIC_MY_CDS_DUBBED/Track01.wav
play FAIL formats: can't open output file `default': snd_pcm_open error: Device or resource busy
root@botic:~#

..also, when I open http://192.168.1.4:8080/#/0 ympd on a PC, I see the remote files, if I close ympd and then re open it the remote files don't show up.
..even when files show up and I select one to play the clock doesn't show that it's playing, stays at 0:00 ??

ichiban · 2015-05-13 1:42 am

What does priority mean in the audio_output section of mpd.conf

audio_output {
type "alsa"
name "Botic"
device "hw:0,0"
dsd_usb "no"
dsd_native "yes"
dsd_native_type "3"
priority "FIFO:32"
period_time "1"
mixer_type "software"

Still getting this error trying to play a file I copied from remote PC to /tmp/MUSIC1 on BBB

root@botic:/# play /tmp/MUSIC1/Track01.wav
play FAIL formats: can't open output file `default': snd_pcm_open error: Device or resource busy

Don't know how to discover why device is busy, even after checking other linux web sites for an answer. One suggestion was to use the command lsof, which doesn't appear to be on this version of debian.

twluke · 2015-05-13 2:09 am

ichiban said:
What does priority mean in the audio_output section of mpd.conf

MPD is a multi-thread binary and you can define the priority of a particular thread to be processed. The priority becomes higher with an increase of the number.

BTW your posts are always color-busy. Using more limited colors will make your posts more legible. Sorry!

miero · 2015-05-13 2:24 am

ichiban, if lsof is not installed then you can ... install it

)

ichiban · 2015-05-13 3:15 am

twluke said:
BTW your posts are always color-busy. Using more limited colors will make your posts more legible. Sorry!

Noted.

ichiban · 2015-05-13 3:25 am

miero said:
ichiban, if lsof is not installed then you can ... install it )

Thanks

Done
apt-get install lsof

ichiban · 2015-05-13 7:26 pm

miero said:
[/code]Also botic v4/v5 has different audio output name:

Code:

root@botic:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Botic [Botic], device 0: external dac-hifi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0

Miero,
not sure if you mean I should change name in 'ALSA output' in 'mpd.conf'
from "Botic" to "dac-hifi-0" ?

Still searching web for solution to this, see below, problem is in MPD or ALSA or SOX ??

root@botic:/# play /data/remote/MUSIC_MY_CDS_DUBBED/Track01.wav

/data/remote/MUSIC_MY_CDS_DUBBED/Track01.wav:

File Size: 52.8M Bit Rate: 1.41M
Encoding: Signed PCM
Channels: 2 @ 16-bit
Samplerate: 44100Hz
Replaygain: off
Duration: 00:04:59.07

In:0.12% 00:00:00.37 [00:04:58.70] Out:12.3k [ -==|== ] Clip:0 play WARN alsa: Input/output error
play FAIL sox: `default' Device or resource busy: Operation not permitted
Done.
root@botic:/#

lintweaker · 2015-05-13 7:37 pm

ichiban said:
Miero,
not sure if you mean I should change name in 'ALSA output' in 'mpd.conf'
from "Botic" to "dac-hifi-0" ?

No need to change the "name" parameter, it is just a way for you to distinguish between multiple audio outputs. The "device" parameter is the one that determines the actual audio device.

ichiban · 2015-05-13 8:01 pm

lintweaker said:
No need to change the "name" parameter, it is just a way for you to distinguish between multiple audio outputs. The "device" parameter is the one that determines the actual audio device.

OK

miero · 2015-05-13 8:49 pm

ichiban: what about lsof output?

ichiban · 2015-05-13 9:22 pm

miero said:
ichiban: what about lsof output?

Here........what am I looking for?

miero · 2015-05-13 10:28 pm

there is nothing interesting in the lsof... eh, what did you do to poor BBB?

please send me output of following commands:

aplay -l
aplay -v PATH_TO_YOUR_WAV_FILE
AUDIODEV=hw:0,0 play PATH_TO_YOUR_WAV_FILE

Also I do not like your earlier response:

ichiban said:
I measure varying DC volts about 160mV .... at these points.......

is this still true?

ichiban · 2015-05-13 11:25 pm

miero said:
there is nothing interesting in the lsof... eh, what did you do to poor BBB?

please send me output of following commands:

aplay -l
aplay -v PATH_TO_YOUR_WAV_FILE
AUDIODEV=hw:0,0 play PATH_TO_YOUR_WAV_FILE

Also I do not like your earlier response:

is this still true?

Last time I measured voltage I used one of the mounting holes for ground, this time I'm using one of the four pads surrounding the MClk pad, and measure 354mV.
Speaker check seems to be ok, I get hiss from L&R spkrs, when I control-C to exit test hiss stops.

miero · 2015-05-13 11:48 pm

Any special settings of botic in kernel params or startup script? Because aplay shall play natively in 44100Hz. and not resample to 88200Hz... ?

ichiban · 2015-05-14 1:03 am

miero said:
Any special settings of botic in kernel params or startup script? Because aplay shall play natively in 44100Hz. and not resample to 88200Hz... ?

Not sure where startup script is, here is /boot/uEnv.txt

root@botic:/# ls boot
SOC.sh config-4.0.0-botic5 uEnv.txt
System.map-3.18.7-botic4 dtbs uboot
System.map-4.0.0-botic5 initrd.img-3.18.7-botic4 vmlinuz-3.18.7-botic4
config-3.18.7-botic4 initrd.img-4.0.0-botic5 vmlinuz-4.0.0-botic5
root@botic:/# cat /boot/uEnv.txt
#Docs: Beagleboard:U-boot partitioning layout 2.0 - eLinux.org

uname_r=4.0.0-botic5
#dtb=
cmdline=quiet init=/lib/systemd/systemd

##Example
#cape_disable=capemgr.disable_partno=
#cape_enable=capemgr.enable_partno=

##enable BBB: eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

uuid=dd765012-0acc-4b80-a7b8-e100eb0bac8a
root@botic:/#

...and attached is /boot/config-4.0.0-botic5 hope that's what you need, I had to do mores and copy pastes into a file to get it all! I thought it would never ge to the end

.

twluke · 2015-05-14 4:27 am

ichiban said:
Here........what am I looking for?

Maybe you need to try this one below.

Code:

lsof | grep snd

ichiban · 2015-05-14 4:40 am

twluke said:
Maybe you need to try this one below.

Code:

lsof | grep snd

root@botic:~# lsof | grep snd
mpd 1061 mpd mem REG 179,2 289448 3780 /usr/lib/arm-linux-gnueabihf/libsndfile.so.1.0.25
mpd 1061 1187 mpd mem REG 179,2 289448 3780 /usr/lib/arm-linux-gnueabihf/libsndfile.so.1.0.25
mpd 1061 1188 mpd mem REG 179,2 289448 3780 /usr/lib/arm-linux-gnueabihf/libsndfile.so.1.0.25
mpd 1061 1189 mpd mem REG 179,2 289448 3780 /usr/lib/arm-linux-gnueabihf/libsndfile.so.1.0.25
mpd 1061 1190 mpd mem REG 179,2 289448 3780 /usr/lib/arm-linux-gnueabihf/libsndfile.so.1.0.25
root@botic:~#

twluke · 2015-05-14 4:54 am

ichiban said:
root@botic:~# lsof | grep snd
mpd 1061 mpd mem REG 179,2 289448 3780 /usr/lib/arm-linux-gnueabihf/libsndfile.so.1.0.25
mpd 1061 1187 mpd mem REG 179,2 289448 3780 /usr/lib/arm-linux-gnueabihf/libsndfile.so.1.0.25
mpd 1061 1188 mpd mem REG 179,2 289448 3780 /usr/lib/arm-linux-gnueabihf/libsndfile.so.1.0.25
mpd 1061 1189 mpd mem REG 179,2 289448 3780 /usr/lib/arm-linux-gnueabihf/libsndfile.so.1.0.25
mpd 1061 1190 mpd mem REG 179,2 289448 3780 /usr/lib/arm-linux-gnueabihf/libsndfile.so.1.0.25
root@botic:~#

So, it appears there is no busy device or resources other than mpd. How do you think, miero?

Support for Botic Linux driver

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Member

Attachments

Member

Member

Attachments

Member

Member

Attachments

Member

Member

Member