• 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
#2,023
miero said:
Hehe, you are right. I should test it before providing a "solution". More modules are needed, but those are not selected. I'll provide a new kernel soon. Thanks for the report!
Click to expand...

y7Hm9.jpg
 
#2,024
miero said:
Hehe, you are right. I should test it before providing a "solution". More modules are needed, but those are not selected. I'll provide a new kernel soon. Thanks for the report!
Click to expand...
Hi miero,

If you are going to build a new kernel, please include the solution to recognize my Amanero USB board. With Botic5 kernel, I could use this board as a USB audio device connected to BBB for MPD output to Buffalo Dac as shown below:[
Code: 
Dec  9 22:53:11 botic systemd[1]: Started Music Player Daemon.
Dec  9 22:53:11 botic mpd[1409]: server_socket: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)
Dec  9 22:53:12 botic ympd[1103]: MPD connected.
Dec  9 22:53:24 botic kernel: [  138.022807] musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_bcon (99, VALID), retry #1, port1 00000104
Dec  9 22:53:24 botic kernel: [  138.433750] usb 1-1: new high-speed USB device number 3 using musb-hdrc
Dec  9 22:53:24 botic kernel: [  138.574280] usb 1-1: New USB device found, idVendor=16d0, idProduct=071a
Dec  9 22:53:24 botic kernel: [  138.574300] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec  9 22:53:24 botic kernel: [  138.574310] usb 1-1: Product: Combo384 Amanero
Dec  9 22:53:24 botic kernel: [  138.574319] usb 1-1: Manufacturer: Amanero Technologies
Dec  9 22:53:24 botic kernel: [  138.574328] usb 1-1: SerialNumber: 413-001
Dec  9 22:53:24 botic kernel: [  138.644962] usbcore: registered new interface driver snd-usb-audio
However, with Botic7, the system always fails to recognize the same board as an audio device as shown below:
Code: 
from /var/log/syslog:
Dec  9 23:02:50 botic ympd[1136]: MPD connection: Connection refused
Dec  9 23:02:50 botic systemd[1]: Starting Music Player Daemon...
Dec  9 23:02:50 botic systemd[1]: Started Music Player Daemon.
Dec  9 23:02:50 botic mpd[1382]: server_socket: bind to '0.0.0.0:6600' failed: Address already in use (continuing anyway, because binding to '[::]:6600' succeeded)
Dec  9 23:02:51 botic ympd[1136]: MPD connection failed.

from /var/log/mpd/mpd.log at the same time:
Dec 09 23:02 : alsa_output: Failed to open "Amanero" [alsa]: Failed to open ALSA device "hw:1,0": No such file or directory
Dec 09 23:02 : output: Failed to open audio output
ALSA lib pcm_hw.c:1667:(_snd_pcm_hw_open) Invalid value for card
BTW, Amanero appears to be recognized as a USB device as well as an alsa device when based on lsusb and aplay -l:
Code: 
root@botic:~# lsusb
Bus 001 Device 002: ID 16d0:071a GrauTec  (--> Amanero)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root 
root@botic:~# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Botic [Botic], device 0: external botic-hifi-0 []
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 1: Amanero [Combo384 Amanero], device 0: USB Audio [USB Audio]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
hub
I'm asking the solution of this issue because the developer is now trying to provide new firmware capable of native DSD support up to DSD512 on linux. I confirmed their latest firmware is able to provide native DSD256 via MPD on Botic5 system with Hermes/Cronus boards to B3SE.

TIA
 
Last edited:
#2,026
miero said:
twluke: no idea why it happens, maybe it is not compatible with the USB audio implementation in the kernel 4.8.11

Can you provide last lines of dmesg command after plugging the Amanero into BBB? Maybe an error would be printed there.
Click to expand...

