Hi Jan, I have now a working version of tcpdump running on my PPC targets...
On 07/02/2005 11:17 AM Jan Kiszka wrote:
> Wolfgang Grandegger wrote:
>> ...
>> OK, now I have another strange behaviour when TDMA is loaded. With
>> rtnet, rt_3c59x/rt_mpc52xx_fec and rtcfg loaded I get:
>>
>> [EMAIL PROTECTED] modules]# rtping 10.0.0.2
>> Real-time PING 10.0.0.2 56(84) bytes of data.
>> 64 bytes from 10.0.0.2: icmp_seq=1 time=430.2 us
>> 64 bytes from 10.0.0.2: icmp_seq=2 time=408.4 us
>> 64 bytes from 10.0.0.2: icmp_seq=3 time=394.6 us
>>
>> and also the round-trip-test returns reasonable values:
>>
>> # showtime
>> Roundtrip = 413us (min: 413us, max: 413us)
>> Roundtrip = 339us (min: 339us, max: 413us)
>> Roundtrip = 349us (min: 339us, max: 413us)
>>
>> But with TDMA running (via "rtnet start") I get on the RTnet slave:
>>
>> Stage 1: searching for master...+/usr/realtime/sbin/rtcfg rteth0
>> client -c
>> +/bin/sh -c
>> TDMACFG=/usr/realtime/sbin/tdmacfg;IPADDR=10.0.0.2;NETMASK_OPT="";
>> $TDMACFG rteth0 slot 0 500;ifconfig vnic0 up $IPADDR $NETMASK_OPT
>
> Mmh, this internal batch of commands should not be dumped to the screen.
> What shell do you use on your target box? standard or busybox bash? At
> least those two are tested and should work. Anyway, cosmetic effect.
>
>> TDMA: calibrated master-to-slave packet delay: 61557080 us (min/max:
>> 61309526/61 804640 us)
>>
>
> Well, this is alarming. Something goes wrong during the calibration, at
> least when printing the results. Could you capture the calibration phase
> on the slave with RTcap+tcpdump and send me the result?
>
Attached is the output of "tcpdump -i rteth0" for the startup:
bash-2.05b# rtnet -cf ../etc/rtnet-tqm860l.conf start
*** RTnet 0.8.3 - built on Jul 5 2005 17:37:45 ***
RTnet: initialising real-time networking
RTnet: stack-mgr started
RTDM: registered protocol device 2:2
RTDM: registered protocol device 17:2
RTnet: registered rteth0
RTnet: rteth0: FEC ENET Version 0.3, irq 9, addr 00:d0:93:80:03:54
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
RTDM: registered named device TDMA0
Stage 1: searching for master...TDMA: calibrated master-to-slave
packet delay: 439754586 us (min/max: 439506992/440002182 us)
Stage 2: waiting for other slaves...
Stage 3: waiting for common setup completion...
Also on my MPC860 module I see large calibrated master-to-slave packet
delays. 440 seconds, this looks like an endianess problem or a wrong
(64-bit?) calculation.
>>
>> and then ping returns rather long delay and big fluctuations:
>>
>> [EMAIL PROTECTED] modules]# rtping 10.0.0.2
>> Real-time PING 10.0.0.2 56(84) bytes of data.
>> 64 bytes from 10.0.0.2: icmp_seq=1 time=5394.8 us
>> 64 bytes from 10.0.0.2: icmp_seq=2 time=9436.8 us
>> 64 bytes from 10.0.0.2: icmp_seq=3 time=8433.4 us
>>
>> I use TDMA_CYCLE=5000 and TDMA_OFFSET=500. Therefore a packet should be
>> sent every 5ms.
>>
>
> At least the three round-trips above are normal. Note that your ping is
> out of sync with the TDMA cycle, thus the ping request first have to
> wait up to a full cycle to get sent. And then the reply may also have to
> be defered on the target side (depends on the slot order of ping sender
> and receiver and on the time between the slots).
>
> Jan
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> RTnet-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/rtnet-users
>
>
tcpdump-slave-start.log.gz
Description: GNU Zip compressed data
