User`s manual

About the X5 XMC Modules
shutting down power to most of the X5 module. The host system power must be toggled in order to reset the module from
this condition.
The Framework Logic implements this feature as standard. Although it is possible for custom user logic to remove this
feature, it is not recommended as it would expose the hardware to potential damage from over-temperature conditions, should
they occur.
The power enable signal is on Virtex-5 pin AF13. This pin must be held high to enable power.
Software support tools provide convenient access to the temperature and thermal controls. These should be used in
application programming configure and monitor the temperature, as illustrated below:
// Open the module
Innovative::X5_400M Module;
Module.Target(0);
Module.Open();
// Create reference to thermal management object on module
const LogicTemperatureIntf & Temp(Module.Thermal());
// Read current temperature
float t = Module.LogicTemperature();
// Read/write current warning temperature
float t = Module.LogicWarningTemperature();
Module.LogicWarningTemperature(70.0);
// Read current failure temperature
float t = Module.LogicFailureTemperature();
// See if the module is in thermal shutdown
bool state = Module.Failed();
Thermal Failures
The X5 modules will shut down if the Virtex-5 die temperature exceeds 85 degrees Celsius. This means that something is
wrong either with the module or with the system design. Damage may occur if the module temperature exceeds this limit. If
your software was monitoring the alert packets, you will receive a temperature warning alert prior to failure. Otherwise, the
temperature reading in the application may provide information pointing to overheating.
The most important thing to do is to determine the root cause of the failure. The module could have failed, the system power
is bad, or the environment is too harsh.
The first thing to do is inspect the module. Is anything discolored or do any ICs show evidence of damage? This may be due
to device failure, system power problems, or from overheating. If damage is noticed, the module is suspect and should be
sent for repair. If not, test the module outside the system in a benign environment such as on an adapter card in a desktop PC
with a small fan. It should not overheat. If it does, this module is is now bad.
Now consider what may have caused the failure. A bad module could be the cause, but it could have went bad due to system
failure or overheating. The system power supply could cause a failure by not providing proper power to the module. This
X5-GSPS User's Manual 40