problems with fei and other network interfaces
Todd L. Montgomery
tried other cards as well with the same result. Most notably
a 3C509 using elt).
I #undef'ed INCLUDE_WDB in all/configAll.h, but it doesn't
change anything either....
If I use the END driver, I get this response when trying to print
the interface mac address....
[VxWorks Boot]: n fei
Network interface fei unknown
Cannot initialize interface named "fei0"
If I #undef INCLUDE_END in pc486/config.h and try it again, it
gets even stranger.
[VxWorks Boot]: n fei
Attaching network interface fei0... done.
Error setting inet address of fei0 to 0, errno = 0
Cannot initialize interface named "fei0"
But, if I then do it again....
[VxWorks Boot]: n fei
Address for device "fei0" == xx:xx:xx:xx:xx:xx
But, no matter, what once it boots, the network won't init or
do anything else.
Ideas welcome! I've scanned the groups archive for ideas, but nothing
has helped yet....
Thanks!
Werner Schiendl
After reading your post, I'm afraid I have absolutely no idea what problem
you wish us to solve.
What do you try to do? Where is the actual problem?
I recommend you clarify the problem a little.
best regards
Werner
"Todd L. Montgomery" <to...@talarian.com> wrote in message
news:14c103be.0110...@posting.google.com...
Todd L. Montgomery
more....
The main problem is that the interface doesn't come up and
can't be used. ifShow, etc. don't work. I've tried using
usrNetInit(), but it fails. I presume due to no working interface.
So, the problem I would like to solve is to generate an
image that contains a working fei interface (or elt) that I can
boot with, download vxWorks via FTP, etc. and do network
testing of a port of a reliable multicast protocol.
What has me stumped is that the drivers are in the image,
they show up when doing a '?' at the Boot prompt. But,
when I try to get their addresses, they fail. And everything
I've tried doesn't seem to get them to do anything after they
boot vxWorks the rest of the way. I.e., useNetInit() fails
when tried by hand.
Thanks!
-- Todd
"Werner Schiendl" <ws-...@gmx.at> wrote in message news:<3bd8231a$1...@brateggebdc5.br-automation.co.at>...
Werner Schiendl
first of all, the configuration for the bootrom image is independent of the
configuration of the VxWorks image (well, most of), if you use the Tornado
II configuration utility. The latter does only apply to the VxWorks image,
you need to configure the settings for the bootrom in config.h of your BSP.
Thus, being able to boot from FTP and using the interface in your
application are two different things.
For the EtherExpress Pro 100B there are some problems. Search the archives
for this newsgroup, there were quite some threads on this in the last couple
weeks. Sorry I cannot remember any details. Alternatively, you can download
a VxWorks driver from Intel, but this does only work for Intel x86 targets.
For Etherlink 3C509 you need to turn off Plug&Play with the does Utility
(you can download this from 3com website) and configure the resources
manually in both, the DOS tool for the network card and in config.h (search
for the interface name in all uppercase and you'll find the macros for IRQ
line and IO address).
The PCI Cards from 3com - 3C905 does not have this limitation, maybe you
have one of those lying around.
hth
Werner
"Todd L. Montgomery" <to...@talarian.com> wrote in message
news:14c103be.01102...@posting.google.com...
Todd L. Montgomery
> Hi,
>
> first of all, the configuration for the bootrom image is independent of the
> configuration of the VxWorks image (well, most of), if you use the Tornado
> II configuration utility. The latter does only apply to the VxWorks image,
> you need to configure the settings for the bootrom in config.h of your BSP.
>
> Thus, being able to boot from FTP and using the interface in your
> application are two different things.
Thanks for that clarification. That is something I was not aware of.
However, I've been editing config.h by hand. Hey, I'm a UNIX guy,
complex
IDEs make me nervous. Even under Windows I prefer an editor
and Makefiles. :)
> For the EtherExpress Pro 100B there are some problems. Search the archives
> for this newsgroup, there were quite some threads on this in the last couple
> weeks. Sorry I cannot remember any details. Alternatively, you can download
> a VxWorks driver from Intel, but this does only work for Intel x86 targets.
I was not able to find a new driver. However, I don't think it is
a driver issue since elt and fei act the same way.
> For Etherlink 3C509 you need to turn off Plug&Play with the does Utility
> (you can download this from 3com website) and configure the resources
> manually in both, the DOS tool for the network card and in config.h (search
> for the interface name in all uppercase and you'll find the macros for IRQ
> line and IO address).
The 3C509 I used came out of a FreeBSD box where I had turned PnP
off. I checked the settings and they seem to be fine.
> The PCI Cards from 3com - 3C905 does not have this limitation, maybe you
> have one of those lying around.
I tried a 3C905C (PCI using elPci) and get the same results as the fei
and
the elt.
But here is more information.......
I booted the PC with the 3C509 (aka elt) with the Boot Disk that came
with my package. When I boot from that disk, I can do 'n elt' at the
boot prompt
and it attaches and seems to be fine. I execute it again, and I get
the 'can not set inet address to 0' warning, but it still seems to
work. When I try to set the config to use device=elt(0,0)
set the IP addresses, o=elt, etc. and then boot, it attaches fine, but
nothing
goes over the wire (evident from a tcpdump at the FTP server that I
told it to contact). Eventually it fails with errno = 0xd0003.
Unfortunately, the bootroms I have been building don't even get this
far....
-- Todd
Werner Schiendl
"Todd L. Montgomery" <to...@talarian.com> wrote in message
news:14c103be.01103...@posting.google.com...
...
> Even under Windows I prefer an editor
> and Makefiles. :)
You can actually modify config.h and build a VxWorks image from your BSP
with 'make vxWorks'.
There are other variants to build it, like romable images and so on, too.
However, this is a _xor_ decision. Mixing the Tornado project facility and
the command line build ends in a hopeless mess.
...
> The 3C509 I used came out of a FreeBSD box where I had turned PnP
> off. I checked the settings and they seem to be fine.
Did you verify this settings are the same than in your config.h file?
The following defines need to be adjusted.
#define IO_ADRS_ELT 0x240
#define INT_LVL_ELT 0x0b
#define NRF_ELT 0x00
#define CONFIG_ELT 0 /* 0=EEPROM 1=AUI 2=BNC 3=RJ45 */
>
> I booted the PC with the 3C509 (aka elt) with the Boot Disk that came
> with my package. When I boot from that disk, I can do 'n elt' at the
> boot prompt
> and it attaches and seems to be fine.
This does not tell you anything. Most WRS network driver 'attach fine' even
if the required hardware is not present.
> I execute it again, and I get
> the 'can not set inet address to 0' warning, but it still seems to
> work. When I try to set the config to use device=elt(0,0)
> set the IP addresses, o=elt, etc. and then boot, it attaches fine, but
> nothing
> goes over the wire (evident from a tcpdump at the FTP server that I
> told it to contact). Eventually it fails with errno = 0xd0003.
>
This is typical behaviour for what I described above -> the driver
'communicates' with non-existent hardware.
> Unfortunately, the bootroms I have been building don't even get this
> far....
>
How do you build your boot floppies?
Normally, in your BSP directory type:
make bootrom_uncmp
format a: [/q]
mkboot a: bootrom_uncmp
With a fresh copy of your BSP, this should be equivalent to using the
shipped floppies.
Make sure, that the bootrom.sys file, that is created on the floppy, is not
fragmented.
It needs to be one single file.
To check:
chkdsk a:\bootrom.sys
Below the usual chkdsk output there is a line telling you whether the file
is in one piece or fragmented.
hth
Werner