On 2012-10-26 17:01, Michael Morscher wrote: > Hi, > > Am Freitag, 26. Oktober 2012 16:34 CEST, Jan Kiszka <jan.kis...@siemens.com> > schrieb: >> The purpose is to tell Linux to unbind the active driver (e1000) from >> the card and bind the rt_e1000 instead. As long as there is only one >> adapter of the same kind, it's basically "rmmod e1000; modprobe >> rt_e1000" (and "rmmod rt_e1000; modprobe e1000" on stop). I don't know >> what you are doing instead, so I cannot asses the difference. I guess >> there is a general bug in rt_e1000 regarding unload and that hardware. >> >> Does avoiding the rebind solve your first issue with TDMA? > > I'm actually nearly doing the same. I'm just doing a "rmmod e1000" and then > "rtnet start" which does load the right module (rt_e1000.ko). > > The TDMA failure is still there. I got one stable handshake out of 5 tries > now. rtnet start/stop works, but after a few seconds the master is spamming > loads of TDMA failures... Looks like I need the right timing when I start > loading on both serial consoles of the boards... > > If I start the slave first and half a second later the master, it works...
That is suspicious. Could you check if the is no IRQ conflict between the rt-nic on some other Linux device? See /proc/interrupts and /proc/xenomai/irq (when the NIC is started). Also, the full dmesg log may reveal further details. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
