|Non-Confidential||PDF version||ARM DUI0446Z|
|Home > Introduction to DS-5 Debugger > Overview: Debugging multi-core (SMP and AMP), big.LITTLE , and multi-cluster targets > Debugging big.LITTLE Systems|
A big.LITTLE™ system optimizes for both high performance and low power consumption over a wide variety of workloads. It achieves this by including one or more high performance processors alongside one or more low power processors.
Awareness for big.LITTLE configurations is built into DS-5 Debugger, allowing you to establish a bare-metal, Linux kernel, or Linux application debug connection, just as you would for a single core processor.
For bare-metal debugging on big.LITTLE systems, you can establish an SMP connection within DS-5 Debugger. In this case, all the processors in the big.LITTLE system are brought under the control of the debugger. The debugger monitors the power state of each processor as it runs and displays it in the Debug Control view and on the command -line. Processors that are powered-down are visible to the debugger, but cannot be accessed. The remaining functionality of the debugger is equivalent to an SMP connection to a homogenous cluster of cores.
For Linux application debugging on
you can establish a
gdbserver connection within
Linux applications are typically unaware of whether they are running on a big
processor or a LITTLE processor because this is hidden by the operating system.
Therefore, there is no difference when debugging a Linux application on a
compared to application debug on any other system.