InTime Software

Auto-detect FPGA toolchain and license information

95 views August 24, 2017 February 25, 2020 pohheng 0

Introduction:

Starting from version 2.4, InTime introduced an automated method of configuring toolchains and licenses. InTime is able to read existing environment variables and use any toolchain that has been set up in that environment. When starting InTime, use a new command argument -tc <toolchain name>, where <toolchain name> is: "quartusii", "quartuspp", "ise", and "vivado" depending on the FPGA tool that you have configured.

Example: Vivado

[user@host]$ source /mnt/opt/Xilinx/2016.1/Vivado/2016.1/settings64.sh
[user@host]$ /mnt/opt/tools/intime/intime.sh -tc vivado

After InTime starts, go to File > Settings > Vendor Toolchain...

Screen Shot 2017-08-24 at 09.36.48

Example: Quartus

Here is another way for a toolchain that does not need the user to 'source' an included script. You can also automate the following commands in .bashrc or other script.

[user@host]$ TOOL=/mnt/opt/Altera/16.0.0/quartus/bin
[user@host]$ export PATH=$TOOL:$PATH
[user@host]$ export LM_LICENSE_FILE=12345@192.168.0.1
[user@host]$ /mnt/opt/tools/intime/intime.sh -tc quartusii

After InTime starts, go to File > Settings > Vendor Toolchain...

Screen Shot 2017-08-24 at 09.54.48

Note: InTime reads and applies the LM_LICENSE_FILE environment variable from the shell where InTime was invoked.

The -tc <toolchain name> argument overrides all previously-configured toolchain settings.
If you would like to revert to a previously-configured toolchain, exit InTime and start InTime without the -tc <toolchain name> argument.

Applies to:

  • Linux Operating System
  • Windows Operating System

Knowledge Base ID: 201708241 - Last Review: Aug 24, 2017 - Revision: 1.0