• Disclaimer: This Vendor's Forum is a paid-for commercial area. Unlike the rest of diyAudio, the Vendor has complete control of what may or may not be posted in this forum. If you wish to discuss technical matters outside the bounds of what is permitted by the Vendor, please use the non-commercial areas of diyAudio to do so.

Support for Botic Linux driver

Jump to Latest
#1,843
Hi,
I've made some simple tests of botic Right Justyfied data output. I was just trying to play several files format. I used squeezelite player.
With player's sample format set as 24bit all my PCM files up to 16-24/192 were played fine: 44.1; 88.2; 176.4; 48; 96; 192k
Unfortunately I can't played DSD files (of course as DoP (DSD over PCM)).
This is strange because I can play DSD64-256 files using other squeezelite player (Raspberry Pi) connected to the same LMS configured the same as BBB.

With player's sample format set as 16 bit I hear only noises. (some kind of suppressed sound).
Regards,
 
#1,845
miero said:
Check that you are really playing PCM by inspecting hw_params file:
- cat /proc/asound/card0/pcm0p/sub0/hw_params

And I'll recheck if the 16bit RJ data works well.
Click to expand...
Thank you miero,
PCM files 16-24bits played with sample format=24 are ok.
-example 16/44.1:
Code: 
root@botic:~# cat /proc/asound/card0/pcm0p/sub0/hw_params
access: MMAP_INTERLEAVED
format: S24_LE
subformat: STD
channels: 4
rate: 44100 (44100/1)
period_size: 441
buffer_size: 1764
DSD64 (over PCM)= silence
Code: 
root@botic:~# cat /proc/asound/card0/pcm0p/sub0/hw_params
access: MMAP_INTERLEAVED
format: S24_LE
subformat: STD
channels: 4
rate: 176400 (176400/1)
period_size: 1764
buffer_size: 7056
DSD256 (over PCM)= silence
Code: 
root@botic:~# cat /proc/asound/card0/pcm0p/sub0/hw_params
no setup
PCM file 16/44.1 played with sample format=16; suppressed (metalic) sound
Code: 
root@botic:~# cat /proc/asound/card0/pcm0p/sub0/hw_params
access: MMAP_INTERLEAVED
format: S16_LE
subformat: STD
channels: 4
rate: 44100 (44100/1)
period_size: 441
buffer_size: 1764
 
#1,847
miero said:
What value do you have in /sys/module/snd_soc_botic/parameters/dai_format ?
And which botic version?
Click to expand...
miero:
Code: 
root@botic:~# grep . /sys/module/snd_soc_botic/parameters/*
/sys/module/snd_soc_botic/parameters/blr_ratio:64
/sys/module/snd_soc_botic/parameters/clk_44k1:22579200
/sys/module/snd_soc_botic/parameters/clk_48k:24576000
/sys/module/snd_soc_botic/parameters/dai_format:16386
/sys/module/snd_soc_botic/parameters/dsd_format_switch:1
/sys/module/snd_soc_botic/parameters/ext_masterclk:3
/sys/module/snd_soc_botic/parameters/pinconfig:default
/sys/module/snd_soc_botic/parameters/serconfig:MMMM
root@botic:~# uname -a
Linux botic 4.5.0-botic7-rc1 #1 PREEMPT Tue May 17 00:51:35 CEST 2016 armv7l GNU/Linux
root@botic:~#
 
#1,848
Anybody have newest instruction for install botic v7 in volumio1.5BBB?
I followed the google doc instruction, but after installation, volumio won't start up, the BBB stuck with two LED light up.
Then I use the newest boticize v7 scripts, the installation procedure goes well but still not boot up.
 
#1,850
nautibuoy said:
A new image is uploading at the moment and should be available in about an hour. Here's a link to it;

https://www.dropbox.com/s/vb0jh2fwcqudi6p/BBB-eMMC-28929.img.gz?dl=0

I hope it works for you.

BTW, you might care to try this tool, it'll unzip and image all in one and is very easy to use;

Etcher by resin.io

Ray
Click to expand...

Hi Ray.
Thanks for your sharing, I use this image and have a good hearing experience.
But when I tried to install MPD to play local music file. I found that the system you provided can not detect my USB stick, lsusb and dmesg command output the correct value, I can see the stick was plugged and information displayed. But fdisk -l can not detect the stick. So I can not mount it.
Any solutions? Pls help.
 
