linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dirk.behme@gmail.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: coresignt etm/etb usage
Date: Sat, 07 Feb 2015 08:16:08 +0100	[thread overview]
Message-ID: <54D5BBB8.20905@gmail.com> (raw)
In-Reply-To: <CAHrpEqR0kPAPCvuFK0XdP9RTojH85xoATt1esbfGTCSPkPu0Tw@mail.gmail.com>

On 06.02.2015 22:56, Zhi Li wrote:
> mathieu:
>
> I try to enable etm/etb in our freescale platform.


About which Freescale platform are you talking?

I've tried using the patches for the Freescale i.MX6 some month ago. 
I've managed to get the nodes like below, too. But never managed to 
get the ETM tracing data into the ETB. Only with attached HW JTAG 
debugger trace data has been recorded. And I never figured out which 
additional configuration the HW JTAG is doing compared to the SW only 
solution.

Best regards

Dirk


> I have ported your patches into our tree.
> coresign node already created in /sys/devices.
>
> 30041000.funnel  31001000.interrupt-controller  platform       software
> 3007c000.etm     backlight.7                    regulators.10  system
> 3007d000.etm     breakpoint                     replicator.1   timer.0
> 30084000.etb     gpio-keys.9                    soc.2          virtual
> 30087000.tpiu    max7322-reset.8                soc0
>
>
> But my problem is how to test it.
> Do you have document to show how to use it?
>
>
> best regards
> Frank Li
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>

  reply	other threads:[~2015-02-07  7:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 21:56 coresignt etm/etb usage Zhi Li
2015-02-07  7:16 ` Dirk Behme [this message]
2015-02-09 14:48   ` Zhi Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54D5BBB8.20905@gmail.com \
    --to=dirk.behme@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).