OVP Peripheral Model: SmscLAN9118
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
Fully functional Model of SMSC LAN9118 for Arm Versatile Express platforms. For full details please consult README-EMAC.txt
Licensing
Open Source Apache 2.0
Limitations
See README-EMAC.txt
Reference
SMSC LAN9118 High Performance single-chip 10/100 Non-PCI Ethernet Controller Datasheet Revision 1.5 (07-11-08)
Location
The LAN9118 peripheral model is located in an Imperas/OVP installation at the VLNV: smsc.ovpworld.org / peripheral / LAN9118 / 1.0.
Peripheral Instance Parameters
This model accepts the following parameters:
Table : Peripheral Parameters
Name | Type | Description |
---|
record | string | Record external events into this file |
replay | string | Replay external events from this file |
tapDevice | string | The name of the TAP device |
redir | string | User mode redirection of host port to virtual port (using SLiRP), command format <protocol>:<host port>:<ip address>:<virtual port> |
tftpPrefix | string | Path to the root of the tftp directory. To use tftp, fetch from the host (gw) IP address. |
macaddress | uns64 | The MAC address (hex number) |
macprefix | uns32 | The first two bytes of MAC addresses (hex number) on the VLAN |
network | string | The (v4) IP address of the local network device. |
logfile | string | The file to which Ethernet frames should be logged. Uses pcap file format, viewable by Wireshark and other programs. Do not use if this device is connected to a packetnet |
Net Ports
This model has the following net ports:
Table 1: Net Ports
Name | Type | Must Be Connected | Description |
---|
irq | output | F (False) | IRQ Pin |
Bus Slave Ports
This model has the following bus slave ports:
Bus Slave Port: bport1
Table 2: Bus Slave Port: bport1
Name | Size (bytes) | Must Be Connected | Description |
---|
bport1 | 0x1000 | F (False) | |
Table 3: Bus Slave Port: bport1 Registers:
Name | Offset | Width (bits) | Description | R/W | is Volatile |
---|
ab_RX_DATA_FIFO | 0x0 | 32 | | | |
ab_RX_DATA_FIFO_1 | 0x4 | 32 | | | |
ab_RX_DATA_FIFO_2 | 0x8 | 32 | | | |
ab_RX_DATA_FIFO_3 | 0xc | 32 | | | |
ab_RX_DATA_FIFO_4 | 0x10 | 32 | | | |
ab_RX_DATA_FIFO_5 | 0x14 | 32 | | | |
ab_RX_DATA_FIFO_6 | 0x18 | 32 | | | |
ab_RX_DATA_FIFO_7 | 0x1c | 32 | | | |
ab_TX_DATA_FIFO | 0x20 | 32 | | | |
ab_TX_DATA_FIFO_1 | 0x24 | 32 | | | |
ab_TX_DATA_FIFO_2 | 0x28 | 32 | | | |
ab_TX_DATA_FIFO_3 | 0x2c | 32 | | | |
ab_TX_DATA_FIFO_4 | 0x30 | 32 | | | |
ab_TX_DATA_FIFO_5 | 0x34 | 32 | | | |
ab_TX_DATA_FIFO_6 | 0x38 | 32 | | | |
ab_TX_DATA_FIFO_7 | 0x3c | 32 | | | |
ab_RX_STATUS_FIFO | 0x40 | 32 | | | |
ab_RX_STATUS_FIFO_PEEK | 0x44 | 32 | | | |
ab_TX_STATUS_FIFO | 0x48 | 32 | | | |
ab_TX_STATUS_FIFO_PEEK | 0x4c | 32 | | | |
ab_ID_REV | 0x50 | 32 | | | |
ab_IRQ_CFG | 0x54 | 32 | | | |
ab_INT_STS | 0x58 | 32 | | | |
ab_INT_EN | 0x5c | 32 | | | |
ab_BYTE_TEST | 0x64 | 32 | | | |
ab_FIFO_INT | 0x68 | 32 | | | |
ab_RX_CFG | 0x6c | 32 | | | |
ab_TX_CFG | 0x70 | 32 | | | |
ab_HW_CFG | 0x74 | 32 | | | |
ab_RX_DP_CTRL | 0x78 | 32 | | | |
ab_RX_FIFO_INF | 0x7c | 32 | | | |
ab_TX_FIFO_INF | 0x80 | 32 | | | |
ab_PMT_CTRL | 0x84 | 32 | | | |
ab_GPIO_CFG | 0x88 | 32 | | | |
ab_GPT_CFG | 0x8c | 32 | | | |
ab_GPT_CNT | 0x90 | 32 | | | |
ab_WORD_SWAP | 0x98 | 32 | | | |
ab_FREE_RUN | 0x9c | 32 | | | |
ab_RX_DROP | 0xa0 | 32 | | | |
ab_MAC_CSR_CMD | 0xa4 | 32 | | | |
ab_MAC_CSR_DATA | 0xa8 | 32 | | | |
ab_AFC_CFG | 0xac | 32 | | | |
ab_E2P_CMD | 0xb0 | 32 | | | |
ab_E2P_DATA | 0xb4 | 32 | | | |
Packetnet Ports
This model has the following packetnet ports:
Packetnet Port: phy
Table 4: phy
Name | Maximum Packet Size (bytes) | Must Be Connected | Description |
---|
phy | 1524 | F (False) | The port to connect the packetnet virtual network |
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 'LAN9118'