Sign In

Don't have a Xilinx account yet?

  • Choose to receive important news and product information
  • Gain access to special content
  • Personalize your web experience on Xilinx.com

Create Account

Username

Password

Forgot your password?
XClose Panel
Xilinx Home
Reply
Visitor
xilinx20@snowdon.id.au
Posts: 8
Registered: ‎11-02-2011
Accepted Solution

Ubuntu 11.10 and impact, chipscope, etc.

Hi all, 

 

I thought I would write in after the last few hours of mucking around trying to get impact to run after upgrading my machine to Ubuntu 11.10 (I realise it's not supported, but there will be plenty of people like me who want to run an up to date OS and applications). 

 

I was having problems with impact crashing whenever it went to access the USB cable. Chipscope analyzer has similar problems. 

 

It turned out that the Digilent plugin is what causes the crash. It happens just after libusb-1.0 is loaded. All you need to do to get things working is to remove the plugin. In my case that involved:  

 

mv /opt/Xilinx/13.2/ISE_DS/ISE/lib/lin64/plugins/Digilent/ tmp/

 

I hope that this saves someone else the few hours it took me (which it shouldn't have, in hindsight). 

 

Dave. 

Regular Contributor
dag1
Posts: 86
Registered: ‎12-08-2007
0

Re: Ubuntu 11.10 and impact, chipscope, etc.

Thanks for that.

Indeed, solved the problem for me too on Ubuntu 11.10.

 

My problem now is how should I deal with my Atlys board ? I still need the Digilent

plugin to work ?

 

Any advise ?

 

Dag

Regular Contributor
dag1
Posts: 86
Registered: ‎12-08-2007

Re: Ubuntu 11.10 and impact, chipscope, etc.

I solved the problem.

 

My mistake was that I first installed Design Suite on windows + Atlys card. Then I copied the Digilent plugin files 

directly from the Windows installation to the Ubuntu installation.

 

You should ensure that you use the Digilent plugin for linux and not for Windows.

http://www.digilentinc.com/Products/Detail.cfm?NavPath=2,66,768&Prod=DIGILENT-PLUGIN

 

Summary: Ubuntu 11.10, Design Suite 13.3, Atlys card (Spartan 6) and cable driver all work fine now.

 

 

Newbie
yatish_tw
Posts: 2
Registered: ‎07-16-2011
0

Re: Ubuntu 11.10 and impact, chipscope, etc.

I also ran into this problem and wasted a bunch of time trying to solve it under Ubuntu 11.04 and 11.10.  Dave's solution will work if impact is crashing and you see a log message about libdpcomm when you run demsg:

 

_impact4[22438]: segfault at 0 ip 00007fcf6d49f5f8 sp 00007fff5e0c87f0 error 4 in libdpcomm.so.2.6.4[7fcf6d493000+31000]

 

Like you mentioned, I hope this info helps others find this thread before wasting too much time.

 

yatish

Regular Visitor
ribalda
Posts: 15
Registered: ‎06-16-2008

Re: Ubuntu 11.10 and impact, chipscope, etc.

Hello. 

 

I have the same problem here with version 13.2 and 13.1, which install the plugin by default...

 

And this fixed it:

 

 

ricardo@newpili:/opt/xilinx/13.1/ISE_DS$ mkdir trash; mv ISE/lib/lin64/plugins/Digilent/libCseDigilent trash/

 

And this is the backtrack, in case someone at xilinx wants to fix it....

 

ricardo@newpili:~$ gdb /opt/xilinx/13.1/ISE_DS/EDK/bin/lin64/xmd
GNU gdb (GDB) 7.3-debian
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /opt/xilinx/13.1/ISE_DS/EDK/bin/lin64/xmd...(no debugging symbols found)...done.
(gdb) r
Starting program: /opt/xilinx/13.1/ISE_DS/EDK/bin/lin64/xmd 
[Thread debugging using libthread_db enabled]
process 6982 is executing new program: /opt/xilinx/13.1/ISE_DS/EDK/bin/lin64/xmd
[Thread debugging using libthread_db enabled]
process 6982 is executing new program: /opt/xilinx/13.1/ISE_DS/EDK/bin/lin64/unwrapped/xmd
[Thread debugging using libthread_db enabled]
Xilinx Microprocessor Debugger (XMD) Engine
Xilinx EDK 13.1 Build EDK_O.40d
Copyright (c) 1995-2009 Xilinx, Inc.  All rights reserved.
[New Thread 0x7ffff2862700 (LWP 6985)]
Found /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libCseJtagTcl.so...
Loading CseJtag Global Variables...
Found /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libCseVIOTcl.so...
Loading CseVIO Global Variables...

Loading custom commands from /home/ricardo/.xmd: 
mem_read_byte
mem_write_byte
mem_read_hwd
memcpy
ppc405_print
ppc405_rm_sa_print
ppc405_read_tlb
ppc405_dcache_print
ppc440_print
ppc440_read_tlb
ppc440_dcache_print
ppc_bt
ppc_dis
mb_print
mb_bt
mb_dis
emaclite_print
lltemac_print
lltemac_read_phy
marvell_phy_print
marvell_phy_probe
national_phy_print
national_phy_probe
lldma_mm_print
lldma_desc_print
uartlite_print
uartns550_print
xps_intc_print
xiic_print
xiic_read_byte
xiic_write_byte
ipv4_packet_decode
en_packet_decode
csum16

XMD% 
XMD% connect ppc hw

Program received signal SIGSEGV, Segmentation fault.
__pthread_mutex_lock (mutex=0x20) at pthread_mutex_lock.c:50
50	pthread_mutex_lock.c: No such file or directory.
	in pthread_mutex_lock.c
(gdb) bt
#0  __pthread_mutex_lock (mutex=0x20) at pthread_mutex_lock.c:50
#1  0x00007ffff13a6dff in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#2  0x00007ffff13ae00c in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#3  0x00007ffff13ae3ce in ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#4  0x00007ffff13a706b in libusb_get_device_list () from /lib/x86_64-linux-gnu/libusb-1.0.so.0
#5  0x00007ffff19de668 in LINUTIL::DetachFtdiUsbDriver() () from /usr/local/lib64/digilent/adept/libdabs.so.2
#6  0x00007ffff1076a6b in DllInit() () from /usr/local/lib64/digilent/adept/libdpcomm.so.2
#7  0x00007ffff1076535 in DpcommAttach() () from /usr/local/lib64/digilent/adept/libdpcomm.so.2
#8  0x00007ffff10786c6 in global constructors keyed to pshmDvtbl () from /usr/local/lib64/digilent/adept/libdpcomm.so.2
#9  0x00007ffff108f796 in __do_global_ctors_aux () from /usr/local/lib64/digilent/adept/libdpcomm.so.2
#10 0x00007ffff1074e9b in _init () from /usr/local/lib64/digilent/adept/libdpcomm.so.2
#11 0x00007ffff1ae9000 in ?? ()
#12 0x00007ffff7deac89 in ?? () from /lib64/ld-linux-x86-64.so.2
#13 0x00007ffff7deadc7 in ?? () from /lib64/ld-linux-x86-64.so.2
#14 0x00007ffff7def183 in ?? () from /lib64/ld-linux-x86-64.so.2
#15 0x00007ffff7dea926 in ?? () from /lib64/ld-linux-x86-64.so.2
#16 0x00007ffff7dee89a in ?? () from /lib64/ld-linux-x86-64.so.2
#17 0x00007ffff391af66 in dlopen_doit (a=<optimized out>) at dlopen.c:67
#18 0x00007ffff7dea926 in ?? () from /lib64/ld-linux-x86-64.so.2
#19 0x00007ffff391b2ec in _dlerror_run (operate=0x7ffff391af00 <dlopen_doit>, args=0x7fffffffaba0) at dlerror.c:164
#20 0x00007ffff391aee1 in __dlopen (file=<optimized out>, mode=<optimized out>) at dlopen.c:88
#21 0x00007ffff78bf9a5 in CseRT::PluginManager::loadModule(stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> >, stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> >, CseRT::Plugin&) ()
   from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libCseJtag.so
#22 0x00007ffff78c1921 in CseRT::PluginManager::addAllPluginsInDir(stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> >) () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libCseJtag.so
#23 0x00007ffff78c290f in CseRT::PluginManager::addAllPlugins() () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libCseJtag.so
#24 0x00007ffff78c496b in CseRT::PluginManager::init() () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libCseJtag.so
#25 0x00007ffff78c5abb in CseRT::PluginManager::PluginManager() () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libCseJtag.so
#26 0x00007ffff78c9fc5 in CseRT::Session::createPluginManager() () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libCseJtag.so
#27 0x00007ffff78cbfcd in CseRT::Session::init(unsigned int, void (*)(unsigned int, unsigned int, char const*), stlp_std::vector<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> >, stlp_std::allocator<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > > >) ()
   from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libCseJtag.so
---Type <return> to continue, or q <return> to quit---
#28 0x00007ffff78cc60b in CseRT::Session::Session(unsigned int, void (*)(unsigned int, unsigned int, char const*), stlp_std::vector<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> >, stlp_std::allocator<stlp_std::basic_string<char, stlp_std::char_traits<char>, stlp_std::allocator<char> > > >) ()
   from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libCseJtag.so
#29 0x00007ffff78a0818 in CseRT::createSession(void (*)(unsigned int, unsigned int, char const*), unsigned int, char const**, unsigned int*) () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libCseJtag.so
#30 0x00007ffff78a4660 in CseJtag_session_create () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libCseJtag.so
#31 0x00000000004eaf97 in JtagCable::openJtagCable() ()
#32 0x00000000004eb6ce in JtagCable::createJtagCable(SdkDebugDialog::CableOption*) ()
#33 0x000000000045b98d in tclBoardConnect ()
#34 0x000000000045bbd8 in createHardwareSystem ()
#35 0x000000000045c1a5 in tclPowerPCConnect ()
#36 0x000000000044c5b1 in tclConnect ()
#37 0x00007ffff725cc94 in TclInvokeStringCommand () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#38 0x00007ffff725e419 in TclEvalObjvInternal () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#39 0x00007ffff725e977 in Tcl_EvalEx () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#40 0x00007ffff725f3be in Tcl_EvalObjEx () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#41 0x00007ffff7265351 in Tcl_EvalObjCmd () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#42 0x00007ffff725e419 in TclEvalObjvInternal () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#43 0x00007ffff7286d80 in ?? () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#44 0x00007ffff728a0dd in TclCompEvalObj () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#45 0x00007ffff72b18f4 in TclObjInterpProc () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#46 0x00007ffff725e419 in TclEvalObjvInternal () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#47 0x00007ffff7286d80 in ?? () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#48 0x00007ffff728a0dd in TclCompEvalObj () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#49 0x00007ffff72b18f4 in TclObjInterpProc () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#50 0x00007ffff725e419 in TclEvalObjvInternal () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#51 0x00007ffff7286d80 in ?? () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#52 0x00007ffff728a0dd in TclCompEvalObj () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#53 0x00007ffff725f2ef in Tcl_EvalObjEx () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#54 0x00007ffff728ff79 in Tcl_RecordAndEvalObj () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#55 0x00007ffff728ffe5 in Tcl_RecordAndEval () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#56 0x00000000004409d5 in SdkTclIf::StdinProc(void*, int) ()
#57 0x00007ffff72963d1 in Tcl_NotifyChannel () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
---Type <return> to continue, or q <return> to quit---
#58 0x00007ffff72c9911 in ?? () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#59 0x00007ffff72a8195 in Tcl_ServiceEvent () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#60 0x00007ffff72a84e1 in Tcl_DoOneEvent () from /opt/xilinx/13.1/ISE_DS/ISE/lib/lin64/libtcl8.4.so
#61 0x000000000043deda in Tcl_Main_XMD(char, char*, int (*)(Tcl_Interp*)) ()
#62 0x000000000043e993 in main ()
(gdb) 

 Regards

 

Newbie
operion
Posts: 1
Registered: ‎12-19-2011
0

Re: Ubuntu 11.10 and impact, chipscope, etc.

thx for the info :smileyhappy:

OPERION
website marketing & design
Newbie
lotussx
Posts: 1
Registered: ‎02-14-2012
0

Re: Ubuntu 11.10 and impact, chipscope, etc.

Thanks for your debugging work. I am filing an internal CR on this issue.
Visitor
tharion
Posts: 5
Registered: ‎02-17-2010
0

Re: Ubuntu 11.10 and impact, chipscope, etc.

Hello,

 

I am using a Spartan6-LX9 Microboard from Avnet and had the same problem with Impact. I didn't want to use the Platform cable because the Microboard is small enough to carry everywhere and I didn't want to take the programmer along with me.

Since the Digilent Tools themselves work I searched further and found that apparently the dynamic linking of the libdpcomm.so.2 library from Digilent creates the segfault.

I found one solution to this problem, which appears to work on several installations: Setting the LD_PRELOAD environment variable to

 

LD_PRELOAD=/usr/local/lib64/digilent/adept/libdpcomm.so.2

 

For 32 bit systems the library can be found in the corresponding folder. This forces the libdpcomm library to be loaded at startup of the program. The needed memory address can then be found by Impact.

Removing the  Digilent_Plugin also stopped Impact from doing a segmentation fautl, but I needed the Digilent Plugin. This worked for me and at least one other user with a Nexys2 board.

I hope it helps to fix the problem in future releases

 

Cheers

Tobias

Visitor
tharion
Posts: 5
Registered: ‎02-17-2010
0

Re: Ubuntu 11.10 and impact, chipscope, etc.

Hi,

 

I forgot to mention:

The problem occured with a fresh install of the Digilent Plugin, the Adept runtime from Digilent and ISE 13.4.

 

Cheers

Tobias

Newbie
gronenberg
Posts: 1
Registered: ‎04-30-2012
0

Re: Ubuntu 11.10 and impact, chipscope, etc.

I encountered a similar (or the same?) problem using WebPack ISE 13.4 64 bit on openSUSE 11.4 64 bit:

 

Impact just closed itself when loading a file and gdb backtrace hinted in the same direction regarding the Digilent plugin.

 

Moving it out of the way eliminated the problem. I then installed the current plugin from Digilent (2.1.7 instead of 2.1.5 delivered as part of ISE 13.4) and the problem reoccured. As gdb output also pointed to Adept, I installed the current version from Digilent (2.9.9 instead of 2.7.4 delivered as part of ISE 13.4) and the problem disappeared.

 

It seems that, at least on my setup, the current versions of the Digilent plugin (2.1.7) and adept runtime (2.9.9) solve this problem.

 

Best regard, Arnd (DJ9PZ / AB2QP)