On Sun, Jan 11, 2009 at 01:21:01PM +0100, Jörg Krein wrote:
> Hi,
> I made an attempt to run OpenOCD under Linux to use
> it for my STM32 Primer.
> After downloading some packages (automake, libusbdev, etc.)
> I successfully configured and compiled it:

...

> Error: usb_claim_interface: could not claim interface 0: Operation not 
> permitted

Sounds like permissions to me.

Ubuntu uses udev, so you need to add a file in /etc/udev/rules.d, which
matches the device and indicates what to do when it is matched.

A simple example might be as follows.
SUBSYSTEM=="usb", ATTRS{idVendor}=="138e", ATTRS{idProduct}=="9000",
MODE="0666"
You might chose to do something other than just setting the mode to
read-write for everybody.  Naming the file is up to you.  Mine just
happens to be called "40-rlink-permissions.rules".

Some people just run such programs (which use libusb) as root to get
around the problem you cite, but that is bad security practice.  It is
better to fix the device permissions.

If it's not permissions, then something else has claimed the interface
already.  As this is a vendor class device, it is probably not claimed
by a class driver.  In that case, the error message would probably
indicate busy, rather than permissions.
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to