Arm Debugger helps you get to the root of software bugs throughout your development process. From device bring-up to application debug, it can be used to develop code on virtual platforms and hardware to help you get your products to market ahead of the competition.
We are big fans of Jython: it gives you a great way of creating complex debug control flows, whilst abstracting away the low-level implementation difficulties.
If you're regression testing your code or working on validation, you can drive Arm Debugger purely from the command line to automate testing.
We've included command line autocompletion to make debugging easier, just hit Ctrl + Space for GDB commands content assist.
Development Stages:
Pre-silicon,OS porting and application development
Debug Connection:
CADI
Development Stages:
Board bring-up, OS porting and application development
Debug Connection:
Development Stages:
Silicon evaluation, firmware development
Debug Connection:
CMSIS-DAP over USB, Arm DSTREAM family, Arm Keil ULINKpro family
Development Stages:
Linux and Android native libraries and application
Debug Connection:
GDB Remote Protocol via ADB or Ethernet.
Utilise the MMU view to automatically complete page table walks, translate virtual to physical memory addresses and present an overview of the memory map.
Target Configuration Editor gives the ability to add custom peripheral registers to the view, thereby enabling tailoring it for target specific peripherals and registers.
Export the settings of the configured target in a CMSIS-SVD compatible format for further work within Keil MDK.
With maximum control over hardware, software and conditional breakpoints, Arm Debugger helps you to eliminate complex bugs.
Conditional breakpoints can be set to stop execution when a C-like expression evaluates to true, allow multiple hits before the breakpoint triggers or run debugger scripts, whilst thread and virtual machine-specific breakpoints can be used to stop the processor when hit from a specific thread.
The type and number of breakpoints you can set depends on the memory region, hardware support in the processor, debug interface and running state.
Similarly, you can also set watchpoints, which monitor the address or value of a data access, rather than instructions executed from a specific address.
Trace in Development Studio is extremely powerful, giving you a non-intrusive way to sort out hard-to-find bugs when it's simply not practical to stop and start a core repeatedly.
To cope with the complex trace topologies of modern systems, Development Studio allows you to set and configure trace start, stop and trigger points.
In Arm Debugger, tracepoints can be set from the Arm assembly editor, C/C++ editor, disassembly view, functions view, memory view or trace view.
Breakpoints, tracepoints, and watchpoints can all be exported for use in a different Development Studio workspace, helping you to debug code as a team.
