The software may issue the following messages during flow execution.
ConnectionProfileOpenFailed (Error)
| Message |
Failed to open connection profile {} |
| Decsription |
Failed to open connection profile |
DeprecatedOption (Warning)
| Message |
Use of efx_pnr option '{}' is deprecated |
| Decsription |
Deprecated efx_pnr option. |
EfinityHomeUnset (Error)
| Message |
The environment variable EFINITY_HOME is not set. Please run '{}' before launching Efinity executables and scripts |
| Decsription |
The environment variable EFINITY_HOME is not set. Refer to the Efinity Quick Start topic for instructions. |
EfxSSLInitFailed (Error)
| Message |
Failed to initialise the SSL encryption library: {} |
| Decsription |
The Efinity software has failed to initialise the SSL encryption library. |
EfxStaFailedToCreateWorkDir (Error)
| Message |
Failed to create temporary work directory '{}'. Please ensure there is sufficient disk space and filesystem permissions |
| Decsription |
The Efinity software has failed to create a temporary work directory. |
EfxStaFailedToWriteWorkFile (Error)
| Message |
Failed to write temporary work file '{}'. Please ensure there is sufficient disk space and filesystem permissions |
| Decsription |
The Efinity software has failed to write a temporary work file. |
EfxStaLoadDatabasesFailed (Error)
| Message |
Failed to load the post-route design databases. Please ensure the design has been fully compiled before running the Efinity Static Timing Analysis Tool |
| Decsription |
The Efinity software has failed to load the post-route design databases. |
EfxStaMissingAction (Error)
| Message |
At least one operation must be specified. Supported operations include: {} |
| Decsription |
At least one operation must be specified |
EnteringTclInteractiveShell (Info)
| Message |
Entering Tcl interactive shell |
| Decsription |
Efinity is entering the Tcl interactive shell |
EvaluatingTclScript (Info)
| Message |
Evaluating user specified Tcl script '{}' |
| Decsription |
Efinity is evaluating the specified Tcl script |
ExitingTclInteractiveShell (Info)
| Message |
Exiting Tcl interactive shell |
| Decsription |
Efinity is exiting the Tcl interactive shell |
FailedToFindInstanceInNetPath (Error)
| Message |
Cannot find inst '{}' in net '{}' connect path |
| Decsription |
Failed to find instance in net path |
FailedToFindNetlistItem (Error)
| Message |
failed to find {} {} |
| Decsription |
Failed to find netlist item |
FailedToFindNetlistItemWithCommand (Error)
| Message |
Cannot find {} '{}'. command: '{}' |
| Decsription |
Cannot find netlist item |
FailedToFindPort (Error)
| Message |
Cannot find port {} with width {} |
| Decsription |
Cannot find port |
FailedToReadMaplibFile (Error)
| Message |
Failed to read maplib {} |
| Decsription |
Failed to read maplib file |
FlowBitstreamSupportNotAvailable (Warning)
| Message |
Bitstream support for this device not available. No bitstream file(s) will be generated |
| Decsription |
The Efinity software cannot generate a bitstream for this device. Bitsteram support will be available in a future software version. |
FlowDeleteXmlReportFileFailed (Warning)
| Message |
Fail to delete XML report file {}. Error : {} |
| Decsription |
The Efinity software has failed to delete the specified XML report file. |
FlowDumpPrimitiveTimingAfterRouting (Info)
| Message |
Dump primitive timing after routing |
| Decsription |
Dump primitive timing after routing |
FlowFailedToOpenLogFile (Warning)
| Message |
Failed to open log file '{}' for writing: {}. File logging will be disabled for this run |
| Decsription |
The Efinity software has failed to open a log file. File logging will be disabled for this compilation. |
FlowIgnoreAutoTimingTradeoff (Warning)
| Message |
Ignoring auto_timing_tradeoff since timing_tradeoff is explicitly set to: {} |
| Decsription |
Ignoring auto_timing_tradeoff since timing_tradeoff is explicitly set |
FlowLeadRouteLoading (Info)
| Message |
Since load_route option is applied, VPR loads existing .place and .route files |
| Decsription |
Since load_route option is applied, VPR loads existing .place and .route files |
FlowMappedClbDimensions (Info)
| Message |
The circuit will be mapped into a {} x {} array of clbs |
| Decsription |
Shows the mapped clb dimensional array size. |
FlowPreparingXmlReportFile (Info)
| Message |
Prepare XML report data, file {} |
| Decsription |
The Efinity software is preparing the specified XML report file. |
FlowReportHighResourceUtilization (Info)
| Message |
High resource utilization found. Software will optimize placement for routability |
| Decsription |
High resource utilization found. Software will optimize placement for routability |
FlowReportReplaced (Warning)
| Message |
{} will be removed and replaced with data in the current run |
| Decsription |
The Efinity software will delete the specified file and replace it during compilation. |
FlowReportTimingTradeoffExceedLimits (Info)
| Message |
This run will use the nearest allowable timing_tradeoff value {} |
| Decsription |
This run will use the nearest allowable timing_tradeoff value |
FlowReportUtilization (Info)
| Message |
The architecture has {} {}. Total {} utilization : {} % |
| Decsription |
The device utilization is displayed. |
FlowReportUtilizationExceedLimits (Info)
| Message |
{} utilization {} % for architecture's device count {} exceeds the allowable limits |
| Decsription |
The design uses too many XLR cells for the target device. |
FlowReportUtilizationIndex (Info)
| Message |
utilization_index : {} and arch_size_index : {} |
| Decsription |
Utilization indexes information is displayed. |
FlowReportUtilizationIndexExceedLimits (Info)
| Message |
New utilization_index : {} and arch_size_index : {} just to get this run going |
| Decsription |
Utilization indexes to get this run going |
FlowReportUtilizationNearlyExceedLimits (Info)
| Message |
High resource utilization found. Software will optimize placement for routability |
| Decsription |
High resource utilization found. Software will optimize placement for routability |
FlowReportUtilizationNearlyExceedLimitsDetailed (Info)
| Message |
The {} utilization {} % for architecture's device count {} nearly exceeds the allowable limits. Still proceeding with placement |
| Decsription |
The EFL+EFT+EFM utilization almost exceeds the allowable limits |
FlowReportWriteFailed (Error)
| Message |
Failed to write to report file '{}' |
| Decsription |
Failed to write to report file |
FlowResettingTimingTradeoff (Info)
| Message |
Resetting timing_tradeoff since auto_timing_tradeoff on is set: |
| Decsription |
Resetting timing_tradeoff since auto_timing_tradeoff on is set |
FlowResettingTimingTradeoffNewValue (Info)
| Message |
{} {}: The timing_tradeoff was {}. New timing_tradeoff is {} |
| Decsription |
The new timing_tradeoff value has been displayed |
FlowTRouteFlowNotSupportedForTrion (Warning)
| Message |
troute router flow (--run_troute) is not yet supported for Trion devices. Reverting to correct router flow and continuing |
| Decsription |
The Efinity software is using the correct routing flow for Trion FPGAs. |
FlowV1RouterOverride (Warning)
| Message |
Forcing use of deprecated V1 Router Flow due to run_v1_router=true |
| Decsription |
The Efinity software is using the V1 router flow. No action needed. |
FlowVerboseOptionEnaabled (Warning)
| Message |
Verbose option is used. More messages would appear and the run would likely be slower |
| Decsription |
With the verbose option turned on, the software issues more messages, resulting in longer compilation time. |
FlowWriteXmlReportFileFailed (Warning)
| Message |
Fail to write XML report file {}. Exception : {} |
| Decsription |
The Efinity software has failed to write the specified XML report file. |
FlowWritingXmlReportFile (Info)
| Message |
Write XML report file {} |
| Decsription |
The Efinity software is writing the specified XML report file. |
FlowXmlReportAddingCoreResourceGroup (Info)
| Message |
Add xml report group : Core Resource |
| Decsription |
Add Core Resource xml report group |
GroupOptions (Info)
| Main Message |
{} Options: |
| Action |
Group options. |
| Sub-Message |
{} : {} |
| Decsription |
Option description. |
HelpUsage (Info)
| Message |
Usage: {} [Options ...] |
| Decsription |
Help text. |
INIPnROptionIgnored (Warning)
| Message |
Ignored place and route setting '{}' from the settings file; This option may not be specified in the context of a settings file |
| Decsription |
A setting has been ignored. |
InvalidCommandLineOption (Error)
| Message |
Invalid command line option(s) : {} |
| Decsription |
The command line option(s) provided to the Efinity software is invalid |
InvalidInstanceNames (Error)
| Main Message |
The given design contains names with reserved characters. {} are reserved characters |
| Action |
The given design contains names with reserved characters. |
| Sub-Message |
Name '{}' contains reserved character(s) |
| Decsription |
Invalid name. |
InvalidOperatingConditionOption (Warning)
| Message |
Specified Operating Condition ({}) is invalid. Will set to the default model ({}) |
| Decsription |
The specified Operating Condition is not a valid option for the current device. |
InvalidOptimizationLevel (Warning)
| Main Message |
Ignoring option 'optimization_level={}' as it is not a valid optimization level |
| Action |
The specified --optimization_level option is not a valid value. |
| Sub-Message |
Supported options: {} |
| Decsription |
List of supported --optimization_level options. |
InvalidPartCellPlaceCnst (Error)
| Main Message |
Invalid placement location constraint(s) have been specified on cells contained within partitions |
| Action |
Invalid placement location constraint(s) have been specified on cells contained within partitions. |
| Sub-Message |
Non-interface cell '{}' in partition '{}' has been assigned to location ({}, {}), which is on the perimeter of the partition bounding box {{ {} }} |
| Decsription |
Invalid placement constraint. |
| Sub-Message |
Interface cell '{}' in partition '{}' has been assigned to location ({}, {}), which is not on the perimeter of the partition bounding box {{ {} }} |
| Decsription |
Invalid placement constraint. |
| Sub-Message |
Cell '{}' in partition '{}' has been assigned to location ({}, {}), which is outside the partition bounding box {{ {} }} |
| Decsription |
Invalid placement constraint. |
MaplibFileNotDefined (Error)
| Message |
Maplib file not defined |
| Decsription |
Maplib file not defined |
MaxThreads (Info)
| Message |
Maximum concurrency has been set to {} |
| Decsription |
The Efinity software will perform compilation with the specifed concurrency level. |
NoConnectionProfileSpecified (Error)
| Message |
No connection profile specified |
| Decsription |
No connection profile specified |
NoModuleOrDesignUnitFound (Error)
| Message |
No module or design unit {} found |
| Decsription |
No module or design unit found |
NoRootDesignNameSpecified (Error)
| Message |
No root design name specified |
| Decsription |
No root design name specified |
NoRootSpecifiedWithRootArchSet (Error)
| Message |
No root specified with root-arch set |
| Decsription |
No root specified with root-arch set |
NoVdbFileSpecified (Error)
| Message |
No VDB file specified |
| Decsription |
No VDB file specified |
OptimizeCongEnabled (Info)
| Message |
Optimizing for congestion improvement |
| Decsription |
Optimizing for congestion improvement. |
PartitionBBoxAdjacent (Error)
| Message |
The bounding box specified for partition '{}' is adjacent to that of partition '{}' |
| Decsription |
Two adjacent bounding boxes have been detected in a partition definition file. |
PartitionBBoxAlignment (Error)
| Message |
y_min and/or y_max of the bounding box in '{}' are not aligned to the clock network |
| Decsription |
y_min and/or y_max of a bounding box are not aligned to the clock network |
PartitionBBoxCoordOutsideOfChip (Error)
| Message |
The bounding box specified for partition '{}' has coordinates which fall outside of the chip dimensions. The bounding box coordinates are x: [{}, {}), y: [{}, {}). The chip dimensions are x: [0, {}), y: [0, {}) |
| Decsription |
Bounding box coordinates detected which lie outside of the chip dimensions. |
PartitionBBoxIllegalCoord (Error)
| Message |
The bounding box specified for partition '{}' has coordinates which do not meet the conditions x_min < x_max and y_min < y_max. The actual coordinates are x_min: x: [{}, {}), y: [{}, {}) |
| Decsription |
Bounding box coordinates detected which do not meet the basic conditions: x_min < x_max and y_min < y_max |
PartitionBBoxIllegalHeight (Error)
| Message |
The bounding box specified for partition '{}' has an illegal height (i.e. a height that is not a multiple of 40) |
| Decsription |
A bounding box with an illegal height has been detected in a partition definition file. |
PartitionBBoxOverlap (Error)
| Message |
The bounding box specified for partition '{}' overlaps that of partition '{}' |
| Decsription |
Two overlapping bounding boxes have been detected in a partition definition file. |
PartitionBBoxSideOnNonXLRColumnErr (Error)
| Message |
The {} side of the bounding box for partition '{}' sits on a {} column |
| Decsription |
Either the x_min or x_max-1 value of the bounding box for a given partition lines up with a non-XLR column. Please adjust the bounding box for this partition. |
PartitionBBoxSideOnNonXLRColumnWarn (Warning)
| Message |
The {} side of the bounding box for partition '{}' sits on a {} column. This may reduce the number of available sites for partition interfaces, and may negatively affect the routability of the design |
| Decsription |
Either the x_min or x_max-1 value of the bounding box for a given partition lines up with a non-XLR column. This may reduce the number of available sites for partition interfaces, and may negatively affect the routability of the design. We recommend adjusting the bounding box for this partition. |
PartitionBBoxSideOnNonXLRRow (Error)
| Message |
The {} side of the bounding box for partition '{}' sits on a {} row |
| Decsription |
Either the y_min or y_max-1 value of the bounding box for a given partition lines up with a non-XLR row. Please adjust the bounding box for this partition. |
PartitionBBoxWidth (Error)
| Message |
The bounding box specified for partition '{}' must have width of at least {} |
| Decsription |
Bounding box with insufficient width detected |
PartitionClockInterfaceDangling (Error)
| Message |
Clock interface '{}' on partition '{}' is not driven |
| Decsription |
A partition clock interface is not driven. All partition clock interfaces must be driven. |
PartitionClockInterfaceLocationConstrained (Error)
| Message |
Clock interface '{}' on partition '{}' has been assigned a location constraint |
| Decsription |
A partition clock interface has been assigned a location constraint. Location constraints may not be specied on clock interfaces. |
PartitionDeclarationFileUsedDuringExport (Error)
| Message |
A partition declaration file '{}' is specified during a team-based-design export compile. Specify a partition definition file with partition bounding boxes instead |
| Decsription |
A partition declaration file is specified during a team-based-design export compile. A partition definition file with partition bounding boxes is required during the team-based-design export stage. |
PartitionDefinitionBBoxesIgnoredDuringImport (Warning)
| Message |
Partition bounding boxes specified in partition definition file '{}' are ignored during the team-based-design import compile |
| Decsription |
Partition bounding boxes specified in partition definition file are ignored during the team-based-design import compile. |
PartitionHierPathMapping (Info)
| Message |
Partition '{}' mapped to design hierarchy path '{}' |
| Decsription |
The specified partition has been matched to a design hierarchy path. |
PartitionHierarchyNotFound (Error)
| Message |
Partition '{}' assigned to unknown hierarchy path '{}' |
| Decsription |
A partition has been assigned to a hierarchy path that does not exist in the design. |
PartitionMissingIfaceCells (Error)
| Message |
Partition '{}' does not contain any interface cell. This is likely because the Synthesis stage was not performed with the same partition declaration file |
| Decsription |
A partition does not contain any interface cell. This is likely because the Synthesis stage was not performed with the same partition declaration file. Rerun the Synthesis stage with the --partitions option to resolve this issue. |
PartitionNesting (Error)
| Message |
The hierarchy path specified for partition '{}' shares a common prefix with that of partition '{}' |
| Decsription |
Hierarchy paths with common prefixes have been detected in a partition definition file. |
PhysicalSynthesisInstanceDoesNotExist (Warning)
| Message |
The instance: {} does not exist in the current netlist |
| Decsription |
The instance in the physical-synthesis split_net command does not exist. |
PhysicalSynthesisLoadGroupsNotArray (Warning)
| Message |
The load_groups field must be an array |
| Decsription |
The load_groups field must be an array. |
PhysicalSynthesisLoadsMissing (Error)
| Message |
There are missing loads for the split_net command for net: {} |
| Decsription |
There are missing loads in the split_net command. All sinks of the given net must be specified in load_groups. |
PhysicalSynthesisMissingInstancePortRefLoads (Error)
| Message |
The physical_synthesis 'split_net' command is invalid. The net: {} is missing a load for portref: {} on instance: {} |
| Decsription |
There are missing instance or portref loads in the split_net command. All sinks of the given net must be specified in load_groups. |
PhysicalSynthesisMissingPortLoads (Error)
| Message |
The physical_synthesis 'split_net' command is invalid. The net: {} is missing a load for top-port: {} |
| Decsription |
There are missing top-port loads in the split_net command. All sinks of the given net must be specified in load_groups. |
PhysicalSynthesisNetDoesNotExist (Warning)
| Message |
The net: {} does not exist in the current netlist |
| Decsription |
The net in the physical-synthesis split_net command does not exist. |
PhysicalSynthesisNoLoads (Error)
| Message |
There are no loads specified in the split_net command |
| Decsription |
There are no loads specified in the split_net command. |
PhysicalSynthesisPortDoesNotExist (Warning)
| Message |
The port: {} does not exist in the current netlist |
| Decsription |
The port in the physical-synthesis split_net command does not exist. |
PhysicalSynthesisPortRefDoesNotExist (Warning)
| Message |
The portref: {} on instance: {} does not exist in the current netlist |
| Decsription |
The portref specified for the instance in the physical-synthesis split_net command does not exist. |
PhysicalSynthesisSplitNetFail (Warning)
| Message |
The physical_synthesis 'split_net' has failed for net: {}. Skipping this command |
| Decsription |
Unable to complete split_net command. Skipping command and moving to next. |
PhysicalSynthesisSplitNetSuccess (Info)
| Message |
Successfully processed the split_net command for net: {} |
| Decsription |
Successfully processed the split_net command for the current net. |
PhysicalSynthesisVerificationFail (Warning)
| Message |
Verification failed after split_net command. Skipping the split_net command for net: {} |
| Decsription |
Verification failed after split_net command. Skipping this split_net command. |
PrjXMLOptionOverriden (Info)
| Message |
The project XML setting '{}' has been overriden from the command line |
| Decsription |
A project XML setting has been overriden from the command line. |
PrjXMLPnROptionIgnored (Warning)
| Message |
Ignored place and route setting '{}' from the project XML file; This option may not be specified in the context of a project XML file |
| Decsription |
A project XML setting has been ignored. |
PrjXMLUnknownPnROption (Warning)
| Message |
Ignored unrecognised place and route setting '{}' from the project XML file |
| Decsription |
An unrecognised project XML setting has been ignored. |
ProjectDatabaseAlreadyExists (Error)
| Message |
Project database has already existed. Fail to create new project |
| Decsription |
Project database has already existed. Fail to create new project |
ProjectDatabaseDoesNotExist (Error)
| Message |
Project XML file '{}' does not exist |
| Decsription |
Project XML file does not exist |
ProjectDatabaseFoundDeprecatedTagName (Warning)
| Message |
Found a deprecated tag name {}. Skipping |
| Decsription |
Found a deprecated tag name |
ProjectDatabaseParseFailed (Error)
| Message |
Failed to parse the project XML file '{}'. The file format is unexpected |
| Decsription |
Failed to parse the project XML file |
ProjectDatabaseReading (Info)
| Message |
Reading project database '{}' |
| Decsription |
Reading project database |
ProjectDatabaseUnexpectedTagName (Error)
| Message |
Unexpected tag name {} |
| Decsription |
Found an unexpected tag name |
ProjectXmlNotSpecified (Error)
| Message |
A project XML file must be specified |
| Decsription |
A project XML file must be specified |
RunningFlowStage (Info)
| Message |
Running {} |
| Decsription |
The Efinity software is starting a flow stage |
StageDuration (Info)
| Main Message |
{} took {} seconds |
| Action |
Stage duration. |
| Sub-Message |
{} took {} seconds (approximately) in total CPU time |
| Decsription |
CPU time. |
TrionBeneficialSkewUnsupported (Warning)
| Message |
Trion devices do not support the --beneficial_skew option |
| Decsription |
Trion devices do not support the --beneficial_skew option. |
TrionFirstIterCSSNotSupported (Warning)
| Message |
Trion devices do not support the --router_first_iter_css option |
| Decsription |
Trion devices do not support the --router_first_iter_css option. |
UnassignedPartitionInterface (Warning)
| Message |
The design contains unassigned partition interfaces. Unassigned partition interfaces will be randomly placed. See the placement report for the list of unassigned partition interfaces |
| Decsription |
The design contains unassigned partition interfaces. Unassigned partition interfaces will be randomly placed. See the placement report for the list of unassigned partition interfaces. |
UnrecognisedPartitionHierPath (Error)
| Main Message |
The partition {} file '{}' contains hierarchy path(s) which do not match any known design hierarchy |
| Action |
The given partition declaration or definition file contains hierarchy path(s) which do not match any known design hierarchy. |
| Sub-Message |
Partition '{}' is mapped to unrecognised hierarchy path '{}' |
| Decsription |
Invalid hierarchy path. |
UnsupportedDevice (Error)
| Main Message |
Unsupported device {} for family {}. Current supported devices for the current family are: |
| Action |
Unsupported device option. |
| Sub-Message |
- {} |
| Decsription |
Family name. |
UnsupportedFamily (Error)
| Main Message |
Unsupported family {}. Current supported families are: |
| Action |
Unsupported family option. |
| Sub-Message |
- {} |
| Decsription |
Family name. |
UnsupportedPartitionDeclarationFileVersion (Error)
| Message |
Unsupported partition {} file version {}.{} specified in '{}' |
| Decsription |
A partition declaration or definition file has a version identifier that is unsupported by the current version of the Efinity software. |
UsingDefaultDevice (Info)
| Message |
Using default device {} for family {} |
| Decsription |
Using the default device for family. |
UsingDefaultFamily (Info)
| Message |
Using default family {} |
| Decsription |
Using the default family. |
UsingDefaultTimingModel (Info)
| Message |
Using default timing model {} for device {} in family {} |
| Decsription |
Using the default timing model for the current device. |
VDBOudatedTeamBasedDesignNotSupported (Error)
| Message |
The Synthesis Verific Database '{}' is from an earlier version of the Efinity software which is not compatible with the team-based-design flow |
| Decsription |
The Synthesis Verific Database provided is from an earlier version of the Efinity software which is not compatible with the team-based-design flow. Rerun the Synthesis compilation stage to resolve this issue. |
VDBOutdatedNoHierUtilReport (Warning)
| Message |
The Synthesis Verific Database '{}' is from an earlier version of the Efinity software. The Place and Router hierarchical utilisation report will not be generated |
| Decsription |
The Synthesis Verific Database provided is from an earlier version of the Efinity software. The Place and Router hierarchical utilisation report will not be generated. Rerun the Synthesis compilation stage to resolve this issue. |
VMUsage (Info)
| Main Message |
{} virtual memory usage: begin : {} MB, end : {} MB, delta : {} MB |
| Action |
Virtual memory usage statistics. |
| Sub-Message |
{} peak virtual memory usage : {} MB |
| Decsription |
Peak virtual memory usage |
VdbDoesNotExist (Error)
| Message |
File {} does not exist, Aborted |
| Decsription |
Vdb file does not exist |
VdbFileNotSpecified (Error)
| Message |
VDB File not specified, Aborted |
| Decsription |
VDB File not specified |
VdbFlowFailed (Error)
| Message |
Vdb Flow has encountered an error: {} |
| Decsription |
Vdb Flow has encountered an error |
VdbLoadFailed (Error)
| Message |
Failed to restore netlist from file '{}', Aborted |
| Decsription |
Failed to restore netlist from file |
VdbMerging (Info)
| Message |
Going to Merge VDB |
| Decsription |
Going to Merge VDB |
VdbPrepareToWrite (Info)
| Message |
Going to Write NetlistDB |
| Decsription |
Going to Write NetlistDB |
VdbWriting (Info)
| Message |
Write NetlistDB {} |
| Decsription |
Writing NetlistDB |
XmlSchemaFileDoesNotExist (Warning)
| Message |
XML schema file '{}' does not exist |
| Decsription |
XML schema file does not exist |