Seshan Govender wrote: >>> I am using RTnet 0.9.2 and would like some additional advice on another >>> matter. >>> >>> I was previously using RTnet 0.8.3 and had successfully tested the system >>> and had used the raw-packets example. >>> I now see that in the newest version of RTnet that this example only runs >>> under Xenomai and I am using RTAI 3.3 Vulcano release. > >> Side note: release 3.3 had some issue with its RTDM interface, please >> upgrade at least to vulcano CVS. > > Thanks, for that. I downloaded the latest vulcano from CVS. > >>> How can I re-build my example to work on the new version of RTnet? > >> Port the Xenomai demo over the RTAI API. This only involves task > management etc., not the rt_dev_xxx calls (RTnet invocation via RTDM). > > What include files do I need? I have added rtai.h, rtai_sched.h, rtdm.h, > rtnet.h and rtmac.h
rtmac.h is not required for the raw-packet example, rtdm.h is included by rtnet.h > but am getting numerous errors when I try to compile the raw-packets example. All headers found? > Can I still use the existing makefile from xenomai and call make raw-packets? Basically, yes. When you compile inside the RTnet tree and you create a new folder + Makefile, you have to update the references in the automake system (parent folder's Makefile.am, configure.ac). Whenever you change some Makefile, you have to re-run scripts/autogen.sh, and configure or make *config afterwards. Likely it's easier to start stand-alone and just add rtnet to the include path. > Also the only part that requires task management is the creation and deletion > of the tasks. Is this correct because I have tried implementing changes to > these tasks and have had no luck thus far. Try to grab the missing pieces from existing examples, also from the RTAI showroom. In general, to write a RTnet application in kernel or user space, you first need a working skeleton. You then have to include rtnet.h and add the rt_dev_xxx functions. The RTnet-specific step should not introduce problems as long as the skeleton is already fine. Jan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ RTnet-users mailing list RTnet-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rtnet-users