Last edited:
#1,853
esonhon said:
Hi Ray.
Thanks for your sharing, I use this image and have a good hearing experience.
But when I tried to install MPD to play local music file. I found that the system you provided can not detect my USB stick, lsusb and dmesg command output the correct value, I can see the stick was plugged and information displayed. But fdisk -l can not detect the stick. So I can not mount it.
Any solutions? Pls help.
Click to expand...

You don't really need Botic if you're going to use USB, I would just install the Beaglebone image on the Signalyst download page;

https://www.signalyst.eu/bins/naa/images/

Ray
 
#1,855
esonhon said:
Ray,
Thanks for your kindly reply. Do you mean I can use Cronus+Hermes cape without botic?
Click to expand...

Ah yes, sorry. I was in a hurry when I replied earlier and obviously didn't read your question properly.

To use Hermes/Cronus you will need to use Botic.

I have never used USB with my Beaglebone/Botic, either for output or for loading content/modules. but assume it still functions on a Botic BBB. I have not knowingly touched USB when loading up the NAA module for the image I made available but never thought to test it. I use the microSD card for installing the base build and after that I pull stuff down from the Internet using apt get or similar, have you tried that?

That said, Botic is already capable of playing music locally as described on miero's botic webpage?

Hope that helps a bit more than my last reply.

Ray
 
#1,856
#1,858
nautibuoy said:
Ah yes, sorry. I was in a hurry when I replied earlier and obviously didn't read your question properly.

To use Hermes/Cronus you will need to use Botic.

I have never used USB with my Beaglebone/Botic, either for output or for loading content/modules. but assume it still functions on a Botic BBB. I have not knowingly touched USB when loading up the NAA module for the image I made available but never thought to test it. I use the microSD card for installing the base build and after that I pull stuff down from the Internet using apt get or similar, have you tried that?

That said, Botic is already capable of playing music locally as described on miero's botic webpage?

Hope that helps a bit more than my last reply.

Ray
Click to expand...

Ray, Thanks.
I've tried and tried for one day. Now, I can confirm that the BOTIC V7 kernel not detect USB stick.
Yesterday, I reported that the system will not boot after boticize by v7, then I found that the nfs-common module kill the network, when delete nfs-common line from 02-install.sh, I got a bootable boticized debian system, but USB stick not work. When I change the kernel back, USB stick works.

@miero Could you pls take a look at the boticize v7 script, which procedure kill the USB stick function?
 
#1,860
miero said:
It could be possible, but no multichannel and no native-DSD playback. So I'm not interested.
Click to expand...
Hi, miero
Sorry for hijack your reply.
As mentioned in discussion with @nautibuoy, I found the botic v7 kernel that do not support USB stick: when USB stick plug in, fdisk -l do not see it, have no entry in /dev
Debug details for your reference:
before stick plugged in, lsusb returns:
Code: 
[EMAIL="machinekit@beaglebone:~$"]machinekit@beaglebone:~$[/EMAIL] lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[EMAIL="machinekit@beaglebone:~$"]machinekit@beaglebone:~$[/EMAIL]
when stick plugged in,
lsusb returns:
Code: 
[EMAIL="machinekit@beaglebone:~$"]machinekit@beaglebone:~$[/EMAIL] lsusb
Bus 001 Device 002: ID 8564:1000
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmesg says:

Code: 
[   51.401364] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[   51.546842] usb 1-1: New USB device found, idVendor=8564, idProduct=1000
[   51.546860] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   51.546870] usb 1-1: Product: Mass Storage Device
[   51.546879] usb 1-1: Manufacturer: JetFlash
[   51.546887] usb 1-1: SerialNumber: 06SGZJBGAVSVALJR
[   51.625898] SCSI subsystem initialized
[   51.643586] usb-storage 1-1:1.0: USB Mass Storage device detected
[   51.644269] scsi host0: usb-storage 1-1:1.0
[   51.646497] usbcore: registered new interface driver usb-storage
[   51.655580] usbcore: registered new interface driver uas
[   52.861522] scsi 0:0:0:0: Direct-Access     JetFlash Transcend 64GB   1100 PQ: 0 ANSI: 6
[EMAIL="machinekit@beaglebone:~$"]machinekit@beaglebone:~$[/EMAIL]

Maybe we missed some driver or things in the kernel?
 
You must log in or register to reply here.
Top Bottom