Re: [beagleboard] BES v0.8 does not recognize the USB Gamepad

2017-02-09 Thread Przemek Klosowski 
it's been a while since I played with gamepads on Linux, but I seem to
remember that the gamepads show up as HID devices  with crazy number
of mouse buttons (MB 1,2,3,4,5,6,7,8,9). So, just write your app
to react to high-numbered mouse buttons. You can see what your gamepad
is generating by running the xev program from your text terminal;
it'll print event records to your screen.

Thu, Feb 9, 2017 at 2:06 PM,   wrote:
> Does anybody know how can I add the support for these USB gamepads?
>
> It would be great to have some help for doing this, even if someone could 
> explain how develop a new driver and compile It.
>
> I have everything ready but the USB gamepads.
>
> --
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/9f60cb1f-d920-40f0-8dca-b9e9070b7662%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAC%3D1GgH8CrO%2B_6CcmBbURN3HAkunhkdnzu3apNEMcNrYB7jBDQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BES v0.8 does not recognize the USB Gamepad

2017-02-09 Thread yolcopc 
Does anybody know how can I add the support for these USB gamepads?

It would be great to have some help for doing this, even if someone could 
explain how develop a new driver and compile It. 

I have everything ready but the USB gamepads.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9f60cb1f-d920-40f0-8dca-b9e9070b7662%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BES v0.8 does not recognize the USB Gamepad

2017-02-01 Thread yolcopc 
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 
,
 
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 beagleboard+unsubscr...@googlegroups.com.
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 4a30.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 d