nesC is simply a super-set of C. There are things that may have to be rewritten to work within the TinyOS programming model or fit within the mote specs and provided run-time. While the external C can (with some effort and subject to various restrictions) be linked in, it might be easiest just to copy (after a review) portions of the C code into an appropriate NC harness and let ncc take care of the rest.
HTH, Paul On Sat, Jul 26, 2008 at 5:14 PM, Faisal Aslam <[EMAIL PROTECTED]> wrote: > Thanks for your reply. If I cannot call TinyOS from my C code then can I > call my C from NecC code? > That might also work although I prefer calling TinyOS. > > best regards, > Faisal > >> "No". >> However, you might try to poke around the ncc-generate "plain" C >> output files (e.g. app.c). >> >> HTH, >> Paul >> >> On Sat, Jul 26, 2008 at 3:50 PM, Faisal Aslam >> <[EMAIL PROTECTED]> wrote: >>> Dear all, >>> >>> I have already some C code that I do not wish to rewrite in Nesc/TinyOS. >>> However, I do not have drivers for radio or a MAC protocol. I like >>> TinyOS >>> MAC layer. Therefore, I wish if I can call TinyOS from my C code and do >>> not have to write radio drivers and MAC. >>> >>> Please help! >>> >>> -- >>> Faisal Aslam >>> >>> >>> _______________________________________________ >>> Tinyos-help mailing list >>> [email protected] >>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>> >> _______________________________________________ >> Tinyos-help mailing list >> [email protected] >> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >> > > > -- > Faisal Aslam > > PhD Student > University of Freiburg > http://cone.informatik.uni-freiburg.de/people/aslam/ > > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
