Information for ArmIntegratorCP

This page provides detailed information about the arm.ovpworld.org ArmIntegratorCP Virtual Platform / Virtual Prototype.

Licensing
Open Source Apache 2.0

Description
This platform models the ARM INTEGRATOR CP development board. It provides the peripherals required to boot and run Operating Systems such as Linux or Nucleus. The main processor is an ARM, by default this is an ARM926EJ-S (Linux) but can be overriden; for example ARM920T (Nucleus).

Limitations
No known limitations for executing Linux and Nucleus operating systems.

Reference
ARM Development Boards Integrator CP BaseBoard and Integrator Core Modules ARM9x6

Location
The ArmIntegratorCP virtual platform is located in an Imperas/OVP installation at the VLNV: arm.ovpworld.org / module / ArmIntegratorCP / 1.0.

Platform Summary

Table 1: Components in platform

TypeInstanceVendorComponent
Processorcpuarm.ovpworld.orgarmCortex-A9UP
Peripheralcmarm.ovpworld.orgCoreModule9x6
Peripheralpic1arm.ovpworld.orgIntICP
Peripheralpic2arm.ovpworld.orgIntICP
Peripheralethlansmsc.ovpworld.orgLAN9118
Peripheralpitarm.ovpworld.orgIcpCounterTimer
Peripheralicparm.ovpworld.orgIcpControl
Peripheralld1arm.ovpworld.orgDebugLedAndDipSwitch
Peripheralkb1arm.ovpworld.orgKbPL050
Peripheralms1arm.ovpworld.orgKbPL050
Peripheralrtcarm.ovpworld.orgRtcPL031
Peripheraluart1arm.ovpworld.orgUartPL011
Peripheraluart2arm.ovpworld.orgUartPL011
Peripheralmmciarm.ovpworld.orgMmciPL181
Peripherallcdarm.ovpworld.orgLcdPL110
PeripheralsmartLoaderarm.ovpworld.orgSmartLoaderArmLinux
Memoryram1ovpworld.orgram
MemoryambaDummyovpworld.orgram
Busbus1(builtin)address width:32
Busmembus(builtin)address width:32
Bridgeram1Bridge(builtin)
Bridgeram2Bridge(builtin)


Platform Simulation Attributes

Table 2: Platform Simulation Attributes

AttributeValueDescription
stoponctrlcstoponctrlcStop on control-C



Processor [arm.ovpworld.org/processor/arm/1.0] instance: cpu

Processor model type: 'arm' variant 'Cortex-A9UP' definition
Imperas OVP processor models support multiple variants and details of the variants implemented in this model can be found in:
- the Imperas installation located at ImperasLib/source/arm.ovpworld.org/processor/arm/1.0/doc
- the OVP website: OVP_Model_Specific_Information_arm_Cortex-A9UP.pdf

Description
ARM Processor Model

Licensing
Usage of binary model under license governing simulator usage.
Note that for models of ARM CPUs the license includes the following terms:
Licensee is granted a non-exclusive, worldwide, non-transferable, revocable licence to:
If no source is being provided to the Licensee: use and copy only (no modifications rights are granted) the model for the sole purpose of designing, developing, analyzing, debugging, testing, verifying, validating and optimizing software which: (a) (i) is for ARM based systems; and (ii) does not incorporate the ARM Models or any part thereof; and (b) such ARM Models may not be used to emulate an ARM based system to run application software in a production or live environment.
If source code is being provided to the Licensee: use, copy and modify the model for the sole purpose of designing, developing, analyzing, debugging, testing, verifying, validating and optimizing software which: (a) (i) is for ARM based systems; and (ii) does not incorporate the ARM Models or any part thereof; and (b) such ARM Models may not be used to emulate an ARM based system to run application software in a production or live environment.
In the case of any Licensee who is either or both an academic or educational institution the purposes shall be limited to internal use.
Except to the extent that such activity is permitted by applicable law, Licensee shall not reverse engineer, decompile, or disassemble this model. If this model was provided to Licensee in Europe, Licensee shall not reverse engineer, decompile or disassemble the Model for the purposes of error correction.
The License agreement does not entitle Licensee to manufacture in silicon any product based on this model.
The License agreement does not entitle Licensee to use this model for evaluating the validity of any ARM patent.
Source of model available under separate Imperas Software License Agreement.

