📄 readme.txt
字号:
------------------------------------------------------------
WIND NET 802.11b Example BSP README file
July 2003 - Copyright 2003 Wind River Systems, Inc.
------------------------------------------------------------
INTRODUCTION:
This README file describes the modifications required to the BSP
directory in order for the target hardware to recognize the
WIND NET 802.11b component.
WIND NET 802.11b requires some existing BSP files to be altered
as described below, and the addition of new 802.11b-specific
files. The examples directory contains versions of these
802.11b-specific files for some of the popular target
architectures.
For more information on WIND NET 802.11b, consult the
appropriate WIND NET 802.11b User's Guide.
BSP CONFIGURATION STEPS:
1. Determine which example target architecture best represents
the actual target system. Things to consider are: big
endian vs. little endian and PCMCIA access vs. PCI access.
2. Copy the files in the selected example BSP directory into
the actual BSP directory. These files will be used as a
starting point for further modifications if required.
NOTE: In some cases, previous versions of these files may
already exist in the actual BSP directory. If so,
make a backup copy of the existing file before
copying the new file across.
3. Edit config.h with the following changes:
a. Add the following line, which will compile the 802.11b END
driver into the BSP:
#define INCLUDE_WLAN_END
b. (optional) Some or all of the following optional components
can be added to config.h to help facilitate driver testing:
#define INCLUDE_SHELL
#define INCLUDE_SHOW_ROUTINES
#define INCLUDE_NET_INIT
#define INCLUDE_NET_SHOW
#define INCLUDE_PING
#define INCLUDE_LOADER
#define INCLUDE_SYM_TBL
#define INCLUDE_NET_SYM_TBL
4. Edit configNet.h with the following changes:
NOTE: Some BSP's no longer use configNet.h to list the supported
END devices, and simply provide a 'template' configNet.h
file with an empty endDevTbl[] array to maintain
compatibility. Some BSP's, such as the wrSbcPxa250, do NOT
require changes to configNet.h as the PCMCIA network driver
entries are added automatically.
However, other BSP's such as the integrator940t, have a
sysLanPciInit() routine that automatically detects and
configures certain ethernet cards. In this case, the
802.11b driver entries still need to be added as described
below, but the sysLanPciInit() routine needs to modified to
index to the end of the endDevTbl[] array before performing
a pciFindDevice().
a. Include the following defines for the INCLUDE_PRISM_END and
INCLUDE_AIRONET_END drivers:
#ifdef INCLUDE_PRISM_END
#define END_PRISM_LOAD_FUNC sysWlanEndPrismLoad
#define END_PRISM_BUFF_LOAN 0
#define END_PRISM_LOAD_STRING ""
IMPORT END_OBJ* END_PRISM_LOAD_FUNC (char*, void*);
#endif /* INCLUDE_PRISM_END */
#ifdef INCLUDE_AIRONET_END
#define END_AIRONET_LOAD_FUNC sysWlanEndAironetLoad
#define END_AIRONET_BUFF_LOAN 0
#define END_AIRONET_LOAD_STRING ""
IMPORT END_OBJ* END_AIRONET_LOAD_FUNC (char*, void*);
#endif /* INCLUDE_AIRONET_END */
b. Include the following entries in endDevTbl[] before the last
entry (which contains the END_TBL_END macro):
#ifdef INCLUDE_AIRONET_END
{0, END_AIRONET_LOAD_FUNC, END_AIRONET_LOAD_STRING,
END_AIRONET_BUFF_LOAN, (void *) ANET_IFNAME, FALSE},
#endif /* INCLUDE_AIRONET_END */
#ifdef INCLUDE_PRISM_END
{0, END_PRISM_LOAD_FUNC, END_PRISM_LOAD_STRING,
END_PRISM_BUFF_LOAN, (void *) WLAN_IFNAME, FALSE},
#endif /* INCLUDE_PRISM_END */
c. Include the following line, which will provide the proper
definitions for INCLUDE_PRISM_END and INCLUDE_AIRONET_END:
#include "configWlan.h"
5. (PCI interface only) Edit sysLib.c with the following changes:
a. Include the following external declaration:
IMPORT STATUS sysWlanPciInit();
b. Include the following line, after the PCI controller has been
initialized (i.e. after sysPciAutoConfig() has been called):
#ifdef INCLUDE_WLAN_END
sysWlanPciInit ();
#endif /* INCLUDE_WLAN_END */
6. (PCMCIA interface only) An 802.11b peripheral entry needs to
be added to the PCMCIA library in order for the 802.11b
PCMCIA card to be detected properly. This may require
memory map modifications to the sysLib.c file, and updates
to the PCMCIA support files. The PCMCIA library will be BSP
specific - refer to one of the PCMCIA example BSP's for more
information on adding PCMCIA support.
7. Edit the Makefile with the following line, to ensure the
802.11b routines are linked into the vxWorks image:
MACH_EXTRA += sysWlanEnd<cpu>.o
where <cpu> is the CPU architecture for the BSP. The C
version of this file should have been copied to the BSP
directory in step #2 above. If the <cpu> designation
of the copied file does not match the actual BSP
CPU architecture, the filename should be edited at this
time with the correct CPU suffix to prevent confusion.
8. Edit sysWlanEnd<cpu>.c to update the sysWlan I/O and
sysWlan interrupt wrapper routines, if required. This
step is critical in getting the 802.11b driver to be
recognized by the target hardware and function properly.
Some I/O and interrupt routines may already exist in
sysLib.c or another supported network driver, and can be
used as a guideline to edit the 802.11b wrapper routines.
9. Edit configWlan.h to configure the 802.11b parameters as
desired. Note that the configuration options in
configWlan.h can be also be performed from the Tornado
Project Facility. For more information on 802.11b
configuration options, consult the WIND NET 802.11b
User's Guide.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -