getting started (libftdi on ubuntu 14.04lts)


awallin

Recommended Posts

Hi all,

trying to get started with a Papilio pro over here!

 

Xilinx ISE tool downloaded, followed switch_led example from the book, built bit-file.

Now trying Papilio Loader 2.6

 

at first it said

/opt/GadgetFactory/papilio-loader/programmer/linux32/papilio-prog: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory

 

so I tried

sudo ln -s /usr/lib/x86_64-linux-gnu/libftdi.so /usr/lib/libftdi.so.1
 

 

now it says:

/opt/GadgetFactory/papilio-loader/programmer/linux32/papilio-prog: error while loading shared libraries: libftdi.so.1: wrong ELF class: ELFCLASS64

 
 
any ideas? 32-bit library needed? Please tell me papilio-loader will work on a 64-bit system!? nobody uses 32-bit OS installs anymore!
 
thanks,
Anders
Link to comment
Share on other sites

Thanks for the link. I tried more or less exactly following those instructions.

 

I still get the same error: (symlink to libftdi.so.1 mentioned in first post now removed)

$ sudo papilio-prog -b switches_leds.bit
papilio-prog: error while loading shared libraries: libftdi.so.1: cannot open shared object file: No such file or directory
 

I noted that "papilio-prog" is a symlink:

/usr/local/bin/papilio-prog -> /opt/GadgetFactory/papilio-loader/programmer/linux32/papilio-prog
 

 

I also noticed that linux-installer.sh simply copies a pre-built binary into above said location.

Maybe I need to build papilio-prog myself, since I'm on a 64-bit system?

 

 


Here are the directions for Papilio Loader under Linux:

http://gadgetfactory.net/learn/2013/09/18/howto-papilio-loader-gui-on-linux/

 

Link to comment
Share on other sites

 

I also noticed that linux-installer.sh simply copies a pre-built binary into above said location.

Maybe I need to build papilio-prog myself, since I'm on a 64-bit system?

 

yep this seems to be solved now.

I re-built papilio-prog like this:

Papilio-Loader-2.6/papilio-prog$ make clean

Papilio-Loader-2.6/papilio-prog$ ./autogen

Papilio-Loader-2.6/papilio-prog$ ./configure

Papilio-Loader-2.6/papilio-prog$ ./make

 

then I copied the resulting binary to where linux-installer.sh expects it to be.

Now it seems to work:

 

 

$ sudo papilio-prog -f switches_leds.bit

Using built-in device list

JTAG chainpos: 0 Device IDCODE = 0x24001093    Desc: XC6SLX9

Created from NCD file: switches_leds.ncd;UserID=0xFFFFFFFF

Target device: 6slx9tqg144

Created: 2014/10/20 21:52:18

Bitstream length: 2724832 bits

Uploading "switches_leds.bit". DNA is 0xf95a50ab8d237dff

 

 

 

does that look right?

 

I was using the UCF example from the book. Maybe that is not right for the Papilio Pro + LogicStart MegaWing 1.2 ?

 

# Constraints for Papilio One

NET switch_1 LOC = "P3" | IOSTANDARD=LVTTL;

NET switch_0 LOC = "P4" | IOSTANDARD=LVTTL;

NET LED_1  LOC = "P16" | IOSTANDARD=LVTTL;

NET LED_0  LOC = "P17" | IOSTANDARD=LVTTL;

 

now when I flip the switches nothing happens - but maybe the pin numbers have changed from the Papilio One? (any chance the book author could take pull-requests with updates on github?)

Link to comment
Share on other sites

Yay! this works now. copy/pasted the pins from "BPM7003-Papilio-Pro-LogicStart-MegaWing-general.UCF" to my UCF file and rebuilt and reprogrammed.

 

# Constraints for Papilio Pro
NET switch_1 LOC = "P114" | IOSTANDARD=LVTTL;
NET switch_0 LOC = "P115" | IOSTANDARD=LVTTL;
NET LED_1    LOC = "P123" | IOSTANDARD=LVTTL;
NET LED_0    LOC = "P124" | IOSTANDARD=LVTTL;

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.