OVP Peripheral Model: SifiveUART

Model Specific Information

This page provides introductory usage information for an Imperas OVP peripheral behavioral model. The page is split into sections providing specific information for this peripheral, including any ports for connecting into a platform, registers, other component parts, and configuration options and general information for peripheral modeling with Imperas OVP.


Open Source Apache 2.0


Sifive UART


When simulatebaud parameter is set to true baud rate delays are modeled for receive only, not transmit. Data always sent immediately.


SiFive Freedom U540-C000 Manual FU540-C000-v1.0.pdf (


The UART peripheral model is located in an Imperas/OVP installation at the VLNV: / peripheral / UART / 1.0.

Peripheral Instance Parameters

This model accepts the following parameters:

Table : Peripheral Parameters

simulatebaudboolDescription Set to true to simulate baud delay determined by the div register value and reference clock frequency. Set to false to run without delay - next read data is made available immediately upon read of Receiver Buffer Register. Defaults to false
charmodeboolDescription Set to true when the port is used to connect to a Telnet program and character mode is desired rather than the default Telnet line mode. When set to true a Telnet command sequence is sent at startup that configures the Telnet program into character mode. In addition null bytes are stripped from the data received.
refClkFrequns32Frequency (in hertz) of reference clock rate used in baud rate calculation
consoleboolIf specified, port number is ignored, and a console pops up automatically
clientboolIf true, model is a client and will connect to portnum. If false, model is a server and will listen on portnum.
portnumuns32If set, listen on, or connect to, this port. If set to zero in listen mode, allocate a port from the pool and listen on that.
hostnamestringName (or IP address) of host to connect to. Valid if listen=true
infilestringName of file to use for device source
outfilestringName of file to write device output
portFilestringIf portnum was specified as zero, write the port number to this file when it's known
logboolIf specified, serial output will go to simulator log
finishOnDisconnectboolIf set, disconnecting the port will cause the simulation to finish
connectnonblockingboolIf set, simulation can begin before the connection is made
xcharsuns32Width of console in characters
ycharsuns32Height of console in characters
recordstringRecord external events into this file
replaystringReplay external events from this file

Net Ports

This model has the following net ports:

Table 1: Net Ports

NameTypeMust Be ConnectedDescription
intOutoutputF (False)
resetinputF (False)

Bus Slave Ports

This model has the following bus slave ports:

Bus Slave Port: bport1

Table 2: Bus Slave Port: bport1

NameSize (bytes)Must Be ConnectedDescription
bport10x1cF (False)

Table 3: Bus Slave Port: bport1 Registers:

NameOffsetWidth (bits)DescriptionR/Wis Volatile

Platforms that use this peripheral component

Peripheral components can be used in many different platforms, including those developed by Imperas or by other users of OVP. You can use this peripheral in your own platforms.

Table 4: Publicly available platforms using peripheral 'UART'

Platform NameVendor

Page was generated in 0.0142 seconds