Blog

The latest news from the Plunify team

One popular example of a custom Tcl script in InTime is one that automatically executes multiple InTime Recipes in a user-defined order. For example, you can create a Tcl script to run InTime Recipe in the order of Hot Start -> InTime Default -> Deep Dive -> Seed Effort Level Exploration When each recipe completes, […]

Continue Reading

In this blog post we evaluate the performance of Vivado 2016.4 and Vivado 2017.1 using InTime. Overall, we conducted three experiments pitting 2016.4 against 2017.1. Under our test conditions, Vivado 2017.1 achieves better results, albeit the difference was slight for Experiment 1. Total Negative Slack and Worst Slack in Vivado 2017.1 were much better in Experiments […]

Continue Reading

Ever wondered how efficient InTime when it is helping you and your team optimize FPGA designs? When using the InTime Private Cloud, are you curious about whether your team has sufficient licenses to meet performance targets on time? Is there a need to increase the number of licenses? These questions represent important metrics for decision maker(s) […]

Continue Reading

Introduction One of our most common customer requests is for a smaller number of compilation runs to get to timing closure. For example, can InTime meet timing in 50 runs instead of 100 on average? Well, that depends; InTime generally has an idea of what settings will help your design meet timing, and in rare cases […]

Continue Reading

For those who know our history, Plunify was born in the cloud. Our very first prototype of InTime was developed, executed and tested on Amazon Web Services. During those days, we only had to contend with EC2, EBS and S3. We even had to implement AES encryption in S3 ourselves (nowadays it is a checkbox!). […]

Continue Reading

If you are reading this, the odds are that you or someone in your company is facing / has faced FPGA design challenges. Timing closure is the single most important obstacle to implementing a successful FPGA application. Bruce Talley, former VP of Software at Xilinx and Plunify technical advisor, is one of the most qualified […]

Continue Reading

We are excited to announce the release of a new feature – Central Database (CD), in InTime. In previous versions of InTime, the visibility of compilation and analysis results is limited to individual users.  With CD, it gathers design data more efficiently across multiple users and different projects within your organization and enables sharing across different workstations and users. Below is […]

Continue Reading

Hi! We are happy to announce that InTime now supports the inheritance of Auto Placement assignments. This means that LogicLock or LogicLock Plus assignments created via the Auto Placement recipe will be passed onto its child revisions. For example, Tommy ran his design in InTime for three rounds. 1st round  : InTime Default 2nd round: Auto Placement 3rd […]

Continue Reading

Based on feedback, we understand that it is sometimes not easy for users to send us InTime log files when they encounter an issue. This is because the log files may contain what is seen as confidential information. In order to set our customers at ease, we have included a Tcl script to replace sensitive […]

Continue Reading

The Auto Placement recipe in InTime now supports Quartus Prime Pro Edition (in addition to Quartus-II and Quartus Prime Std Edition). Recall from Automatic placement adjustments in Quartus that the Auto Placement recipe analyses the locations of failing timing paths, and re-locates them based on what the tool learns about the design’s characteristics, without changing any source […]

Continue Reading