Limitations
Instruction pipelines are not modeled in any way. All instructions are assumed to complete immediately. This means that instruction barrier instructions (e.g. ISB, CP15ISB) are treated as NOPs, with the exception of any undefined instruction behavior, which is modeled. The model does not implement speculative fetch behavior. The branch cache is not modeled.
Caches and write buffers are not modeled in any way. All loads, fetches and stores complete immediately and in order, and are fully synchronous (as if the memory was of Strongly Ordered or Device-nGnRnE type). Data barrier instructions (e.g. DSB, CP15DSB) are treated as NOPs, with the exception of any undefined instruction behavior, which is modeled. Cache manipulation instructions are implemented as NOPs, with the exception of any undefined instruction behavior, which is modeled.
Real-world timing effects are not modeled: all instructions are assumed to complete in a single cycle.
Performance Monitors are implemented as a register interface only.
TLBs are architecturally-accurate but not device accurate. This means that all TLB maintenance and address translation operations are fully implemented but the cache is larger than in the real device.

Verification
Models have been extensively tested by Imperas. ARM Cortex-A models have been successfully used by customers to simulate SMP Linux, Ubuntu Desktop, VxWorks and ThreadX on Xilinx Zynq virtual platforms.

Core Features
Thumb-2 instructions are supported.
Trivial Jazelle extension is implemented.

Memory System
Security extensions are implemented (also known as TrustZone). Non-secure accesses can be made visible externally by connecting the processor to a 41-bit physical bus, in which case bits 39..0 give the true physical address and bit 40 is the NS bit.
VMSA secure and non-secure address translation is implemented.

Advanced SIMD and Floating-Point Features
SIMD and VFP instructions are implemented.
The model implements trapped exceptions if FPTrap is set to 1 in MVFR0 (for AArch32) or MVFR0_EL1 (for AArch64). When floating point exception traps are taken, cumulative exception flags are not updated (in other words, cumulative flag state is always the same as prior to instruction execution, even for SIMD instructions). When multiple enabled exceptions are raised by a single floating point operation, the exception reported is the one in least-significant bit position in FPSCR (for AArch32) or FPCR (for AArch64). When multiple enabled exceptions are raised by different SIMD element computations, the exception reported is selected from the lowest-index-number SIMD operation. Contact Imperas if requirements for exception reporting differ from these.
Trapped exceptions not are implemented in this variant (FPTrap=0)

Integration Support
This model implements a number of non-architectural pseudo-registers and other features to facilitate integration.

Memory Transaction Query
Two registers are intended for use within memory callback functions to provide additional information about the current memory access. Register transactPL indicates the processor execution level of the current access (0-3). Note that for load/store translate instructions (e.g. LDRT, STRT) the reported execution level will be 0, indicating an EL0 access. Register transactAT indicates the type of memory access: 0 for a normal read or write; and 1 for a physical access resulting from a page table walk.

Page Table Walk Query
A banked set of registers provides information about the most recently completed page table walk. There are up to six banks of registers: bank 0 is for stage 1 walks, bank 1 is for stage 2 walks, and banks 2-5 are for stage 2 walks initiated by stage 1 level 0-3 entry lookups, respectively. Banks 1-5 are present only for processors with virtualization extensions. The currently active bank can be set using register PTWBankSelect. Register PTWBankValid is a bitmask indicating which banks contain valid data: for example, the value 0xb indicates that banks 0, 1 and 3 contain valid data.
Within each bank, there are registers that record addresses and values read during that page table walk. Register PTWBase records the table base address. Registers PTWAddressL0-PTWAddressL3 record the addresses of level 0 to level 3 entries read, respectively, and register PTWAddressValid is a bitmask indicating which address registers contain valid data: for example, the value 0xe indicates that PTWAddressL1-PTWAddressL3 are valid but PTWAddressL0 is not. Registers PTWValueL0-PTWValueL3 contain entry values read at level 0 to level 3. Register PTWInput contains the input address that starts a walk and Register PTWOutput contains the result address (valid only if the page table walk completes). Register PTWValueValid is a bitmask indicating which value registers contain valid data: bits 0-3 indicate PTWValueL0-PTWValueL3, respectively, bit 4 indicates PTWBase, bit 5 indicates PTWInput and bit 6 indicates PTWOutput.

