| Type | Instance | Vendor | Component | |
|---|---|---|---|---|
| Processor | arm1 | arm.ovpworld.org | arm | ARM926EJ-S |
| Peripheral | cm | arm.ovpworld.org | CoreModule9x6 | |
| Peripheral | pic1 | arm.ovpworld.org | IntICP | |
| Peripheral | pic2 | arm.ovpworld.org | IntICP | |
| Peripheral | ethlan | smsc.ovpworld.org | LAN9118 | |
| Peripheral | pit | arm.ovpworld.org | IcpCounterTimer | |
| Peripheral | icp | arm.ovpworld.org | IcpControl | |
| Peripheral | ld1 | arm.ovpworld.org | DebugLedAndDipSwitch | |
| Peripheral | kb1 | arm.ovpworld.org | KbPL050 | |
| Peripheral | ms1 | arm.ovpworld.org | KbPL050 | |
| Peripheral | rtc | arm.ovpworld.org | RtcPL031 | |
| Peripheral | uart1 | arm.ovpworld.org | UartPL011 | |
| Peripheral | uart2 | arm.ovpworld.org | UartPL011 | |
| Peripheral | mmci | arm.ovpworld.org | MmciPL181 | |
| Peripheral | lcd | arm.ovpworld.org | LcdPL110 | |
| Peripheral | smartLoader | arm.ovpworld.org | SmartLoaderArmLinux | |
| Memory | ram1 | ovpworld.org | ram | |
| Memory | ambaDummy | ovpworld.org | ram | |
| Bus | bus1 | (builtin) | address width:32 | |
| Bus | membus | (builtin) | address width:32 | |
| Bridge | ram1Bridge | (builtin) | ||
| Bridge | ram2Bridge | (builtin) |
LIBRARY | COMPANIES | PLATFORMS | PROCESSORS | PERIPHERALS
ArmArmintegratorcp
When running a platform in a Windows or Linux shell several command arguments can be specified. Typically there is a '-help' command which lists the commands available in the platforms.
For example: myplatform.exe -help
Some command line arguments require a value to be provided.
For example: myplatform.exe -program myimagefile.elf
- the Imperas installation located at ImperasLib/source/arm.ovpworld.org/processor/arm/1.0/doc
- the OVP website: OVP_Model_Specific_Information_arm_ARM926EJ-S.pdf
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.
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.
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.
Trivial Jazelle extension is implemented.
VMSA address translation is implemented.
TLB behavior is controlled by parameter ASIDCacheSize. If this parameter is 0, then an unlimited number of TLB entries will be maintained concurrently. If this parameter is non-zero, then only TLB entries for up to ASIDCacheSize different ASIDs will be maintained concurrently initially; as new ASIDs are used, TLB entries for less-recently used ASIDs are deleted, which improves model performance in some cases (especially when 16-bit ASIDs are in use). If the model detects that the TLB entry cache is too small (entry ejections are very frequent), it will increase the cache size automatically. In this variant, ASIDCacheSize is 8
1 ITCM is implemented.
1 DTCM is implemented.
Value 0x004: enable debugging of MMU/MPU mappings.
Value 0x080: enable debugging of all system register accesses.
Value 0x100: enable debugging of all traps of system register accesses.
Value 0x200: enable verbose debugging of other miscellaneous behavior (for example, the reason why a particular instruction is undefined).
Value 0x800: enable dynamic validation of TLB entries against in-memory page table contents (finds some classes of error where page table entries are updated without a subsequent flush of affected TLB entries).
All other bits in the debug bitmask are reserved and must not be set to non-zero values.
Value "undefined": any reference to R15 in such a situation is treated as UNDEFINED;
Value "nop": any reference to R15 in such a situation causes the instruction to be treated as a NOP;
Value "raz_wi": any reference to R15 in such a situation causes the instruction to be treated as a RAZ/WI (that is, R15 is read as zero and write-ignored);
Value "execute": any reference to R15 in such a situation is executed using the current value of R15 on read, and writes to R15 are allowed (but are not interworking).
Value "assert": any reference to R15 in such a situation causes the simulation to halt with an assertion message (allowing any such unpredictable uses to be easily identified).
In this variant, the default value of "unpredictableR15" is "execute".
In this variant, the default value of "unpredictableModal" is "nop".
Within each bank, there are registers that record addresses and values read during that page table walk. Register PTWBase records the table base address, register PTWInput contains the input address that starts a walk, register PTWOutput contains the result address and register PTWPgSize contains the page size (PTWOutput and PTWPgSize are valid only if the page table walk completes). Registers PTWAddressL0-PTWAddressL3 record the addresses of level 0 to level 3 entries read, respectively. Register PTWAddressValid is a bitmask indicating which address registers contain valid data: bits 0-3 indicate PTWAddressL0-PTWAddressL3, respectively, bit 4 indicates PTWBase, bit 5 indicates PTWInput, bit 6 indicates both PTWOutput and PTWPgSize. For example, the value 0x73 indicates that PTWBase, PTWInput, PTWOutput, PTWPgSize and PTWAddressL0-L1 are valid but PTWAddressL2-L3 are not. Register PTWAddressNS is a bitmask indicating whether an address is in non-secure memory: bits 0-3 indicate PTWAddressL0-PTWAddressL3, respectively, bit 4 indicates PTWBase, bit 6 indicates PTWOutput (PTWInput is a VA and thus has no secure/non-secure info). Registers PTWValueL0-PTWValueL3 contain page table entry values read at level 0 to level 3. Register PTWValueValid is a bitmask indicating which value registers contain valid data: bits 0-3 indicate PTWValueL0-PTWValueL3, respectively.
Bit 1: EL0/EL1 stage 1 non-secure TLB
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.
Processor instance 'arm1' is connected to bus 'bus1' using master port 'DATA'.
There are no configuration options set for this peripheral instance.
There are no configuration options set for this peripheral instance.
There are no configuration options set for this peripheral instance.
There are no configuration options set for this peripheral instance.
There are no configuration options set for this peripheral instance.
There are no configuration options set for this peripheral instance.
There are no configuration options set for this peripheral instance.
There are no configuration options set for this peripheral instance.
There are no configuration options set for this peripheral instance.
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
There are no configuration options set for this peripheral instance.
ArmHoldingsPlatforms
OVP Virtual Platform: ArmIntegratorCP
This page provides detailed information about the OVP Virtual Platform Model of the arm.ovpworld.org ArmIntegratorCP platform.Licensing
Open Source Apache 2.0Description
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 ARM9x6Location
The ArmIntegratorCP virtual platform is located in an Imperas/OVP installation at the VLNV: arm.ovpworld.org / platform / ArmIntegratorCP / 1.0.Platform Summary
Table : Components in platform
Platform Simulation Attributes
Table 1: Platform Simulation Attributes
| Attribute | Value | Description |
|---|---|---|
| stoponctrlc | stoponctrlc | Stop on control-C |
Command Line Control of the Platform
Built-in Arguments
Table 2: Platform Built-in Arguments
| Attribute | Value | Description |
|---|---|---|
| allargs | allargs | The Command line parser will accept the complete imperas argument set. Note that this option is ignored in some Imperas products |
For example: myplatform.exe -help
Some command line arguments require a value to be provided.
For example: myplatform.exe -program myimagefile.elf
Platform Specific Command Line Arguments
Table 3: Platform Arguments
| Name | Type | Description |
|---|---|---|
| kernel | stringvar | The Linux Kernel image e.g. zImage |
| ramdisk | stringvar | Boot Linux Kernel from the specified ramdisk image e.g. fs.img |
| uartport | uns64var | set the port number to open on the UART (uart1) |
| uartconsole | boolvar | open a console terminal on the UART (uart1) |
| semihost | stringvar | Specify a semihost library (full path) |
| nographics | boolvar | Disable the LCD graphics window. |
Processor [arm.ovpworld.org/processor/arm/1.0] instance: arm1
Processor model type: 'arm' variant 'ARM926EJ-S' 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_ARM926EJ-S.pdf
Description
ARM Processor ModelLicensing
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.
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. ARM9 models have been successfully used by customers to simulate Linux and Nucleus on ArmIntegrator virtual platforms.Features
The precise set of implemented features in the model is defined by ID registers. Use overrides to modify these if required (for example override_PFR0 or override_AA64PFR0_EL1).Core Features
Thumb instructions are supported.Trivial Jazelle extension is implemented.
Memory System
FCSE extension is implemented.VMSA address translation is implemented.
TLB behavior is controlled by parameter ASIDCacheSize. If this parameter is 0, then an unlimited number of TLB entries will be maintained concurrently. If this parameter is non-zero, then only TLB entries for up to ASIDCacheSize different ASIDs will be maintained concurrently initially; as new ASIDs are used, TLB entries for less-recently used ASIDs are deleted, which improves model performance in some cases (especially when 16-bit ASIDs are in use). If the model detects that the TLB entry cache is too small (entry ejections are very frequent), it will increase the cache size automatically. In this variant, ASIDCacheSize is 8
1 ITCM is implemented.
1 DTCM is implemented.
Debug Mask
It is possible to enable model debug features in various categories. This can be done statically using the "override_debugMask" parameter, or dynamically using the "debugflags" command. Enabled debug features are specified using a bitmask value, as follows:Value 0x004: enable debugging of MMU/MPU mappings.
Value 0x080: enable debugging of all system register accesses.
Value 0x100: enable debugging of all traps of system register accesses.
Value 0x200: enable verbose debugging of other miscellaneous behavior (for example, the reason why a particular instruction is undefined).
Value 0x800: enable dynamic validation of TLB entries against in-memory page table contents (finds some classes of error where page table entries are updated without a subsequent flush of affected TLB entries).
All other bits in the debug bitmask are reserved and must not be set to non-zero values.
AArch32 Unpredictable Behavior
Many AArch32 instruction behaviors are described in the ARM ARM as CONSTRAINED UNPREDICTABLE. This section describes how such situations are handled by this model.Equal Target Registers
Some instructions allow the specification of two target registers (for example, double-width SMULL, or some VMOV variants), and such instructions are CONSTRAINED UNPREDICTABLE if the same target register is specified in both positions. In this model, such instructions are treated as UNDEFINED.Floating Point Load/Store Multiple Lists
Instructions that load or store a list of floating point registers (e.g. VSTM, VLDM, VPUSH, VPOP) are CONSTRAINED UNPREDICTABLE if either the uppermost register in the specified range is greater than 32 or (for 64-bit registers) if more than 16 registers are specified. In this model, such instructions are treated as UNDEFINED.Floating Point VLD[2-4]/VST[2-4] Range Overflow
Instructions that load or store a fixed number of floating point registers (e.g. VST2, VLD2) are CONSTRAINED UNPREDICTABLE if the upper register bound exceeds the number of implemented floating point registers. In this model, these instructions load and store using modulo 32 indexing (consistent with AArch64 instructions with similar behavior).If-Then (IT) Block Constraints
Where the behavior of an instruction in an if-then (IT) block is described as CONSTRAINED UNPREDICTABLE, this model treats that instruction as UNDEFINED.Use of R13
In architecture variants before ARMv8, use of R13 was described as CONSTRAINED UNPREDICTABLE in many circumstances. From ARMv8, most of these situations are no longer considered unpredictable. This model allows R13 to be used like any other GPR, consistent with the ARMv8 specification.Use of R15
Use of R15 is described as CONSTRAINED UNPREDICTABLE in many circumstances. This model allows such use to be configured using the parameter "unpredictableR15" as follows:Value "undefined": any reference to R15 in such a situation is treated as UNDEFINED;
Value "nop": any reference to R15 in such a situation causes the instruction to be treated as a NOP;
Value "raz_wi": any reference to R15 in such a situation causes the instruction to be treated as a RAZ/WI (that is, R15 is read as zero and write-ignored);
Value "execute": any reference to R15 in such a situation is executed using the current value of R15 on read, and writes to R15 are allowed (but are not interworking).
Value "assert": any reference to R15 in such a situation causes the simulation to halt with an assertion message (allowing any such unpredictable uses to be easily identified).
In this variant, the default value of "unpredictableR15" is "execute".
Unpredictable Instructions in Some Modes
Some instructions are described as CONSTRAINED UNPREDICTABLE in some modes only (for example, MSR accessing SPSR is CONSTRAINED UNPREDICTABLE in User and System modes). This model allows such use to be configured using the parameter "unpredictableModal", which can have values "undefined" or "nop". See the previous section for more information about the meaning of these values.In this variant, the default value of "unpredictableModal" is "nop".
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, register PTWInput contains the input address that starts a walk, register PTWOutput contains the result address and register PTWPgSize contains the page size (PTWOutput and PTWPgSize are valid only if the page table walk completes). Registers PTWAddressL0-PTWAddressL3 record the addresses of level 0 to level 3 entries read, respectively. Register PTWAddressValid is a bitmask indicating which address registers contain valid data: bits 0-3 indicate PTWAddressL0-PTWAddressL3, respectively, bit 4 indicates PTWBase, bit 5 indicates PTWInput, bit 6 indicates both PTWOutput and PTWPgSize. For example, the value 0x73 indicates that PTWBase, PTWInput, PTWOutput, PTWPgSize and PTWAddressL0-L1 are valid but PTWAddressL2-L3 are not. Register PTWAddressNS is a bitmask indicating whether an address is in non-secure memory: bits 0-3 indicate PTWAddressL0-PTWAddressL3, respectively, bit 4 indicates PTWBase, bit 6 indicates PTWOutput (PTWInput is a VA and thus has no secure/non-secure info). Registers PTWValueL0-PTWValueL3 contain page table entry values read at level 0 to level 3. Register PTWValueValid is a bitmask indicating which value registers contain valid data: bits 0-3 indicate PTWValueL0-PTWValueL3, respectively.
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.TLB Invalidation
A simulation environment can cause TLB state for one or more address translation regimes in the processor to be flushed by writing to the artifact register ResetTLBs. The argument is a bitmask value, in which non-zero bits select the TLBs to be flushed, as follows:Bit 1: EL0/EL1 stage 1 non-secure TLB
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 'arm1' it has been instanced with the following parameters:Table 4: Processor Instance 'arm1' Parameters (Configurations)
| Parameter | Value | Description |
|---|---|---|
| endian | little | Select processor endian (big or little) |
| simulateexceptions | simulateexceptions | Causes the processor simulate exceptions instead of halting |
| mips | 200.0 | The nominal MIPS for the processor |
Table 5: Processor Instance 'arm1' Parameters (Attributes)
| Parameter Name | Value | Type |
|---|---|---|
| variant | ARM926EJ-S | enum |
| compatibility | ISA | enum |
| showHiddenRegs | 0 | bool |
Memory Map for processor 'arm1' bus: 'bus1'
Processor instance 'arm1' is connected to bus 'bus1' using master port 'INSTRUCTION'.Processor instance 'arm1' is connected to bus 'bus1' using master port 'DATA'.
Table 6: Memory Map ( 'arm1' / 'bus1' [width: 32] )
| Lo Address | Hi Address | Instance | Component |
|---|---|---|---|
| 0x0 | 0x7FFFFFF | ram1Bridge | bridge |
| 0x10000000 | 0x10000FFF | cm | CoreModule9x6 |
| 0x13000000 | 0x13000FFF | pit | IcpCounterTimer |
| 0x14000000 | 0x14000FFF | pic1 | IntICP |
| 0x15000000 | 0x15000FFF | rtc | RtcPL031 |
| 0x16000000 | 0x16000FFF | uart1 | UartPL011 |
| 0x17000000 | 0x17000FFF | uart2 | UartPL011 |
| 0x18000000 | 0x18000FFF | kb1 | KbPL050 |
| 0x19000000 | 0x19000FFF | ms1 | KbPL050 |
| 0x1A000000 | 0x1A000FFF | ld1 | DebugLedAndDipSwitch |
| 0x1C000000 | 0x1C000FFF | mmci | MmciPL181 |
| 0x1D000000 | 0x1D000FFF | ambaDummy | ram |
| 0x80000000 | 0x87FFFFFF | ram2Bridge | bridge |
| 0xC0000000 | 0xC0000FFF | lcd | LcdPL110 |
| 0xC8000000 | 0xC8000FFF | ethlan | LAN9118 |
| 0xCA000000 | 0xCA000FFF | pic2 | IntICP |
| 0xCB000000 | 0xCB00000F | icp | IcpControl |
Table 7: Bridged Memory Map ( 'arm1' / 'ram1Bridge' / 'membus' [width: 32] )
| Lo Address | Hi Address | Instance | Component |
|---|---|---|---|
| 0x0 | 0x7FFFFFF | ram1 | ram |
| remappable | remappable | lcd | LcdPL110 |
Table 8: Bridged Memory Map ( 'arm1' / 'ram2Bridge' / 'membus' [width: 32] )
| Lo Address | Hi Address | Instance | Component |
|---|---|---|---|
| 0x0 | 0x7FFFFFF | ram1 | ram |
| remappable | remappable | lcd | LcdPL110 |
Net Connections to processor: 'arm1'
Table 9: Processor Net Connections ( 'arm1' )
| Net Port | Net | Instance | Component |
|---|---|---|---|
| irq | irq | pic1 | IntICP |
| fiq | fiq | pic1 | IntICP |
Peripheral Instances
Peripheral [arm.ovpworld.org/peripheral/CoreModule9x6/1.0] instance: cm
Description
ARM Integrator Board 9x6 Core Module RegistersLimitations
noneReference
ARM Integrator CM926EJ-S, CM946E-S, CM966E-S, CM1026EJ-S, and CM1136JF-S User Guide (DUI 0138)Licensing
Open Source Apache 2.0There are no configuration options set for this peripheral instance.
Peripheral [arm.ovpworld.org/peripheral/IntICP/1.0] instance: pic1
Description
ARM Integrator Board interrupt controllerLimitations
noneReference
Integrator User Guide Compact Platform Baseboard HBI-0086 (DUI 0159B)Licensing
Open Source Apache 2.0There are no configuration options set for this peripheral instance.
Peripheral [arm.ovpworld.org/peripheral/IntICP/1.0] instance: pic2
Description
ARM Integrator Board interrupt controllerLimitations
noneReference
Integrator User Guide Compact Platform Baseboard HBI-0086 (DUI 0159B)Licensing
Open Source Apache 2.0There 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.txtLicensing
Open Source Apache 2.0Limitations
See README-EMAC.txtReference
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 ModuleLimitations
noneReference
Integrator User Guide Compact Platform Baseboard HBI-0086 (DUI 0159B)Licensing
Open Source Apache 2.0There are no configuration options set for this peripheral instance.
Peripheral [arm.ovpworld.org/peripheral/IcpControl/1.0] instance: icp
Description
ARM Integrator Board Controller ModuleLimitations
noneReference
Integrator User Guide Compact Platform Baseboard HBI-0086 (DUI 0159B)Licensing
Open Source Apache 2.0There 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 InterfaceLimitations
noneReference
Integrator User Guide Compact Platform Baseboard HBI-0086 (DUI 0159B)Licensing
Open Source Apache 2.0There 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 controllerLimitations
NoneReference
ARM PrimeCell PS2 Keyboard/Mouse Interface (PL050) Technical Reference Manual (ARM DDI 0143)Licensing
Open Source Apache 2.0Table 10: Configuration options (attributes) set for instance 'kb1'
| Attributes | Value |
|---|---|
| isMouse | 0 |
| grabDisable | 0 |
Peripheral [arm.ovpworld.org/peripheral/KbPL050/1.0] instance: ms1
Description
ARM PL050 PS2 Keyboard or mouse controllerLimitations
NoneReference
ARM PrimeCell PS2 Keyboard/Mouse Interface (PL050) Technical Reference Manual (ARM DDI 0143)Licensing
Open Source Apache 2.0Table 11: Configuration options (attributes) set for instance 'ms1'
| Attributes | Value |
|---|---|
| isMouse | 1 |
| grabDisable | 1 |
Peripheral [arm.ovpworld.org/peripheral/RtcPL031/1.0] instance: rtc
Description
ARM PL031 Real Time Clock (RTC)Limitations
noneReference
ARM PrimeCell Real Time Clock (PL031) Technical Reference Manual (ARM DDI 0224)Licensing
Open Source Apache 2.0There are no configuration options set for this peripheral instance.
Peripheral [arm.ovpworld.org/peripheral/UartPL011/1.0] instance: uart1
Description
ARM PL011 UARTLimitations
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.0Table 12: Configuration options (attributes) set for instance 'uart1'
| Attributes | Value |
|---|---|
| variant | ARM |
| outfile | uart1.log |
| finishOnDisconnect | 1 |
Peripheral [arm.ovpworld.org/peripheral/UartPL011/1.0] instance: uart2
Description
ARM PL011 UARTLimitations
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.0Table 13: Configuration options (attributes) set for instance 'uart2'
| Attributes | Value |
|---|---|
| variant | ARM |
| outfile | uart2.log |
| finishOnDisconnect | 1 |
Peripheral [arm.ovpworld.org/peripheral/MmciPL181/1.0] instance: mmci
Description
ARM PrimeCell Multimedia Card Interface (MMCI)Limitations
NoneLicensing
Open Source Apache 2.0Reference
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 ControllerLimitations
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.0Table 14: Configuration options (attributes) set for instance 'lcd'
| Attributes | Value |
|---|---|
| busOffset | 0x80000000 |
| scanDelay | 50000 |
Peripheral [arm.ovpworld.org/peripheral/SmartLoaderArmLinux/1.0] instance: smartLoader
Licensing
Open Source Apache 2.0Description
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 endianReference
See ARM Linux boot requirements in Linux source tree at documentation/arm/BootingThere are no configuration options set for this peripheral instance.
ArmHoldingsPlatforms
Page was generated in 0.0625 seconds