TRACE32® includes support for Windows 10

Lauterbach has recently extended its support for the Windows® Standard OS family. It now supports the latest version Windows 10 32bit and 64bit flavours. TRACE32® allows easy development and test of kernel modules, drivers, processes and DLLs, be it on single core or SMP systems. The support is available for all x86/x64 and ATOMTM boards having a JTAG interface. 

As a successor to Windows® 8, Windows 10 codenamed Thresholdis currently in public in its technical preview version and will launch in late-2015. Lauterbach has already extended its "Windows Standard Awareness" for the TRACE32 debugger to include this new version. Using "Windows Standard Awareness", the user is able to inspect the present processes, threads and libraries, as well as kernel modules and drivers. Using the extended MMU support of the TRACE32 debugger, the developer gets access to the complete virtual address space at any time - i.e. you can debug device drivers and applications simultaneously. At the same time you can debug several processes at once, which is especially interesting for testing inter-process communications or driver calls. 

TRACE32 uses the JTAG interface to access the target system. No special OS setting, interface or driver is necessary to debug the target. Even if the complete system "hangs", the debugger is still able to show all system resources. This "stop mode debugging" - where no running software such as a debug stub is required - also allows debugging of interrupts; from the interrupt entry point up to ISRs, drivers and even the responding applications. 

Post-mortem debug is also supported. Raw memory images could be loaded into TRACE32 x86/x64 instruction set simulators. By setting a few MMU configuration registers and loading Windows awareness, you have easy access to your system state, at the moment where the memory dump was created. 

Lauterbach's Windows Awareness is fully SMP capable. The debugger can switch to any CPU at any time, showing the view of each CPU or hyper-thread. It evaluates the call stacks of all active and passive application threads and shows where an active thread currently runs or where a passive thread is waiting. The system is started and stopped synchronously for all CPUs; a breakpoint hit halts the complete system, regardless which CPU reaches the breakpoint. On this event, the debugger automatically switches the view to the CPU that hit the breakpoint. 

Using these features the developer gains access to the complete system and all resources. You're debugging on "system level" rather than on "CPU level". 

Support for Windows 10 is available immediately.

More information