I'm compiling out of contrib now, and it seemed to work -- even a functional test loaded to flash on a mote. But I don't understand how the includes are working in the .platform file.

Here is some of the one I copied from telosb and added to:

# Includes that should take precedence come first.  Platforms come before
# chips because they may override files (first file found is the one). These must be specified as
# @includes instead of -I's to @opts, otherwise the %T won't be processed
# by ncc. the %T gets expanded to the full location of tinyos-2.x/tos, using the TOS2DIR
# environment variable.

push( @includes, qw(

  %T/platforms/ecosens1
  %T/platforms/ecosens1/chips/stm25p
  %T/platforms/ecosens1/chips/cc2420
  %T/chips/cc2420
  %T/chips/cc2420/alarm
  %T/chips/cc2420/control
  %T/chips/cc2420/csma
  %T/chips/cc2420/interfaces
.
.
chopped off
====

Is %T replaced with /opt/tinyos-2.x/tos ? If so, none of my platform chips dirs were found...by this list at least. So how did it work? Without the Hpl files about MSP430 and CC2420? I doubt it.

So how did it work?   From the ecosens1.target file?  That has a line:

$(call TOSMake_include_platform,msp)

Does the .platform list need to have paths to contrib dir defined by you? I think so...

John Griessen

--
Ecosensory
tinyOS devel on:  ubuntu Linux;   tinyOS v2.0.2;   telosb ecosens1
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to