Now, I have been trying to find out what it is happening with the BES after 
flashing the v0.8 in a new uSD card.

The main issue is with the USB controller 
<https://www.aliexpress.com/snapshot/8080469704.html?orderId=78163662725973&productId=32668671882>,
 
let me explain what I have found.

Just flashed the uSD, the BBB boots up perfectly, shows the @IP, and I can 
connect through the web server. That is fine.
Now, the steps I did were:

   1. Upload some ROMs to BBB. Meanwhile, I uploaded the ROMs, the screen 
   automatically change to 'PAUSE' screen. 
   2. I removed the USB gamepad (it neither work), and restart the BBB. 
   Here, there is no time to watch which ROMs are in the uSD, as screens 
   changes to 'PAUSE' automatically.
   3. Web server is out of business because of previous step, I can not 
   connect to it anymore.
   4. Checked in *Windows* the vendor ID and other parameters from the USB 
   gamepad. With 'joy.cpl' I can check the USB Gamepad is working fine.
   5. Format again the uSD, reflashes the BES v0.8, and without upload any 
   ROMs, modify the controller #1 buttons configuration with the one obtain 
   from 'joy.cpl'.
   6. Reboot with USB gamepad connected the BBB. Connect BBB through ssh, 
   check with 'dmesg' and 'lsusb' the USB devices. The USB gamepad is not 
   shown, it has not been detected.
   7. Unplug the USB gamepad, BBB and its ethernet still works.
   8. Plug again the USB gamepad, ethernet goes down, then nor ssh neither 
   the web browser works.

Please, find attached a document with the outputs of the different commands 
I tested, and also the VendorID information from Windows. Maybe, you can 
figure out what it is happening.

Does anyone knows how can I force the system to detect the USB gamepad? Is 
it possible to add support for this USB gamepad?

Thanks in advance.

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/598e7327-f770-4c12-99a3-c8020c664669%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
=================
=== WINDOWS 7 ===
=================

        ID. HARDWARE
                HID\VID_0079&PID_0011&REV_0106
                HID\VID_0079&PID_0011
                HID_DEVICE_SYSTEM_GAME
                HID_DEVICE_UP:0001_U:0004
                HID_DEVICE_SYSTEM_GAME
        
=================
====== BES ======
=================

        ID. HARDWARE
                
                
                
                
                
                
                
                
                
___________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________

dmesg
                [    8.892982] CAUTION: musb: Babble Interrupt Occurred
                [    8.992993] musb-hdrc musb-hdrc.1.auto: Restarting MUSB to 
recover from Babble
                [    8.995027] musb-hdrc: setup fifo_mode 4
                [    8.995055] musb-hdrc: 28/31 max ep, 16384/16384 memory
                [    9.667291] pruss_uio 4a300000.pruss: pins are not 
configured from the driver
                [   10.174956] EXT4-fs (mmcblk0p1): re-mounted. Opts: 
errors=remount-ro
                [   10.688513] net eth0: initializing cpsw version 1.12 (0)
                [   10.763188] net eth0: phy found : id is : 0x7c0f1
                [   10.763386] libphy: PHY 4a101000.mdio:01 not found
                [   11.026139] net eth0: phy 4a101000.mdio:01 not found on 
slave 1
                [   11.430123] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not 
ready
                [   13.843094] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
                [   13.843181] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link 
becomes ready
                [   19.312404] usb 1-1: device not accepting address 2, error 
-110
                [   19.579227] musb-hdrc musb-hdrc.1.auto: otg: 
usb_otg_kick_fsm: invalid host/gadget device
                [   20.092880] musb-hdrc musb-hdrc.1.auto: otg: 
usb_otg_kick_fsm: invalid host/gadget device
                [   20.432359] usb 1-1: new low-speed USB device number 4 using 
musb-hdrc
                [   25.573692] usb 1-1: device descriptor read/all, error -71
                [   25.648151] musb-hdrc musb-hdrc.1.auto: otg: 
usb_otg_kick_fsm: invalid host/gadget device
                [   25.862338] usb 1-1: new low-speed USB device number 5 using 
musb-hdrc
                [   31.003571] usb 1-1: device descriptor read/all, error -71
                [   31.142594] musb-hdrc musb-hdrc.1.auto: otg: 
usb_otg_kick_fsm: invalid host/gadget device
                [   31.462526] usb 1-1: new low-speed USB device number 6 using 
musb-hdrc
                [   31.483816] usb 1-1: device descriptor read/8, error -71
                [   31.743678] usb 1-1: device descriptor read/8, error -71
                [   31.992553] musb-hdrc musb-hdrc.1.auto: otg: 
usb_otg_kick_fsm: invalid host/gadget device
                [   32.312524] usb 1-1: new low-speed USB device number 7 using 
