Once a NoC solution has been found, it can be locked down to save time and ensure the NoC solution is consistent from run to run. The following Tcl code locks down all NoC routes in the design.
set noc_routes [get_noc_net_routes -of [get_noc_logical_paths]]
foreach noc_route $noc_routes {
set_property LOCK true $noc_route # Use this to lock
#set_property LOCK false $noc_route # Use this to unlock
}
If you need to update the solution, unlock it to allow the compiler to run
efficiently, then re-lock it. Uncomment the appropriate set_property line above to lock or unlock the routes.
Note: In project mode, Vivado keeps track of locked NoC routes between NoC compiler runs and
between Vivado sessions.
When writing the NoC compiler solution to a file using the write_noc_solution Tcl command, the locked nets are
preserved. The solution, complete with locked routes can later be restored using the
read_noc_solution command.