Artifact Page Table Walks
Registers are also available to enable a simulation environment to initiate an artifact page table walk (for example, to determine the ultimate PA corresponding to a given VA). Register PTWI_EL1S initiates a secure EL1 table walk for a fetch. Register PTWD_EL1S initiates a secure EL1 table walk for a load or store (note that current ARM processors have unified TLBs, so these registers are synonymous). Registers PTW[ID]_EL1NS initiate walks for non-secure EL1 accesses. Registers PTW[ID]_EL2 initiate EL2 walks. Registers PTW[ID]_S2 initiate stage 2 walks. Registers PTW[ID]_EL3 initiate AArch64 EL3 walks. Finally, registers PTW[ID]_current initiate current-mode walks (useful in a memory callback context). Each walk fills the query registers described above.

MMU and Page Table Walk Events
Two events are available that allow a simulation environment to be notified on MMU and page table walk actions. Event mmuEnable triggers when any MMU is enabled or disabled. Event pageTableWalk triggers on completion of any page table walk (including artifact walks).

Artifact Address Translations
A simulation environment can trigger an artifact address translation operation by writing to the architectural address translation registers (e.g. ATS1CPR). The results of such translations are written to an integration support register artifactPAR, instead of the architectural PAR register. This means that such artifact writes will not perturb architectural state.

Halt Reason Introspection
An artifact register HaltReason can be read to determine the reason or reasons that a processor is halted. This register is a bitfield, with the following encoding: bit 0 indicates the processor has executed a wait-for-event (WFE) instruction; bit 1 indicates the processor has executed a wait-for-interrupt (WFI) instruction; and bit 2 indicates the processor is held in reset.

System Register Access Monitor
If parameter enableSystemMonitorBus is True, an artifact 32-bit bus "SystemMonitor" is enabled for each PE. Every system register read or write by that PE is then visible as a read or write on this artifact bus, and can therefore be monitored using callbacks installed in the client environment (use opBusReadMonitorAdd/opBusWriteMonitorAdd or icmAddBusReadCallback/icmAddBusWriteCallback, depending on the client API). The format of the address on the bus is as follows:
bits 31:26 - zero
bit 25 - 1 if AArch64 access, 0 if AArch32 access
bit 24 - 1 if non-secure access, 0 if secure access
bits 23:20 - CRm value
bits 19:16 - CRn value
bits 15:12 - op2 value
bits 11:8 - op1 value
bits 7:4 - op0 value (AArch64) or coprocessor number (AArch32)
bits 3:0 - zero
As an example, to view non-secure writes to writes to CNTFRQ_EL0 in AArch64 state, install a write monitor on address range 0x020e0330:0x020e0333.

System Register Implementation
If parameter enableSystemBus is True, an artifact 32-bit bus "System" is enabled for each PE. Slave callbacks installed on this bus can be used to implement modified system register behavior (use opBusSlaveNew or icmMapExternalMemory, depending on the client API). The format of the address on the bus is the same as for the system monitor bus, described above.

Instance Parameters
Several parameters can be specified when a processor is instanced in a platform. For this processor instance 'cpu' it has been instanced with the following parameters:

Table 3: Processor Instance 'cpu' Parameters (Configurations)

ParameterValueDescription
endianlittleSelect processor endian (big or little)
simulateexceptionssimulateexceptionsCauses the processor simulate exceptions instead of halting
mips200.0The nominal MIPS for the processor

Table 4: Processor Instance 'cpu' Parameters (Attributes)

Parameter NameValueType
variantCortex-A9UPenum
compatibilityISAenum
showHiddenRegs0bool


Memory Map for processor 'cpu' bus: 'bus1'
Processor instance 'cpu' is connected to bus 'bus1' using master port 'INSTRUCTION'.

Processor instance 'cpu' is connected to bus 'bus1' using master port 'DATA'.

Table 5: Memory Map ( 'cpu' / 'bus1' [width: 32] )

