Information for BareMetalArcSingle
This page provides detailed information about the arc.ovpworld.org BareMetalArcSingle Virtual Platform / Virtual Prototype. Table 1: Components in platform
Bare Metal Platform for an ARC Processor. The bare metal platform instantiates a single ARC processor instance. The processor operates using little endian data ordering. It creates contiguous memory from 0x00000000 to 0xFFFFFFFF. The platform can be passed any application compiled to an ARC elf format. ./platform.
Open Source Apache 2.0
BareMetal platform for execution of ARC binary files compiled with FOSS for Synopsys DesignWare ARC Processors CrossCompiler toolchain.
None, baremetal platform definition
The BareMetalArcSingle virtual platform is located in an Imperas/OVP installation at the VLNV: arc.ovpworld.org / platform / BareMetalArcSingle / 1.0.
Table 1: Components in platform
Platform Simulation Attributes
Table 2: Platform Simulation Attributes
|stoponctrlc||stoponctrlc||Stop on control-C|
Command Line Control of the Platform
Table 3: Platform Built-in Arguments
|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
No platform specific command line arguments have been specified.
Processor [arc.ovpworld.org/processor/arc/1.0] instance: cpu1
Processor model type: 'arc' variant '700' 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/arc.ovpworld.org/processor/arc/1.0/doc
- the OVP website: OVP_Model_Specific_Information_arc_700.pdf
ARC 700 processor model (ARCv1 architecture)
Usage of binary model under license governing simulator usage. Source of model available under Imperas Software License Agreement.
Instruction pipelines are not modeled in any way. All instructions are assumed to complete immediately.
Instruction and data caches are not modeled, except for the auxiliary register interface.
External host debug is not modeled, except for the auxiliary register interface.
Real-world timing effects are not modeled. All instructions are assumed to complete in a single cycle.
Models have been validated correct in a cooperative project between Imperas and ARC
ARC Processor ARC6xx/ARC7xx Reference Documentation
The model has been designed for debug using GNU gdb ARCompact/ARCv2 ISA elf32 version 7.5.1. To ensure correct behavior, enter the following command into gdb before attempting to connect to the processor:
set architecture ARC700
Failure to do this may cause the debugging session to fail because of g-packet size mismatch.
The model implements the full ARCv1 instruction set.
The exact set of core instructions present can be configured by a number of parameters: see information for opt-swap, opt-bitscan, opt-extended-arith and opt-multiply in the table below.
Timer 0 and Timer 1 can be enabled using parameters opt-timer0 and opt-timer1, respectively.
The versions of DCCM and ICCM build config registers can be specified using parameters opt-dccm-version and opt-iccm-version, respectively. The sizes of DCCM, ICCM0 and ICCM1 can be specified using parameters opt-dccm-size, opt-iccm0-size and opt-iccm1-size, respectively. Reset base addresses for the ICCMs can be specified using opt-iccm0-base and opt-iccm1-base. Note that the DCCM reset base address is architecturally defined (0x80000000) and not configurable. When CCMs are present, bus ports called DCCM0, ICCM0 and ICCM1 are created so that CCM contents may be viewed or modified externally by connecting to these ports. Parameter opt-internal-ccms specifies whether CCM memory is modeled internally or externally. If modeled externally, the CCMs must be implemented on a bus which is then connected to the CCM bus ports listed above (this parameter is ignored if CCM ports are unconnected; in that case, CCMs are always modeled internally). Parameter opt-reset-internal-ccms indicates that internally-modeled CCMs should be cleared to zero on a processor reset; if False, then internally-modeled CCMs retain their previous state after a reset.
The set of core registers can be specified using parameter opt-extension-core-regs. This is a 64-bit value in which a 1-bit implies the presence of that core extension register. For example, a value of 0xf00000000ULL implies that extension registers r32-r35 should be configured.
The reset value of the exception vector base register can be specified using parameter opt-intvbase-preset.
Auxiliary Register External Implementation
If parameter "enable-aux-bus" is True, an artifact 36-bit bus "Auxiliary" is enabled. Slave callbacks installed on this bus can be used to implement auxiliary register behavior (use opBusSlaveNew or icmMapExternalMemory, depending on the client API). An auxiliary with 32-bit index 0xABCDEFGH is mapped on the bus at address 0xABCDEFGH0.
Several parameters can be specified when a processor is instanced in a platform. For this processor instance 'cpu1' it has been instanced with the following parameters:
Table 4: Processor Instance 'cpu1' Parameters (Configurations)
|mips||100||The nominal MIPS for the processor|
|semihostvendor||arc.ovpworld.org||The VLNV vendor name of a Semihost library|
|semihostname||arcNewlib||The VLNV name of a Semihost library|
Table 5: Processor Instance 'cpu1' Parameters (Attributes)
Memory Map for processor 'cpu1' bus: 'bus'
Processor instance 'cpu1' is connected to bus 'bus' using master port 'INSTRUCTION'.
Processor instance 'cpu1' is connected to bus 'bus' using master port 'DATA'.
Table 6: Memory Map ( 'cpu1' / 'bus' [width: 32] )
|Lo Address||Hi Address||Instance||Component|
Net Connections to processor: 'cpu1'
There are no nets connected to this processor.
Information on the BareMetalArcSingle 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
http://www.ovpworld.org: Writing C Platforms and Modules using the OVP OP API
http://www.ovpworld.org: Creating Behavioral (Peripheral) components using BHM/PPM APIs and adding them to Platforms
Currently available Imperas / OVP Virtual Platforms / Virtual Prototypes for Embedded Software Development and Test Automation.