This may not be of much help:
Code: 
root@botic:~# tail -f /var/log/dmesg
[    5.872296] net eth0: phy 4a101000.mdio:01 not found on slave 1
[    5.909898] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    8.861419] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[    8.861479] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   13.847855] FS-Cache: Loaded
[   13.900860] FS-Cache: Netfs 'cifs' registered for caching
[   13.901004] Key type cifs.spnego registered
[   13.901060] Key type cifs.idmap registered
[   15.379179] random: nonblocking pool is initialized
[   19.748311] Installing knfsd (copyright (C) 1996 [EMAIL="okir@monad.swb.de"]okir@monad.swb.de[/EMAIL]).
However, tail -f /var/log/syslog at the same time after plugging Amanero shows:
Code: 
root@botic:~# tail -f /var/log/syslog
Dec 10 00:38:41 botic kernel: [   51.761728] musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_bcon (89, <AValid), retry #1, port1 00000104
Dec 10 00:38:42 botic kernel: [   52.170752] usb 1-1: new high-speed USB device number 2 using musb-hdrc
Dec 10 00:38:42 botic kernel: [   52.401703] usb 1-1: New USB device found, idVendor=16d0, idProduct=071a
Dec 10 00:38:42 botic kernel: [   52.401728] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 10 00:38:42 botic kernel: [   52.401737] usb 1-1: Product: Combo384 Amanero
Dec 10 00:38:42 botic kernel: [   52.401746] usb 1-1: Manufacturer: Amanero Technologies
Dec 10 00:38:42 botic kernel: [   52.401755] usb 1-1: SerialNumber: 413-001
Dec 10 00:38:42 botic kernel: [   52.497130] Unable to handle kernel NULL pointer dereference at virtual address 0000000c
Dec 10 00:38:42 botic kernel: [   52.505401] pgd = dcbd0000
Dec 10 00:38:42 botic kernel: [   52.508126] [0000000c] *pgd=9dc53831, *pte=00000000, *ppte=00000000
Dec 10 00:38:42 botic kernel: [   52.516487] Internal error: Oops: 17 [#1] PREEMPT THUMB2
Dec 10 00:38:42 botic kernel: [   52.521835] Modules linked in: snd_usb_audio(+) snd_hwdep snd_usbmidi_lib snd_rawmidi snd_seq_device usb_f_acm u_serial usb_f_rndis g_multi usb_f_mass_storage u_ether libcomposite nfsd arc4 md4 nls_utf8 cifs fscache binfmt_misc ti_am335x_adc omap_aes crypto_engine omap_sham omap_rng rng_core spi_omap2_mcspi snd_soc_davinci_mcasp snd_soc_edma(O) snd_soc_botic_codec snd_soc_botic ti_am335x_tscadc snd_soc_core snd_pcm_dmaengine snd_pcm snd_timer snd soundcore
Dec 10 00:38:42 botic kernel: [   52.562734] CPU: 0 PID: 1353 Comm: systemd-udevd Tainted: G           O    4.5.0-botic7-rc1 #1
Dec 10 00:38:42 botic kernel: [   52.571392] Hardware name: Generic AM33XX (Flattened Device Tree)
Dec 10 00:38:42 botic kernel: [   52.577519] task: ddefee40 ti: dddf6000 task.ti: dddf6000
Dec 10 00:38:42 botic kernel: [   52.583159] PC is at usb_audio_probe+0x17d/0x6dc [snd_usb_audio]
Dec 10 00:38:42 botic kernel: [   52.589210] LR is at proc_register+0x6d/0xf4
Dec 10 00:38:42 botic kernel: [   52.593503] pc : [<bfaf467e>]    lr : [<c0246c65>]    psr: 60000033
Dec 10 00:38:42 botic kernel: [   52.593503] sp : dddf7c70  ip : 00000000  fp : 00000001
Dec 10 00:38:42 botic kernel: [   52.605046] r10: bfb0b600  r9 : ddc3a400  r8 : dcaa3319
Dec 10 00:38:42 botic kernel: [   52.610298] r7 : 00000000  r6 : dde64a24  r5 : 00000000  r4 : dde64a00
Dec 10 00:38:42 botic kernel: [   52.616859] r3 : 9134fe4e  r2 : 9134fe4e  r1 : dca9da2c  r0 : 00000000
Dec 10 00:38:42 botic kernel: [   52.623448] Flags: nZCv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment none
Dec 10 00:38:42 botic kernel: [   52.630817] Control: 50c5387d  Table: 9cbd0019  DAC: 00000051
Dec 10 00:38:42 botic kernel: [   52.636603] Process systemd-udevd (pid: 1353, stack limit = 0xdddf6210)
Dec 10 00:38:42 botic kernel: [   52.643264] Stack: (0xdddf7c70 to 0xdddf8000)
Dec 10 00:38:42 botic kernel: [   52.647656] 7c60:                                     ddc3a404 dddf7c98 c0a02048 c0a02048
Dec 10 00:38:42 botic kernel: [   52.655903] 7c80: 16d0071a dd972e00 ddc3a470 ddde5d88 00000618 9134fe4e ddee3800 53551829
Dec 10 00:38:42 botic kernel: [   52.664150] 7ca0: 64363142 37303a30 00006131 9134fe4e dd972e20 dd972e20 00000000 ddc3a470
Dec 10 00:38:42 botic kernel: [   52.672395] 7cc0: ddc3a400 bfb07c7c dd972e00 bfb094ac 00000000 c03fd6a3 c03fd565 dd972e20
Dec 10 00:38:42 botic kernel: [   52.680641] 7ce0: c0afe3ec c0afe3f4 c0a99180 00000000 bfb07c7c 0000001a 00000618 c03ba64d
Dec 10 00:38:42 botic kernel: [   52.688887] 7d00: 00000001 bfb094ac dd972e54 dd972e20 bfb07c7c c0a02048 c0a990a8 bfb0b400
Dec 10 00:38:42 botic kernel: [   52.697133] 7d20: 220f029c c03ba927 00000000 bfb07c7c c03ba889 c03b8e4f dde64d34 dda06dcc
Dec 10 00:38:42 botic kernel: [   52.705378] 7d40: dda7c9b0 9134fe4e 00000000 bfb07c7c dde64d00 c0a75838 00000000 c03b9d37
Dec 10 00:38:42 botic kernel: [   52.713623] 7d60: bfb04828 c034f603 bfb07c7c 00000000 c0a75838 bfb04168 bfb07c7c c03bacfd
Dec 10 00:38:42 botic kernel: [   52.721869] 7d80: c03fd0f9 bfb07c4c 00000000 c03fc767 00000000 c0a056a0 c0a02048 c0a056a0
Dec 10 00:38:42 botic kernel: [   52.730115] 7da0: ddf0fcc0 bfb17001 00000000 bfb17019 00000000 c01015d3 00000000 c0b00d8c
Dec 10 00:38:42 botic kernel: [   52.738361] 7dc0: dc94be40 00000001 00000000 c01b7d31 00000000 de7a356c 00000000 c01b7d31
Dec 10 00:38:42 botic kernel: [   52.746607] 7de0: c0a63b60 c01e0c0d bfb0b448 00000000 de7a356c e0ce3000 de36d000 c01b29cf
Dec 10 00:38:42 botic kernel: [   52.754853] 7e00: ddf0fd88 00000000 00000618 9134fe4e ddf0fd88 bfb0b400 00000001 dde71e00
Dec 10 00:38:42 botic kernel: [   52.763098] 7e20: bfb0b400 00000001 ddf0fd88 220f029c 00000618 c01b29f9 00000001 ddf0fd80
Dec 10 00:38:42 botic kernel: [   52.771344] 7e40: dddf7f38 00000001 ddf0fd80 c017061b bfb0b40c 00007fff bfb0b400 c016eaa9
Dec 10 00:38:42 botic kernel: [   52.779589] 7e60: c0a02048 bfb0b448 d
Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.516487] Internal error: Oops: 17 [#1] PREEMPT THUMB2
df0fd80 00000000 bfb0b5d4 bfb0b40c 00000000 c0a96f30
Dec 10 00:38:42 botic kernel: [   52.787835] 7e80: c0604f5c c07d1014 fffff000 c086ee08 00033018 9134fe4e 00000022 c034b018
Dec 10 00:38:42 botic kernel: [   52.796079] 7ea0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Dec 10 00:38:42 botic kernel: [   52.804326] 7ec0: 00000000 00000000 6e72656b 00006c65 00000000 00000000 00000000 00000000
Dec 10 00:38:42 botic kernel: [   52.812571] 7ee0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
Dec 10 00:38:42 botic kernel: [   52.820816] 7f00: 00000000 9134fe4e 20000033 00003018 b6745018 00000000 e0d16018 c0a02048
Dec 10 00:38:42 botic kernel: [   52.829061] 7f20: b6f7bd50 dddf6000 00000051 c0170b2f 00000000 c01cb159 e0ce3000 00033018
Dec 10 00:38:42 botic kernel: [   52.837308] 7f40: e0d15a00 e0cffcff e0d06f3c 00017804 0001cc04 bfb0af58 00000030 00000000
Dec 10 00:38:42 botic kernel: [   52.845553] 7f60: 0000da2c 00000025 00000026 0000001a 0000001e 0000000f 00000000 9134fe4e
Dec 10 00:38:42 botic kernel: [   52.853798] 7f80: 00000002 00000000 00d73c40 00d6b420 00000080 c0106de4 dddf6000 00000000
Dec 10 00:38:42 botic kernel: [   52.862043] 7fa0: 00000000 c0106c21 00000000 00d73c40 b6712000 00033018 b6f7bd50 00000002
Dec 10 00:38:42 botic kernel: [   52.870289] 7fc0: 00000000 00d73c40 00d6b420 00000080 00000000 b6f7bd50 00033018 00000000
Dec 10 00:38:42 botic kernel: [   52.878534] 7fe0: 00020000 beeda94c b6f75b07 b6edd6f4 60000010 b6712000 00012a2f 0000176a
Dec 10 00:38:42 botic kernel: [   52.886902] [<bfaf467e>] (usb_audio_probe [snd_usb_audio]) from [<c03fd6a3>] (usb_probe_interface+0x13f/0x21c)
Dec 10 00:38:42 botic kernel: [   52.897001] [<c03fd6a3>] (usb_probe_interface) from [<c03ba64d>] (driver_probe_device+0xc5/0x300)
Dec 10 00:38:42 botic kernel: [   52.905951] [<c03ba64d>] (driver_probe_device) from [<c03ba927>] (__driver_attach+0x9f/0xb4)
Dec 10 00:38:42 botic kernel: [   52.914460] [<c03ba927>] (__driver_attach) from [<c03b8e4f>] (bus_for_each_dev+0x4b/0x74)
Dec 10 00:38:42 botic kernel: [   52.922707] [<c03b8e4f>] (bus_for_each_dev) from [<c03b9d37>] (bus_add_driver+0x14b/0x1bc)
Dec 10 00:38:42 botic kernel: [   52.931043] [<c03b9d37>] (bus_add_driver) from [<c03bacfd>] (driver_register+0x39/0x8c)
Dec 10 00:38:42 botic kernel: [   52.939115] [<c03bacfd>] (driver_register) from [<c03fc767>] (usb_register_driver+0x57/0xe0)
Dec 10 00:38:42 botic kernel: [   52.947689] [<c03fc767>] (usb_register_driver) from [<bfb17019>] (usb_audio_driver_init+0x18/0x1f [snd_usb_audio])
Dec 10 00:38:42 botic kernel: [   52.958192] [<bfb17019>] (usb_audio_driver_init [snd_usb_audio]) from [<c01015d3>] (do_one_initcall+0x9b/0x198)
Dec 10 00:38:42 botic kernel: [   52.968366] [<c01015d3>] (do_one_initcall) from [<c01b29f9>] (do_init_module+0x4d/0x31c)
Dec 10 00:38:42 botic kernel: [   52.976530] [<c01b29f9>] (do_init_module) from [<c017061b>] (load_module+0x1657/0x1a74)
Dec 10 00:38:42 botic kernel: [   52.984601] [<c017061b>] (load_module) from [<c0170b2f>] (SyS_init_module+0xf7/0x14c)
Dec 10 00:38:42 botic kernel: [   52.992504] [<c0170b2f>] (SyS_init_module) from [<c0106c21>] (ret_fast_syscall+0x1/0x4c)
Dec 10 00:38:42 botic kernel: [   53.000665] Code: fe18 1e07 f2c0 816f (7b2b) b11b 

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.636603] Process systemd-udevd (pid: 1353, stack limit = 0xdddf6210)

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.643264] Stack: (0xdddf7c70 to 0xdddf8000)

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.647656] 7c60:                                     ddc3a404 dddf7c98 c0a02048 c0a02048

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.655903] 7c80: 16d0071a dd972e00 ddc3a470 ddde5d88 00000618 9134fe4e ddee3800 53551829

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.664150] 7ca0: 64363142 37303a30 00006131 9134fe4e dd972e20 dd972e20 00000000 ddc3a470

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.672395] 7cc0: ddc3a400 bfb07c7c dd972e00 bfb094ac 00000000 c03fd6a3 c03fd565 dd972e20

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.680641] 7ce0: c0afe3ec c0afe3f4 c0a99180 00000000 bfb07c7c 0000001a 00000618 c03ba64d

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.688887] 7d00: 00000001 bfb094ac dd972e54 dd972e20 bfb07c7c c0a02048 c0a990a8 bfb0b400

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.697133] 7d20: 220f029c c03ba927 00000000 bfb07c7c c03ba889 c03b8e4f dde64d34 dda06dcc

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.705378] 7d40: dda7c9b0 9134fe4e 00000000 bfb07c7c dde64d00 c0a75838 00000000 c03b9d37

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.713623] 7d60: bfb04828 c034f603 bfb07c7c 00000000 c0a75838 bfb04168 bfb07c7c c03bacfd

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.721869] 7d80: c03fd0f9 bfb07c4c 00000000 c03fc767 00000000 c0a056a0 c0a02048 c0a056a0

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.730115] 7da0: ddf0fcc0 bfb17001 00000000 bfb17019 00000000 c01015d3 00000000 c0b00d8c

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.738361] 7dc0: dc94be40 00000001 00000000 c01b7d31 00000000 de7a356c 00000000 c01b7d31

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.746607] 7de0: c0a63b60 c01e0c0d bfb0b448 00000000 de7a356c e0ce3000 de36d000 c01b29cf

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.754853] 7e00: ddf0fd88 00000000 00000618 9134fe4e ddf0fd88 bfb0b400 00000001 dde71e00

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.763098] 7e20: bfb0b400 00000001 ddf0fd88 220f029c 00000618 c01b29f9 00000001 ddf0fd80

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.771344] 7e40: dddf7f38 00000001 ddf0fd80 c017061b bfb0b40c 00007fff bfb0b400 c016eaa9

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.779589] 7e60: c0a02048 bfb0b448 ddf0fd80 00000000 bfb0b5d4 bfb0b40c 00000000 c0a96f30

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.787835] 7e80: c0604f5c c07d1014 fffff000 c086ee08 00033018 9134fe4e 00000022 c034b018

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.796079] 7ea0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.804326] 7ec0: 00000000 00000000 6e72656b 00006c65 00000000 00000000 00000000 00000000

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.812571] 7ee0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.820816] 7f00: 00000000 9134fe4e 20000033 00003018 b6745018 00000000 e0d16018 c0a02048

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.829061] 7f20: b6f7bd50 dddf6000 00000051 c0170b2f 00000000 c01cb159 e0ce3000 00033018

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.837308] 7f40: e0d15a00 e0cffcff e0d06f3c 00017804 0001cc04 bfb0af58 00000030 00000000

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.845553] 7f60: 0000da2c 00000025 00000026 0000001a 0000001e 0000000f 00000000 9134fe4e

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.853798] 7f80: 00000002 00000000 00d73c40 00d6b420 00000080 c0106de4 dddf6000 00000000

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.862043] 7fa0: 00000000 c0106c21 00000000 00d73c40 b6712000 00033018 b6f7bd50 00000002

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.870289] 7fc0: 00000000 00d73c40 00d6b420 00000080 00000000 b6f7bd50 00033018 00000000

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   52.878534] 7fe0: 00020000 beeda94c b6f75b07 b6edd6f4 60000010 b6712000 00012a2f 0000176a

