|
|
|
|
|
During an editing session, the system keeps track of all commands performed on your design. The commands are written into a temporary command log file, design_name_fpga_editor.out, in the same directory where your design is located. This file is updated as each command is performed.
You can set the number of saved commands in the fpga_editor.ini file, or in the fpga_editor_user.ini file. See the flush_rate attribute in “Setattr” section of the “Command Line Syntax” chapter. The default is to update the file after each ten commands. Each time you save a design file, the commands are erased from design_name_fpga_editor.out.
When you end an FPGA Editor session, this file is erased when the FPGA Editor window closes. However, if a session is unexpectedly terminated (for example, if you lose power or a software error causes the session to end prematurely), the design_name_fpga_editor.out file remains in your current design directory.
The next time you start the FPGA Editor, the design_name_fpga_editor.out file is renamed design_name_fpga_editor.rcv. A new design_name_fpga_editor.out file is created for the current FPGA Editor session. A message box appears in the FPGA Editor Array window with a message similar to the following.
A crash recovery file was found for this design indicating that fpga_editor previously terminated abnormally. The changes that you made can be recovered. (This process will overwrite your current design file).
Do you want to run recovery?
If you want to run recovery, click Yes. Click No if you do not want to run the recovery process. The recovery process executes the commands in the design_name_fpga_editor.rcv, restoring the session up to the point where it was terminated. If you do not run the recovery process, the design_name.rcv file is ignored and the commands in the file are not applied to the design file.
The recovery file records the number of valid commands in order to prevent repeating the command that caused the abnormal termination of the FPGA Editor. However, some commands issued before the command that caused the crash may not be replayed as well.