BBB Joypad not opening

I've followed the instructions for setting up a joypad with a BBB and after seeing 'Loading cape-bone-iio overlay' during startup, I get 'No input devices could be opened. This usually indicates a misconfigured system. Please read the section 'PERMISSIONS AND UDEV' in the hal_input manpage.'

I followed the instructions and created a file 51-plugdev.rules and saved it in /etc/udev/rules.d containing SUBSYSTEM=="input", mode="0660", group="plugdev" . I've rebooted and I still get the same error. I have checked with terminal command 'less /proc/bus/input/devices' and I can see the joypad.

Any ideas welcome!

Hi,

I'm not sure what is causing your problem, but I was able to get a keypad set up using the instructions on this page:

softsolder.com/2013/02/25/linuxcnc-hal-p...stromo-n52-speedpad/

You might want to look there to see if it can help.

Jeff

Thanks Jeff - I'll give this a go.

Richard

I've followed the instructions as far as possible:

1. 'less /proc/bus/input/devices' gives me a sensible list - my joypad is at the bottom, 'Bus=0003 Vendor=0f30 Product=0112 Version=0110', 'Name="Jess Tech Dual Analog Pad"
2. 'll /dev/input' returns command not found
3. 'lsusb' returns 'BUS 001 Device 006: ID 0f30:0112 Jess Technology Co., Ltd'
4. 'udevadm info --query=all --attribute-walk --name=/dev/bus/usb/006' returns command not found

I created a rules file 90-Jess.rules, and added a single line 'ATTRS{product}=="Jess",MODE="0660",GROUP="plugdev"

But it still doesn't work - I've also tried ATTRS{manufacturer}=="Jess" and SYSFS{idProduct}=="0112",SYSFS{idVendor}=="0f30" but with no luck...

I'm not sure what I'm missing - it's difficult because I can't dump the attributes with udevadm.

Hi,

ll is short for ls -l
so try:
ls -l /dev/input

some commands like udevadm may need the "sudo" in front like:
sudo udevadm ......

Jeff

Thank Jeff - I can know get responses to all the commands.

After completing the final step in the instructions:

I get (snippet):

I'm not sure what the 'T' is on the end of the permissions - the mouse and keyboard event handlers have this too.

It's still not working, and this is the only thing I can see wrong, apart from a question about the Syntax in the rules file - the udevadm query returns ATTR{} and the .rules file uses ATTRS{}, which may well be correct.

The only other possibility is the order of execution of the .rules files - the instructions says:

Note that the file name must start with a number around 90- to avoid being clobbered by a rule in /lib/udev/rules.d/50-udev-default.rules that (re)sets the permissions to 0640; the doc suggests that rules without numbers happen after all the number rules, so perhaps you could just use meaningful names.

I've tried renaming my file 'xdual.rules' to force it to be at the end of any rules without numbers (there are two system rules files 'rtheap.rules' and 'rt-pipe.rules', and also tried renaming it '90-dual.rules' to force it higher than the system files '50-LINUXCNC-shmdrv.rules' and '70-persistent-net.rules' - both to no avail...

I changed the permissions in the .rules file to 0777 and it works now - not sure this is strictly correct though!

When I check the event handler file permissions after doing the above, they now show crwxrwxrwt (not sure why sticky bit 'T' has now changed to 't') - it seems changing them to crw-rw---T with 0660 is insufficient as per all the documentation.