Intel® Quartus® Prime Software
Intel® Quartus® Prime Design Software, Design Entry, Synthesis, Simulation, Verification, Timing Analysis, System Design (Platform Designer, formerly Qsys)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
17267 Discussions

ECO usage issues need you help

Altera_Forum
Honored Contributor II
‎01-21-2013 04:42 AM
1,258 Views

Hello all: 

 

I'm using ECO to modify my project manually. As attached file show, signal "|SEP2MCS|TDC_VJ:inst14|tdc_ctrl_set[0]" feeds into ALUT from DATAC, and "|SEP2MCS|SEP_TDC_7ch:inst13|inst19" feeds into ALUT from DATAD. I want to exchange these two signal path, in other word, "|SEP2MCS|SEP_TDC_7ch:inst13|inst19" feeds into ALUT from DATAC, and "|SEP2MCS|TDC_VJ:inst14|tdc_ctrl_set[0]" feeds into ALUT from DATAD. 

 

I can change it, but i don't know how to modify the LUT equation? 

 

 

Or, can i constrain it as above comments in QSF file, instead of using ECO? So the QII can process it automatically!
Preview file
299 KB
0 Kudos

Link Copied

1 Reply
Altera_Forum
Honored Contributor II
‎01-21-2013 04:56 AM
536 Views

PS: Because i don't want to change the logic function, so i should need to modify LUT equation when i exchange these 2 nodes path. 

 

The Carryout equation and sumout equation should show the logic functions, but user can't modify them directly. They should be modified thru modifying LUT equations.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.