You copied the Doc URL to your clipboard.

9.6. Programming the TPIU for trace capture

You must consider the following when programming the TPIU registers for trace capture:

  • TPAs that are only capable of operation with tracectl must only use the formatter in either bypass or normal mode, not in continuous mode.

  • ARM recommends that following a trigger event within a multi-trace source configuration, a flush is performed to ensure that all historical information related to the trigger is output.

  • If Flush on Trigger Event and Stop on Trigger Event options are chosen then any data after the trigger is not captured by the TPA. When the TPIU is instructed to stop, it discards any subsequent trace data, including data returned by the flush. Select Stop on Flush completion instead.

  • Although multiple flushes can be scheduled using Flush on Trigger Event, Flush on flushin, and manual flush, when one of these requests are made, it masks additional requests of the same type. This means repeated writing to the manual flush bit does not schedule multiple manual requests unless each is permitted to complete first.

  • Unless multiple triggers are required, it is not advisable to set both Trigger on Trigger Event and Trigger on Flush Completion, if Flush on Trigger Event is also enabled. In addition, if Trigger on trigin is enabled with this configuration, it can also cause multiple trigger markers from one trigger request.