Lauterbach has announced that its TRACE32 development tool now supports Windows 10 aware debugging on the ARM architecture. Lauterbach's TRACE32 is an integrated, universal development system that can be connected to most work stations and can contain any combination of instruments which may be required for microprocessor systems development, including debugger, tracing tool, logic analyser, protocol analyser and similar tools.
"We have been providing Windows aware debugging for all x86/x64 devices since April 2015, and I am pleased that we can now provide the same support for devices with ARM cores," said Barry Lock, UK Manager, Lauterbach. "Using the so called “stop mode debugging” over JTAG interface, the developer gains access to all system resources. No special stub, 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. The user can inspect running processes, threads and libraries, as well as kernel modules and drivers, at any time."
"Also, Thanks to its extended MMU support, TRACE32 allows access to the complete virtual address space. This gives the developer the ability to switch to the context of any process and inspect its status at any time. This means that you can debug drivers and/or multiple applications simultaneously."
Lauterbach will be hosting a free workshop at the 2016 UK Device Developers' Conference. Entitled 'How to Optimise ARM Cortex-M Code and Build Better Embedded Systems', this 2-hour presentation will explain all the Cortex-M debug Coresight bits and show how they can be used to debug and analyse an embedded system.
Lauterbach debug tools have become a favourite with many hi-tech engineers, and the company is recognised for both engineering excellence and exceptional technical support. Lauterbach tools support all the major families of microprocessor cores, covering products from 75 silicon companies. The quality and capability of Lauterbach tools enable engineering teams to develop robust code whilst minimising development time lost to debugging.