Ok, so we're not too far off. I suggest we continue on our journey to get a good solution for V7/8. When it's all done we can look at what is missing for V11.
Mathieu
On 19 January 2016 at 10:00, Mike Leach Mike.Leach@arm.com wrote:
Hi Mathieu,
ETM11 outputs ETMv3.2 trace protocol.
In principle the ETMv3 decode should work on this, though there may be issues with the instruction set decode - OpenCSD has an IS decoder for ARMv7 and ARMv8 architectures. The ARM 11 core (which is what has to be attached to an ETM 11) is ARMv6 architecture.
Currently the ETMv3 decoder has the first stage of packet processing only - full decode to follow after PTM full decode.
Regards
Mike
Mike Leach +44 (0)1254 893911 (Direct) Principal Engineer +44 (0)1254 893900 (Main) Arm Blackburn Design Centre +44 (0)1254 893901 (Fax) Belthorn House Walker Rd mailto:mike.leach@arm.com Guide Blackburn BB1 2QE
-----Original Message----- From: CoreSight [mailto:coresight-bounces@lists.linaro.org] On Behalf Of Mathieu Poirier Sent: 19 January 2016 16:12 To: coresight@lists.linaro.org Cc: Linus Walleij Subject: ETM11 and openCSD
Hey Mike,
A colleague of mine, Linus Walleij, stumbled on a board equipped with an ETM11 and started looking into it. From his point of view it looks simple enough to endeavour providing driver support for it.
What kind of trace format does it output? How far are we in openCSD to support traces generated by an ETM11?
Thanks, Mathieu _______________________________________________ CoreSight mailing list CoreSight@lists.linaro.org https://lists.linaro.org/mailman/listinfo/coresight
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.