InTime 2.4 Release

Blog Tag_new2

Besides fixing a few bugs, for example, in the Clock Margin recipe introduced in version 2.3,  the new features for InTime 2.4 mainly focus on providing more convenience and enhancing usability. Here is a quick summary.

Auto detect FPGA tool chain and license information

One of the biggest issues faced by users in large organizations is the array of different setups created by individual departments for their tools. Sometimes we need to source the right scripts, e.g. settings64.csh, or set up multiple environment variables to be able to run the right FPGA software version and license. InTime 2.4 introduces a new argument to ensure it can auto-detect the current FPGA toolchain and license that you want to use for the current project. Get more information from our Knowledge Base  article — Auto-detect FPGA toolchain and license information

Use LM_LICENSE_FILE to specify InTime Server location

Most customers use environment variables to specify their flexLM license server. Similarly, you can now enter 39940@x.x.x.x in the same variable for the InTime Server. InTime will pick up the port number 39940 (for InTime server) and auto configures the client to use it. This works well when you have multiple agents running and you just want to perform the InTime Private Cloud setup once.

Preview your results directly on InTime Server

After firing off multiple jobs from InTime, you might not want to download all the results due to slow network speeds or prohibitive bandwidth costs. By executing the following command on the Private Cloud Console,

.result=<jobid>

you will get a summary of the results and decide specifically what to download. See the corresponding Knowledge Base article – Preview results in Private Cloud Console

More support for Stratix 10

Although Quartus Prime Pro 17.1 is not officially released yet, we provide support for Stratix 10 in the Early Access version due to customer demand. Feel free to contact us to evaluate a copy of InTime for Stratix 10 devices.

Leave A Comment

*
*