OVP Peripheral Model: AndesATCUART100

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


Andes UART


Register View Model Only


Andes AE350 Platform User Manual


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

Peripheral Instance Parameters

This model accepts the following parameters:

Table : Peripheral Parameters

uart16450boolRun in 16450 mode (no FIFOs)
fifoSizeuns32Size of fifos
refClkFrequns32Frequency (in hertz) of reference clock rate used in baud rate calculation
simulatebaudboolDescription Set to true to simulate baud delay determined by the Divisor Latch 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.
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
resetNetinputF (False)Reset signal
intOutoutputF (False)Interrupt signal

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
bport10x40T (True)

Table 3: Bus Slave Port: bport1 Registers:

NameOffsetWidth (bits)DescriptionR/Wis Volatile
ab_IDREV0x032ID and Revision Register
ab_CFG0x1032Hardware Configure Register
ab_OSCR0x1432Over Sample Control Register
ab_RBR_DLL0x2032Receiver Buffer Register / Divisor Latch LSB
ab_THR_DLL0x2032Transmitter Holding Register / Divisor Latch LSB
ab_IER_DLM0x2432Interrupt Enable Register / Divisor Latch MSB
ab_IIR0x2832Interrupt Identification Register
ab_FCR0x2832FIFO ControlRegister
ab_LCR0x2c32Line Control Register
ab_MCR0x3032Modem Control Register
ab_LSR0x3432Line Status Register
ab_MSR0x3832Modem Status Register
ab_SCR0x3c32Scratch Register

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 'ATCUART100'

Platform NameVendor

Page was generated in 0.0203 seconds