Login

Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

ARM websites use two types of cookie: (1) those that enable the site to function and perform as required; and (2) analytical cookies which anonymously track visitors only while using the site. If you are not happy with this use of these cookies please review our Privacy Policy to learn how they can be disabled. By disabling cookies some features of the site will not work.

ARM Community: AXI CCI-400 ACE shareability domains - ARM Community

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

AXI CCI-400 ACE shareability domains Rate Topic: -----

#1 User is offline   Zijay 

  • Member
  • Pip
  • Group: Members
  • Posts: 3
  • Joined: 09-March 10

Posted 13 January 2012 - 08:11 AM

Hi all,

Recently, I'm studying AXI4 ACE spec. and working on ACE design,
but getting confused about the usage of shareability domain.

As per ACE spec.
"A shareability domain is a set of master components that enables a master component
to determine which other master components to include when issuing coherency
or barrier transactions."

Some questions:
1) A master component issues a coherent trans on an address region, it must set AxDOMAIN
as suitable domain (Inner/Outer/System), how to determine the address or access region of a AXI trans
belongs to which shareability domain ?

2) When the interconnect component (ex: CCI400) receives a coherent trans from ACE master,
it read the AxDOMAIN to determine which masters need to issue snoop trans,
but how to interpret the AxDOMAIN mapped to which masters ?
The relations of mapping Inner/Outer/System domains to a set of masters should be determined
in design time, such as memory map of all slaves connected to interconnect module ?

Above are my understanding and questions,
if anything wrong, please correct me, thanks.
0

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic