VxWorks 5.1.1 BSP 使用指南：EUROCOM-17板级支持

需积分: 7 22 浏览量更新于2024-07-21 收藏 128KB PDF 举报

"该文档是VxWorks 5.1.1版本的BSP(BSP:Board Support Package，板级支持包)手册，专门针对EUROCOM-17硬件平台。内容涵盖了系统内存管理、文件系统、系统函数及调度等核心知识点，并详细介绍了如何在EUROCOM-17上配置和运行VxWorks操作系统。" VxWorks是一个实时操作系统（RTOS），被广泛用于嵌入式系统开发，特别是在航空航天、通信设备和工业自动化等领域。VxWorks 5.1.1 BSP手册针对EUROCOM-17板卡提供了详细的使用指南，帮助开发者理解和配置VxWorks在该硬件上的运行环境。 1. **系统内存**：VxWorks在运行时需要管理不同类型的内存，包括初始化数据区、堆内存和栈内存等。在EUROCOM-17上，手册会讲解如何配置和使用这些内存区域，以及如何通过RMon（Resident Monitor）进行内存初始化。 2. **系统文件**：VxWorks支持文件系统，允许在嵌入式设备上存储和操作文件。手册可能会涵盖如何在EUROCOM-17上挂载和管理不同的文件系统类型，如FAT或VFAT，并讨论文件I/O操作。 3. **系统函数**：VxWorks提供了一系列的库函数，用于任务创建、同步、通信等。这些函数包括任务管理、信号量、互斥锁、消息队列等。手册将详细介绍如何使用这些函数来编写高效的实时应用程序。 4. **调度**：VxWorks支持抢占式调度，能够确保关键任务得到及时响应。手册会解释VxWorks的调度策略，包括优先级分配、任务调度和上下文切换机制，以及如何在EUROCOM-17上调整和优化这些设置。 5. **BOOTROMs**：BOOTROM是嵌入式系统中的固件，负责启动过程。EUROCOM-17的RMon驻留在Flash EPROM中，手册详细描述了如何配置RMon以从用户EPROM加载VxWorks。这涉及到设置跳线和旋转开关，以确保RMon能自动执行用户EPROM中的程序。 6. **硬件接口**：由于BSP是硬件与操作系统之间的桥梁，手册还会涉及EUROCOM-17板卡的硬件接口，如串行RS-232连接，以及如何通过这些接口进行诊断和测试。通过阅读并理解这个手册，开发者可以有效地在EUROCOM-17平台上搭建和调试VxWorks系统，确保软件在硬件上的高效运行和稳定性能。同时，手册也会包含故障排查和维护的信息，帮助解决在实际操作中可能遇到的问题。

Rev: 19 Oct 94 8

if_il(1) VXWORKS REFERENCE MANUAL if_il(1)

NAME

if_il - AMD 79900 ILACC Ethernet network interface driver

SYNOPSIS

ilattach() - publish the interface, and initialize the

driver and device

STATUS ilattach

(int unit, char *devAdrs, int ivec, int ilevel,

char *memAdrs, ULONG memSize, int memWidth, int spare,

int spare2)

DESCRIPTION

GENERAL INFORMATION

This module implements the AMD 79900 ILACC Ethernet network

interface driver.

This driver is designed to achieve a moderate level of gen-

ericism, across the range of architectures and targets that

VxWorks 5.1 supports. This allows the driver to be run,

unmodified, on a variety of target hardware. To achieve

this goal, the driver must be given several target-specific

parameters, and some external support routines must be pro-

vided. These parameters, and the mechanisms used to commun-

icate them to the driver, are detailed below. If any of the

assumptions mentioned below are not true for your particular

hardware, this driver will probably not function correctly.

This driver supports only one ILACC unit per CPU. The

driver can be configured to support big-endian or little-

endian architectures.

BOARD LAYOUT

This device is onboard. No jumpering diagram required.

EXTERNAL INTERFACE

This driver provides the standard external interface with

the following exceptions. All initialization is performed

within the attach() routine and there is no separate init()

routine. Therefore, in the global interface structure, the

function pointer to the init() routine is NULL.

There is one user-callable routine: ilattach(). See the

manual entry for this routine for usage details.

TARGET SPECIFIC PARAMETERS

buss mode