Lo AddressHi AddressInstanceComponent
0x00x7FFFFFFram1Bridgebridge
0x100000000x10000FFFcmCoreModule9x6
0x130000000x13000FFFpitIcpCounterTimer
0x140000000x14000FFFpic1IntICP
0x150000000x15000FFFrtcRtcPL031
0x160000000x16000FFFuart1UartPL011
0x170000000x17000FFFuart2UartPL011
0x180000000x18000FFFkb1KbPL050
0x190000000x19000FFFms1KbPL050
0x1A0000000x1A000FFFld1DebugLedAndDipSwitch
0x1C0000000x1C000FFFmmciMmciPL181
0x1D0000000x1D000FFFambaDummyram
0x800000000x87FFFFFFram2Bridgebridge
0xC00000000xC0000FFFlcdLcdPL110
0xC80000000xC8000FFFethlanLAN9118
0xCA0000000xCA000FFFpic2IntICP
0xCB0000000xCB00000FicpIcpControl

Table 6: Bridged Memory Map ( 'cpu' / 'ram1Bridge' / 'membus' [width: 32] )

Lo AddressHi AddressInstanceComponent
0x00x7FFFFFFram1ram
remappableremappablelcdLcdPL110

Table 7: Bridged Memory Map ( 'cpu' / 'ram2Bridge' / 'membus' [width: 32] )

Lo AddressHi AddressInstanceComponent
0x00x7FFFFFFram1ram
remappableremappablelcdLcdPL110


Net Connections to processor: 'cpu'

Table 8: Processor Net Connections ( 'cpu' )

Net PortNetInstanceComponent
irqirqpic1IntICP
fiqfiqpic1IntICP



Peripheral Instances


Peripheral [arm.ovpworld.org/peripheral/CoreModule9x6/1.0] instance: cm

Description
ARM Integrator Board 9x6 Core Module Registers

Limitations
none

Reference
ARM Integrator CM926EJ-S, CM946E-S, CM966E-S, CM1026EJ-S, and CM1136JF-S User Guide (DUI 0138)

Licensing
Open Source Apache 2.0

There are no configuration options set for this peripheral instance.


Peripheral [arm.ovpworld.org/peripheral/IntICP/1.0] instance: pic1

Description
ARM Integrator Board interrupt controller

Limitations
none

Reference
Integrator User Guide Compact Platform Baseboard HBI-0086 (DUI 0159B)

Licensing
Open Source Apache 2.0

There are no configuration options set for this peripheral instance.


Peripheral [arm.ovpworld.org/peripheral/IntICP/1.0] instance: pic2

Description
ARM Integrator Board interrupt controller

Limitations
none

Reference
Integrator User Guide Compact Platform Baseboard HBI-0086 (DUI 0159B)

Licensing
Open Source Apache 2.0

There are no configuration options set for this peripheral instance.


Peripheral [smsc.ovpworld.org/peripheral/LAN9118/1.0] instance: ethlan

Description
Fully functional Model of SMSC LAN9118 for Arm Versatile Express platforms. For full details please consult README-EMAC.txt

Licensing
Open Source Apache 2.0

Limitations
See README-EMAC.txt

Reference
SMSC LAN9118 High Performance single-chip 10/100 Non-PCI Ethernet Controller Datasheet Revision 1.5 (07-11-08)

There are no configuration options set for this peripheral instance.


Peripheral [arm.ovpworld.org/peripheral/IcpCounterTimer/1.0] instance: pit

Description
ARM Integrator Board Counter/Timer Module

Limitations
none

Reference
Integrator User Guide Compact Platform Baseboard HBI-0086 (DUI 0159B)

Licensing
Open Source Apache 2.0

There are no configuration options set for this peripheral instance.


Peripheral [arm.ovpworld.org/peripheral/IcpControl/1.0] instance: icp

Description
ARM Integrator Board Controller Module

Limitations
none

Reference
Integrator User Guide Compact Platform Baseboard HBI-0086 (DUI 0159B)

Licensing
Open Source Apache 2.0

There are no configuration options set for this peripheral instance.


Peripheral [arm.ovpworld.org/peripheral/DebugLedAndDipSwitch/1.0] instance: ld1

Description
ARM Integrator Board Debug LEDs and DIP Switch Interface

Limitations
none

