EasyManua.ls Logo

ARM CoreLink GIC-600AE

Default Icon
268 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Arm
®
CoreLink™ GIC-600AE Generic Interrupt Controller
Technical Reference Manual
Document ID: 101206_0003_04_en
Issue: 04
Components and configuration
3.7.1 Interconnect configuration
The internal interconnect is configured automatically in accordance with the number of cores and
ITS blocks in the system. The configuration produces a balanced tree structure with minimum Clock
Domain Crossings (CDCs).
The Arm internal scripts limit a single interconnect crossbar to 16 destinations. To work around this
limitation, you can use domains in the config file. For example, instead of 32 Redistributors in one
domain, you can use two domains that each contain 16.
3.8 Hierarchy
There are three structure options that can be selected using the structure configuration
parameter.
wrap This option provides the lowest level of structure, and wraps the following
blocks:
The Redistributor is wrapped with interconnect components between
the Redistributor and the cores. The components that are wrapped at
this level are shown within the blue dashed lines in the following figure.
If the core is in a different clock domain, in accordance with the domain
tags, then half of the CoreLink
ADB-400 domain bridge is included in a
stitched file that is named gic600ae_ppi_wrap_<n>_<usrcfg>.v.
If a bypass switch is selected as shown in Figure 3-3: ITS block
on page 34, the ITS block is wrapped in a file that is named
gic600ae_its_wrap_<n>_<usrcfg>.v.
If the GIC-600AE is configured to share ACE-Lite ports between the ITS
and GICD (configuration parameter monolithic==1), the ITS and GICD are
stitched together in a file that is named gic600ae_gicd_wrap_<usrcfg>.v.
domain All blocks and wrapped components that are in the same domain are stitched
together in a file that is named gic600ae_domain_<name>_<usrcfg>.v and
includes ADB-400 domain bridges and collated Low-Power Interfaces. Blocks
and components at this level are shown within the red dashed lines in the
following figure.
full All domains are stitched together to create a single top-level GIC-600AE file
called gic600ae_<usrcfg>.v.
The following figure shows the top-level options.
Copyright © 2018–2020, 2022 Arm Limited (or its affiliates). All rights reserved.
Non-Confidential
Page 46 of 268

Table of Contents

Related product manuals