Test Data Out (TDO)

Rooting out impossible bugs

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, possibly due to their drive for shorter lead times and reduced costs. This myopia has lead to many news-worthy stories in recent times. But it wasn’t always like this…

In-Circuit Test—heavy metal blues

Once upon a time, circa mid-1980's, surface mount technology (SMT) was becoming all the rage and it was widely reported that in-circuit test (ICT) was doomed! Along came the Joint Test Action Group (JTAG) to the rescue and in 1990 they gave us IEEE-1149.1 standard boundary scan as salve. But lo, ICT had (at least) nine lives and would not die—the purveyors of "heavy metal" kept (keep) coming up with new innovations to keep the heart of the beast ticking…

Ircona, IBIST, and a great Signal Integrity story

Last week I had the privilege of speaking with the staff of Ircona (www.ircona.com), a firm with special expertise in high-speed processor-based designs and BIOS customization. Based in West Dublin and a development partner for Phoenix Technologies, Ircona has recently used our Intel® Interconnect Built-In Self Test (IBIST) tool to troubleshoot some very elusive signal integrity issues on a high-end server design.

Who will use IEEE 1687?

Who gets the benefit of using IEEE 1687 (IJTAG)? The simple answer is, “there is something for everyone!”

Once organizations and engineers have been exposed to IEEE P1687 IJTAG, the Proposed Draft Standard for Access to Embedded Instruments, and no matter which part of the semiconductor-based product lifecycle they are involved with, they all seem to find something that excites them. The IEEE 1687 standard resonates with engineers and managers because it either solves a technical problem, it provides a cost advantage, it reduces the amount of work, or it enables automation of some (onerous) task…

No Trouble Found?

In my earlier blog on Debugging Watchdog Timeouts I mentioned the dreaded No Trouble Found (NTF) problem. Some have asked why NTF is important. Well, the answer is because NTF is a huge cost to companies, compounded by the fact that NTF 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…