LIBRARY  |  COMPANIES |   PLATFORMS |   PROCESSORS |   PERIPHERALS
ArmBaremetalarmcortexmsingle



OVP Virtual Platform: BareMetalArmCortexMSingle

What is a Bare Metal Platform?

A 'Bare Metal' Platform consists of a single processor with memory available over its complete address range.

Bare Metal Platform

This is ideal for execution of a user application that has been compiled for the target processor core using cross-compilation.

Obtaining the BareMetalArmCortexMSingle platform and the OVP Simulator

The source and binary of the bare metal platforms are part of the OVP/Imperas downloads and live on a VLNV (Vendor Library Name Version) path.

To download from OVPworld, browse the OVP downloads page and download the OVPsim package. Click here to browse available downloads.

When installed this platform is found in your installation here: ImperasLib/source/arm.ovpworld.org/platform/BareMetalArmCortexMSingle/1.0.

Running the Bare Metal Platform

1. Run the installer to install into a local directory on your PC. We recommend you use a path without spaces, for example your home directory.

2. Enter the Demo Directory IMPERAS_HOME/Demo/BareMetalArmCortexMSingle

3. On Windows, double-click on the batch file xx.bat and on Linux run the script xx.sh to run a simple application elf file on the Bare Metal Platform.

You will see output something like:
Info (ARM_NEWLIB_RDI_HEAP_INFO) RDI heap_base=0xc0000000 
Hello
Info (ARM_NEWLIB_RDI_EXIT) Process has ended (exit)
Info 
Info ---------------------------------------------------
Info CPU 'CPU1' STATISTICS
Info   Type                  : arm
Info   Nominal MIPS          : 100
Info   Final program counter : 0x91a4
Info   Simulated instructions: 4,175
Info ---------------------------------------------------
Info 
Info ---------------------------------------------------
Info SIMULATION TIME STATISTICS
Info   Simulated time        : 0.00 seconds
Info   User time             : 0.02 seconds
Info   System time           : 0.00 seconds
Info ---------------------------------------------------

Setting Up for Re-building the Application

To rebuild the application and create the elf file you will need 3 things:
  • Cross-Compiler toolchain for thi processor
  • An OVP Installation
  • MSYS / MINGW environment (Windows Users Only)

Download and Installing the Cross-Compiler Toolchain

To download an appropriate tool chain, browse the OVP downloads page and download the package. Click here to browse.
If there is not one available please ask on the forum.

Once downloaded run the installer <packageName>.Windows32.exe for Windows and <packageName>.Linux32.exe for Linux to install on your PC.

Installing MSYS / MINGW Environment (Windows Users Only)

Obtaining and installing the MSYS and MINGW environment is described in Imperas_Installation_and_Getting_Started.pdf.

Rebuilding

You will need to be in the Demo/'baremetaldemodir' directory using an MSYS shell for Windows or a Linux shell.

Re-building the Application
> make application

Re-building the Bare Metal Platform
> make platform

Executing the application on the platform
You can just double click on the .bat file as done previously, or you can run from the msys command line:
> ./BareMetal.OS.exe hello.CROSS.elf



This page provides detailed information about the OVP Virtual Platform Model of the arm.ovpworld.org BareMetalArmCortexMSingle platform.

Description

Bare Metal Platform for an ARM Cortex-M series Processor (default Cortex-M3). The bare metal platform instantiates a single ARM Cortex-M series 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 ARM elf format. It may also be passed a new variant to be used (default Cortex-M3) ./platform.OS.exe --program application.CROSS.elf [ --variant ]

Licensing

Open Source Apache 2.0

Limitations

BareMetal platform for execution of ARM binary files compiled with Linaro 32-bit CrossCompiler toolchain for Cortex-M.

Location

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

Platform Summary

Table : Components in platform

TypeInstanceVendorComponent
Processorcpu1arm.ovpworld.orgarmmCortex-M3
Memorymemoryovpworld.orgram
Busbus(builtin)address width:32

Platform Simulation Attributes

Table 1: Platform Simulation Attributes

AttributeValueDescription
stoponctrlcstoponctrlcStop on control-C



Command Line Control of the Platform

Built-in Arguments

Table 2: Platform Built-in Arguments

AttributeValueDescription
allargsallargsThe Command line parser will accept the complete imperas argument set. Note that this option is ignored in some Imperas products

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

Platform Specific Command Line Arguments

No platform specific command line arguments have been specified.



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

Processor model type: 'armm' variant 'Cortex-M3' 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/armm/1.0/doc
- the OVP website: OVP_Model_Specific_Information_armm_Cortex-M3.pdf

Description

ARMM 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.
The License agreement does not entitle Licensee to use the model to emulate an ARM based system to run application software in a production or live environment.
Source of model available under separate Imperas Software License Agreement.

Limitations

Performance Monitors are not implemented.
Debug Extension and related blocks are not implemented.

Verification

Models have been extensively tested by Imperas. ARM Cortex-M models have been successfully used by customers to simulate the Micrium uC/OS-II kernel and FreeRTOS.

Features

The model is configured with 16 interrupts and 3 priority bits (use override_numInterrupts and override_priorityBits parameters to change these).
Thumb-2 instructions are supported.
MPU is present. Use parameter override_MPU_TYPE to disable it or change the number of MPU regions if required.
SysTick timer is present. Use parameter SysTickPresent to disable it if required.
FPU extension is not present. Use parameter override_MVFR0 to enable it if required.
DSP extension is not present. Use parameter override_InstructionAttributes3 to enable it if required.
Bit-band region is present. Use parameter BitBandPresent to disable it if required.

Unpredictable Behavior

Many 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.

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

Use of R13 is described as CONSTRAINED UNPREDICTABLE in many circumstances. This model allows R13 to be used like any other GPR.

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.
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".

Instance Parameters

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 3: Processor Instance 'cpu1' Parameters (Configurations)

ParameterValueDescription
endianlittleSelect processor endian (big or little)
mips100The nominal MIPS for the processor
semihostvendorarm.ovpworld.orgThe VLNV vendor name of a Semihost library
semihostnamearmNewlibThe VLNV name of a Semihost library

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

Parameter NameValueType
variantCortex-M3enum
compatibilitynopBKPTenum
resetAtTime00bool
UAL1bool

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 5: Memory Map ( 'cpu1' / 'bus' [width: 32] )

Lo AddressHi AddressInstanceComponent
0x00xFFFFFFFFmemoryram

Net Connections to processor: 'cpu1'

There are no nets connected to this processor.


ArmHoldingsPlatforms
Page was generated in 0.0318 seconds