Message from syslogd@botic at Dec 10 00:38:42 ...
 kernel:[   53.000665] Code: fe18 1e07 f2c0 816f (7b2b) b11b 
Dec 10 00:38:42 botic kernel: [   53.018461] ---[ end trace cf8c90c8c00a1367 ]---
Dec 10 00:38:42 botic systemd-udevd[145]: worker [1353] terminated by signal 11 (Segmentation fault)
Dec 10 00:38:42 botic systemd-udevd[145]: worker [1353] failed while handling '/devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.1'
Dec 10 00:39:16 botic systemd-udevd[145]: worker [1352] /devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.1/sound/card1/controlC1 timeout; kill it
Dec 10 00:39:16 botic systemd-udevd[145]: seq 1730 '/devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1.auto/usb1/1-1/1-1:1.1/sound/card1/controlC1' killed
Dec 10 00:39:16 botic systemd-udevd[145]: worker [1352] terminated by signal 9 (Killed)
Hope this can be of help. Is this VBUS_ERROR related to insufficient voltage supply to the USB socket?

Regards,
 
#2,029
Hi Miero,

do you know if there are any problems with alsa in the Debian version Volumio 2 is based on, especially in conjuntion with mpd 0.19.latest/ 0.18.latest or DSD/real-time related?

