![]() Note that if debug-cable debugging is not support then a proprietary interposing device is required via a purchase from Intel.įrom the documentation I've read, the USB3 hardware on a supported machine decodes DCI commands, forwards them to an appropriate hardware module on the target CPU that translates them to JTAG sequences. This means you only need the inexpensive debug cable linked above. These combinations should support "DCI USB 3.x Debug Class" debugging. Kaby Lake / Intel 100 or 200 series SunrisePoint.I have not found the specific CPU/chipsec combinations but my educated guess from the Core series is as follows: ![]() This applies to some 6th-generation CPU and chipset combinations, and most 7th-generation and newer setups. Newer Intel CPUs support debugging over USB3 via a proprietary Direct Connection Interface (DCI) with the use of off-the-shelf hardware. ![]() Be careful with this cable as unsupported machines will have undefined behavior due to the electronics of USB. The cable is a USB 3.0 debugging cable and is similar to an ethernet crossover cable in the sense that the internal wiring is crossed. ![]() ![]() TL DR, if you have a newer CPU & chipset you can purchase a $15 off-the-shelf cable and single-step your hardware threads. Debugging an example exploitable UEFI application on hardware.Using Intel System Studio and System Debugger to single-step a Coffee Lake-S i7-8700 CPU.Configuring an ASRock H370M-ITX/ac to allow DCI DbC debugging. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |