Hi Jan
Its me again, Ok. In that case I tried setting up my other station to act
as a client.But it requires a 3c59x driver. I am not sure if the 3c59x-rt driver is
not doing its job or my hardware is faulty, error shows when I
rtifconfig, which then the system goes into a crash situation. I
wrote few printk lines inside the RTCap.c file and found that after
running the signal handling twice.. it goes to halt. howcome ? Has it
got to do with the bus error ?
The printk is as shown below
RTnet: initialising real-time networking
RTnet: stack-mgr started
PCI Found IRQ 10 for deice 00:0f.0
3c59x for RTnet: Donald Becker and others www.....
00:0f.0:3com PCI 3c900 Boomerang 10Mbps Combo at 0xfc40 vers LK1.1.16
RTnet:registered rteth0
RTcap: real-time capturing interface
rteth0:Host error, FIFO diagnostic register 2000
rteth0:PCI bus error, bus status 00a00029
RTnet:unknown layer-3 protocol
<system goes to halt>
config file
-----------
# RTnet installation path
RTNET_PATH="/usr/local/rtnet"
# RT-NIC driver
RT_DRIVER="eepro100-rt"
RT_DRIVER_OPTIONS="cards=1"
# IP address and netmask of this station
IPADDR="129.94.173.69"
NETMASK="255.255.252.0"
# Start realtime loopback device ("yes" or "no")
RT_LOOPBACK="no"
# Start capturing interface ("yes" or "no")
RTCAP="yes"
# Common RTcfg stage 2 config data (master mode only)
STAGE_2_SRC=""
# Stage 2 config data destination file (client mode only)
STAGE_2_DST=""
# Command to be executed after stage 2 phase (client mode only)
STAGE_2_CMDS=""
# TDMA mode of the station ("master" or "client")
TDMA_MODE="client"
# List of TDMA clients (master mode only)
TDMA_CLIENTS="129.94.173.69"
# Cycle time in microsecond (master mode only)
TDMA_CYCLE="5000"
# Offset in microsecond between TDMA slots (master mode only)
TDMA_OFFSET="200"
The specs for this machines are
vendor_id : GenuineIntel
cpu family : 6
model : 3
model name : Pentium II (Klamath)
stepping : 3
cpu MHz : 266.617
cache size : 512 KB
...
...
..
My other computer that runs as a Master uses the epro100 driver and never
showed any error. However it seems to be doing a inifinite loop printing
out the "unknown layer-3 protocol" line
config file for the master machine
# RTnet installation path
RTNET_PATH="/usr/local/rtnet"
# RT-NIC driver
RT_DRIVER="eepro100-rt"
RT_DRIVER_OPTIONS="cards=1"
# IP address and netmask of this station
IPADDR="129.94.172.190"
NETMASK="255.255.252.0"
# Start realtime loopback device ("yes" or "no")
RT_LOOPBACK="no"
# Start capturing interface ("yes" or "no")
RTCAP="yes"
# Common RTcfg stage 2 config data (master mode only)
STAGE_2_SRC=""
# Stage 2 config data destination file (client mode only)
STAGE_2_DST=""
# Command to be executed after stage 2 phase (client mode only)
STAGE_2_CMDS=""
# TDMA mode of the station ("master" or "client")
TDMA_MODE="master"
# List of TDMA clients (master mode only)
TDMA_CLIENTS="129.94.173.69"
# Cycle time in microsecond (master mode only)
TDMA_CYCLE="5000"
# Offset in microsecond between TDMA slots (master mode only)
TDMA_OFFSET="200"
What is RTcap suppose to show when up and working ? Is there any possible
ways in checking the kind of packages receiving for the Master computer
(thats is working - only waiting for client i suppose ? ).
Currently I can only reboot the computer when it goes into this infinite
loop. Is there any chance I can break out of the function or what it is
doing ?
I am really running out of idea in how to fix the problem. What do you
think I should do ?
Thanks for much
Bret
On Sat, 15 May 2004, Jan Kiszka wrote:
> Bret Yen-Ting Lin wrote:
> > Hi Jan
> >
> > Sorry to bug you about the same question again, but I keep getting the
> > same reponse even having the conf file adapted. Bellow is the response I
> > am getting after "rtnet start"
> > ...
>
> You could check the content of that incoming messages by enabling RTcap
> and running some packet sniffer on the capturing device (=>README.rtcap).
>
> >
> >
> > Here is my "master" config file. I have not yet set up the client, but I
> > am sure it should have worked even if there is no client "yet" right?
> >
>
> No, "rtnet start" will block until it gets in contact with the expected
> client(s). This also means that RTmac/TDMA will not be started until then.
>
> When running such basic tests, it's generally better to follow the exact
> descriptions (in this case: use >= 2 stations) to get a running system
> first. Then you can play with the parameters and try to understand the
> details. Otherwise you would have to dig deeper first and only modify
> what you may have understood.
>
> > # RTnet installation path
> > RTNET_PATH="/usr/local/rtnet"
> >
> > # RT-NIC driver
> > RT_DRIVER="eepro100-rt"
> > RT_DRIVER_OPTIONS="cards=1"
> >
> > # IP address and netmask of this station
> > IPADDR="129.94.172.190"
> > NETMASK="255.255.252.0"
> >
>
> Note that RTcfg requires all stations to be in the same network segment,
> i.e. they all receive Ethernet broadcasts. Just in case you are planning
> to run RTnet over a router...
>
> Jan
>
-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
RTnet-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/rtnet-users