- This parameter is globally accessed.

The ILACC control register #3 determines the buss mode

of the device. This allows the support of big-endian

and little-endian architectures. This parameter,

Rev: 19 Oct 94 9

if_il(1) VXWORKS REFERENCE MANUAL if_il(1)

defined as "u_short ilCSR_3B", is the value that will

be placed into ILACC control register #3. The default

value supports Motorola type busses. See the ILACC

manual to change this parameter.

base address of device registers

- This parameter is passed to the driver with the ilat-

tach() routine.

The ILACC presents two registers to the external inter-

face, the RDP register, and the RAP register. This

driver assumes that these two registers occupy two

unique addresses in a memory space that is directly

accessable by the CPU executing this driver. This

driver assumes that the RDP register is mapped at a

lower address than the RAP register, and is therefore

considered the "base address".

This parameter indicates to the driver where to find

the RDP register.

interrupt vector

- This parameter is passed to the driver with the ilat-

tach() routine.

This driver configures the ILACC device to generate

hardware interrupts for various events within the dev-

ice. Therefore, this driver contains an interrupt

handler routine. This driver will call the VxWorks

system function intConnect() to connect its interrupt

handler to the interrupt vector generated as a result

of the ILACC interrupt.

interrupt level

- This parameter is passed to the driver with the ilat-

tach() routine.

Some target hardware use additional interrupt con-

troller devices to help organize and service the vari-

ous interrupt sources. This driver avoids all board-

specific knowledge of such devices. During the ini-

tialization of this driver, an external routine is

called to perform any board-specific operations

required to allow the servicing of a ILACC interrupt.

This routine is described below. This parameter is

passed to the external routine.

shared memory address

Rev: 19 Oct 94 10

if_il(1) VXWORKS REFERENCE MANUAL if_il(1)

- This parameter is passed to the driver with the ilat-

tach() routine.

The ILACC device is a DMA type of device and typically

shares access to some region of memory with the CPU.

This driver is designed for systems that directly share

memory between the CPU and the ILACC. This driver

assumes that this shared memory is directly available

to this driver without any arbitration or timing con-

cerns.

This parameter may be used to specify an explicit

memory region for use by the ILACC. This should be

used on hardware that restricts the ILACC to a particu-

lar memory region. The constant NONE may be used to

indicate that there are no memory limitations. In this

case, the driver will attempt to allocate the shared

memory from the system space.

shared memory size

- This parameter is passed to the driver with the ilat-

tach() routine.

This parameter can be used to explicitly limit the

amount of shared memory (bytes) this driver will use.

The constant NONE may be used to indicate no specific

size limitation. This parameter is only used if a

specific memory region is being provided to the driver.

shared memory width

- This parameter is passed to the driver with the ilat-

tach() routine.

Some target hardware that restricts the shared memory

region to a specific location, also restricts the

access width to this region by the CPU. On these tar-

gets, performing an access of an invalid width will

cause a buss error.

This parameter can be used to specify the number of

bytes of access width to be used by the driver during

access to the shared memory. The constant NONE may be

used to indicate no restrictions.

The current internal implementation of supporting this

mechanism is not robust, and may not work on all tar-

gets requiring these restrictions.

shared memory buffer size

剩余59页未读，继续阅读

czh8762

粉丝: 0
资源: 1

VxWorks 5.1.1 BSP 使用指南：EUROCOM-17板级支持

VxWorks_7_Third-Party_Software_Support__SR0620.pdf

libminigui-gpl-3_0_12.tar.gz

VxWorks-operate-on-vmWare.rar_vmware_vxwor_vxworks bsp VMware_vx

VxWorks-based-online-programming.rar_vxworks_vxworks pdf

AT91RM9200-vxWorks-BSP.zip_AT91RM9200-vxWorks_at91rm9200 vxworks

mpc8545vxworks-6.4.rar_mpc8545vxWorks-6.4_river_sysMtd.c_vxworks

cp6000-bsp.rar_BSP_CP6000 vxworks_CPCI_cp6000

VxWorks-PCI-Driver.rar_PCI Builder_PCI vxworks_driver VxWorks_vx

82559end-driver-for-Vxworks.zip_82559 vxworks_intel 82559_vxwork

VxWorks 7 BSP with the Zynq-7000 AP SoC

最新资源