The term AMP stands for Asymmetric MultiProcessing. This term describes multicore systems in which each core processes its specific task. How the tasks are distributed to the cores is determined in the design phase of the system.
When debugging AMP systems an individual TRACE32 instance
is started for each core. There are two reasons for this:
- An AMP system can contain different core architectures. In the case of an AURIX™ chip: up to three TriCore cores, a Cortex-M core and a Generic Timing Module.
- Each core processes a separate part of the application. This means the majority of the symbol and debug information is assigned exclusively to the corresponding core.
However, because the cores do not work independently, but perform the application task together and in parallel, it is required to start and stop all cores under debug
simultaneously. This is the only way to test the interaction between the cores and to monitor and control the entire application.
Because debugging individual cores of an AMP system is performed over separate TRACE32 instances, trace information is also displayed on these individual
To test the interaction of the cores and to quickly locate complex system errors, it is possible to display the individual
trace views and also their relationship to each other over time. To do this, TRACE32 trace tools provide a common time base. This allows the
developer to select a point in time in the trace view on one core and see exactly which command was being executed by the other cores
at the same time.
Lauterbach GmbH supports all available AURIX™ devices. New derivatives will be added as soon as they become available (do not hestitate to contact us).
For detailed configuration information click on your chip: