miero: Thanks for the quick response. I figured things would have changed a bit since more than a year ago when you posted the instructions ��
But how is hardware volume control implemented now?
I dont have a Bufalo dac but the dac I have is still with an es9018 chip. So I am trying to find a way to modify the i2c commands that are sent between bbb och es9018. It works fine in bash prompt but I know to little a bout alsa and linux to find out where I should do my changes.
But how is hardware volume control implemented now?
I dont have a Bufalo dac but the dac I have is still with an es9018 chip. So I am trying to find a way to modify the i2c commands that are sent between bbb och es9018. It works fine in bash prompt but I know to little a bout alsa and linux to find out where I should do my changes.
To avoid bricking the BBB when attaching a I2S DAC you either have create a power on/off sequence or isolate the BBB and DAC. I hpe I have understood this right, correct me if I am wrong.
What chips are used for isolation? Which signals need to be isolated? How much jitter do they introduce? How big is the audible effect? Can reclocking be avoided? I have no intention in buying a ready made device like from TP because they add too much to the total cost. I might as well get me an Auralic mini.
What chips are used for isolation? Which signals need to be isolated? How much jitter do they introduce? How big is the audible effect? Can reclocking be avoided? I have no intention in buying a ready made device like from TP because they add too much to the total cost. I might as well get me an Auralic mini.
Hello,
I want to use one simple external oscillator (CCHD-575), but I don't understand if the load cap is needed. In the datasheet it says that the tests is done with a 15pF load. Should I put that cap like in the draw?
Also, if this particular oscillator hasn't a disable pin, will it be a problem if at the pin 25 will always be a signal comming from the oscillator?
I want to use one simple external oscillator (CCHD-575), but I don't understand if the load cap is needed. In the datasheet it says that the tests is done with a 15pF load. Should I put that cap like in the draw?
Also, if this particular oscillator hasn't a disable pin, will it be a problem if at the pin 25 will always be a signal comming from the oscillator?
Attachments
But how is hardware volume control implemented now?
The TPA DACs have a pot-based controller built into the firmware. Lacking that, you will have to look into scripting your own. A command-line interface is not very user friendly, but the sound quality of attenuating on the 9018 is quite good. If you are sufficiently motivated I suggest NetIO, with a volume control script in Python. Code examples are available, and Python is fairly straightforward. A thread exists here: http://www.diyaudio.com/forums/twisted-pear/281776-control-bbb-based-audio-appliances.html
Cheers!
Hi ,
I am trying to install new lirc module on my fresh 4.8.13-botic7-rc3 debian jassie using
LIRC driver for BeagleBone Black
I have installed hearers: linux-headers-4.8.13-botic7-rc3_1_armhf.deb and paste make prepare and make install
but it seems like the module hasn't been created.
despite I added 'lirc_bbb' line to the /etc/modules
I see only:
I probably missed something. I will be grateful for any hint.
TIA,
bern
I am trying to install new lirc module on my fresh 4.8.13-botic7-rc3 debian jassie using
LIRC driver for BeagleBone Black
I have installed hearers: linux-headers-4.8.13-botic7-rc3_1_armhf.deb and paste make prepare and make install
Code:
root@beaglebone:/opt/lirc-bbb-master# make prepare
make -C /lib/modules/`uname -r`/build scripts
make[1]: Entering directory '/usr/src/linux-headers-4.8.13-botic7-rc3'
make[1]: Leaving directory '/usr/src/linux-headers-4.8.13-botic7-rc3'
root@beaglebone:/opt/lirc-bbb-master# make install
make -C /lib/modules/`uname -r`/build M=$PWD INSTALL_MOD_DIR=kernel/drivers/staging/media/lirc modules_install
make[1]: Entering directory '/usr/src/linux-headers-4.8.13-botic7-rc3'
DEPMOD 4.8.13-botic7-rc3
make[1]: Leaving directory '/usr/src/linux-headers-4.8.13-botic7-rc3'
depmod -A
despite I added 'lirc_bbb' line to the /etc/modules
I see only:
Code:
root@beaglebone:/opt/lirc-bbb-master# dmesg | grep lirc
[ 5.395057] lirc_dev: IR Remote Control driver registered, major 245
TIA,
bern
I was trying to add (manually) compiled version of lirc-bbb (4.5.0-botic7-rc1 (see #1638)) to my current 4.8.13-botic7-rc3. But it was not successful... I believe there is mismatch in the Linux versions:
Code:
root@beaglebone:~# dmesg | grep lirc
[ 5.187076] lirc_dev: IR Remote Control driver registered, major 245
[ 5.194216] lirc_bbb: disagrees about version of symbol module_layout
[ 11.301292] lirc_bbb: disagrees about version of symbol module_layout
Hi ,
I am trying to install new lirc module on my fresh 4.8.13-botic7-rc3 debian jassie using
LIRC driver for BeagleBone Black
I have installed hearers: linux-headers-4.8.13-botic7-rc3_1_armhf.deb and paste make prepare and make install
but it seems like the module hasn't been created.Code:root@beaglebone:/opt/lirc-bbb-master# make prepare make -C /lib/modules/`uname -r`/build scripts make[1]: Entering directory '/usr/src/linux-headers-4.8.13-botic7-rc3' make[1]: Leaving directory '/usr/src/linux-headers-4.8.13-botic7-rc3' root@beaglebone:/opt/lirc-bbb-master# make install make -C /lib/modules/`uname -r`/build M=$PWD INSTALL_MOD_DIR=kernel/drivers/staging/media/lirc modules_install make[1]: Entering directory '/usr/src/linux-headers-4.8.13-botic7-rc3' DEPMOD 4.8.13-botic7-rc3 make[1]: Leaving directory '/usr/src/linux-headers-4.8.13-botic7-rc3' depmod -A
despite I added 'lirc_bbb' line to the /etc/modules
I see only:
I probably missed something. I will be grateful for any hint.Code:root@beaglebone:/opt/lirc-bbb-master# dmesg | grep lirc [ 5.395057] lirc_dev: IR Remote Control driver registered, major 245
TIA,
bern
Hi, I tried to build this module only just out of curiosity and I suppose it went well without problems on my Botic7 system (running on a debian stretch).
Code:
root@arm:/usr/src/lirc-bbb-master# make prepare
make -C /lib/modules/`uname -r`/build scripts
make[1]: Entering directory '/usr/src/linux-headers-4.8.13-botic7-rc3'
HOSTCC scripts/basic/fixdep
HOSTCC scripts/basic/bin2c
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --silentoldconfig Kconfig
HOSTCC scripts/dtc/dtc.o
HOSTCC scripts/dtc/flattree.o
HOSTCC scripts/dtc/fstree.o
HOSTCC scripts/dtc/data.o
HOSTCC scripts/dtc/livetree.o
HOSTCC scripts/dtc/treesource.o
HOSTCC scripts/dtc/srcpos.o
HOSTCC scripts/dtc/checks.o
HOSTCC scripts/dtc/util.o
HOSTCC scripts/dtc/dtc-lexer.lex.o
HOSTCC scripts/dtc/dtc-parser.tab.o
HOSTLD scripts/dtc/dtc
HOSTCC scripts/genksyms/genksyms.o
HOSTCC scripts/genksyms/parse.tab.o
HOSTCC scripts/genksyms/lex.lex.o
HOSTLD scripts/genksyms/genksyms
CC scripts/mod/empty.o
HOSTCC scripts/mod/mk_elfconfig
MKELF scripts/mod/elfconfig.h
HOSTCC scripts/mod/modpost.o
CC scripts/mod/devicetable-offsets.s
GEN scripts/mod/devicetable-offsets.h
HOSTCC scripts/mod/file2alias.o
HOSTCC scripts/mod/sumversion.o
HOSTLD scripts/mod/modpost
HOSTCC scripts/kallsyms
HOSTCC scripts/conmakehash
HOSTCC scripts/recordmcount
HOSTCC scripts/sortextable
make[1]: Leaving directory '/usr/src/linux-headers-4.8.13-botic7-rc3'
root@arm:/usr/src/lirc-bbb-master# make install
make -C /lib/modules/`uname -r`/build M=$PWD INSTALL_MOD_DIR=kernel/drivers/staging/media/lirc modules_install
make[1]: Entering directory '/usr/src/linux-headers-4.8.13-botic7-rc3'
DEPMOD 4.8.13-botic7-rc3
make[1]: Leaving directory '/usr/src/linux-headers-4.8.13-botic7-rc3'
depmod -A
root@arm:/usr/src/lirc-bbb-master# vi /etc/modules
[SIZE=2]#to include lirc-bbb gpio_in_pin=66 in the file[/SIZE]
root@arm:/usr/src/lirc-bbb-master# reboot
root@arm:~# lsmod
Module Size Used by
-snip-
ir_lirc_codec 4860 0
lirc_dev 10665 1 ir_lirc_codec
root@arm:~# dmesg | grep lirc
[ 7.016007] lirc_dev: IR Remote Control driver registered, major 244
[ 7.021104] rc rc0: lirc_dev: driver ir-lirc-codec
root@arm:~# ls -ld /dev/lirc0
crw-rw---- 1 root video 244, 0 Feb 19 21:47 /dev/lirc0
Last edited:
Thanks twluke🙂Hope this will be of help.
Could you please add
Code:
lirc_bbb
'dmesg | grep lirc'?
There should be something like this:
Code:
root@botic:~# dmesg | grep lirc
[ 4.003371] lirc_dev: IR Remote Control driver registered, major 245
[ 4.013349] lirc_bbb lirc_bbb.0: lirc_dev: driver lirc_bbb registered at minor = 0
[ 4.970950] lirc_bbb: auto-detected active low receiver on GPIO pin 66
[ 4.970975] lirc_bbb: transmitter on GPIO pin 67
Thanks,
line into your /etc/modules file, restart and showCode:lirc_bbb
'dmesg | grep lirc'?
There should be something like this:
It was in my previous wheezy before the system's change to jessie.Code:root@botic:~# dmesg | grep lirc [ 4.003371] lirc_dev: IR Remote Control driver registered, major 245 [ 4.013349] lirc_bbb lirc_bbb.0: lirc_dev: driver lirc_bbb registered at minor = 0 [ 4.970950] lirc_bbb: auto-detected active low receiver on GPIO pin 66 [ 4.970975] lirc_bbb: transmitter on GPIO pin 67
Thanks,
My apologies. lirc_bbb was not found in dmesg after adding this module to /etc/modules and there was no module in my /lib/modules/4.8.13-botic7-rc3/kernel/drivers/staging/media/lirc. So, it appears that irc_bbb was not built despite there was no error messages during make prepare and make install.
Regards,
Thank you very much twluke.My apologies. lirc_bbb was not found in dmesg after adding this module to /etc/modules and there was no module in my /lib/modules/4.8.13-botic7-rc3/kernel/drivers/staging/media/lirc. So, it appears that irc_bbb was not built despite there was no error messages during make prepare and make install.
Regards,
Now I know that the issue with irc_bbb is not only in my system but the problem is broader.
Regards, bern
I don't know exactly how but I managed to install lirc_bbb module finally😉
Being in building lirc-bbb directory I've just entered:
and module 'lirc_bbb.ko' has been created in directory:
/lib/modules/4.8.13-botic7-rc3/kernel/drivers/staging/media/lirc
Being in building lirc-bbb directory I've just entered:
Code:
make prepare
make clean
make
make install
/lib/modules/4.8.13-botic7-rc3/kernel/drivers/staging/media/lirc
Hello Guys!
I noticed very strange behavior Volumio, the fact is: I have system based on Volumio-2.041-2016-12-11-bbb, which plays music from Minimserver based on Linux. Volumio plays music well, but if the folder with music in FLAC doesn't contain any picture, I mean scans of discs, photos of musicians etc, then Volumio disconnects connection with tablet i.e I can't control Volumio, although it plays music. I can redress a control when I delete this folder from playlist of Volumio. Now I must paste pictures in all folders with music in my 5TB Minimserver. I have to notice that my local net,where tablet, Minimserver , Volumio are, doesn't have the Internet connection. Any suggestions regarding this issue are appreciated. And one more question, could you please tell me password to this distributiv, Botic and Volumio don't work with root.
Regards,
Andrew
I noticed very strange behavior Volumio, the fact is: I have system based on Volumio-2.041-2016-12-11-bbb, which plays music from Minimserver based on Linux. Volumio plays music well, but if the folder with music in FLAC doesn't contain any picture, I mean scans of discs, photos of musicians etc, then Volumio disconnects connection with tablet i.e I can't control Volumio, although it plays music. I can redress a control when I delete this folder from playlist of Volumio. Now I must paste pictures in all folders with music in my 5TB Minimserver. I have to notice that my local net,where tablet, Minimserver , Volumio are, doesn't have the Internet connection. Any suggestions regarding this issue are appreciated. And one more question, could you please tell me password to this distributiv, Botic and Volumio don't work with root.
Regards,
Andrew
Loud pop when locking on DSD256
Hi everyone
I have another question.. I'm running a Botic7 image with B3SE dac, hermes/cronus isolation and reclocking.
I get a loud pop when locking onto a DSD256 track but not for PCM, PCM 384, DSD64.
Anyone know why?
Hi everyone
I have another question.. I'm running a Botic7 image with B3SE dac, hermes/cronus isolation and reclocking.
I get a loud pop when locking onto a DSD256 track but not for PCM, PCM 384, DSD64.
Anyone know why?
Hi everyone
I have another question.. I'm running a Botic7 image with B3SE dac, hermes/cronus isolation and reclocking.
I get a loud pop when locking onto a DSD256 track but not for PCM, PCM 384, DSD64.
Anyone know why?
Which type of Hermes board are you using? Hermes-BBB or Hermes-Amanero? If it is the latter, it may be difficult for you to get answers here, because this is the thread for BBB/Botic-I2S, not for BBB/Amanero-I2S.
BTW, I don't experience any pop noise in playing DSD256 or even DSD512 including the transition period to the next track with Hermes-BBB and MPD-2.0.
Regards,
Hi everyone
I have another question.. I'm running a Botic7 image with B3SE dac, hermes/cronus isolation and reclocking.
I get a loud pop when locking onto a DSD256 track but not for PCM, PCM 384, DSD64.
Anyone know why?
It has been my experience that a pop occurs when there is a change from PCM to DSD playback. I don't think there is a solution short of setting up some kind of auto muting.
I'm using a Hermes BBB.
As pixelpusher said, it also happens when transitioning from PCM to DSD.
But if transitioning from one DSD256 track to another, then there's no pop.
As pixelpusher said, it also happens when transitioning from PCM to DSD.
But if transitioning from one DSD256 track to another, then there's no pop.
Last edited:
volumio2/botic password
Hi Andrew,
My Volumio2/Botic/BeagleboneBlack is located at 192.168.0.14 on my home network. I connected with the following:
ssh volumio@192.168.0.14
Using the password "volumio" when prompted, I got the usual volumio welcome. I have not tried anything beyond poking around the directories.
- David
Hello Guys!
-----
And one more question, could you please tell me password to this distributiv, Botic and Volumio don't work with root.
Regards,
Andrew
Hi Andrew,
My Volumio2/Botic/BeagleboneBlack is located at 192.168.0.14 on my home network. I connected with the following:
ssh volumio@192.168.0.14
Using the password "volumio" when prompted, I got the usual volumio welcome. I have not tried anything beyond poking around the directories.
- David
Hi David!
Thank you very much for your answer.
Now I have an ability to look over and edit directories.
Regards,
Andrew
Thank you very much for your answer.
Now I have an ability to look over and edit directories.
Regards,
Andrew
Volumio question
Hi all,
I'd like to give Volumio a try using the latest (?) img
volumio-2.041-2016-12-11-bbb.img
I take it this is .img will totally replace the current v7
botic now on the BBB eMMC !?
Does the Volumio .img also contain the Logitech Squeeze Player ?
Cheers
Hi all,
I'd like to give Volumio a try using the latest (?) img
volumio-2.041-2016-12-11-bbb.img
I take it this is .img will totally replace the current v7
botic now on the BBB eMMC !?
Does the Volumio .img also contain the Logitech Squeeze Player ?
Cheers
Hi,
I am trying to install botic on new debian stretch.
First I've flashed newest image from:
https://rcn-ee.com/rootfs/bb.org/testing/2017-02-19/stretch-iot/?C=S;O=A
And after that I saw following sound devices:
then I installed newest botic 4.8.13-botic7-rc3 kernel, firmware and headers from *.deb files.
Unfortunately there are no sound devices recognised:
my /boot/uEnv.txt is as follows:
What should I do to install botic on stretch successfully?
TIA,
I am trying to install botic on new debian stretch.
First I've flashed newest image from:
https://rcn-ee.com/rootfs/bb.org/testing/2017-02-19/stretch-iot/?C=S;O=A
And after that I saw following sound devices:
Code:
root@beaglebone:~#aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
default:CARD=Black
TI BeagleBone Black,
Default Audio Device
sysdefault:CARD=Black
TI BeagleBone Black,
Default Audio Device
dmix:CARD=Black,DEV=0
TI BeagleBone Black,
Direct sample mixing device
dsnoop:CARD=Black,DEV=0
TI BeagleBone Black,
Direct sample snooping device
hw:CARD=Black,DEV=0
TI BeagleBone Black,
Direct hardware device without any conversions
plughw:CARD=Black,DEV=0
TI BeagleBone Black,
Hardware device with all software conversions
Unfortunately there are no sound devices recognised:
Code:
root@beaglebone:~# uname -a
Linux beaglebone 4.8.13-botic7-rc3 #1 PREEMPT Sat Dec 10 01:35:51 CET 2016 armv7l GNU/Linux
root@beaglebone:~# aplay -L
null
Discard all samples (playback) or generate zero samples (capture)
root@beaglebone:~#
Code:
uname_r=4.8.13-botic7-rc3
uuid=d6702ba9-9aac-4592-9770-fe899f5af80b
dtb=am335x-boneblack-botic.dtb
optargs=snd_soc_botic.ext_masterclk=3 snd_soc_botic.serconfig=MMMM snd_soc_botic.dai_format=16386 snd_soc_botic.blr_ratio=64
enable_uboot_overlays=1
cmdline=coherent_pool=1M net.ifnames=0 quiet cape_universal=enable
TIA,
- Home
- More Vendors...
- Twisted Pear
- Support for Botic Linux driver