Hello

From: Jan Kiszka <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: rtnet-users@lists.sourceforge.net
Subject: Re: [RTnet-users] RTnet and RTAI 3.3 master and slave problem
Date: Wed, 15 Mar 2006 17:27:18 +0100

matrix_df hotmail wrote:
> Hello
>
> rtcfg problem
> Master and slave do not find each other!
>
> Master sends RTmac broadcast packets, but slave does not respond.
>
> With Intel 8257/8/9 cards the system CRASHES !!!!!

During cleanup or already during startup? In the latter case, please
check for potential IRQ conflicts between the RT-NIC and some Linux
devices. They must be resolved first.

During startup.
I have not checked for IRQ conflicts when using the Intel 8257/8/9 cards.
When using the realtek 8139 there seem to be no conflict.
[EMAIL PROTECTED] rtnet]# cat /proc/interrupts
          CPU0
 0:   66293852          XT-PIC  timer, rtai_jif_chk
 1:      42863          XT-PIC  i8042
 2:          0          XT-PIC  cascade
 8:          1          XT-PIC  rtc
 9:   15354264          XT-PIC  eth0, [EMAIL PROTECTED]:0000:01:05.0
10:     244259          XT-PIC  eth1
12:     810417          XT-PIC  i8042
14:     214209          XT-PIC  ide0
15:         32          XT-PIC  ide1
NMI:          0
ERR:          0

and the realtek 8139 card  on master uses IRQ 11.



> With Realtek 8139:  see the following debug messages.
>
> ##########################################################################
> ON MASTER:
> [EMAIL PROTECTED] rtnet]# sbin/rtnet start
>
> *** RTnet 0.9.2 - built on Mar 15 2006 14:37:33 ***
>
> RTnet: initialising real-time networking
> eepro100-rt.c:1.36-RTnet-0.7 2002-2005 Jan Kiszka <[EMAIL PROTECTED]>
> eepro100-rt.c: based on eepro100.c 1.36 by D. Becker, A. V. Savochkin
> and othersrteth0: 0000:00:0b.0, 00:90:27:71:70:EA, IRQ 11.
> RTnet: registered rteth0
> initializing loopback...
> RTnet: registered rtlo
> RTcfg: init real-time configuration distribution protocol
> RTmac: init realtime media access control
> RTmac/TDMA: init time division multiple access control mechanism
> RTcfg: rtcfg_do_main_event() rtdev=1, event=RTCFG_CMD_SERVER,
> state=RTCFG_MAIN_OFF
> RTcfg: next main state=RTCFG_MAIN_SERVER_RUNNING
> RTcfg: rtcfg_do_main_event() rtdev=1, event=RTCFG_CMD_ADD,
> state=RTCFG_MAIN_SERVER_RUNNING
> RTcfg: rtcfg_do_main_event() rtdev=1, event=RTCFG_CMD_ADD,
> state=RTCFG_MAIN_SERVER_RUNNING
> RTcfg: rtcfg_do_main_event() rtdev=1, event=RTCFG_CMD_ADD,
> state=RTCFG_MAIN_SERVER_RUNNING

Hmm, adding three slaves here... Do you expect so many nodes? Otherwise,
trim the list in rtnet.conf or tdma.conf.

Ok, I have changed it to one slave.


> Waiting for all slaves...RTcfg: rtcfg_do_main_event() rtdev=1,
> event=RTCFG_CMD_WAIT, state=RTCFG_MAIN_SERVER_RUNNING
> RTcfg: error -105 while sending stage 1 frame
> RTcfg: error -105 while sending stage 1 frame
> RTcfg: error -105 while sending stage 1 frame
> RTcfg: error -105 while sending stage 1 frame

