James Kilts wrote: > I'm running into another problem porting the ns9xxx-eth.c network > driver to RTnet. Slave mode works well when connecting to a known > working PC with RTnet, and rtping works fine after the connection is > established. But device cannot establish a connection in master mode, > neither while broadcasting for the PC nor while using another > identical device (which obviously is known to work in slave mode). > > I've verified that the RTcfg Stage 1 Config packets are identical > (except for IP addresses) between the working setup (in slave mode) > and the non-working condition (in master mode). The problem seems to > be with the TDMA Sync packets. There are a number of fields which are > simply not populated. The "Cycle Number" is incrementing and > "Scheduled Transmission Time" appears to be a somewhat reasonable > value. Why would the other values not be populated? (see data > capture below)
(Better include the parsed frames as wireshark displays them - easier to read unless one knows all protocol bits by heart.) Is your driver trying to time-stamp outgoing frame already? If yes, maybe the is a problem with the required late update of the frame. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ RTnet-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rtnet-developers
