• Content Count

  • Joined

  • Last visited

Everything posted by cramcram

  1. Hi @attila Added it to the Makefile but I got the same result. armv7l-timesys-linux-gnueabi-g++ '-D_GLIBCXX_USE_CXX11_ABI=0' -O3 -Wall -I../include -I../include -I../drivers -DCPC_TARGET -I ./Digilent/digilent.adept.sdk_2.4.2/inc -L ./Digilent/digilent.adept.runtime_2.19.2-armhf/data/usr/lib/digilent/adept -ldjtg -ldmgr -ldpcutil -ldpcomm -ldepp -ldspi -ldstm -ldpio -ldabs -ldftd2xx -o DjtgDemo DjtgDemo.cpp ./Digilent/digilent.adept.runtime_2.19.2-armhf/data/usr/lib/digilent/adept/ undefined reference to `operator delete(void*, unsigned int)@CXXABI_1.3.9' collect
  2. Linux cpc1 4.4.0-ts-armv7l-xilinx #8 SMP PREEMPT Fri Jul 29 14:24:19 PDT 2016 armv7l GNU/Linux I've seen other postings on the net that say to link with -lstdc++ or use -fdefine-sized-deallocation or variants of this. Nothing gets me past the error message however. Thanks, Marc
  3. Hi, We have a custom embedded board with a Zynq processor. There is a JTAG-SMT2 on the board connected to the JTAG chain of other boards. We want to use this for Fpga configuration as well as remote ChipScope debugging. I think I've the runtime code installed correctly (/dev/ptmx is created when the JTAG-SMT2 is detected). But I can't compile the DjtgDemo program to compile: armv7l-timesys-linux-gnueabi-gcc-color -O3 -Wall -I../include -I../include -I../drivers -DCPC_TARGET -I ./Digilent/digilent.adept.sdk_2.4.2/inc -L ./Digilent/digilent.adept.runtime_2.19.2-armhf/data/usr
  4. Hi, We're designing several boards that have a mixture of XIlinx Fpgas. One such board has multiple Virtex 5's, a Kintex 7 and a Spartan 6. We want to use a JTAG-SMT2 board to both configure the Fpgas and then use Chipscope for debugging. This means that all the Fpgas would be on a single JTAG chain. Has this been done before? Should a configuration like this work? We would be driving (via USB) the JTAG-SMT2 from an embedded linux processor and use the ADEPT SDK for configuration as well as implementing USB over Ethernet so that the Xilinx debug tools could run seamlessly on