System and method for fault sequence recording
Through the fault sequence recording system, the problem of difficulty in recording event sequences during power failure is solved, detailed recording of power failure events and high time resolution tracking are achieved, and the accuracy of fault analysis and system reliability are improved.
Patent Information
- Application Number
- CN202410566735.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-11-28
- Filing Date
- 2024-05-09
- Publication Date
- 2024-11-26
AI Technical Summary
Existing electronic systems cannot effectively record the sequence of failure events in the event of a power failure, resulting in difficulty in failure analysis, and the digital bus delay of the hot-swap controller makes it impossible to track fast continuous failure events in real time.
A fault sequence recording system is designed, including fault logic circuit, write control circuit and timer. By comparing sensor data with thresholds, a fault signal is generated, and event information and time information are recorded in the fault register, using non-volatile Sex memory is saved for subsequent analysis.
It realizes detailed recording of power failure events and tracking of fault events with high time resolution, helps determine the cause of failure, and improves the reliability of the system and the accuracy of fault analysis.
Smart Images

Figure CN119028042A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to Indian Patent Application No. 202341036568 filed on May 26, 2023, which is incorporated herein by reference in its entirety. Technical Field
[0003] The present specification relates to fault sequence recording, particularly as it is used to record data from certain types of electronic devices after a system shutdown caused by a power failure condition. The types of systems that may use this type of fault sequence recording may include enterprise server systems and large data processing units, such as may be found in remote computing and cloud storage facilities. Background Art
[0004] As an illustration, an aircraft typically includes a black box that records certain information about the aircraft, including certain important parameters at the time of the aircraft crash. The information is then read back from the black box to piece it together and infer what happened and how the aircraft was operating at the time of the crash, which can help understand the cause of the crash. Similarly, certain types of electronic systems may include a fault recording system that is capable of recording certain system parameters and events that occurred at the time of the system shutdown caused by a power failure condition.
[0005] Electronic fuses (efuses) are sometimes used in circuits to help protect against power failures such as short circuits, overvoltage conditions, overcurrent conditions, overtemperature, etc. The main purpose of an electronic fuse is to provide protection to the system in the event of a power failure. In most cases, the system is able to recover from the failure and continue to operate. However, if the system cannot recover due to a power failure and actually shuts down, some electronic fuses have the ability to store specific system parameters and events that occurred at the time of the failure. This information can be used to debug and failure analyze a system that has a power failure that causes the system to shut down. Summary of the invention
[0006] In a first example, a fault monitoring system includes a fault logic circuit having a fault logic input and a first fault logic output and a second fault logic output. The fault logic input is adapted to be coupled to a sensor input. The fault logic circuit is configured to compare a plurality of data values provided by respective sensor inputs with respective fault thresholds and to provide respective fault signals at the first fault logic output in response to a fault event in which the respective data values exceed their respective fault thresholds.
[0007] The write control circuit has a write control input, a write control output, and a reset output. The write control input is coupled to the first fault logic output. The timer has a timer input and a timer output. The timer input is coupled to the reset output. The data register has a first data register input and a second data register input and a data register output, wherein the first data register input is coupled to the write control output and the second data register input is coupled to the timer output. The data register is configured to receive fault data, the fault data comprising an event identifier, a timer value, and a timer expiration indicator.
[0008] In a second example, a method for monitoring and reporting system faults includes clearing a fault register and setting a fault register address pointer to an initial value. Sensor data values are received at an input of a fault logic circuit. Each respective sensor data value represents a measurement result of a respective system parameter. Each respective sensor data value is compared to a respective fault threshold using the fault logic circuit.
[0009] A corresponding fault signal is provided at an output of the fault logic circuit in response to a fault event in which the corresponding sensor data value exceeds its corresponding fault threshold. Event information and time information for each corresponding fault event are recorded in a fault register, and a fault register address pointer is incremented to a next value. A determination is made as to whether the fault register address pointer is at a maximum address value. The fault register address pointer is reset to an initial value in response to the fault register being at the maximum address value. The event information and time information are stored in a non-volatile memory. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 A block diagram showing an example enterprise server system.
[0011] Figure 2 An example graph of events over time for power failure events in a system, such as a computing server system, is shown.
[0012] Figure 3 Shows an example controller register diagram resulting from a system power fault event.
[0013] Figure 4 Bitmap of the RAM buffer showing an example fault event sequence generated by a system power fault event.
[0014] Figure 5 A block diagram of an example fault sequence recording system according to the present invention is shown.
[0015] Figure 6 A flow chart showing an exemplary fault sequence recording method according to the present invention is shown. DETAILED DESCRIPTION
[0016] In this specification, the same reference numerals depict the same or similar (in function and / or structure) features.The drawings are not necessarily drawn to scale.
[0017] Electronic fuses (efuses) are used in many types of equipment including enterprise servers and cloud data center server systems. Electronic fuses are circuits that help protect systems from power failures such as short circuits, overvoltage conditions, overcurrent conditions, overtemperature, etc. In many cases, the system is able to recover after a power failure and continue to operate normally. However, if the system cannot recover and actually shuts down due to a power failure, some electronic fuses have the ability to store potentially helpful information about the event that caused the failure. This information can be used to debug and failure analyze the system after a power failure that caused the system to shut down.
[0018] Some industries, such as remote data servers, place great emphasis on the reliability of servers, which must run continuously without downtime. If an enterprise server goes down due to a power failure, it is possible to detect what happened, troubleshoot the cause of the failure, fix the failure, and try to ensure that the failure does not occur again. For this reason, it is helpful to obtain information about the failure and any information that may help track down the root cause of the failure. To this end, it may be important to be able to recreate the sequence of events that led to the power failure and subsequent system shutdown.
[0019] Many enterprise server systems have multiple electronic circuit boards that plug into a common power source or backplane. Some systems require the ability to remove a circuit board and replace it with a new one in the event of a fault on the circuit board without shutting down the system power. This capability is known as hot-swap capability. An important component in a hot-swap system is a hot-swap controller, which provides some of the functionality that allows the system to continue running in real time during a hot-swap without disturbing the backplane.
[0020] Hot-swap controllers and e-fuses perform the same function, but e-fuses are typically more integrated versions of hot-swap controllers. Therefore, hot-swap controllers may still require some external components, such as current sensing resistors and power transistors. In contrast, e-fuses can combine all of these in one packaged device. A hot-swap controller or e-fuse may have the ability to provide power fault protection to the system and log potentially helpful information, including electrical parameters and the events that led to the failure.
[0021] Figure 1A block diagram of an example enterprise server system 100 is shown. Enterprise server system 100 includes an input power supply 104 and a server motherboard 102. Input power supply 104 is typically a 12V power supply, but can be at different voltages. Server motherboard 102 includes a hot-swap controller 106, a voltage regulator (VR) controller 112, a voltage regulator module (VRM) 114, dynamic random access memory (DRAM) 116, a processor 118, and a board management controller (BMC) 108. DRAM 116 can be synchronous dynamic random access memory (SDRAM) or can be double data rate memory (DDR).
[0022] The VRM 114 receives the voltage provided by the input power supply 104 and generates other voltages required to provide power to other system components such as the processor 118, DRAM 116, and system fans. The VRM 114 is the power stage of the voltage regulator that provides the drive current for the voltage regulator. The VR controller contains the voltage regulator feedback and control circuitry and provides control signals to the VRM 114.
[0023] BMC 108 is like a supervisor microcontroller that controls fault monitoring and reads back information from memory. BMC 108 continuously reads hot-swap controller 106 and stores the information in memory. However, BMC 108 can only keep up if the monitored events occur relatively slowly. That is, BMC 108 can only keep up if there is a significant delay from the first event to the next event. However, many times, when a fault occurs, several events occur in rapid succession, and BMC 108 cannot keep up with all events. In this case, information that occurs just before BMC 108 can read out the data will be lost, and the information contains the sequence of events that occurred. This is caused by the delay of the digital bus between BMC and hot-swap controller 106, which may be a PM bus.
[0024] Due to the latency involved, enterprise server system 100 is not adequate to track fault events that occur relatively close together in time. If fault events need to be tracked with fine time resolution (e.g., <1 millisecond apart), BMC 108 may not be able to track the fault. Hot-swap controller 106 has a digital interface through which parameters such as temperature, voltage, current, and other status information can be read. Other status information may include how well the system is running or whether a certain type of fault has occurred.
[0025] The ability to read this information comes from the status register, which may only show a single snapshot of the last state before the system was shut down. There is no information in the snapshot about the sequence of events that occurred before the system was shut down. In some cases, a timestamp may be added to the information provided in the snapshot. However, the timestamp does not provide any information about the relative timing between consecutive individual events. This may not provide a clear indication of the original event and the subsequent events that led to the system failure.
[0026] Figure 2 An example graph 200 of events over time for a power failure event in a system, such as a computing server system, is shown. Initially at 210, the power supply voltage is stable at 12V and the system is operating normally. At 220, the server demands a burst of current from the power supply. The server's demand for the current burst causes the power supply voltage to begin to drop. At 230, the power supply voltage drops below an under voltage warning threshold, i.e., a UVLO warning.
[0027] The computing server system has drawn a certain amount of power and will be used to maintain a constant power draw. Therefore, as the supply voltage continues to drop, the system begins to draw more current to compensate for the voltage drop. Due to the response time, the load current remains above the overcurrent threshold for a longer period of time. This causes the current to become higher. In the case where the current remains high, the electronic fuse or hot swap controller will begin to shut down the system power because the system senses a power fault condition. When the current is interrupted at 240, the supply voltage rises sharply due to the energy stored in the input inductor. This produces a peak in the supply voltage. At 250, the supply voltage rises above the overvoltage warning threshold, i.e., the OVLO warning.
[0028] Figure 3 An example controller fault register graph 300 resulting from the system power event shown in graph 200 is shown. Controller fault register graph 300 shows an example fault register graph after a typical power fault event. When the server requests a current increase at 220, the current increases, causing an overcurrent warning bit 330 to be set in the register. The current continues to increase until the current exceeds the overcurrent threshold and an overcurrent fault bit 340 is set.
[0029] The additional current demand from the server causes the output voltage to drop. When the voltage drops below the UVLO warning threshold at 230, the undervoltage warning bit 310 is set in the fault register. When the overcurrent threshold is exceeded, the system shuts down at 240 and the current demand is removed. When the current demand is removed, the output voltage begins to rise. The output voltage rises, exceeding the overvoltage (OVLO) warning at 250, which sets the overvoltage warning bit 320.
[0030] Due to the system power failure event in 200, specific bits are set in the controller fault register map 300. The system power failure causes the power to shut down, and a single snapshot is taken of some events that occur in the system, and the snapshot is stored for later analysis. The bits set in the controller fault register map 300 contain indications of warnings and fault signals that occurred due to the power failure event. However, only a single snapshot of the events is taken and saved in the fault status register, and the snapshot does not record the sequence in which the fault occurred.
[0031] The data does not contain information indicating which event occurred first, which event occurred second, etc., and whether the events occurred within 1 microsecond, 1 millisecond, or 10 seconds of each other. Based on this snapshot in controller fault register map 300, it may be difficult to determine whether the cause of a system power failure may be: (1) poor regulation of the power supply; (2) wear and tear of components in the power path; (3) a short circuit; (4) an overcurrent event; or (5) some other cause. Most digital bus interfaces have too much latency to monitor individual events in real time as they occur, so sending real-time feedback to a separate processor is not a viable option in most cases.
[0032] This can make system troubleshooting and fault analysis after a power failure event very difficult. Inspection of the controller fault register map 300 shows four fault bits set, but does not give enough information to recreate the situation that occurred in the system to cause the power failure event. More than one system fault scenario may cause the same four bits to be set in the system fault register map. Therefore, when debugging and analysis of a power failure event begins, the wrong root cause may be sought, resulting in wasted time and resources or incorrect conclusions.
[0033] Figure 4 A bitmap of an example fault event sequence RAM buffer 400 generated by a system power fault event is shown. The contents of the fault event sequence RAM buffer 400 correspond to the power fault event shown in the graph 200. The controller fault register map 300 will also be included in the data provided for debugging and troubleshooting the cause of the power event failure. The fault event sequence RAM buffer 400 does not replace the controller fault register map 300, but is provided to supplement the controller fault register map. The device still detects each of the individual power fault events as they occur. However, not only will the snapshot provided by the controller fault register map 300 be stored, but the fault event sequence RAM buffer 400 will also be stored in non-volatile memory for later analysis.
[0034] The contents of the fault event sequence RAM buffer 400 may be stored in RAM in the same device package as the fault event sequence RAM buffer 400. Alternatively, the contents of the fault event sequence RAM buffer 400 may be stored in an external RAM. The fault event sequence RAM buffer 400 is updated in a circular buffer manner. Events are recorded in the buffer individually and sequentially. When the end of the buffer is reached, the contents of the buffer are overwritten with new data. Therefore, the contents of the buffer will always be information about the most recent fault event.
[0035] Fault event sequence RAM buffer 400 shows four power fault events. The first power fault event that occurs is power fault event 410, which is an over current (OC) warning. The second power fault event that occurs is power fault event 420, which is an input voltage under voltage (UV) warning. The third power fault event that occurs is power fault event 430, which is an OC failure. The fourth power fault event that occurs is power fault event 440, which is an input voltage over voltage (OV) warning.
[0036] Initially at system power up, the Fault Event Sequence RAM buffer 400 is clean and has no entries. When the server demands a burst of current at 220, and causes the current draw to rise above the overcurrent warning threshold, an entry for a power fault event 410 is made in RAM location 0 of the Fault Event Sequence RAM buffer 400, recording that an OC warning has occurred. An OC warning has a unique three-digit event identifier 412. In this case, the event identifier for the OC warning is 101, the event identifier for the UV warning is 111, and the event identifier for the OV warning is 110. However, in other cases, other event identifiers may be used.
[0037] Additional timing information is also stored in the fault event sequence RAM buffer 400. The timing information is saved in two fields. The first timing information field is the timer value field 414, and the second timer information field is the timer expiration field 416. The timer value field 414 provides a four-bit value representing the incremental time from the previous power fault event to the current power fault event. The timer expiration field 416 provides a true / false indication of whether the time between the previous power fault event and the current power fault event exceeds the four-bit timer value and restarts at 0000b.
[0038] In at least one case, the timer is a clock internal to the device that provides an absolute time of the occurrence of a power failure event in a format such as date / hour / minute / second. However, in many other instances, the device uses a free-running counter derived from a master reference clock having a known frequency. In the case of a free-running clock, clock pulses are counted to determine how many clock ticks have passed between a previous power failure event and a current power failure event. This provides a relative timing between the two events. From power failure event 410 to power failure event 420, no timer ticks occurred according to timer indicator 424. From power failure event 420 to power failure event 430, eleven (1011b) timer ticks occurred. From power failure event 430 to power failure event 440, no timer ticks occurred.
[0039] Some finite time elapses between power failure event 410 and power failure event 420 and between power failure event 430 and power failure event 440. However, the timer tick count is also a function of the resolution of the timer. If the timer ticks at a rate of 1 millisecond / tick, any events that occur within 1 millisecond of each other will always be reported as zero elapsed time. However, if the timer period is 1 microsecond, there will be many more timer ticks between the same two events.
[0040] The tick value, or the time between consecutive timer ticks, is set by the frequency of the master clock (e.g., 12 MHz) and a clock divider. The clock divider divides the master clock frequency down to a lower frequency to produce a slower timer, or a longer time between timer ticks (e.g., 50 microseconds to 3.2 milliseconds). The value of the clock divider can be user programmable by writing to a clock register to set the clock divide factor, or the value can be fixed in hardware to a specific clock divide factor.
[0041] If cost and silicon area are not significant considerations, the Fault Event Sequence RAM Buffer 400 may be large enough to store all power events that occur during the useful life of the system, and circuitry may be added to provide an absolute time stamp on each event. However, many systems require economic cost and space optimization. The bitmap of the Fault Event Sequence RAM Buffer 400 provides a relatively large amount of information to be stored in a single byte.
[0042] The event information for each of power failure event 410, power failure event 420, power failure event 430, and power failure event 440 is stored in only one byte for each of the power failure events. This one byte of information contains a three-bit event identifier, a four-bit timer value, and a one-bit timer expiration bit. Because there are only a limited number of bits for storing timer information, if the time between events is too long, some information about the timer may be lost and the timer runs from 0000b to 1111b, after which the register value then returns to 0000b.
[0043] Thus, if the power failure events occur far enough apart in time, the timer may overflow and reset to 0000b, and then continue to count upward. Depending on when the snapshot was taken, the timer may have expired multiple times, and the value recorded in the timer field of the failure event sequence RAM buffer 400 may not be correct. The timer expiration bit (e.g., 416) indicates whether the timer has run at least once. The timer expiration bit provides information to help determine whether the previous power failure event occurred in the recent past or a longer time in the past relative to the current power failure event.
[0044] A '0' in the Timer Expiration field means that the timer has not expired between the previous event and the current event. Therefore, the time shown in the Timer field is the actual number of timer ticks that have occurred between the previous power failure event and the current power failure event. A '1' in the Timer Expiration field means that the timer has expired at least once between the previous event and the current event. It does not provide information about how many times the timer expired during the period, but only that the timer did expire. In this case, it is known that the timer value is a rough value rather than an exact value, and the time between the two events is greater than or equal to the maximum time of 16x (4-bit) clock tick period.
[0045] Figure 5 A block diagram of an exemplary fault sequence recording system 500 according to the present invention is shown. The fault sequence recording system 500 is composed of four subsystems. The four subsystems include a fault logic block 504, an event identification and RAM storage subsystem 510, a tick timer 520, and a memory control subsystem 530.
[0046] The event identification and RAM storage subsystem 510 includes a RAM write control block 512, a write control block 516, and a fault event sequence RAM buffer 514. The memory control subsystem 530 includes a read logic block 532, a write register 534, and a read register 536. In some cases, the memory control subsystem 530 may also include an I2C interface block 538, but in other cases, the I2C interface block 538 may not be necessary.
[0047] The fault logic block 504 has a first output and a second output coupled to the event identification and the RAM storage subsystem 510 at the RAM write control block 512 and the write control block 516, respectively. The RAM write control block has a first output and a second output coupled to the fault event sequence RAM buffer 514 and the tick timer 520, respectively. The tick timer block 520 has an output coupled to an input of the fault event sequence RAM buffer 514.
[0048] The fault sequence of events RAM buffer 514 has a first output and a second output coupled to the memory control subsystem 530 at the inputs of the read logic block 532 and the write register 534, respectively. The read register 536 has an output coupled to the second input of the read logic block 532. The I2C interface block 538 has a first input and a second input and an output. The first input and the second input of the I2C interface block 538 are coupled to the write register 534 and the output of the write control block 516, respectively. In some cases, the I2C interface block 538 is also coupled to the external EEPROM 540.
[0049] The fault sequence recording system 500 receives inputs from sensors (not shown) that monitor important parameters such as input and output voltages, current draw, and temperature. The fault logic block 504 receives information from the outputs of the voltage, current, and temperature monitors and compares these parameters to their respective thresholds and warning limits. Other example systems may have different monitors or additional monitors that provide information to the fault logic block 504.
[0050] The fault logic block 504 has an output coupled to an input of a RAM write control block 512. When a fault occurs, the fault logic block 504 provides information about the fault to the RAM write control block 512. The information provided by the fault logic block 504 to the RAM write control block 512 includes what kind of fault occurred. However, there is no timing information that includes the information from the fault logic block 504, so the information is only a synchronization event. However, the RAM write control block 512 can obtain timing information from the tick timer 520. Therefore, the RAM write control block 512 is able to provide information on what kind of fault event occurred and how many times the tick timer has ticked from the previous fault event until the fault event occurred.
[0051] In another example embodiment, the information of how many ticks of the tick timer have passed between the previous fault event and the current fault event can be provided directly to the fault event sequence RAM buffer 514 through the tick timer 520. Then, after the event occurs and is recorded in the fault event sequence RAM buffer 514, the RAM write control block 512 resets the tick timer 520.
[0052] The Fault Sequence of Events RAM buffer 514 is a volatile memory and therefore loses its contents when power is removed. Therefore, it is necessary to write the information contained in the Fault Sequence of Events RAM buffer 514 to a non-volatile memory to aid in troubleshooting and determining the cause of the power fault event. The non-volatile memory may be contained within the same device as the Fault Sequence of Events RAM buffer 514, or the non-volatile memory may be external to the device, such as an external EEPROM 540.
[0053] The operation of writing the contents of the Fault Sequence of Events RAM buffer 514 to non-volatile memory is performed by the memory control subsystem 530. If the device senses that it is losing power, the Fault Sequence of Events RAM buffer 514 writes its contents to a write register 534. In the case of external non-volatile memory, the write register 534 communicates with an external EEPROM 540 through an interface such as an I2C interface 538. In other cases, the non-volatile memory may be an EEPROM, flash memory, or some other type of one-time programmable (OTP) memory internal to the device. The read logic block 532 allows information stored in the system to be read back into the device or to read back the contents of the non-volatile memory.
[0054] Figure 6 A flow chart of an example fault sequence recording method 600 according to the present invention is shown. At 604, the system receives a power-on reset (POR) start operation of the system. At this time, the system is turned on, and at 608, all RAM and status bits are cleared and set to their default values (e.g., zero). At 612, the system idles and continues to be in an idle state until a fault event occurs.
[0055] When the first fault event occurs at 616, the fault logic is awakened and determines whether the fault event is an identified event. If the fault event is an identified event, the event identification (ID) and timer information are saved to the RAM register at 620. At 624, the RAM register pointer value is queried to determine whether the contents of the RAM register are full. If the RAM register is not full, the RAM register pointer is incremented to the next value at 636. If the RAM register is full, the full status bit is set at 628 and the RAM register pointer value is reset to zero. Subsequently, the system returns to idle at 612 and remains idle until the next fault event occurs.
[0056] At 640, when the system is operating, the timer is free running. The time between ticks will be determined by how the master clock frequency and the clock divider ratio are configured. If an identified fault event occurs at 620, the free running timer records its tick value and is then reset to zero at 644.
[0057] At 648, the timer value is queried to determine if a timer register overflow has occurred and the tick value register has been reset to zero at least once. If an overflow of the tick value register occurred between the last fault event and the current fault event, the overflow bit is set in the RAM register. When a fault event is detected at 654, the fault ID and timer information are written to non-volatile memory at 656 to be available for later retrieval and analysis.
[0058] In this specification, "terminal", "node", "interconnect", "lead" and "pin" are used interchangeably. Unless specifically stated to the contrary, these terms generally mean the interconnection between device elements, circuit elements, integrated circuits, devices or other electronic or semiconductor components or their ends.
[0059] In this specification, "ground" includes chassis ground, earth ground, floating ground, virtual ground, digital ground, common ground, and / or any other form of ground connection that is applicable or suitable for the teachings of this specification.
[0060] In this specification, the term "coupled" may cover connections, communications, or signal paths that enable a functional relationship consistent with this specification. For example, if device A generates a signal to control device B to perform an action, then: (a) in the first instance, device A is coupled to device B through a direct connection; or (b) in the second instance, if the intermediate component C does not change the functional relationship between device A and device B, device A is coupled to device B through the intermediate component C, so that device B is controlled by device A via the control signal generated by device A.
[0061] In this specification, even if operations are described in a particular order, some operations may be optional, and the operations need not be performed in the particular order to achieve the specified results. In some instances, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the embodiments described above does not necessarily require such separation in all embodiments.
[0062] Modifications may be made in the described embodiments, and other embodiments are possible, within the scope of the claims.
Claims
1. A fault monitoring system, comprising: a fault logic circuit having a fault logic input and a first fault logic output and a second fault logic output, wherein the fault logic input is adapted to be coupled to a sensor input, and the fault logic circuit is configured to compare a plurality of data values provided by respective sensor inputs to respective fault thresholds and to provide respective fault signals at the first fault logic output in response to a fault event in which a respective data value exceeds its respective fault threshold; a write control circuit having a write control input, a write control output, and a reset output, wherein the write control input is coupled to the first fault logic output; a timer having a timer input and a timer output, wherein the timer input is coupled to the reset output; as well as a data register having a first data register input and a second data register input and a data register output, wherein the first data register input is coupled to the write control output and the second data register input is coupled to the timer output; Wherein the data register is configured to receive fault data, the fault data comprising an event identifier, a timer value, and a timer expiration indicator. 2 . The fault monitoring system of claim 1 , wherein the fault data is one byte, the event identifier is 3 bits, the timer value is 4 bits, and the timer expiration indicator is 1 bit.
3. The fault monitoring system of claim 1, wherein the data values include values of voltage and current. 4 . The fault monitoring system according to claim 3 , wherein the fault event is one of: an overvoltage fault, an undervoltage fault, an overcurrent fault, and a temperature fault. 5 . The fault monitoring system of claim 1 , wherein the timer output provides an indication of a time between a first fault event and a second fault event.
6. The fault monitoring system of claim 1, wherein the timer output provides an indication of an absolute time at which each respective fault event occurred. 7 . The fault monitoring system of claim 1 , wherein the data register output is coupled to a non-volatile storage device, the non-volatile storage device being configurable to receive the fault data provided by the data register output.
8. The fault monitoring system of claim 7, further comprising a non-volatile write control circuit having a non-volatile write control input and a non-volatile write control output, wherein the non-volatile write control input is coupled to the second fault logic output and the non-volatile write control output is coupled to the non-volatile storage device.
9. The fault monitoring system of claim 7, wherein the data register output is coupled to the non-volatile storage device through a bus interface.
10. The fault monitoring system according to claim 9, wherein the bus interface is an I2C bus interface.
11. The fault monitoring system according to claim 7, wherein the non-volatile storage device is one of the following: an electrically erasable programmable read-only memory (EEPROM), a flash memory, and a one-time programmable (OTP) memory.
12. A method for monitoring and reporting system failures, comprising: Clear the fault register and set the fault register address pointer to the initial value; receiving sensor data values at an input of the fault logic circuit, wherein each respective sensor data value represents a measurement of a respective system parameter; comparing each respective sensor data value to a respective fault threshold using the fault logic circuit; providing a respective fault signal at an output of said fault logic circuit in response to a fault event in which a respective sensor data value exceeds its respective fault threshold; recording event information and time information of each corresponding fault event in the fault register, and incrementing the fault register address pointer to a next value; determining whether a fault register address pointer is at a maximum address value, and resetting the fault register address pointer to the initial value in response to the fault register being at the maximum address value; as well as The event information and the time information are stored in a non-volatile memory.
13. The method of claim 12, wherein the event information comprises an event identifier, a timer value, and a timer expiration indicator.
14. The method of claim 13, wherein the event identifier is 3 bits, the timer value is 4 bits, and the timer expiration indicator is 1 bit.
15. The method of claim 14, wherein the timer value provides an indication of a time between a first fault event and a second fault event.
16. The method of claim 13, wherein the timer value provides an indication of an absolute time at which each respective fault event occurred. The method of claim 12 , wherein the sensor data values include values of voltage and current.
18. The method of claim 17, wherein the fault event is one of: an overvoltage fault, an undervoltage fault, an overcurrent fault, and a temperature fault.
19. The method of claim 15, wherein the time between the first fault event and the second fault event is determined by counting a number of clock cycles that occur between the first fault event and the second fault event.
20. The method of claim 19, wherein the timer expiration indicator provides an indication of whether the timer value has reached a maximum timer value during the counting period.
21. The method of claim 20, further comprising resetting the timer value in response to the timer value reaching the timer maximum value.
22. The method of claim 12, wherein the non-volatile memory is one of: an electrically erasable programmable read-only memory (EEPROM), a flash memory, and a one-time programmable (OTP) memory.
