Category: Embedded Diagnostics

The challenge of system debug on Intel (and other) systems can be huge. What new tricks are available for debugging system hangs, crashes, or application errors?
Is your laptop highly available? Maybe not yet, but... The author ruminates on why he's spending his precious weekend hours troubleshooting gadgets that should work all the time.
ScanWorks Embedded Diagnostics is embedded firmware which uses a CPU’s debug port to access a system’s architecturally visible registers, memory and I/O. See the technology and benefits behind this "debugger on steroids".
ScanWorks Embedded Diagnostics for x86 systems requires a connection between the embedded service processor (BMC, FPGA or other) supporting run control and the target CPU(s). The nature of these connections is described herein.
The use of effective embedded diagnostics to identify failures in today’s high-availability systems becomes more critical as semiconductor and board technologies increase in speed and integration. But many OEMs seem to be overlooking this vital aspect of their products’ post-sales operation...
In my earlier blog on Debugging Watchdog Timeouts I mentioned the dreaded No Trouble Found (NTF) problem. NTF is a huge cost to companies and is extremely difficult to quantify and to address. Something as simple as an errant wedding ring can cost companies millions of dollars. Let me explain…
Watchdog timeouts occur in crashed or hung systems when the main processor no longer sends a heartbeat to an ancillary service processor. These can occur in high- and low-end systems, anywhere from routers to servers to cell phones. Debugging them can be difficult…
Archives