Re: [fpgalink-users] errors when installing flcli in win.x64

[Chris McClelland]

The error is the result of an earlier failure which is not visible here. If you get errors, don't send screenshots, send the actual build log. You can rebuild from scratch and get a build log like this:

cd $HOME

rm -rf apps/* libs/* common

cd apps

msget.sh makestuff/flcli/20140524

cd flcli

(make deps 2>&1) > build.log

...then reply here with build.log attached.

Chris

On Tue, Mar 29, 2016 at 1:26 PM, Wang Jiangyue <jiangy...@gmail.com> wrote:

Dear Chris,

i am trying to use flcli to write data to an Atlys board, i am using windows 8 64-bit. And i followed the steps in the links below that you wrote from: https://gist.github.com/makestuff/7486988

when i start to fetch and build flcli, and when i go to line 69 :

     make deps

there are errors occurred, 

and when i go to the line 80 line

../../../../../../apps/flcli/msvc.x64/rel/flcli -v 1d50:602b:0002 -i 1443:0007 # x64

it shown bash: ../../../../../../apps/flcli/msvc.x86/rel/flcli :no such file or directory..

so what should i do to fix this problem?

Thank you very much,

Jiangyue

--
You received this message because you are subscribed to the "FPGALink Users" mailgroup (see https://github.com/makestuff/libfpgalink/wiki/FPGALink).
 
To post to this group, send email to fpgalin...@googlegroups.com
To unsubscribe from this group, send email to
fpgalink-user...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/fpgalink-users?hl=en
---
You received this message because you are subscribed to the Google Groups "FPGALink Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fpgalink-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Wang Jiangyue]

Dear Chris,

thank you so much for replying me so quick, and i am using the 20151202 version of flcli instead of 2014 one, will that be the problem?

and here is the build.log:

Fetching libbuffer/20151220 from GitHub...

wget -qO libbuffer.tgz --no-check-certificate https://github.com/makestuff/libbuffer/archive/20151220.tar.gz

tar xvzf libbuffer.tgz

libbuffer-20151220/

libbuffer-20151220/COPYING

libbuffer-20151220/COPYING.LESSER

libbuffer-20151220/Makefile

libbuffer-20151220/README

libbuffer-20151220/binio.c

libbuffer-20151220/conv.c

libbuffer-20151220/conv.h

libbuffer-20151220/core.c

libbuffer-20151220/hexio.c

libbuffer-20151220/libbuffer.h

libbuffer-20151220/misc.c

libbuffer-20151220/private.h

libbuffer-20151220/release.sh

libbuffer-20151220/tests/

libbuffer-20151220/tests/Makefile

libbuffer-20151220/tests/main.cpp

libbuffer-20151220/tests/testBinIO.cpp

libbuffer-20151220/tests/testConv.cpp

libbuffer-20151220/tests/testCore.cpp

libbuffer-20151220/tests/testHexIO.cpp

rm libbuffer.tgz

mv libbuffer-20151220 /c/makestuff/libs/libbuffer

echo 20151220 > /c/makestuff/libs/libbuffer/.branch

make -C /c/makestuff/libs/libbuffer/ BRANCH=20151220 deps

make[1]: Entering directory `/c/makestuff/libs/libbuffer'

Fetching liberror/20151220 from GitHub...

wget -qO liberror.tgz --no-check-certificate https://github.com/makestuff/liberror/archive/20151220.tar.gz

tar xvzf liberror.tgz

liberror-20151220/

liberror-20151220/COPYING

liberror-20151220/COPYING.LESSER

liberror-20151220/Makefile

liberror-20151220/README

liberror-20151220/liberror.c

liberror-20151220/liberror.h

liberror-20151220/tests/

liberror-20151220/tests/Makefile

liberror-20151220/tests/main.cpp

liberror-20151220/tests/testError.cpp

rm liberror.tgz

mv liberror-20151220 /c/makestuff/libs/liberror

echo 20151220 > /c/makestuff/libs/liberror/.branch

make -C /c/makestuff/libs/liberror/ BRANCH=20151220 deps

make[2]: Entering directory `/c/makestuff/libs/liberror'

make BRANCH=20151220

make[3]: Entering directory `/c/makestuff/libs/liberror'

mkdir -p msvc.x64

echo '-I${ROOT}/libs/liberror ' > msvc.x64/incs.txt

mkdir -p msvc.x64/dbg

(echo '${ROOT}/libs/liberror/msvc.x64/dbg/liberror.lib'; ) > msvc.x64/dbg/libs.txt

mkdir -p msvc.x64/dbg/.build

cl -Od -DBYTE_ORDER=1234 -DWIN32 -D_CRT_SECURE_NO_WARNINGS -EHsc -W4 -wd4127 -nologo -c -errorReport:prompt   -I. -I/c/makestuff/common   -D_DEBUG -D_WINDOWS -D_USRDLL -DLIBERROR_EXPORTS -D_WINDLL -RTC1 -MDd -Zi -Fomsvc.x64/dbg/.build/liberror.obj -Fdmsvc.x64/dbg/liberror.pdb liberror.c

liberror.c

link -OUT:msvc.x64/dbg/liberror.dll -INCREMENTAL -NOLOGO -DLL -MANIFEST -MANIFESTFILE:msvc.x64/dbg/liberror.dll.intermediate.manifest -MANIFESTUAC:"level='asInvoker' uiAccess='false'" -DEBUG -PDB:msvc.x64/dbg/liberror.pdb -SUBSYSTEM:WINDOWS -DYNAMICBASE -NXCOMPAT -MACHINE:x64 -ERRORREPORT:PROMPT msvc.x64/dbg/.build/liberror.obj   kernel32.lib user32.lib 

   Creating library msvc.x64/dbg/liberror.lib and object msvc.x64/dbg/liberror.exp

mt.exe -nologo -manifest msvc.x64/dbg/liberror.dll.intermediate.manifest "-outputresource:msvc.x64/dbg/liberror.dll;#2"

for i in  ; do cp -rp $i msvc.x64/dbg; done

mkdir -p msvc.x64/rel

(echo '${ROOT}/libs/liberror/msvc.x64/rel/liberror.lib'; ) > msvc.x64/rel/libs.txt

mkdir -p msvc.x64/rel/.build

cl -O2 -Oi -DBYTE_ORDER=1234 -DWIN32 -D_CRT_SECURE_NO_WARNINGS -EHsc -W4 -wd4127 -nologo -c -errorReport:prompt   -I. -I/c/makestuff/common   -DNDEBUG -D_WINDOWS -D_USRDLL -DLIBERROR_EXPORTS -D_WINDLL -GL -FD -MD -Gy -Zi -Fomsvc.x64/rel/.build/liberror.obj -Fdmsvc.x64/rel/liberror.pdb liberror.c

liberror.c

link -OUT:msvc.x64/rel/liberror.dll -INCREMENTAL:NO -NOLOGO -DLL -MANIFEST -MANIFESTFILE:msvc.x64/rel/liberror.dll.intermediate.manifest -MANIFESTUAC:"level='asInvoker' uiAccess='false'" -PDB:msvc.x64/rel/liberror.pdb -SUBSYSTEM:WINDOWS -OPT:REF -OPT:ICF -LTCG -DYNAMICBASE -NXCOMPAT -MACHINE:x64 -ERRORREPORT:PROMPT msvc.x64/rel/.build/liberror.obj   kernel32.lib user32.lib 

   Creating library msvc.x64/rel/liberror.lib and object msvc.x64/rel/liberror.exp

Generating code

Finished generating code

mt.exe -nologo -manifest msvc.x64/rel/liberror.dll.intermediate.manifest "-outputresource:msvc.x64/rel/liberror.dll;#2"

for i in  ; do cp -rp $i msvc.x64/rel; done

make[4]: Entering directory `/c/makestuff/libs/liberror/tests'

Fetching libutpp/20151220 from GitHub...

wget -qO libutpp.tgz --no-check-certificate https://github.com/makestuff/libutpp/archive/20151220.tar.gz

tar xvzf libutpp.tgz

libutpp-20151220/

libutpp-20151220/AssertException.cpp

libutpp-20151220/AssertException.h

libutpp-20151220/COPYING

libutpp-20151220/CheckMacros.h

libutpp-20151220/Checks.cpp

libutpp-20151220/Checks.h

libutpp-20151220/Config.h

libutpp-20151220/CurrentTest.cpp

libutpp-20151220/CurrentTest.h

libutpp-20151220/DeferredTestReporter.cpp

libutpp-20151220/DeferredTestReporter.h

libutpp-20151220/DeferredTestResult.cpp

libutpp-20151220/DeferredTestResult.h

libutpp-20151220/ExecuteTest.h

libutpp-20151220/Makefile

libutpp-20151220/MemoryOutStream.cpp

libutpp-20151220/MemoryOutStream.h

libutpp-20151220/PosixUtils/

libutpp-20151220/PosixUtils/SignalTranslator.cpp

libutpp-20151220/PosixUtils/SignalTranslator.h

libutpp-20151220/PosixUtils/TimeHelpers.cpp

libutpp-20151220/PosixUtils/TimeHelpers.h

libutpp-20151220/README

libutpp-20151220/ReportAssert.cpp

libutpp-20151220/ReportAssert.h

libutpp-20151220/Test.cpp

libutpp-20151220/Test.h

libutpp-20151220/TestDetails.cpp

libutpp-20151220/TestDetails.h

libutpp-20151220/TestList.cpp

libutpp-20151220/TestList.h

libutpp-20151220/TestMacros.h

libutpp-20151220/TestReporter.cpp

libutpp-20151220/TestReporter.h

libutpp-20151220/TestReporterStdout.cpp

libutpp-20151220/TestReporterStdout.h

libutpp-20151220/TestResults.cpp

libutpp-20151220/TestResults.h

libutpp-20151220/TestRunner.cpp

libutpp-20151220/TestRunner.h

libutpp-20151220/TestSuite.h

libutpp-20151220/TimeConstraint.cpp

libutpp-20151220/TimeConstraint.h

libutpp-20151220/TimeHelpers.h

libutpp-20151220/UnitTest++.h

libutpp-20151220/Win32Utils/

libutpp-20151220/Win32Utils/TimeHelpers.cpp

libutpp-20151220/Win32Utils/TimeHelpers.h

libutpp-20151220/XmlTestReporter.cpp

libutpp-20151220/XmlTestReporter.h

libutpp-20151220/docs/

libutpp-20151220/docs/UnitTest++.html

libutpp-20151220/tests/

libutpp-20151220/tests/Main.cpp

libutpp-20151220/tests/Makefile

libutpp-20151220/tests/RecordingReporter.h

libutpp-20151220/tests/ScopedCurrentTest.h

libutpp-20151220/tests/TestAssertHandler.cpp

libutpp-20151220/tests/TestCheckMacros.cpp

libutpp-20151220/tests/TestChecks.cpp

libutpp-20151220/tests/TestCurrentTest.cpp

libutpp-20151220/tests/TestDeferredTestReporter.cpp

libutpp-20151220/tests/TestMemoryOutStream.cpp

libutpp-20151220/tests/TestTest.cpp

libutpp-20151220/tests/TestTestList.cpp

libutpp-20151220/tests/TestTestMacros.cpp

libutpp-20151220/tests/TestTestResults.cpp

libutpp-20151220/tests/TestTestRunner.cpp

libutpp-20151220/tests/TestTestSuite.cpp

libutpp-20151220/tests/TestTimeConstraint.cpp

libutpp-20151220/tests/TestTimeConstraintMacro.cpp

libutpp-20151220/tests/TestUnitTest++.cpp

libutpp-20151220/tests/TestXmlTestReporter.cpp

rm libutpp.tgz

mv libutpp-20151220 /c/makestuff/libs/libutpp

echo 20151220 > /c/makestuff/libs/libutpp/.branch

make -C /c/makestuff/libs/libutpp/ BRANCH=20151220 deps

make[5]: Entering directory `/c/makestuff/libs/libutpp'

make BRANCH=20151220

make[6]: Entering directory `/c/makestuff/libs/libutpp'

mkdir -p msvc.x64

echo '-I${ROOT}/libs/libutpp ' > msvc.x64/incs.txt

mkdir -p msvc.x64/dbg

((echo '${ROOT}/libs/libutpp/msvc.x64/dbg/libutpp.lib'; for i in ; do cat $i 2>/dev/null; done); ) > msvc.x64/dbg/libs.txt

mkdir -p msvc.x64/dbg/.build

mkdir -p msvc.x64/dbg/.build/Win32Utils

cl -Od -DWIN32 -D_CRT_SECURE_NO_WARNINGS -EHa -W4 -nologo -c -errorReport:prompt -I/c/makestuff/common   -D_DEBUG -D_LIB -RTC1 -MDd -Zi -Fomsvc.x64/dbg/.build/AssertException.obj -Fdmsvc.x64/dbg/libutpp.pdb AssertException.cpp

AssertException.cpp

cl -Od -DWIN32 -D_CRT_SECURE_NO_WARNINGS -EHa -W4 -nologo -c -errorReport:prompt -I/c/makestuff/common   -D_DEBUG -D_LIB -RTC1 -MDd -Zi -Fomsvc.x64/dbg/.build/Checks.obj -Fdmsvc.x64/dbg/libutpp.pdb Checks.cpp

Checks.cpp

cl -Od -DWIN32 -D_CRT_SECURE_NO_WARNINGS -EHa -W4 -nologo -c -errorReport:prompt -I/c/makestuff/common   -D_DEBUG -D_LIB -RTC1 -MDd -Zi -Fomsvc.x64/dbg/.build/CurrentTest.obj -Fdmsvc.x64/dbg/libutpp.pdb CurrentTest.cpp

CurrentTest.cpp

cl -Od -DWIN32 -D_CRT_SECURE_NO_WARNINGS -EHa -W4 -nologo -c -errorReport:prompt -I/c/makestuff/common   -D_DEBUG -D_LIB -RTC1 -MDd -Zi -Fomsvc.x64/dbg/.build/DeferredTestReporter.obj -Fdmsvc.x64/dbg/libutpp.pdb DeferredTestReporter.cpp

DeferredTestReporter.cpp

c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\INCLUDE\intrin.h(26) : fatal error C1083: Cannot open include file: 'ammintrin.h': No such file or directory

make[6]: *** [msvc.x64/dbg/.build/DeferredTestReporter.obj] Error 2

make[6]: Leaving directory `/c/makestuff/libs/libutpp'

make[5]: *** [deps] Error 2

make[5]: Leaving directory `/c/makestuff/libs/libutpp'

make[4]: *** [/c/makestuff/libs/libutpp/msvc.x64] Error 2

make[4]: Leaving directory `/c/makestuff/libs/liberror/tests'

make[3]: *** [all] Error 2

make[3]: Leaving directory `/c/makestuff/libs/liberror'

make[2]: *** [deps] Error 2

make[2]: Leaving directory `/c/makestuff/libs/liberror'

make[1]: *** [/c/makestuff/libs/liberror/msvc.x64] Error 2

make[1]: Leaving directory `/c/makestuff/libs/libbuffer'

make: *** [/c/makestuff/libs/libbuffer/msvc.x64] Error 2

 

Chris McClelland於 2016年3月29日星期二 UTC+11下午11時49分20秒寫道：

[Chris McClelland]

No, the 20151220 release should also work fine.

If you google the actual error message you get taken to this KB: https://connect.microsoft.com/VisualStudio/feedback/details/660584/

...in which we see Microsoft admitting to breaking their own software with an update, and furthermore stating that they will not fix it because others have found "workarounds", namely, reinstalling the Windows SDK. You should try this workaround; if it fails, I suggest you ask on a MS-specific site, because you're unlikely to find Windows experts on this forum.

I've tried to make the build process as simple as possible on Windows, but as you can see, Microsoft are pretty incompetent. You will almost certainly have a less painful experience if you use a better OS.

Chris

[Wang Jiangyue]

Hi Chris,

Thank you very much for you advice, i will give it a shoot, if it fails i must change another OS.

And one more question, can i use visual studio instead of windows SDK?

Thanks 

Jiangyue

Chris McClelland於 2016年3月30日星期三 UTC+11上午12時08分39秒寫道：

[Chris McClelland]

> can i use visual studio instead of windows SDK

>

Yes, you can. If you have VS installed, there should be a corresponding entry (perhaps even two; one for x86 and another for x64) in the "Compilers" drop-down list when you run c:/makestuff/setup.exe. You can then create a desktop shortcut that uses the VS compiler rather than the SDK compiler.

Chris

[Michael Simmonds]

Hi Jiangyue,

I find myself in a similar situation, needing to compile flcli and its libraries for a Win7 system.
After much un-installing/re-installing of components, I was able to get the 7.1 SDK (and compatible DotNet 4 framwork) installed.

I suspect I will be running into the same problems with the SDK compilers that you reported. But Chris' liked the idea of using a VS compiler instead.
If you try doing it that way, please post anything you learn in the process.

[Michael Simmonds]

Chris,

FWIW, your Quickstart LX9 guide worked perfectly on my Win7 box when compiling with the 7.1 SDK.

My main problem was to get that SDK to install due to incompatibilities with MSVC++ 2010 runtimes and DotNet 4 framework versions.
Had to rip them all out and re-install DotNet 4 before the SDK would install. 

[Chris McClelland]

Hey Michael,

Yeah the instructions mention using the SDK 7.1, purely because that can be installed with a download of "only" a couple of hundred megabytes, whereas installing the full Visual Studio Express is well over a gigabyte. But the aim with the installer was to allow people to use whichever compiler they have installed. I've tested the build on Windows XP, 7, 8 and 8.1, with SDK7.1 and pretty much every release of Visual Studio since VS2010. The only Microsoft platform I've seen the FPGALink build fail on is Windows 10 (I have a Win10 cloud VM; I'll fix that when I get time).

I think the main problem is that FPGALink is designed to be a set of APIs. It's designed to be used by someone who not only understands electronics and FPGA development, but also some software engineering and command-line oriented development environment. I designed it like that on the assumption that people who are interested in FPGALink are interested in it because they want to build applications around it, incorporating some application software and some application VHDL or Verilog, with FPGALink forming the glue between. And I designed it like that because that's what I'm comfortable with, and I'm conceited enough to think that my way of doing things is the best way. But if I've learned one thing from this project, it's the realisation that everyone is different: two people may work in completely different ways, yet both will be effective. So there are people using FPGALink in ways I didn't intend, and I'm sure there are people NOT using FPGALink because they fall at the first hurdle. I suppose I could put the effort in to update the documentation and make it easier to get started, but it's kinda soul-destroying for me because it seems no matter what I do to make it easy, problems like this always crop up (usually with Windows, interestingly). I guess Windows is an environment that's very friendly to users, but incredibly hostile to developers (new developers especially). Conversely, Linux is an environment that's very friendly to developers but rather hostile to users (new users especially).

Chris

[Wang Jiangyue]

Hi Chris,

I have installed VS as the compiler, however, after i create the shortcut and click on it, the terminal window opens and suddenly disappears. 

Windows really got me, so now i am using ubuntu OS, and trying to installed it again, and there is another error occur when i go to line 22

../../../../../bin/hdlmake.py -t ../../templates/fx2all/vhdl -b atlys -p fpga

after this line, the terminal starts to running test, and it finished testing due to 

ERROR: THe xst process failed

i trying to find way of build.log, i used  script log.txt, but after i stop it , there is nothing in the txt file, so, wondering would you be able to help solve the error above without the log?

Thanks,

Jiangyue 

Chris McClelland於 2016年3月30日星期三 UTC+11上午12時48分01秒寫道：

[Chris McClelland]

On Windows, all the c:/makestuff/setup.exe installer does is create a desktop shortcut with the correct additions to PATH and one or two other environment variables. So if you right-click the created desktop shortcut and select "properties", then copy&paste the "target" text into a regular command prompt window, it should tell you what the problem is.

On Linux, it looks like you forgot to add the Xilinx installation directory to your PATH. You will want something like this in your .bash_aliases (or similar):

export PATH=${PATH}:/opt/Xilinx/14.7/ISE_DS/ISE/bin/lin64

Obviously this will be different depending on where you installed ISE, and whether you have installed a 64-bit OS or not.For a 32-bit OS, it's "bin/lin" rather than "bin/lin64".

Chris

[Chris McClelland]

> i am sorry to keep bothering you
>

Not at all. If my instructions don't work for you, then I should be apologising to you, not the other way around.

Your problem is that you ran line 25 as root (i.e "sudo ..."), so it succeeded, whereas you ran line 28 as yourself (i.e no "sudo ..."). I admit the error message you receive is misleading; it should be made clear that the reason for the failure is a permissioning problem. You *could* just run all the commands as root, but that's not ideal. A better solution is to tell the OS to allow specific users (including you) access to the FPGALink device. This is described in the manual, but broadly the process is:

1) Choose a group that you're a member of; running "groups" from the command-prompt will list them. I use "users".

2) As root, create the file "/etc/udev/rules.d/10-local.rules" with these two lines (or append them if the file already exists):

ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="1443", ATTR{idProduct}=="0007", GROUP="users", MODE="0660"
ACTION=="add", SUBSYSTEM=="usb", ATTR{idVendor}=="1d50", ATTR{idProduct}=="602b", GROUP="users", MODE="0660"

The first line tells the OS to allow members of the group "users" access to the USB device 1443:0007 (i.e the Atlys, on power-on). The second does a similar thing for the FPGALink device 1d50:602b. You can now restart udev service (with "sudo service udev restart"), or just reboot. Now you should be able to run each flcli command without needing "sudo".

Chris

On Sat, Apr 2, 2016 at 12:32 PM, Wang Jiangyue <jiangy...@gmail.com> wrote:

Hi Chris, 
it did work out after add the XIlinx installation directory to my PATH.
And i am sorry to keep bothering you, there is another problem occurred.

after running the code in line 25:
j@J~/20140524/makestuff/hdlmake/apps/makestuff/swled/cksum/vhdl$ sudo ../../../../../../apps/flcli/lin.x64/rel/flcli -v 1d50:602b:0002 -i 1443:0007
Attempting to open connection to FPGALink device 1d50:602b:0002...
Loading firmware into 1443:0007...
Awaiting renumeration....
Attempting to open connection to FPGLink device 1d50:602b:0002 again...
Connected to FPGALink device 1d50:602b:0002 (firmwareID: 0xFFFF, firmwareVersion: 0x20140311)

as you can see after line 25, i can be able to load fpgalink firmware into the atlys, however, when i go to line 28, it shown
j@J:~/20140524/makestuff/hdlmake/apps/makestuff/swled/cksum/vhdl$ ../../../../../../apps/flcli/lin.x64/rel/flcli -v 1d50:602b -p J:D0D2D3D4:fpga.xsvf
Attempting to open connection to FPGALink device 1d50:602b...
Could not open FPGALink device at 1d50:602b and no initial VID:PID was supplied

i also tried to program fpalink like u wrote in the uses manual:

wotan$ <PLATFORM>/rel/flcli -v <VID:PID> -i <VID:PID> -j <JTAG> -s \

    -x hdl/apps/makestuff/swled/cksum/vhdl/csvf/<TEMPLATE>-<BOARD>.csvf
things are still not working.

Chris McClelland於 2016年3月31日星期四 UTC+11上午4時42分36秒寫道：