Re: [RTnet-developers] Suspect packet
Brought to you by:
bet-frogger,
kiszka
Menu
▾
▴
Re: [RTnet-developers] Suspect packet
|
From: Jan K. <jan...@we...> - 2009-11-24 08:39:41
|
Frank Tkalcevic wrote: > I've just started playing around with RTNet. The plan is to use a master on > my EMC2 machine, and talk to slaves to do real time control of machines (my > toy robot arm first). The slave will be a small embedded device. I'm > currently developing on an NGW100 which has an Atmel AP7000 on it. > Unfortunately there isn't a realtime kernel patch for this CPU, so I'm going There were some guys on xenomai-help talking about porting ipipe to the NGW100, but it's too early to asses this effort. > to make the clients standalone - either by porting the rtnet software, or > implementing it myself based on the packet specification. The plan is to > move it to a smaller self contain microcontroller (AVR32UC3 range) when it > is up and running. > > Anyhow, I've just got the basic networking going and noticed a strange > packet appearing every now and then.... > > > Received 93 bytes > 0000 FF FF FF FF FF FF 00 40 63 F6 3D 51 90 21 00 01 .......@c.=Q.!.. > 0010 02 00 02 01 00 00 00 01 20 38 00 00 00 82 DB 43 ........ 8.....C > 0020 15 4B 00 00 00 82 DB 43 15 3D 00 00 00 00 00 00 .K.....C.=...... > 0030 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ > 0040 6E 69 63 30 20 75 70 20 24 49 50 41 44 44 52 20 nic0 up $IPADDR > 0050 24 4E 45 54 4D 41 53 4B 5F 4F 50 54 0A $NETMASK_OPT.... > > > It looks like a corrupt buffer, half sync packet, and half a config packet. > Not necessarily corrupted, but too long. Where and how did you capture this frame? Does it fit into the TDMA cycle? > > This is the normal traffic I see... > > Received 60 bytes > 0000 FF FF FF FF FF FF 00 40 63 F6 3D 51 90 21 00 01 .......@c.=Q.!.. > 0010 02 00 02 01 00 00 00 00 06 A1 00 00 0A 78 1B 65 .............x.e > 0020 A1 64 00 00 0A 78 1B 65 99 C8 00 00 00 00 00 00 .d...x.e........ > 0030 00 00 00 00 00 00 00 00 00 00 00 00 ................ > > > Received 85 bytes > 0000 00 04 25 00 01 02 00 40 63 F6 3D 51 90 22 00 00 ..%....@c.=Q.".. > 0010 04 00 42 24 54 44 4D 41 43 46 47 20 72 74 65 74 ..B$TDMACFG rtet > 0020 68 30 20 73 6C 6F 74 20 30 20 32 30 30 3B 69 66 h0 slot 0 200;if > 0030 63 6F 6E 66 69 67 20 76 6E 69 63 30 20 75 70 20 config vnic0 up > 0040 24 49 50 41 44 44 52 20 24 4E 45 54 4D 41 53 4B $IPADDR $NETMASK > 0050 5F 4F 50 54 0A _OPT............ > > This is coming from my master, a VIA Pico, with a via rhine ethernet > controller, using kernel 2.6.24-16-rtai (stock EMC2 deploy). I noticed that > a comment in the rtnet rhine driver source say Rhine II, but the board has a > rhine III. Could it be due to this? Or is this an undocumented packet? I guess the Rhine III is operated by the same driver as the II in standard Linux. Then is may make some sense to check the original code for diffs with our version, specifically for changes that target III support. Jan |
