• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 1198 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM335x ETM ( Embeeded Trace Macrocell ) adress

Marcin Jabrzyk
Prodigy 20 points

Hi,


I've been looking over AM335x ARM® CortexTM-A8 Microprocessors (MPUs) Technical Reference Manual for address of Embedded Trace Macrocell. The only information in the TRM is

"The CoreSight ETM is embedded with the ARM core. The 32KB buffer (ETB) exists at the Chip Level (DebugSS)"


The only adres I've found in the memory map is the adress of ETB, but I need the address of ETM too.
Looking forward for help.


Thanks,

Marcin

  • 0
    Mastermind 8040 points

    I've added a "Debug" sheet to my (work-in-progress) memory map spreadsheet.  It is based on the dm814x but as far as I can tell the am335x is the same (minus the DSP trace bridge of course).

  • 0 in reply to Matthijs van Duin
    Prodigy 20 points

    Thanks,

    I'll give it a try and tell if it's working. From the first sight I see that the ETB addressees are the same in AM335x TRM and that region where you have ETB is marked as "Reserved" so it might be it.

  • 0 in reply to Marcin Jabrzyk
    Mastermind 8040 points

    You can be pretty sure about the L4_EMU address map, I confirmed that it's the same on the am335x, right down to the module IDs and interconnect revision values, so that part seems copy/pasted.

    There is however some possibility that the MPUSS-embedded part of the interconnect might be different.  I didn't check that, and can't right now since I lent out my BBB.  Apparently am335x has a different MPUSS ("Sabertooth") than the one in dm814x ("Modena"), although I'm not sure what the differences are exactly, they look pretty similar to me, but it's conceivable that the debug interconnect may be affected.

    In case of differences, the modules should be easy enough to locate/identify though, the (Sonics S3220) interconnect registers are identifiable by the id/version word at offset zero: low halfword is revision (so far I've seen those range from 0x6431 to 0x6438), high halfword is 0x0010 for Address/protection (or Initiator agent, confusingly they use same id), 0x0020 for Link agent, 0x0100 for Target agent.

    The remaining modules (except for the debug resource manager) have standard CoreSight identification info:  TI modules have vendor 0x097 (versus ARM's 0x4BB), part code 0x113 for ICECrusher-CS, 0x120 for system trace (SDTI / STM), 0xADF for DSP trace formatter.