musb-hdrc
                [   32.333738] usb 1-1: device descriptor read/8, error -71
                [   32.593731] usb 1-1: device descriptor read/8, error -71
                [   32.832569] hub 1-0:1.0: unable to enumerate USB device on 
port 1
                                
dmesg | grep usb
                [    2.174229] usbcore: registered new interface driver usbfs
                [    2.174305] usbcore: registered new interface driver hub
                [    2.174510] usbcore: registered new device driver usb
                [    2.462667] usbcore: registered new interface driver 
usb-storage
                [    2.465112] 47401300.usb-phy supply vcc not found, using 
dummy regulator
                [    2.495229] musb-hdrc musb-hdrc.0.auto: Failed to request 
rx1.
                [    2.565945] musb-hdrc musb-hdrc.0.auto: musb_init_controller 
failed with status -517
                [    2.659623] platform musb-hdrc.0.auto: Driver musb-hdrc 
requests probe deferral
                [    2.660746] 47401b00.usb-phy supply vcc not found, using 
dummy regulator
                [    2.735013] musb-hdrc musb-hdrc.1.auto: Failed to request 
rx1.
                [    2.805630] musb-hdrc musb-hdrc.1.auto: musb_init_controller 
failed with status -517
                [    2.899271] platform musb-hdrc.1.auto: Driver musb-hdrc 
requests probe deferral
                [    3.072735] usbcore: registered new interface driver usbhid
                [    3.072748] usbhid: USB HID core driver
                [    3.320612] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, 
bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
                [    3.320634] musb-hdrc: MHDRC RTL version 2.0
                [    3.320644] musb-hdrc: setup fifo_mode 4
                [    3.320660] musb-hdrc: 28/31 max ep, 16384/16384 memory
                [    3.330228] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, 
bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
                [    3.330249] musb-hdrc: MHDRC RTL version 2.0
                [    3.330257] musb-hdrc: setup fifo_mode 4
                [    3.330271] musb-hdrc: 28/31 max ep, 16384/16384 memory
                [    3.330402] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
                [    3.330790] musb-hdrc musb-hdrc.1.auto: new USB bus 
registered, assigned bus number 1
                [    3.331069] usb usb1: New USB device found, idVendor=1d6b, 
idProduct=0002
                [    3.331083] usb usb1: New USB device strings: Mfr=3, 
Product=2, SerialNumber=1
                [    3.331094] usb usb1: Product: MUSB HDRC host driver
                [    3.331104] usb usb1: Manufacturer: Linux 3.14.79-ti-r92.2 
musb-hcd
                [    3.331113] usb usb1: SerialNumber: musb-hdrc.1.auto
                [    3.612448] musb-hdrc musb-hdrc.1.auto: otg: 
usb_otg_kick_fsm: invalid host/gadget device
                [    3.773723] usb 1-1: new low-speed USB device number 2 using 
musb-hdrc
                [    8.892982] CAUTION: musb: Babble Interrupt Occurred
                [    8.992993] musb-hdrc musb-hdrc.1.auto: Restarting MUSB to 
recover from Babble
                [    8.995027] musb-hdrc: setup fifo_mode 4
                [    8.995055] musb-hdrc: 28/31 max ep, 16384/16384 memory
                [   19.312404] usb 1-1: device not accepting address 2, error 
-110
                [   19.579227] musb-hdrc musb-hdrc.1.auto: otg: 
usb_otg_kick_fsm: invalid host/gadget device
                [   20.092880] musb-hdrc musb-hdrc.1.auto: otg: 
usb_otg_kick_fsm: invalid host/gadget device
                [   20.432359] usb 1-1: new low-speed USB device number 4 using 
musb-hdrc
                [   25.573692] usb 1-1: device descriptor read/all, error -71
                [   25.648151] musb-hdrc musb-hdrc.1.auto: otg: 
usb_otg_kick_fsm: invalid host/gadget device
                [   25.862338] usb 1-1: new low-speed USB device number 5 using 
musb-hdrc
                [   31.003571] usb 1-1: device descriptor read/all, error -71
                [   31.142594] musb-hdrc musb-hdrc.1.auto: otg: 
usb_otg_kick_fsm: invalid host/gadget device
                [   31.462526] usb 1-1: new low-speed USB device number 6 using 
musb-hdrc
                [   31.483816] usb 1-1: device descriptor read/8, error -71
                [   31.743678] usb 1-1: device descriptor read/8, error -71
                [   31.992553] musb-hdrc musb-hdrc.1.auto: otg: 
usb_otg_kick_fsm: invalid host/gadget device
                [   32.312524] usb 1-1: new low-speed USB device number 7 using 
musb-hdrc
                [   32.333738] usb 1-1: device descriptor read/8, error -71
                [   32.593731] usb 1-1: device descriptor read/8, error -71

lsusb
                Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
                
ls -lrt /dev/tty*
                crw-rw---- 1 root tty     4, 64 Jan 25 18:54 /dev/ttyS0
                

Reply via email to