Note:You are reading this message because your browser either doesn't support cascading style sheet (CSS) standards or is unable to access our CSS files (perhaps a browser setting). The majority of websites now use CSS to dramatically improve page layout. Virtually all recent browsers support CSS, so why not upgrade to view sites how they were intended to be seen?

User Settings
 Worldwide Locations  |  Contact Us

 

Dead Board Debug

Debug Dead Boards

MicroMaster is able to debug dead boards because it doesn't need to boot a board in order to test it.

Most functional tests rely on a board booting before faults can be diagnosed. In the example below, the dead terminal could be caused by more than 50% of the board's buses and devices. The lack of feedback prevents any diagnosis of the fault(s).

Dead board without feedback

However, when testing the same faulty board (shown below), MicroMaster has no problems giving a detailed diagnosis because it doesn't need to boot the board. Instead it takes direct control of the CPU and instructs it to set up and test all devices and buses, working progressively outwards from the CPU. Even if a device like the Boot ROM has failed, MicroMaster can still reach all other devices to test them. This allows all failing devices to be identified.

Dead board tested by uMaster

For a complete description of Debugging Dead Boards with MicroMaster, see this whitepaper.

HomeBackTopMore