>
> *Also, the BBB has long had a history of USB problems that I remember from
> a few years ago...this is one reference:*
> *https://groups.google.com/forum/#!topic/beagleboard/nuyyVDhU6bw
> <https://groups.google.com/forum/#%21topic/beagleboard/nuyyVDhU6bw>*
>

Fast forward two years, and we have kernel 4.x, and much better USB support
it seems.

SO, I do not know about the USB ALSA adapters, but a couple years ago I
experimented with a few USB bluetooth adapters, and the conclusion I came
to was that these cheap ( 1 buck 20 ea. ) bt adapters all use the same MAC
address . . . and that's where the problems stem from . . . but I'm also no
expert in bluetooth adapters either. I can look into it again, with this
new 4.1.x kernel I'm using, and in fact had already been considering it.

The major turn off for me was that I was unaware off any reasonably sized
bluetooth stacks / set of utilities. WHen I experimented a couple years
ago, I found I had to pull in ~200M or more of garbage just to get it to
*almost* work.

On Fri, Nov 13, 2015 at 11:37 AM, Steve French <voltvis...@gmail.com> wrote:

> Erik,
> To be thorough, I just went back and plugged the USB midi device into my
> BBB and got this:
>
> [You can see the midi adapter in the list below]
> debian@vBBB9-Office-Cl4:~$ lsusb
> Bus 001 Device 002: ID 1a86:752d QinHeng Electronics CH345 MIDI adapter
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> [Below shows that the alsa endpoints were NOT created for the device,
> which is very different from the rPi situation in my previous response!]
> debian@vBBB9-Office-Cl4:~$ sudo aconnect -i
> client 0: 'System' [type=kernel]
>     0 'Timer           '
>     1 'Announce        '
>
> [Notice the strange descriptor errors below...]
> debian@vBBB9-Office-Cl4:~$ dmesg | grep usb
> [    0.147858] usbcore: registered new interface driver usbfs
> [    0.147956] usbcore: registered new interface driver hub
> [    0.148299] usbcore: registered new device driver usb
> [    1.028641] usbcore: registered new interface driver cdc_ether
> [    1.028726] usbcore: registered new interface driver rndis_host
> [    1.028895] usbcore: registered new interface driver cdc_ncm
> [    1.031189] usbcore: registered new interface driver cdc_acm
> [    1.031473] usbcore: registered new interface driver usb-storage
> [    1.031701] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)
> [    1.032076] musb-hdrc musb-hdrc.0.auto: pdev->id = 0
> [    1.032101] musb-hdrc musb-hdrc.0.auto:
> drivers/usb/musb/musb_dsps.c:480 dsps_musb_init: OK
> [    1.032138] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk
> combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
> [    1.032155] musb-hdrc: MHDRC RTL version 2.0
> [    1.032168] musb-hdrc: setup fifo_mode 4
> [    1.032192] musb-hdrc: 28/31 max ep, 16384/16384 memory
> [    1.032339] musb-hdrc musb-hdrc.0.auto: *** mode=3
> [    1.032357] musb-hdrc musb-hdrc.0.auto: *** power=250
> [    1.033058] musb-hdrc musb-hdrc.1.auto: pdev->id = 1
> [    1.033085] musb-hdrc musb-hdrc.1.auto:
> drivers/usb/musb/musb_dsps.c:480 dsps_musb_init: OK
> [    1.033119] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk
> combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
> [    1.033135] musb-hdrc: MHDRC RTL version 2.0
> [    1.033147] musb-hdrc: setup fifo_mode 4
> [    1.033248] musb-hdrc: 28/31 max ep, 16384/16384 memory
> [    1.033396] musb-hdrc musb-hdrc.1.auto: *** mode=1
> [    1.033415] musb-hdrc musb-hdrc.1.auto: *** power=250
> [    1.033432] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
> [    1.033750] musb-hdrc musb-hdrc.1.auto: new USB bus registered,
> assigned bus number 1
> [    1.033797] musb-hdrc musb-hdrc.1.auto: supports USB remote wakeup
> [    1.033895] usb usb1: default language 0x0409
> [    1.033949] usb usb1: udev 1, busnum 1, minor = 0
> [    1.033969] usb usb1: New USB device found, idVendor=1d6b,
> idProduct=0002
> [    1.033988] usb usb1: New USB device strings: Mfr=3, Product=2,
> SerialNumber=1
> [    1.034005] usb usb1: Product: MUSB HDRC host driver
> [    1.034022] usb usb1: Manufacturer: Linux 3.8.13-bone70 musb-hcd
> [    1.034038] usb usb1: SerialNumber: musb-hdrc.1.auto
> [    1.034690] usb usb1: usb_probe_device
> [    1.034715] usb usb1: configuration #1 chosen from 1 choice
> [    1.034778] usb usb1: adding 1-0:1.0 (config #1, interface 0)
> [    1.034949] hub 1-0:1.0: usb_probe_interface
> [    1.034969] hub 1-0:1.0: usb_probe_interface - got id
> [    1.136944] usb usb1: bus auto-suspend, wakeup 1
> [    1.145404] usbcore: registered new interface driver usbhid
> [    1.145422] usbhid: USB HID core driver
> [    1.245144] usb usb1: usb wakeup-resume
> [    1.245189] usb usb1: usb auto-resume
> [    1.453267] usb 1-1: new full-speed USB device number 2 using musb-hdrc
> [    1.572342] usb 1-1: ep0 maxpacket = 8
>
>
>
>
> *[    1.573188] usb 1-1: skipped 1 descriptor after interface[
> 1.573205] usb 1-1: skipped 7 descriptors after interface[    1.573216] usb
> 1-1: skipped 1 descriptor after endpoint[    1.573226] usb 1-1: skipped 1
> descriptor after endpoint*[    1.573316] usb 1-1: default language 0x0409
> [    1.573482] usb 1-1: udev 2, busnum 1, minor = 1
> [    1.573497] usb 1-1: New USB device found, idVendor=1a86, idProduct=752d
> [    1.573508] usb 1-1: New USB device strings: Mfr=0, Product=2,
> SerialNumber=0
> [    1.573517] usb 1-1: Product: USB2.0-MIDI
> [    1.573924] usb 1-1: usb_probe_device
> [    1.573941] usb 1-1: configuration #1 chosen from 1 choice
> [    1.574048] usb 1-1: adding 1-1:1.0 (config #1, interface 0)
> [    1.574303] usb 1-1: adding 1-1:1.1 (config #1, interface 1)
> [    3.772427] rtusb init rt2870 --->
> [    3.772585] usbcore: registered new interface driver rt2870
> [    9.394238] snd-usb-audio 1-1:1.0: usb_probe_interface
> [    9.394273] snd-usb-audio 1-1:1.0: usb_probe_interface - got id
> [   10.029579] usbcore: registered new interface driver snd-usb-audio
> [   11.088773] usb0: MAC 90:59:af:58:eb:d0
> [   11.088791] usb0: HOST MAC 90:59:af:58:eb:dc
> [   11.108282] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver
> [   11.109291] musb-hdrc musb-hdrc.0.auto: new USB bus registered,
> assigned bus number 2
> [   11.109325] musb-hdrc musb-hdrc.0.auto: supports USB remote wakeup
> [   11.112544] usb usb2: default language 0x0409
> [   11.112586] usb usb2: udev 1, busnum 2, minor = 128
> [   11.112599] usb usb2: New USB device found, idVendor=1d6b,
> idProduct=0002
> [   11.112610] usb usb2: New USB device strings: Mfr=3, Product=2,
> SerialNumber=1
> [   11.112620] usb usb2: Product: MUSB HDRC host driver
> [   11.112629] usb usb2: Manufacturer: Linux 3.8.13-bone70 musb-hcd
> [   11.112639] usb usb2: SerialNumber: musb-hdrc.0.auto
> [   11.115740] usb usb2: usb_probe_device
> [   11.115763] usb usb2: configuration #1 chosen from 1 choice
> [   11.115817] usb usb2: adding 2-0:1.0 (config #1, interface 0)
> [   11.115942] hub 2-0:1.0: usb_probe_interface
> [   11.115954] hub 2-0:1.0: usb_probe_interface - got id
> [   11.217066] usb usb2: bus auto-suspend, wakeup 1
> [   14.943620] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
>
>
> I am thinking the above descriptor issues are somehow related to the fact
> that the midi doesnt work on the BBB and the endpoints are not showing up
> in the "aconnect -i" list.  But why this problem when neither the rPi nor
> my Ubuntu laptop have the problem?
>
>
> Still not sure if USB Vbus is a problem on the BBB, but I remember this
> thread from some time ago:
> https://groups.google.com/forum/#!msg/beagleboard/tYYMzO2M4LQ/SpXZxewcCLoJ
>
> Also, the BBB has long had a history of USB problems that I remember from
> a few years ago...this is one reference:
> https://groups.google.com/forum/#!topic/beagleboard/nuyyVDhU6bw
>
> good luck!
> -frenchy (Steve French)
> www.voltvision.com
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to