Examples of Using Chip Planner, Resource Property Editor, and Change Manager Together to Implement Changes

While there are many different types of post-compilation changes that you can implement using the Chip Planner, Resource Property Editor, and Change Manager, the principles are similar regardless of the property being changed.

The following examples illustrate the work flow for two common types of changes.

Right-click a resource in the Chip Planner and display it in the Resource Property Editor by clicking Locate in Resource Property Editor.
On the View menu, point to Utility Windows, and then click Change Manager.
In the Resource Property Editor's Schematic View, right-click an input term that you want to invert, and then click Inverted.

A new line is added to the Change Manager, indicating the change that you have just made.

To save the change, on the File menu, click Save.

At this point the change is applied to the netlist in memory, but is not committed to the netlist on disk until it successfully passes a netlist check.
In the Change Manager, right-click the row representing the change, and then click Check and Save All Netlist Changes.

The Change Manager evaluates the change against the netlist data on disk, to verify that the change is legal and does not conflict with any netlist parameters.

If the change passes the netlist check, a success message appears and the change is written to disk.

If the change does not pass the netlist check, a message appears indicating that the netlist check was unsuccessful, and all changes performed since the previous successful netlist check are reversed.
After a successful netlist check, you can use the Assembler to create a new Programmer Object File (.pof) incorporating your latest changes.

Right-click an I/O resource in the Chip Planner and display it in the Resource Property Editor by clicking Locate in Resource Property Editor.
In the Schematic View of the Resource Property Editor, right-click the delay chain that you want to change, and choose a new delay value from the displayed options.
Click Save on the File menu to save the change.

At this point the change is applied to the netlist in memory, but is not committed to the netlist on disk until it successfully passes a netlist check.
In the Change Manager, right-click the row representing the change, and then click Check and Save All Netlist Changes.

Change Manager evaluates the change against the netlist data on disk, to verify that the change is legal and does not conflict with any netlist parameters.

If the change passes the netlist check, a success message appears and the change is written to disk.

If the change does not pass the netlist check, a message appears indicating that the netlist check was unsuccessful, and all changes performed since the previous successful netlist check are reversed.
After a successful netlist check, you can use the Assembler to create a new Programmer Object File (.pof) incorporating your latest changes.