Ok, actually I try to decompose rtnet script. so I load step by step modules and make initialization of rtroute. the tdma configuration in slave has blocked the entire system. in the master side it seems ok.
in slave side: cd /usr/rtnet/modules/ insmod rtnet.ko insmod rtipv4.ko insmod rtpacket.ko insmod rt_loopback.ko insmod rt_dm9000.ko mac_addr=0x00,0x14,0x2D,0x00,0x01,0x02 insmod rtmac.ko insmod tdma.ko insmod rtcfg.ko insmod rtudp.ko rtifconfig rteth0 up 10.0.0.2 rtifconfig rtlo up 127.0.0.1 #10.0.0.1 is master #rtroute add 10.0.0.1 00:14:2D:00:01:01 dev rteth0 #10.0.0.2 is slave rtroute add 10.0.0.2 00:14:2D:00:01:02 dev rteth0 #slave tdmacfg rteth0 slave tdmacfg rteth0 slot 0 400 #blocked system if the tdmacfg is omitted, the rtping would work, without timing constraint though. r...@mbs270:/usr/neue_rtnet$ rtping 10.0.0.1 Real-time PING 10.0.0.1 56(84) bytes of data. 64 bytes from 10.0.0.1: icmp_seq=1 time=320.0 us 64 bytes from 10.0.0.1: icmp_seq=2 time=287.4 us Thank you Jan Kiszka <jan.kis...@web.de> a écrit : > Am 16.09.2010 17:05, Michel He wrote: >> Hello, >> >> I have to continue debugging the RTnet dm9000 driver which was >> under development previously. It's about the chip aside the PXA270 on >> Toradex & Mobisense platform. The threads were inside >> http://thread.gmane.org/gmane.linux.real-time.rtnet.user >> >> Most parts of the works have been done on alignment problem >> (2010-07-19) and Internal error : Oops (2010-03-30). >> >> Here, there are some remaining bugs to figure out. >> The initialization has been done by loading modules and rtifconfig, >> rtroute. (tdma configuration seems not really fully working though >> with "rtnet start"). >> >> r...@mbs270:~$ rtifconfig >> rteth0 Medium: Ethernet Hardware address: 00:14:2D:00:01:DD >> IP address: 10.0.0.2 Broadcast address: 10.255.255.255 >> UP BROADCAST RUNNING MTU: 1536 >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> >> r...@mbs270:~$ rtroute >> Host Routing Table >> Hash Destination HW Address Device >> 00 0.0.0.0 00:00:00:00:00:00 rtlo >> 01 10.0.0.1 00:14:2D:22:50:E2 rteth0 >> 01 127.0.0.1 00:00:00:00:00:00 rtlo >> 02 10.0.0.2 00:14:2D:00:01:DD rteth0 >> 02 10.0.0.2 00:00:00:00:00:00 rtlo >> 3F 10.255.255.255 FF:FF:FF:FF:FF:FF rteth0 >> >> r...@mbs270:~$ rtping 10.0.0.1 >> RTnet: main(). ipv4_cmd : 0x11c18 >> Real-time PING 10.0.0.1 56(84) bytes of data. >> ioctl: Resource temporarily unavailable >> >> >> The error in dmesg: >> hard_start_xmit returned -11 >> >> What could cause that problem ? >> So, how to deal with the ioctl problem in rtping -> rtdev_xmit (rtdev.c) ? > > -11 == -EAGAIN. I bet you are running out of rtskbs as the transmitted > frames are not released, maybe because not TX completion IRQ arrives, > maybe no IRQ at all? > > Jan > > ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
