Method for responding to a control module failure
View Patent ↗A method is provided for saving system information immediately following a hardware or software failure that causes a processor to reset. After failure is imminent and before the processor allows the reset to occur, the processor is instructed to copy a fixed amount of the system stack SRAM, in addition to any processor registers that can be used to determine the reset cause, into a preserved area of SRAM. During the initialization sequence, the preserved area of SRAM is tested, but not overwritten. This allows all of the preserved SRAM data including previous stack contents and register settings at the time of the failure to be available for analysis.
1. A method for responding to a control module failure comprising:
initializing the control module;
determining whether a reset of the control module was caused by an unexpected event;
copying data recorded prior to said reset of the control module from a first memory location of a first memory device to a second memory location of the first memory device, and from said second memory location to at least one of a non-volatile memory device and an external tool for analysis, if said reset was caused by an unexpected event.
2. The method of claim 1 , further comprising running periodic task processes of the control module.
3. The method of claim 1 , wherein said copying data from said second memory device to said non-volatile memory device includes copying data from a SRAM device to a ROM device.
4. The method of claim 1 , further comprising copying data from a microprocessor to the first memory device if said reset was caused by an unexpected event.
5. The method of claim 1 , further comprising resetting the control module after said step of copying data from a first memory location of the first memory device to a second memory location of the first memory device.
6. The method of claim 1 , further comprising running a defined logic program after said determining step if said reset was not caused by an unexpected event.
7. The method of claim 1 , further comprising receiving a vehicle ignition signal.
8. A method for responding to a control module failure comprising:
initializing the control module;
determining whether a reset of the control module was caused by an unexpected event;
after said determining step, copying data recorded prior to said reset of the control module from a first memory device to a second non-volatile memory device if the reset was caused by an unexpected event;
transmitting the data recorded prior to said reset of the control module to an external tool for analysis;
running periodic task processes of the control module; and
after said determining step, copying the data recorded prior to said reset of the control module from a first memory location of the first memory device to a second memory location of the first memory device if said reset was caused by an unexpected event.
9. The method of claim 8 , wherein said copying the data recorded prior to said reset of the control module includes copying data from a SRAM device to a ROM device.
10. The method of claim 8 , further comprising copying data from a microprocessor to a SRAM device if said reset was caused by an unexpected event.
11. The method of claim 8 , further comprising resetting the control module after said step of copying data from said first memory location of the first memory device to said second memory location of said first memory device.
12. The method of claim 8 , further comprising running a defined logic program after said determining step if said reset was not caused by an unexpected event.
13. The method of claim 8 , further comprising receiving a vehicle ignition signal.
14. A method for responding to a control module failure comprising:
receiving a vehicle ignition signal;
initializing the control module;
determining whether a reset of the control module was caused by an unexpected event;
after said determining step, copying data recorded prior to said reset of the control module from a SRAM device to a non-volatile memory device if the reset was caused by an unexpected event;
transmitting the data recorded prior to said reset of the control module to an external tool for analysis;
running periodic task processes of the control module;
after said determining step, copying the data recorded prior to said reset of the control module from a first memory location of the SRAM device to a preserved memory location of the SRAM device if said reset was caused by an unexpected event.
after said determining step, running a defined logic program if said reset was not caused by an unexpected event; and
resetting the control module.