Link problem? This error is reported when the NIC failed to transmit
frames queued by RTcfg so that the latter ran out of buffers. This might
be due to physical transmission problems, or there is no fitting TDMA
slot available (shouldn't be the case when using the standard configs).

I am using the standard script. (only master and slave adopted)

Please check /proc/rtnet/rtmac/tdma_slots. BTW, further state
information about RTcfg is available via /proc/rtnet/rtcfg/rteth0/*.

[EMAIL PROTECTED] sjoc]# cat /proc/rtnet/rtcfg/rteth0/state
state:                  1 (SERVER_RUNNING)
flags:                  00010000
other stations:         1
stations found:         0
stations ready:         0
configured clients:     0
burstrate:              4
heartbeat period:       1000 ms

[EMAIL PROTECTED] rtnet]# cat /proc/rtnet/rtmac/tdma_slots
Interface       Slots (id[->joint]:offset:phasing/period:size)
rteth0          0:0:1/1:1500


>
>> sbin/rtnet stop
> hard_start_xmit returned -11
> RTcfg: error -11 while sending stage 1 frame
> hard_start_xmit returned -11
> RTcfg: error -11 while sending stage 1 frame
> hard_start_xmit returned -11
> RTcfg: error -11 while sending stage 1 frame
> RTDM: INFO > IRQ: 11, INTRCNT: 4373
> RTmac/TDMA: unloaded
> RTmac: unloaded
> RTcfg: error -100 while sending stage 1 frame
> RTcfg: error -100 while sending stage 1 frame
> RTcfg: error -100 while sending stage 1 frame
> RTcfg: error -100 while sending stage 1 frame
> RTcfg: error -100 while sending stage 1 frame
> RTcfg: error -100 while sending stage 1 frame
> RTcfg: unloaded
> removing loopback...
> RTnet: unregistered rtlo
> RTnet: unregistered rteth0
> RTnet: unloaded
> [EMAIL PROTECTED] rtnet]#
> #######################################################################
>
> ON SLAVE:
> #######################################################################
> SLAVE:
> [EMAIL PROTECTED] rtnet]# sbin/rtnet start
>
> *** RTnet 0.9.2 - built on Mar 15 2006 16:22:20 ***
>
> RTnet: initialising real-time networking
> rt_8139too Fast Ethernet driver 0.9.24-rt0.4
> ACPI: PCI Interrupt 0000:03:08.0[A] -> Link [LNKB] -> GSI 9 (level, low) ->
> IRQ
> 9
> RTnet: registered rteth0
> initializing loopback...
> RTnet: registered rtlo
> RTcap: real-time capturing interface
> RTcfg: init real-time configuration distribution protocol
> RTmac: init realtime media access control
> RTmac/TDMA: init time division multiple access control mechanism
> rteth0:   rtl8139_set_rx_mode(0002) done -- Rx config 0000f78a.
> Stage 1: searching for master...RTcfg: rtcfg_do_main_event() rtdev=1,
> event=RTCFG_CMD_CLIENT, state=RTCFG_MAIN_OFF
> RTcfg: next main state=RTCFG_MAIN_CLIENT_0

If this is the last RTcfg-related message, no invitation by the master
arrives at the slave. That explains the lacking progress of the rtnet
script.

Yes, this is all.


> ###########################################################
>
> see attached ethereal file for tdma, tdmac packets

On which box did you capture, master or slave? Or on an independent
sniffer box? Only the sync messages are included in the dump, no RTcfg
frame which should pop up at least once per second. Either you skipped
them accidentally (the dump includes only 20 ms), or the RTcfg service
has some real problem here.

I just shortend the capturing, because the sync is the only message.
Messages were captured on master, but also verified by a third computer (sniffer).
There are no "RTcfg frames" !!

Who should send the RTcfg frames (invitation), the master or?

So what should I check next?
What are about kernel configuration options, ACPI, .....!!



Is there a reference system which works?
Perhaps a system with Xenomai.
(Please attach all vital information, kernel, xenomai version, configuration)

regards
    Jochen


>
> ---------------------------------------------------------------------------------------------
>
> Systemconfiguration:
> kernel: 2.6.15.4 (tried 2.6.9 also)
> kernel patch:
> rtai-3.3/base/arch/i386/patches/hal-linux-2.6.15-i386-1.2-00.patch
> RTAI 3.3
> RTnet 0.9.2 (svn)
> -------------------------------------------------------------------------------------------------
>
>
> Any suggestion what to do?
>
> Jochen
>

Jan



<< signature.asc >>




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
RTnet-users mailing list
RTnet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rtnet-users

Reply via email to