LIBRARY  |  COMPANIES |   PLATFORMS |   PROCESSORS |   PERIPHERALS
TiUartInterface



OVP Peripheral Model: TiUartInterface



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.

Description

UART: Universal Asynchronous Receiver Transmitter This model contains an accurate Register set interface for the TI Stellaris ARM Cortex-M3 based device.

Limitations

The functionality of this model is limited. Basic status flag setting allows character reception and transmission.

Reference

FreeRTOS Cortex-M3 / GCC Port LM3S102 with GCC for Luminary Micros Stellaris microcontrollers http://www.freertos.org/portcortexgcc.html

Licensing

Open Source Apache 2.0

Location

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



Peripheral Instance Parameters

This model accepts the following parameters:

Table : Peripheral Parameters

NameTypeDescription
loopbackboolWhen enabled transmit data is looped back to the receiver data register.
consoleboolIf specified, port number is ignored, and a console pops up automatically
portnumuns32If set, listen on this port. If set to zero, allocate a port from the pool and listen on that.
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
irqoutputF (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
bport10x1000T (True)

Table 3: Bus Slave Port: bport1 Registers:

NameOffsetWidth (bits)DescriptionR/Wis Volatile
ab_dr0x032UARTDR
ab_rsrecr0x432UARTRSRECR
ab_fr0x1832UARTFR
ab_fbrd0x2432UARTFBDR
ab_ibrd0x2832UARTIBRD
ab_lcrh0x2c32UARTLCRH
ab_ctl0x3032UARTLCTL
ab_ifls0x3432UARTIFLS
ab_im0x3832UARTIM
ab_ris0x3c32UARTRIS
ab_mis0x4032UARTMIS
ab_icr0x4432UARTICR
ab_pid00xfd032
ab_pid10xfd432
ab_pid20xfd832
ab_pid30xfdc32
ab_pid40xfe032
ab_pid50xfe432
ab_pid60xfe832
ab_pid70xfec32
ab_cid00xff032
ab_cid10xff432
ab_cid20xff832
ab_cid30xffc32



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

Platform NameVendor
ArmCortexMFreeRTOSimperas.ovpworld.org
ArmCortexMFreeRTOSimperas.ovpworld.org



TexasInstrumentsPeripherals
Page was generated in 0.0265 seconds