twluke mentions a problem with DSD with mpd 0.19.19, where all DSD is played at half speed, but otherwise everything is normal. Could it be possible, that for DSD the software options regarding the speed (I think of the clock speed options or the "Force BCLK/LRCLK ratio" is ignored while encoding DSD, but not with PCM?

@ twluke
And just a thought, perhaps the parameter for the BCLK/LRCLK ratio was wrong?

Maybe it got solved with 0.19.20 or alsa causes the problem?
 
#2,030
p { margin-bottom: 0.25cm; line-height: 120%; } Sorry that I answer just now. Life just happened in my family.

Hi Mikaelangelo, Miero, and all others!
Here I try to answer what Mikaelangelo, the developer of Volumio, asked for. As I'm not an expert on this field, and here are lot's of people with plenty of experience, please check and answer! I think that Volumio is perhaps the answer for many for an easy to install solution, which has thanks to Miero's and Mikelangelos cooperation all the bells and whistles of Miero's botic distribution, and we get a nice user interface! And if you don't like that, just keep using a client for MPD. I like gmpc most, if you have Linux, just try it!

I don't know which version of MPD brings the best experience, the aged (but solid) 0.18.x branch, or the newer 0.19. twluke has tried both (patched with DSD and rt (realtime) patches), see posts #1980 and #1982.
He uses lintweaker's patches, which can be found here: https://github.com/lintweaker/mpd-dsd-019
And, we are lucky, the guys of mpd just released version 0.19.20! (Since some versions of the 0.19-branch mpd has build-in DSD capabilities, just the realtime fix is missing. According to twluke they should be patched into the mpd-version, because this makes DSD512 possible.
The rt-patch can be found, like twluke mentions in post #1982, here: https://onedrive.live.com/?cid=CE384832F08DA832&id=CE384832F08DA832!105

As alsa is also a major part in this puzzle, and I don't know anything about problems, I thing that Miero is the best person to ask! As I understand, twluke didn't had problems with the 0.19 version relating to alsa.

Now the description of kernel options which change the DAC's behaviour:
Miero provides information on how and what to alter with kernel options on his page: http://bbb.ieero.com/ It starts at: "Changing kernel options".

The according file is /boot/uboot/uEnv.txt

Changing the external masterclock frequencies:
kernel option snd_soc_botic.clk_44k1
snd_soc_botic.clk_44k1=45158400
kernel option snd_soc_botic.clk_48k
snd_soc_botic.clk_48k=49152000

But there should be a field just to fill in the matching clock speed number to easily change this.

And a possibility to switch between "normal Boric driver version" and the one with "I2C control of ESS Sabre32 ES9018 DAC".
dtb=am335x-boneblack-botic.dtb or
dtb=am335x-boneblack-botic-sabre32.dtb

On the mentioned homepage of Miero there are tons of other options, but I'm not sure if it makes sense to include all possibilities, because then it gets messy. The other possibility is to include everything, and place this under a new tab "configuration" or something like this. I don't want to post the information here, as this post then get's really lengthy, and it would be just a copy&paste.

Thank you all for making this possible!
Matthias
 
#2,033
miero said:
OK, it seems working.

You can use this package:
http://repo.ieero.com/botic/pool/main/l/linux-upstream/linux-image-4.8.13-botic7-rc3_1_armhf.deb
Click to expand...

Wow, this is great, really great. Thank you, miero, for your quick work. The new kernel is working well.

Code: 
root@arm:/home/debian# uname -a
Linux arm 4.8.13-botic7-rc3 #1 PREEMPT Sat Dec 10 01:35:51 CET 2016 armv7l GNU/Linux
No problem with MPD playing a DSD512 source on Hermes-BBB/Cronus, permitting occasional contamination of white-noise-like noise that is not relevant to this new kernel.
Code: 
access: RW_INTERLEAVED
format: DSD_U32_LE
subformat: STD
channels: 2
rate: 705600 (705600/1)
period_size: 19600
buffer_size: 352800
/proc/asound/card0/pcm0p/sub0/hw_params (END)
The Amanero board was also well recognized as on Botic5:

Code: 
root@botic:~# ./log
Dec 10 14:51:28 botic ntpdate[1077]: adjust time server 202.181.103.212 offset 0.000436 sec
Dec 10 14:51:29 botic ntpdate[1051]: no server suitable for synchronization found
Dec 10 14:52:48 botic kernel: [  103.402218] musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_bcon (89, <AValid), retry #1, port1 00000104
Dec 10 14:52:48 botic kernel: [  103.871105] usb 1-1: new high-speed USB device number 2 using musb-hdrc
Dec 10 14:52:48 botic kernel: [  104.041631] usb 1-1: New USB device found, idVendor=16d0, idProduct=071a
Dec 10 14:52:48 botic kernel: [  104.041647] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Dec 10 14:52:48 botic kernel: [  104.041653] usb 1-1: Product: Combo384 Amanero
Dec 10 14:52:48 botic kernel: [  104.041659] usb 1-1: Manufacturer: Amanero Technologies
Dec 10 14:52:48 botic kernel: [  104.041665] usb 1-1: SerialNumber: 413-001
Dec 10 14:52:49 botic kernel: [  104.129516] usbcore: registered new interface driver snd-usb-audio
The new kernel, like the old one, is also working well as NAA for HQ player, enabling upsampling of PCM source to DSD512

Code: 
access: RW_INTERLEAVED
format: DSD_U32_LE
subformat: STD
channels: 2
rate: 705600 (705600/1)
period_size: 176400
buffer_size: 352800
/proc/asound/card0/pcm0p/sub0/hw_params (END)
Best Regards,
 
#2,035
Ok so here's my progress...

BBB Rev C - I can do everything as expected. Boticized Volumio v2 seems to act normally. Haven't tested audio because I'm not at this phase yet. Only caveats are that HDMI monitor doesn't work for me; I can connect to unit via SSH over Ethernet. Also, USB Ethernet (192.168.7.2) and cable only work with eMMC flash. Not sure if this is expected behavior or not.

SanCloud BBB Enhanced - Only way to connect was via serial debug. HDMI monitor not working. Also, Ethernet still not working. On startup here are some red flags...

These fail on start up:
Failed to start dhcpd.service
Failed to start LSB IPv4 DHCP client with IPv4LL support

So I ran
Code: 
systemctl status dhcpd.service
as requested by console.

This was my readout:

Code: 
Dec 04 15:36:58 volumio hotspot[620]: Not configured to listen on any interfaces!
Dec 04 15:36:58 volumio hotspot[620]: If you think you have received this message due to a bug rather
Dec 04 15:36:58 volumio hotspot[620]: than a configuration issue please read the section on submitting
Dec 04 15:36:58 volumio hotspot[620]: bugs on either our web page at [url]www.isc.org[/url] or in the README file
Dec 04 15:36:58 volumio hotspot[620]: before submitting a bug.  These pages explain the proper
Dec 04 15:36:58 volumio hotspot[620]: process and the information we find helpful for debugging..
Dec 04 15:36:58 volumio hotspot[620]: exiting.
Dec 04 15:36:58 volumio systemd[1]: dhcpd.service: control process exited, code=exited status=1
Dec 04 15:36:58 volumio systemd[1]: Failed to start dhcpd.service.
Dec 04 15:36:58 volumio systemd[1]: Unit dhcpd.service entered failed state.

Not sure what the solution is.

I also noticed that these items fail on startup they might be related or not related:

asoc-botic-card botic: ASoC: CPU DAI (null) not registered
asoc-botic-card botic: snd_soc_register_card failed (-517)
omap-sham 53100000.sham: initialization failed
Bluetooth: hci0: Failed to load rtl_bt/rt18723b_fw.bin
usb 1-1.4: Fatal - failed to load firmware

Things I've tried:

Once logged in I tried to make the Ethernet a static IP. ifconfig sees the proper IP after a reboot, but I still can't ping or reach the BBB Enhanced via Ethernet. For now I put the settings back to DHCP vs. static.

Any advice would be appreciated.
 
#2,036
Murdoc said:
I don't know which version of MPD brings the best experience, the aged (but solid) 0.18.x branch, or the newer 0.19. twluke has tried both (patched with DSD and rt (realtime) patches), see posts #1980 and #1982.
He uses lintweaker's patches, which can be found here: https://github.com/lintweaker/mpd-dsd-019
And, we are lucky, the guys of mpd just released version 0.19.20! (Since some versions of the 0.19-branch mpd has build-in DSD capabilities, just the realtime fix is missing. According to twluke they should be patched into the mpd-version, because this makes DSD512 possible.
The rt-patch can be found, like twluke mentions in post #1982, here: https://onedrive.live.com/?cid=CE384832F08DA832&id=CE384832F08DA832!105
Click to expand...
Hi Matthias, I recently compiled a 0.20 version of MPD from the github source and found that it can play DSD512 without realtime option. It will replace the 0.18.xx and 0.19.xx as my main MPD binary.

Just for your information.
 
#2,039
@Michelangelo
As twluke found out, version mpd 0.19.20 is superior to all other versions without rt-patch he tested. And so I think it is best to use it in your newest Volumio build, as it just works without the need of any patching.

twluke said:
Hi Matthias, I recently compiled a 0.20 version of MPD from the github source and found that it can play DSD512 without realtime option. It will replace the 0.18.xx and 0.19.xx as my main MPD binary.
Just for your information.
Click to expand...

@twluke
Do you use any "special" version of alsa? Which version do you use? (The version Debian stretch delivers?)

Regards,
Matthias
 
#2,040
Mull3t said:
Bluetooth: hci0: Failed to load rtl_bt/rt18723b_fw.bin
Click to expand...
Are you using a Bluetooth neworking? Or is this a change on Sancloud BBB?

To solve this an image must contain firmware-ralink package from "non-free" repository. This should be easily solved.

The HDMI is intentionaly disabled on BBB Botic kernel. If you want to use HDMI, you can edit the /boot/boot/uEnv.txt and select standard BBB device table file:

Warning: These do not have enabled Botic driver!
(for standard BBB) am335x-boneblack.dtb
(for BeagleBone Green) am335x-bonegreen.dtb
(for Sancloud BBB) am335x-sancloud-bbe.dtb
 
Last edited:
You must log in or register to reply here.
Top Bottom