Saving ECO Changes
After you have completed the changes and closed the opens, if you are satisfied with the result, you must commit the changes to have them saved using the eco_commit command.
The following example shows the global router commands added to the buffer insertion sequence and the eco_commit command added at the end to save the changes.
# The global router initialization is only needed if the global router
# has not been run in this session. For example, if you loaded a pre-routed design.
global_route -mode init
set eco [eco_begin]
eco_create_instance -eco_control $eco -cell MB -view abstract -lib libname -name B -origin {$x $y}
eco_create_net -eco_control $eco -name n2
eco_disconnect_inst_term -eco_control $eco -inst_name I2 -term_name A
eco_connect_inst_term -eco_control $eco -inst_name B -term_name A -net_name n1
eco_connect_inst_term -eco_control $eco -inst_name B -term_name Y -net_name n2
eco_connect_inst_term -eco_control $eco -inst_name I2 -term_name A -net_name n2
eco_connect_inst_term -eco_control $eco -inst_name B -term_name POWR -net_name VDD
eco_connect_inst_term -eco_control $eco -inst_name B -term_name GRND -net_name VSS
global_route -mode eco
eco_commit -eco_control $eco
Using the remastering example, the following sequence remasters an instance, routes the changes with the point-to-point router, then saves the change after the results are checked.
set eco [eco_begin]
eco_remaster_instance -eco_control $eco -lib mlib -cell B -view abstract -name I1
eco_move_instance -eco_control $eco -name I -origin {$x $y}
eco_repair_net -eco_control $eco -name n1
eco_repair_net -eco_control $eco -name n2
# Interactively select the guides for the disconnects before proceeding p2p_route -set [get_selection_set] -show_failures # Analyze the changes; check timing eco_commit -eco_control $eco
Related Topics
Return to top