UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Explorer
Explorer
821 Views
Registered: ‎06-21-2013

processing system and OOC constraints

Jump to solution

Hi all,

 

We have recently moved to partitioning our FPGA design into multiple Board Designs and then setting these board designs to be generated in OOC mode.  This was done to reduce the synthesis times for the overall design.  It works well but gives a critical warning w.r.t a board design which contains a Zynq processing system.  The problem seems to be related to the auto generate processing_system7 MIO constraints file and the setting of the package pin properties.   The board design is called PS.

 

All the critical warnings are generated during the implementation stage of the design. A typical message is shown below.

 

[Netlist 29-160] Cannot set property 'iostandard', because the property does not exist for objects of type 'pin'. ["/home/developer/LinOOC-N2/flightNESIE/flightNESIE.srcs/sources_1/bd/PS/ip/PS_processing_system7_0_0/PS_processing_system7_0_0.xdc":33]

 

 

The corresponding line in the Vivado OOC generated PS_processing_system7_0_0.xdc is

set_property iostandard "LVCMOS18" [get_ports "MIO[53]"]

 

These warnings only occur when the design is built in OOC mode.  The tool normally handles these MIO configuration type constraints as part of the processing_system7 IP configuration.  

 

Are these warnings to be expected in the OOC flow as they are from a generated constraints file?  Are there any ways to alter the constraints files or IP generation for the processing system to prevent these warnings.

 

Regards

 

Walter

 

Regards

 

Walter

 

0 Kudos
1 Solution

Accepted Solutions
Explorer
Explorer
852 Views
Registered: ‎06-21-2013

Re: processing system and OOC constraints

Jump to solution

Update,

 

The issue was down to neglecting to connecting the FIXED_IO in the PS systems instantiation.  

 

Regards

 

Walter

0 Kudos
2 Replies
Explorer
Explorer
773 Views
Registered: ‎06-21-2013

Re: processing system and OOC constraints

Jump to solution

Update,

 

I think there maybe a naming issue w.r.t Vivado 2015.2 and the PS IP core when OOC is used.  The instantiation template for the PS system as generated by Vivado specifies the port FIXED_IO_mio [53:0].   However the OOC generated constraints refer to port  MIO[53:0] which is not a valid port name. I think  it should be referencing FIXED_IO_mio and not MIO hence the critical warning?

 

Regards

 

Walter

0 Kudos
Explorer
Explorer
853 Views
Registered: ‎06-21-2013

Re: processing system and OOC constraints

Jump to solution

Update,

 

The issue was down to neglecting to connecting the FIXED_IO in the PS systems instantiation.  

 

Regards

 

Walter

0 Kudos