Reference
Integrator User Guide Compact Platform Baseboard HBI-0086 (DUI 0159B)

Licensing
Open Source Apache 2.0

There are no configuration options set for this peripheral instance.


Peripheral [arm.ovpworld.org/peripheral/KbPL050/1.0] instance: kb1

Description
ARM PL050 PS2 Keyboard or mouse controller

Limitations
None

Reference
ARM PrimeCell PS2 Keyboard/Mouse Interface (PL050) Technical Reference Manual (ARM DDI 0143)

Licensing
Open Source Apache 2.0

Table 9: Configuration options (attributes) set for instance 'kb1'

AttributesValue
isMouse0
grabDisable0



Peripheral [arm.ovpworld.org/peripheral/KbPL050/1.0] instance: ms1

Description
ARM PL050 PS2 Keyboard or mouse controller

Limitations
None

Reference
ARM PrimeCell PS2 Keyboard/Mouse Interface (PL050) Technical Reference Manual (ARM DDI 0143)

Licensing
Open Source Apache 2.0

Table 10: Configuration options (attributes) set for instance 'ms1'

AttributesValue
isMouse1
grabDisable1



Peripheral [arm.ovpworld.org/peripheral/RtcPL031/1.0] instance: rtc

Description
ARM PL031 Real Time Clock (RTC)

Limitations
none

Reference
ARM PrimeCell Real Time Clock (PL031) Technical Reference Manual (ARM DDI 0224)

Licensing
Open Source Apache 2.0

There are no configuration options set for this peripheral instance.


Peripheral [arm.ovpworld.org/peripheral/UartPL011/1.0] instance: uart1

Description
ARM PL011 UART

Limitations
This is not a complete model of the PL011. There is no modeling of physical aspects of the UART, such as baud rates etc.

Reference
ARM PrimeCell UART (PL011) Technical Reference Manual (ARM DDI 0183)

Licensing
Open Source Apache 2.0

Table 11: Configuration options (attributes) set for instance 'uart1'

AttributesValue
variantARM
outfileuart1.log
finishOnDisconnect1



Peripheral [arm.ovpworld.org/peripheral/UartPL011/1.0] instance: uart2

Description
ARM PL011 UART

Limitations
This is not a complete model of the PL011. There is no modeling of physical aspects of the UART, such as baud rates etc.

Reference
ARM PrimeCell UART (PL011) Technical Reference Manual (ARM DDI 0183)

Licensing
Open Source Apache 2.0

Table 12: Configuration options (attributes) set for instance 'uart2'

AttributesValue
variantARM
outfileuart2.log
finishOnDisconnect1



Peripheral [arm.ovpworld.org/peripheral/MmciPL181/1.0] instance: mmci

Description
ARM PrimeCell Multimedia Card Interface (MMCI)

Limitations
None

Licensing
Open Source Apache 2.0

Reference
ARM PrimeCell Multimedia Card Interface (Pl180) Technical Reference Manual (ARM DDI 0172)

There are no configuration options set for this peripheral instance.


Peripheral [arm.ovpworld.org/peripheral/LcdPL110/1.0] instance: lcd

Description
ARM PL110 LCD Controller

Limitations
The VGA display refresh is not optimised resulting in the VGA peripheral causing a limit on the maximum performance of a platform it contains to be around 300 MIPS (actual dependent upon refresh rate of LCD).
The LCD peripheral utilises memory watchpoints to optimise display refresh. This requires the use of ICM memory for the frame buffers, which currently may stop its use in SystemC TLM2 platforms.
Interrupts are not supported

Reference
ARM PrimeCell Color LCD Controller (PL111) Technical Reference Manual (ARM DDI 0293)

Licensing
Open Source Apache 2.0

Table 13: Configuration options (attributes) set for instance 'lcd'

AttributesValue
busOffset0x80000000
scanDelay50000



Peripheral [arm.ovpworld.org/peripheral/SmartLoaderArmLinux/1.0] instance: smartLoader

Licensing
Open Source Apache 2.0

Description
Psuedo-peripheral to perform memory initialisation for an ARM based Linux kernel boot: Loads Linux kernel image file and (optional) initial ram disk image into memory. Writes ATAG data into memory. Writes tiny boot code at physical memory base that configures the registers as expected by Linux Kernel and then jumps to boot address (image load address by default).

