LIBRARY  |  COMPANIES |   PLATFORMS |   PROCESSORS |   PERIPHERALS
AtmelUsartInterface



OVP Peripheral Model: AtmelUsartInterface



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

Limitations

This model is sufficient to boot Linux

Description

USART: Universal Synchronous/Asynchronous Receiver Transmitter This model contains an accurate Register set interface. The functionality has only been implemented to sufficiently boot uClinux. The USART has its own baud rate generator, and two dedicated Peripheral Data Controller. channels. The data format includes a start bit, up to 8 data bits, an optional programmable parity bit and up to 2 stop bits. The USART also features a Receiver Timeout register, facilitating variable length frame support when it is working with the PDC, and a Time-guard register, used when interfacing with slow remote equipment. for more information visit http://www.atmel.com/products/at91

Reference

Rev. 1354D ARM08/02

Location

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



Peripheral Instance Parameters

This model accepts the following parameters:

Table : Peripheral Parameters

NameTypeDescription
xcharsuns32Width of console in characters
connectnonblockingboolIf set, simulation can begin before the connection is made
finishOnDisconnectboolIf set, disconnecting the port will cause the simulation to finish
logboolIf specified, serial output will go to simulator log
portFilestringIf portnum was specified as zero, write the port number to this file when it's known
outfilestringName of file to write device output
infilestringName of file to use for device source
portnumuns32If set, listen on this port. If set to zero, allocate a port from the pool and listen on that.
consoleboolIf specified, port number is ignored, and a console pops up automatically
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 Master Ports

This model has the following bus master ports:

Bus Master Port: asb

Table 2: asb

NameAddress Width (bits)Description
asb32



Bus Slave Ports

This model has the following bus slave ports:

Bus Slave Port: apb

Table 3: Bus Slave Port: apb

NameSize (bytes)Must Be ConnectedDescription
apb0x4000T (True)

Table 4: Bus Slave Port: apb Registers:

NameOffsetWidth (bits)DescriptionR/Wis Volatile
REG_US_TCR0x3c32
REG_US_TPR0x3832
REG_US_RCR0x3432
REG_US_RPR0x3032
REG_US_TTGR0x2832
REG_US_RTOR0x2432
REG_US_BRGR0x2032
REG_US_THR0x1c32
REG_US_RHR0x1832
REG_US_CSR0x1432
REG_US_IMR0x1032
REG_US_IDR0xc32
REG_US_IER0x832
REG_US_MR0x432
REG_US_CR0x032



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 5: Publicly available platforms using peripheral 'UsartInterface'

Platform NameVendor
AtmelAT91SAM7atmel.ovpworld.org
AtmelAT91SAM7atmel.ovpworld.org



AtmelPeripherals
Page was generated in 0.0223 seconds