Success! This week, I managed to compile a debug version of the UEFI, load it into the Minnowboard, and see UEFI source code in SourcePoint for the first time.
Last week, I wrote about my out-of-the-box experience with the Minnowboard Turbot, and how easy it was to start JTAG-based debugging on it with the SourcePoint tool. This week, I explored the UEFI shell, and updated the board firmware.
It may not be everyone’s idea of a good time, but I was delighted to receive a MinnowBoard Turbot for Christmas. I hooked it up to my copy of SourcePoint, and the results were pretty cool.
Run-control technology is rapidly becoming a de facto standard for forensics retrieval within high-availability, Intel Xeon-class servers. How did this standard come to be established?
The conventional approach to hardware-assisted debugging on Intel platforms involves physically connecting an external probe to the target. Is there a better way?
In my last blog, I referred to the use of run-control technology to very quickly exercise the PCI Express link training state machine. What other kinds of tests can be run with this approach?
It is often part of a hardware validation test suite to initiate multiple PCIe bus retrains, looking for hardware design issues, or LTSSM RTL bugs in the device under test. These test suites take a very long time to run. Is there a way to speed them up?