NI LabVIEW 2013 FPGA Module Xilinx Tools 10.1 Download Troubles

I am trying to download the  Xilinx Tools 10.1 to use with a 9113 chassis in LV2011.  Based on this white paper the compiler below should work just fine.  The problem is I can't get it to download all the way.
I can't seem to get past ~336MB using the standard or NI downloader.  Any ideas?  Anybody else having this problem?
http://www.ni.com/download/labview-fpga-module-2013/4249/en/
    thanks,
         -PBD
Solved!
Go to Solution.

Well... on the bright side, you don't want 10.1 anyway!
Virtex-5 LX50 <- REQUIRES Xilinx 14.4.
10.1 is only for Virtex-II devices! (...after LabVIEW 2009 that is, just so everyone reading this knows).
soo.... try this link: http://www.ni.com/download/labview-fpga-module-2013/4248/en/
Cheers!
TJ G

Similar Messages

  • NI Update Service: Upgrades & Service Packs: LabVIEW 2012 FPGA Module Xilinx Tools 10.1

    Hi,
    I downloaded / installed the newest LV 2012 release - everythin fine so far (its great )
    NI-Update Service proposed the installation of a service pack - download and installation worked too.
    NI-US also suggests to update the Xilinx tools for the FPGA module, but the download is not working. Seems like the download-link is broken??
    Any suggestions?
    Another interesting question: I live in Austria (German speaking), but we use Windows & LV entirely in English in our company. The NI-US however is heavily localized - even the item description is in German. While this is OK for me, I still wonder if I could change it to English too.
    (for the attachment: "Fehler beim Herunterl..." => "failed to download")
    -Benjamin
    CLA
    Solved!
    Go to Solution.
    Attachments:
    ni-us.png ‏23 KB

    Hi Benjamin,
    OK, I see, if the PC doesn't have any Xilinx tools installed at all, then Update Service will not offer you the update. It only displays upgrades to software that is already installed.
    This log from the other PC shows that the Xilinx 10.1 update fails to download, as your message said initially, but unfortunately it doesn't say anything more.
    We released a bunch of new updates last week, and since then there have been a few cases like this, but it doesn't seem widespread or easily reproducible. I can see in our server reports that other users successfully downloaded this update yesterday.
    I attached a downloader file that you can try. Unzip the file and run the exe. All it does is point to the same download location that Update Service is using to download this file. If the downloader works, then the problem is with Update Service. If the downloader doesn't work, then we'd know that something on our web servers isn't delivering this file properly.
    Also, if you happen to have any HTTP traffic monitoring software (like Fiddler), I'd be interested to know what it says is happening during the file download request.
    LaRisa Mohr
    Staff Product Support Engineer - NI Update Service
    National Instruments R&D
    Attachments:
    Xilinx10_1_downloader.zip ‏142 KB

  • Where can I find LabVIEW 2012 FPGA module

    Hi
    I uase LabVIEW 2012. Could you please let me know where can I find LabVIEW 2012 FPGA module to download?

    Where are you entering your serial number?  I am able to simply download it using the webpage:
    EDIT:
    You could also try downloading it with direct links:
    1. NI Downloader for FPGA Module 2012: http://download.ni.com/evaluation/labview/ekit/other/downloader/2012FPGA-Eng_downloader.exe
    2. Installer for FPGA Module 2012: http://download.ni.com/evaluation/labview/ekit/other/downloader/2012FPGA-Eng.exe
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    If someone helped you out, please select their post as the solution and/or give them Kudos!

  • Help Labview 2012 FPGA module

    Hi
    I have a project on Spartan 3e with Labview program but I can not install the driver cause of labview 2012 FPGA module
    Thanks

    Hi again 
    Why i can't download the fpga module on this link : http://www.ni.com/download/labview-fpga-module-201​2/3088/en/
    can anyone send me a link to download the module?
    Thanks 

  • Windows 8 and Labview 2013 FPGA

    I installed Labview 2013 including the FPGA design suite on a Windows 8 (x64) host. I was surprised to see Windows 8 on the list of supported OS as I was aware that up to this day no Xilinx design suite supported Windows 8.
    But as a matter of fact it didn't took long before I hit:
    ERROR: Simulator:861 - Failed to link the design
    following this tutorial while clicking on check syntax (using one of the VHDL file provided with the tutorial). The error is clearly linked to a lack of Windows 8 compatibility from the XIlinx tools running underneath. Is there a known workaround? Thanks.
    Solved!
    Go to Solution.

    That I could do but Linux is not listed here ... but Windows 8 is listed as supported for the farm server and not for the development environment. Isn't is the other way around? On top of that it looks like we should read GB instead of MB for the farm toolkit.

  • LabVIEW 2013 Fpga will not compile tutorial solutions

    Y'all
    I am working to get the CRIO evaluation software to compile the tutorial solutions.  so far it will not and complains about missing XILINX_EDK (warning.)  Attached is the xilinx log.     (Do I need to reinstall? or what)
    Thanks for help! 
    Sincerely,
    Paul
    Attachments:
    XilinxLog.txt ‏130 KB

    Hi Paul,
    What version of LabVIEW (2013/2013 SP1), LabVIEW FPGA and Xilinx Compile Tools do you have (or are you compiling on an external server)?
    Which example specifically are you trying to compile? You mentioned tutorials, but I'm not sure exactly what example you are referring to.
    Thanks!
    Xavier
    Applications Engineering Specialist
    National Instruments

  • LabVIEW 2013 SP1 Compile Worker Fails

    Hello,
    after receiving the new DVDs with LabVIEW 2013 SP1 and successfull installation, I wanted to compile my FPGA.vi.
    The Compile Worker does not start an I get the attached error Message. The additional Download of Xilinx Compilation tools 14.4 from the NI Website does not help.
    When I choose the FPGA Compilation Tools via the Start menu, the Compile Worker does not start. When I try to start the FPGACompileServerConfiguration an Error occurs (see picture).
    At the Moment I hav not Idea what to do. Perhaps someone can help.
    What does I have to do to convert my system back to the Version 2013?
    Attachments:
    FehlermeldungCompileWorker.jpg ‏41 KB
    ErrorwhenstartingFPGACompileServerConfiguration.jpg ‏15 KB

    dfschunk,
    Thanks for your post. We are aware of an issue with the compile tools installed from the 2014 developer suite (2013 sp1) where the compile worker is installed with missing dependencies. We are taking immediate action to push out a fix for this and you will receive a notification through NI update service when the fix is available.
    In the meantime, our recommendation is to downgrade to the 2013 installation of the Xilinx tools. No fixes were made between 2013 and 2013 sp1 in the compile worker or in the Xilinx tools so no worries there.
    Go to Control Panel >> Programs and Features and select National Instruments Software. 
    This will launch a window where you have the option to select various NI software products and modify/repair/remove them.
    Select NI LabVIEW FPGA Xilinx 14.4 Tools and select Remove.
    After the software has been un-installed, go to the NI LabVIEW 2013 FPGA Module Xilinx Tools 14.4 donwloads page and install this version of the tools (released with 2013) or you may install the tools from your original LabVIEW 2013 developer suite disks.
    Please post back or call support if you have any problems with this process, we want to make sure you are up and running until we push out a fix.
    Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

  • Bug in LabVIEW 2013 RTETT Download

    I've called this in to NI, but am posting it here in case you've downloaded LabVIEW 2013 before they fix the problem.
    Downloading the toolkits from ni.com/trylabview usually is a three-step process.  First, you download a "downloader", a small program (154 KB) that manages the download of the Installer.  When you run the Downloader, it downloads the Installer, usually as an executable ZIP file.  The final step is to run the Installer, which first unzips itself into a folder (by default, C:\National Instruments Downloads), then executes the unzipped Setup.exe contained therein.
    There is a (usually) consistent naming convention to these various files.  For example, the files for LabVIEW Real Time are 2013RealTime-Eng_Downloader, 2013RealTime-Eng (the Installer), and LabVIEW RT (the name of the folder that the Installer "unzips" into).  I've downloaded 8 modules, and (with the exception below) they all follow a similar pattern.
    The "bug" is in the Real Time Execution Trace Toolkit (RTETT).  The Downloader is 2013RTETT_downloader, and it brings in 2013RTETT as the Installer.  However, the Installer is set to unzip into LabVIEW RT, the same folder that is used for LabVIEW Real Time.  The "fix" is to change the name of the UnZip folder to LabVIEW Real Time Trace Execution Toolkit (this name is analogous to the LabVIEW Desktop Execution Trace Toolkit name for 2013DETT).  Alternatively, you can run one installer, rename the folder, run the other, and adjust the folder names to your liking.
    Bob Schor

    I am using Windows 7 (x64), fully patched.  As I understand it, the purpose of the Installers is two-fold -- to extract themselves to individual folders (by default in C:\National Instruments Downloads) and then to run their respective Setup executable to actually install themselves.
    I have not (yet) installed RTETT, but I have installed LabVIEW RealTime.  However, in the interest of time-efficiency, I first did downloads of all of the elements I wanted to install (which included both RealTime and RTETT), ran the Installer, but only the "extractor", then planned to run the actual installations from the folders in the Downloads folder.  That's when I discovered that the folder labelled LabVIEW RT did not contain LabVIEW Real Time, but LabVIEW Real Time Execution Trace Toolkit.  Thinking I'd forgotten to extract Real-Time, I tried extracting it again, and discovered that it and RTETT "shared" the same folder in NI Downloads.  I fixed the problem for myself by manually relabelling the folders so one was LabVIEW RT (for LabVIEW Real Time) and one was LabVIEW Real Time Execution Trace Toolkit.  With these distinctive names, I'm much less likely to install "the wrong thing".
    I consider this a "bug", as NI clearly (and logically) intended for the different Toolkits to be downloaded into their own folders.  I mentioned it here in case others faced a similar confusion of "Where did my download folder go?".  Note that if you only download Real Time or only download RTETT, the "reuse" of the folder name won't matter to you.
    BS

  • Labview 2010 Student Edition, will it work with the Labview FPGA module and Xilinx Spartan 3E??

    Just as the title states.
    I did a search here on compatibility, but I am coming up short with not much to show for it.
    I have Labview 2010 student edition, 32bit and 64 bit. I am trying to do a Senior Design project for my undergrad, and I am having some issues.
    I was able to download the Support for the Xilinx Spartan 3E and Labview FPGA.
    I install it, it runs through the unzipping process, installs, and then mysteriously I cannot find it. I have looked through my programs list and it is not listed. I open both editions of LabView and I find ABSOLUTELY NOTHING indicating that either one has ANYTHING to do with FPGA.
    Did I install it wrong? Or is it just not supported in the studend version of Labview???
    Can someone help me, please?

    M Boat wrote:
    What about the trial version? Any chance of it being on there?
    I think everything is available for download, and without activation it will be in trial mode and you have about a month (?) before the trial expires.
    A trial version of the FPGA module is available for download here. I have no idea if it would work with the student version.
    I would recommend to talk to your local NI sales representative for advice. Good luck.
    LabVIEW Champion . Do more with less code and in less time .

  • Labview fpga vs xilinx ise

    hi all 
    i am new to fpga and my question is fairly simple one which one is better ? 
    labview fpga or the xilinx ise platform ?
    or does it depend upon the application? 
    Regards
    Solved!
    Go to Solution.

    It always depends on the application.  Better in what way?
    I like programming in LabVIEW, so I think LabVIEW FPGA is a much better choice.  Learn just a little more than regular LabVIEW and you can program an FPGA!  Unless you have experience using ise, I suspect LabVIEW would be the easier route.
    If you are looking at price, maybe ise wins.  It isn't cheap to get buy LabVIEW and the FPGA module (and probably RT module) so you have all the tools.
    If the task is very complex, you might manage to make the program slightly more efficient using a lower level tool like ise.  You might shave off a few nanoseconds of loop time.  In 99.9% of the cases, this is unlikely.  LabVIEW code does a pretty good job converting over to FPGA.
    Bruce
    Bruce Ammons
    Ammons Engineering

  • LabVIEW FPGA: An internal software error in the LabVIEW FPGA Module has occurred

    Hi,
    I am trying to build a LabView FPGA VI. During compilation, I always get error stating "LabVIEW FPGA:  An internal software error in the LabVIEW FPGA Module has occurred.  Please contact National Instruments technical support at ni.com/support".  At the time, comiplation process is almost at the end.  "Final Timing (place and route)" shows as completed. When Checked the Xilinx log session, at the end it states that "  Process "Generate Programming File" completed successfully". However, I do not see any generated bitfile.
    When clicked on error details, it shows following: 
    LabVIEW: An unknown error occurred.
    Error -2629 occurred at Error occurred while loading XML string. Invoke Node in niFpgaXml_PrettyPrint.vi->niFpgaWriteBitfileXml_Core.vi->niFpgaCompileWorker_CreateBitfile.vi->niFpgaCompileWorker_JobComplete.vi->niFpgaCompile_Worker.vi:6460001
    Possible reason(s):
    LabVIEW: An unknown error occurred.
    I tried multiple times but so far no luck to generate bitfile for this VI.  What could be wrong here?
    I am using Labview 2013

    Hi Mark,
    Here is the device utilization Summary. My development system is running with Windows-7 (32 bit) with 3GB RAM and Labview 2013. 
    Device Utilization
    Total Slices: 90.0% (11970 out of 13300)
    Slice Registers: 40.7% (43258 out of 106400)
    Slice LUTs: 71.6% (38103 out of 53200)
    DSP48s: 1.4% (3 out of 220)
    Block RAMs: 22.1% (31 out of 140)
    Timing
    40 MHz Onboard Clock
    : 40.00 MHz (57.90 MHz maximum)
    80MHz (Used by non-diagram components)
    : 80.00 MHz (100.19 MHz maximum)
    --WillsG

  • How do I install Labview 64 bit support for the labview fpga module?

    see subject.

    Hi,
    The LabVIEW FPGA Module uses the 32-bit version of the Xilinx tools, even on the 64-bit OS.
    There is no 64 bit version of LabVIEW FPGA and you must have LabVIEW 32 bit
    installed on your 64-bit machine to use the compatible version of
    LabVIEW FPGA.
    NI LabVIEW FPGA Module will run within the 32-bit emulation layer, Windows on Windows (WOW64).
    regards,
    Houssam Kassri
    NI Germany

  • Why should I adopt LABVIEW FPGA as a tool for developing my FPGA projects?

    Dear Friends, 
    Since I have started using LABVIEW FPGA, I got too many questions in my mind looking for answers! 
    1-      Does anybody can tell me “why should I adopt LABVIEW FPGA as a tool for developing my FPGA projects?”
    I mean there are many great tools in this field (e.g. Xilinx ISE, ….); what makes LABVIEW FPGA the perfect tools that can save my time and my money? 
    I’m looking for a comparison can show the following points:
    ·         The Code size and speed optimization.
    ·         Developing time.
    ·         Compiling time.
    ·         Verifying time.
    ·         Ability to developing in future.
    ·         …etc.. 2-     
    I’ve Spartan-3E kit, I’m so glad that LABVIEW support this kit; I do enjoyed programming the kit using LABVIEW FPGA, but there are too many obstacles!
    The examples come with Spartan-3E driver don't cover all peripherals on board (e.g. LAN port is not covered)! There is a declaration at NI website which is "LabVIEW FPGA drivers and examples for all on-board resources" Located at: http://digital.ni.com/express.nsf/bycode/spartan3eI don’t think that is true!
    Anyway, I will try to develop examples for the unsupported peripherals, but if the Pins of these peripherals are not defined in the UCF file, the effort is worthless! The only solution in this case is to develop VHDL code in ISE and use it in Labview FPGA using HDL node!?
    3-      I wonder if NI has any plan to add support for Processor setup in Labview FPGA (Like we do in EDK)?
    4-      I wonder if NI has any plan to develop a driver for Virtex-5 OpenSPARC Evaluation Platform ?http://www.digilentinc.com/Products/Detail.cfm?Nav​Path=2,400,599&Prod=XUPV5 
    Thnaks & regards,Walid
    Solved!
    Go to Solution.

    Thanks for your questions and I hope I can answer them appropriately
    1. LabVIEW FPGA utilizes the intuitive graphical dataflow language of LabVIEW to target FPGA technology. LabVIEW is particularly nice for FPGA programming because of its ability to represent parallelism inherent to FPGAs. It also serves as a software-like programming experience with loops and structures which has become a focus of industry lately with C-to-gates and other abstraction efforts. Here are some general comparison along the vectors you mentioned
    Code Size and speed optimization - LabVIEW FPGA is a programming language. As such, one can program badly and create designs that are too big to fit on a chip and too slow to meet timing. However, there are two main programming paradigms which you can use. The normal LabVIEW dataflow programming (meaning outside a single-cycle loop) adds registers in order to enforce dataflow and synchronization in parity with the LabVIEW model of computation. As with any abstraction, this use of registers is logic necessary to enforce LabVIEW dataflow and might not be what an expert HDL programmer would create. You trade off the simplicity of LabVIEW dataflow in this case. On the other hand, when you program inside a Single-Cycle timed loop you can achieve size and speed efficiencies comparable to many VHDL implementations. We have had many users that understand that way LabVIEW is transformed to hardware and program in such a way to create very efficient and complex systems.
    Development Time - Compared to VHDL many of our users get near infinite improvements in development time due to the fact that they do not know (nor do they have to know) VHDL or Verilog. Someone who knows LabVIEW can now reach the speeds and parallelism afforded by FPGAs without learning a new language. For harware engineers (that might actually have an alternative to LabVIEW) there are still extreme time saving aspects of LabVIEW including ready-made I/O interfaces, Simple FIFO DMA transfers, stichable IP blocks, and visualizable parallism.  I talk to many hardware engineers that are able to drastically improve development time with LabVIEW, especially since they are more knowledgable about the target hardware.
    Compilation Time - Comparable to slightly longer to due to the extra step of generating intermediate files from the LabVIEW diagram, and the increased level of hierarchy in the design to handle abstraction.
    Verification Time - One of our key development initiatives moving forward is increased debugging capabilities. Today we have the abilities to functionally simulate anything included in LabVIEW FPGA, and we recently added simluation capabilities for Imported IP through the IP Integration node on NI Labs and the ability to excite your design with simulated I/O. This functional simualation is very fast and is great for verification and quick-turn design iteration. However, we still want to provide more debugging from the timing prespective with better cycle-accurate simulation. Although significantly slower than functional simulation. Cycle-accuracy give us the next level of verification before compilation. The single cycle loop running in emulation mode is cycle accurate simluation, but we want more system level simulation moving forwrad. Finally, we have worked to import things like Xilinx chipscope (soon to be on NI Labs) for on-chip debugging, which is the final step in the verification process. In terms of verification time there are aspects (like functional simulation) that are faster than traditional methods and others that are comparable, and still other that we are continuing to refine.
    Ability to develop in the future - I am not sure what you mean here but we are certainly continuing to activiely develop on the RIO platform which includes FPGA as the key diffentiating technolgoy.  If you take a look at the NI Week keynote videos (ni.com/niweek) there is no doubt from both Day 1 and Day 2 that FPGA will be an important well maintained platform for many years to come.
    2. Apologies for the statement in the document. The sentence should read that there are example for most board resources.
    3. We do have plans to support a processor on the FPGA through LabVIEW FPGA. In fact, you will see technology on NI Labs soon that addresses this with MicroBlaze.
    4. We do not currently have plans to support any other evaluation platforms. This support was created for our counterparts in the academic space to have a platform to learn the basics of digital design on a board that many schools already have in house. We are currently foccussing on rounding out more of our off-the-shelf platform with new PCI Express R Series boards, FlexRIO with new adapter modules, cRIO with new Virtex 5 backplanes, and more.
     I hope this has anwered some of the questions you have.
    Regards 
    Rick Kuhlman | LabVIEW FPGA Product Manager | National Instruments | ni.com/fpga
    Check out the FPGA IPNet for browsing, downloading, and learning about LabVIEW FPGA IP Cores

  • How can I install (download) a Labview FPGA code onto Altera FPGA chip using Labview FPGA module?

    Hi there
    Guys i'm a very new labview user (PhD student), my project is about ( design and implementation of a high speed-yet sophisticated system using Labview environment then install this project's code (using Labview FPGA module) onto Altera-made FPGA chip).
    so kindly, can any body help me in this?...is there any way to connect labview with Altera FPGA?...please anything would be said 'd be of great benifits
    thanks a lot in advance.

    as previously mentioned, labview fpga only supports national instruments targets utilizing xilinx fpgas. the hdl generated by labview fpga is encrypted and cannot be used to synthesize a design outside the labview fpga design flow. 
    however, if you must use labview for your project, it might be possible for you to design the system in labview and use one of the labview embedded modules ( http://www.ni.com/embedded )to generate c code which you can then port to systemc and compile for the altera fpga. i'm not saying it will be easy, but it should be possible. 

  • Labview fpga module Spartan 6 LX9 FPGA

    Does Spartan 6 LX9 FPGA  supported in labview FPGA module ?

    varunme,
    The only FPGA targets that can be programmed with LabVIEW FPGA are National Instruments FPGA products (cRIO, sbRIO, R-Series, FlexRIO, etc) and the Xilinx Spartan 3E XUP board. Unfortunately, LabVIEW FPGA doesn't support third party devices containing the LX9 FPGA.
    -Nick-
    Nick C | Staff LabVIEW Platform Product Support Engineer | National Instruments

Maybe you are looking for