In HES-DVM, there are many factors which will be taken into the consideration to decide the maximum achievable runtime speed? The maximum delay in the data path reported/analyzed by Xilinx tools is one those factors. Is HES-DVM able to modify timing constraints automatically generated for P&R implementation process?


HES-DVM also allows for a “custom” implementation strategy in which the user fine tunes several emulation core options using environment variables.

Printed version of site: