Guest mathk

Loading bitstream under ubuntu 12.04

13 posts in this topic

I am trying to load a simple test.bit bitstream file with the papilio-prog but I got an error.

[tt]

$ papilio-prog -f test.bit

Could not access USB device 0403:6010.[/tt]

It is a papilio-prog compile from github. I did have a quick look at the source code and add more debug information and here is the actual output:

[tt]ftdi_usb_open_desc: unable to claim usb device. Make sure the default FTDI driver is not in use.[/tt]

It seems to me that I am missing some driver.

Thanks for the help

Share this post


Link to post
Share on other sites

Does a lsusb show that the Papilio is connected and everything?

Jack.

Share this post


Link to post
Share on other sites

[tt]

$ papilio-prog -f test.bit

Could not access USB device 0403:6010.[/tt]

This requires special privileges. There must be a way of doing that in user space, tweaking config files here and there, but I'm just too lazy to look into it: I just 'sudo' the call to papilio-prog

Share this post


Link to post
Share on other sites

Ahhhh, right! It probably just needs a sudo...

Jack.

Share this post


Link to post
Share on other sites

I have currently the same problem after updating my ubuntu 12.04 LTS distro.

I use this added file:

/etc/udev/rules.d/45-ftdi2232-libftdi.rules

wich contains these lines:

#ftdi

SYSFS{idProduct}=="6010", SYSFS{idVendor}=="0403", MODE="666", GROUP="dialout"

I wonder if my libftdi1 version 0.19-4 that is no longer working fine ?

any idea ?

Share this post


Link to post
Share on other sites

First thing first: Thank you Jack for your answer :)

I should have read the manual before :)

I did a sudo. it works.

However I wasn't shure where to put the libftdi.rules file, so I did both locations:

/lib/udev/rules.d and /etc/udev/rules.d

Hope this helps someone else too :)

and don't forget command "lsusb" to fullfill the libftdi.rules!

Share this post


Link to post
Share on other sites

c bien de voir des francai ici sur le forum et qui sont des utilisateurs de Papilio :)

Don't ask me how I knew you are from france :P I'm going to tell you in a private message.

I'm Glad you found the answer here Colin.

Share this post


Link to post
Share on other sites

I have currently the same problem after updating my ubuntu 12.04 LTS distro.

I use this added file:

/etc/udev/rules.d/45-ftdi2232-libftdi.rules

wich contains these lines:

#ftdi

SYSFS{idProduct}=="6010", SYSFS{idVendor}=="0403", MODE="666", GROUP="dialout"

I wonder if my libftdi1 version 0.19-4 that is no longer working fine ?

any idea ?

Hi Colin

Ubuntu 12.04 use Udev version that have deprecated SYSFS.

If i remember well i provide you this udev rule last year at the LOG ^^

I got the same issue this morning after several month away of the papilio board. I just fix the problem on my system. Here is what i put in this file

/etc/udev/rules.d/45-ftdi2232-libftdi.rules:

$$cat /etc/udev/rules.d/45-ftdi2232-libftdi.rules

#ftdi

#SYSFS{idProduct}=="6010", SYSFS{idVendor}=="0403", MODE="666", GROUP="dialout"

ATTR{idProduct}=="6010", ATTR{idVendor}=="0403", MODE="666", GROUP="dialout"

You need to be part of dialout. To know if you are:

$$groups $USER

After a reboot (the reboot could be avoid, but udev restart seem not to be enough ...) you can use or reuse FDTI FT2232H device without sudo command.

Thomas

Share this post


Link to post
Share on other sites

so..

sudo usermod -a -G dialout YOUR_USERNAME

in most linux distros to add dialout group to user?

Share this post


Link to post
Share on other sites

Yes, this should work. Consult man page in case of doubt.

Share this post


Link to post
Share on other sites

Hi I had the same problem, "Could not access USB device 0403:6010. If this is linux then use sudo" it was intermittent. Rebooting the computer seemed to help but it would fail after 10 mins or so. I found this forum and twoothers and tried the recommendations to no avail but then found at the end of this forum;

 

http://embeddedprogrammer.blogspot.co.uk/2012/07/hacking-ov7670-camera-module-sccb-cheat.html

 

The conclusion that the cable was the problem. I replaced my cable with a shorter one and it all worked! :-)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now