| Type | Instance | Vendor | Component | |
|---|---|---|---|---|
| Processor | cpu1 | ovpworld.org | or1k | |
| Peripheral | uart1 | national.ovpworld.org | 16550 | |
| Memory | mem1 | ovpworld.org | ram | |
| Memory | mem2 | ovpworld.org | ram | |
| Bus | bus1 | (builtin) | address width:32 |
LIBRARY | COMPANIES | PLATFORMS | PROCESSORS | PERIPHERALS
ImperasOr1kuclinux
This is ideal for execution of a user application that has been compiled for the target processor core using cross-compilation.
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/imperas.ovpworld.org/platform/Or1kUclinux/1.0.
2. Enter the Demo Directory IMPERAS_HOME/Demo/Or1kUclinux
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:
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.
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 imperas.ovpworld.org Or1kUclinux platform.
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
Processor instance 'cpu1' is connected to bus 'bus1' using master port 'DATA'.
The serial input/output from the simulator is implemented using the Serial Device Support described in OVP BHM and PPM API Functions Reference, which describes the parameters that control how the model interacts with the host computer.
Interrupts and FIFOs are supported.
Registers are aligned on 1 byte boundaries.
Values written to the MCR are ignored. Loopback mode is not supported.
The LSR is read-only. The model never sets the LSR 'Parity Error', 'Framing Error', 'Break Interrupt' or 'Error in RCVR FIFO' bits.
The MSR 'Data Set Ready' and 'Clear To Send' bits are set at reset and all other MSR bits are cleared. MSR bits will only be changed by writes to the MSR and values written to the Modem Status Register do not effect the operation of the model.
ImperasPlatforms
OVP Virtual Platform: Or1kUclinux
What is a Bare Metal Platform?
A 'Bare Metal' Platform consists of a single processor with memory available over its complete address range.This is ideal for execution of a user application that has been compiled for the target processor core using cross-compilation.
Obtaining the Or1kUclinux 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/imperas.ovpworld.org/platform/Or1kUclinux/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/Or1kUclinux
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 imperas.ovpworld.org Or1kUclinux platform.
Description
Platform for an Or1k Processor to execute uCLinux.Licensing
Open Source Apache 2.0Limitations
Provides sufficient functionality to execute uCLinux operating system and OR1K elf filesLocation
The Or1kUclinux virtual platform is located in an Imperas/OVP installation at the VLNV: imperas.ovpworld.org / platform / Or1kUclinux / 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
No platform specific command line arguments have been specified.Processor [ovpworld.org/processor/or1k/1.0] instance: cpu1
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)
| Parameter | Value | Description |
|---|---|---|
| mips | 100 | The nominal MIPS for the processor |
Memory Map for processor 'cpu1' bus: 'bus1'
Processor instance 'cpu1' is connected to bus 'bus1' using master port 'INSTRUCTION'.Processor instance 'cpu1' is connected to bus 'bus1' using master port 'DATA'.
Table 4: Memory Map ( 'cpu1' / 'bus1' [width: 32] )
| Lo Address | Hi Address | Instance | Component |
|---|---|---|---|
| 0x0 | 0x8FFFFFFF | mem1 | ram |
| 0x90000000 | 0x90000007 | uart1 | 16550 |
| 0x90000008 | 0xFFFFFFFF | mem2 | ram |
Net Connections to processor: 'cpu1'
Table 5: Processor Net Connections ( 'cpu1' )
| Net Port | Net | Instance | Component |
|---|---|---|---|
| intr2 | int1 | uart1 | 16550 |
Peripheral Instances
Peripheral [national.ovpworld.org/peripheral/16550/1.0] instance: uart1
Licensing
Open Source Apache 2.0Description
16550 UART modelThe serial input/output from the simulator is implemented using the Serial Device Support described in OVP BHM and PPM API Functions Reference, which describes the parameters that control how the model interacts with the host computer.
Interrupts and FIFOs are supported.
Registers are aligned on 1 byte boundaries.
Limitations
Resolution of the baud rate is limited to the simulation time slice (aka quantum) size.Values written to the MCR are ignored. Loopback mode is not supported.
The LSR is read-only. The model never sets the LSR 'Parity Error', 'Framing Error', 'Break Interrupt' or 'Error in RCVR FIFO' bits.
The MSR 'Data Set Ready' and 'Clear To Send' bits are set at reset and all other MSR bits are cleared. MSR bits will only be changed by writes to the MSR and values written to the Modem Status Register do not effect the operation of the model.
Reference
PC16550D Universal Asynchronous Receiver/Transmitter with FIFOs datasheet (http://www.ti.com/lit/ds/symlink/pc16550d.pdf)Table 6: Configuration options (attributes) set for instance 'uart1'
| Attributes | Value |
|---|---|
| finishOnDisconnect | 1 |
ImperasPlatforms
Page was generated in 0.0317 seconds