4.12. Dynamic Reconfiguration Error Recovery Handling
The Recovery enabled option in the Dynamic Reconfiguration Suite GUI allows you to easily recover from an error condition which you might encounter during the dynamic reconfiguration process.
By default, the Recovery enabled parameter is set to Yes. If you are concerned about the size of your combined .mif file, set to No and do not use this feature. Setting this parameter to No reduces the size of your combined .mif file.
If the DR firmware terminates with an error with this feature enabled, it allows you to recover and restore the protocol IP from any state back to the startup profile for the corresponding "Supreme Parent Group". In order to accomplish this restoration, you must set the dyn_rcfg_dr_next_profile_0_reg to 1'b1 and provide any profile ID along with it from the corresponding "Supreme Parent Group" as well as re-trigger the DR process. The Dynamic Reconfiguration Suite IP restores the protocol IP back to the startup profile for the corresponding “Supreme Parent Group”.
If the design consists of 16 independent MRIPs, the .mif file displays the 16 supreme_parent_group_ids and their corresponding user_provided_ids.
- Restore back to startup mode; In this example, the startup mode is profile 1
- avmm_write(32'h04, 32'h00060001); //dyn_rcfg_dr_next_profile_0_reg
- avmm_write(32'h0, 32'h00000001); //trigger dynamic reconfiguration
- Trigger DR to target profile 3
- avmm_write(32'h04, 32'h00040001); //bit set to 1 in simulation to disable CPI sequence
- avmm_write(32'h08, 32'h00008003); //dyn_rcfg_dr_next_profile_1_reg
- avmm_write(32'h0, 32'h00000001);// trigger dynamic reconfiguration
If the recovery feature is not enabled and you attempt to run the recovery process, the dyn_rcfg_local_error_stat_ctrl_reg indicates the ERROR_CODE_29.