Limitations
Only supports little endian

Reference
See ARM Linux boot requirements in Linux source tree at documentation/arm/Booting

There are no configuration options set for this peripheral instance.


Other Sites/Pages with similar information

Information on the ArmIntegratorCP Virtual Platform can also be found on other web sites :
www.ovpworld.org has the library pages http://www.ovpworld.org/library/wikka.php?wakka=CategoryPlatform
www.imperas.com has more information on the model library

A couple of documents (from other related sites that might be of interest)
http://www.ovpworld.org: Function by function Reference Guide for BHM / PPM APIs.
http://www.ovpworld.org: VMI Memory Modeled Component (VMI MMC) API Reference Guide

Two Videos on these models (from other sites)
http://www.ovpworld.org: OR1K Demo Video Presentation
http://www.ovpworld.org: Altera Nios II Bare Metal & Cyclone III Linux Booting Demo Video


Currently available Imperas / OVP Virtual Platforms / Virtual Prototypes.

FamilyVirtual Platform / Virtual Prototype
ARM Based Platforms    BareMetalArm7Single BareMetalArmCortexADual BareMetalArmCortexASingle BareMetalArmCortexASingleAngelTrap BareMetalArmCortexMSingle AlteraCycloneV_HPS ArmIntegratorCP ArmVersatileExpress ArmVersatileExpress-CA15 ArmVersatileExpress-CA9 AtmelAT91SAM7 ArmCortexMFreeRTOS ArmCortexMuCOS-II HeteroArmNucleusMIPSLinux FreescaleKinetis60 FreescaleKinetis64 FreescaleVybridVFxx AlteraCycloneV_HPS ArmIntegratorCP ARMv8-A-FMv1 ArmVersatileExpress ArmVersatileExpress-CA15 ArmVersatileExpress-CA9 AtmelAT91SAM7 ArmCortexMFreeRTOS ArmCortexMuCOS-II ArmuKernel Zynq_PS
MIPS Based Platforms    BareMetalM14KSingle BareMetalMips32Dual BareMetalMips32Single BareMetalMips64Single BareMetalMipsDual BareMetalMipsSingle HeteroArmNucleusMIPSLinux MipsMalta MipsMalta
Vendor Platforms    BareMetalNios_IISingle AlteraCycloneIII_3c120 AlteraCycloneV_HPS AlteraCycloneIII_3c120 AlteraCycloneV_HPS BareMetalArcSingle BareMetalArm7Single BareMetalArmCortexADual BareMetalArmCortexASingle BareMetalArmCortexASingleAngelTrap BareMetalArmCortexMSingle ArmIntegratorCP ArmVersatileExpress ArmVersatileExpress-CA15 ArmVersatileExpress-CA9 ArmIntegratorCP ARMv8-A-FMv1 ArmVersatileExpress ArmVersatileExpress-CA15 ArmVersatileExpress-CA9 AtmelAT91SAM7 AtmelAT91SAM7 FreescaleKinetis60 FreescaleKinetis64 FreescaleVybridVFxx Or1kUclinux ArmCortexMFreeRTOS ArmCortexMuCOS-II HeteroArmNucleusMIPSLinux ArmCortexMFreeRTOS ArmCortexMuCOS-II ArmuKernel ArmuKernelDual Quad_ArmVersatileExpress-CA15 BareMetalM14KSingle BareMetalMips32Dual BareMetalMips32Single BareMetalMips64Single BareMetalMipsDual BareMetalMipsSingle MipsMalta MipsMalta BareMetalOr1kSingle BareMetalM16cSingle BareMetalPowerPc32Single BareMetalV850Single ghs-multi RenesasUPD70F3441 ghs-multi RenesasUPD70F3441 Zynq_PL_DualMicroblaze Zynq_PL_NoC Zynq_PL_NoC_node Zynq_PL_NostrumNoC Zynq_PL_NostrumNoC_node Zynq_PL_RO Zynq_PL_SingleMicroblaze Zynq_PL_TTELNoC Zynq_PL_TTELNoC_node XilinxML505 XilinxML505 zc702 zc706 Zynq Zynq_PL_Default Zynq_PS