---

OVP Peripheral Model: National16550

---

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.

Licensing

Open Source Apache 2.0

Description

16550 UART model

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.

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)

Location

The 16550 peripheral model is located in an Imperas/OVP installation at the VLNV: national.ovpworld.org / peripheral / 16550 / 1.0.

---

Peripheral Instance Parameters

This model accepts the following parameters:

Table : Peripheral Parameters

---

Net Ports

This model has the following net ports:

Table 1: Net Ports

---

Bus Slave Ports

This model has the following bus slave ports:

Bus Slave Port: bport1

Table 2: Bus Slave Port: bport1

Table 3: Bus Slave Port: bport1 Registers:

---

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