Hello,
I found a little problem about
net.tinyos.message.MessageSelection.java ( 1.9 ) in line 198 of the
code.
196 if (isRelated(newClass, messageClass) &&
197 !alreadyHave(newClass)) {
198Message m = (Message)newClass.newInstance();
199
Hi
when I post a task, for instance the example in the
tutorials\BlinkTask\BlinkTaskC,
post toggle() implicitly uses an instance of the TaskBasic interface,
but in the SchedulerBasicP component,TaskBasic.postTask command has a
parameter[uint8_t id].
But when I post the task toggle() in the
On Dec 17, 2007 12:39 AM, Michael Schippling <[EMAIL PROTECTED]> wrote:
> In my humble, humbling, and limited experience with academically
> driven software, upgrading to the new-improved version of something
> generally exposes one to the Latest Software Engineering Paradigms,
> since such softwa
Hi to all,
my problem is following: i send a buffer of byte (fill from me) to serial
port. I read tep 113 and i decided to use the interface SerialByteComm. The
problem is this:
What is the module for a micaz providing this interface?
Do you know other ways to solve this problem?
For my tests,
[EMAIL PROTECTED] wrote:
> Hi
>
> when I post a task, for instance the example in the
> tutorials\BlinkTask\BlinkTaskC,
> post toggle() implicitly uses an instance of the TaskBasic interface,
> but in the SchedulerBasicP component,TaskBasic.postTask command has a
> parameter[uint8_t id].
> But whe
On Dec 16, 2007, at 9:35 AM, Michael Schippling wrote:
Well, isn't this nice... "portable" TOS demo apps have
some platform dependencies defined into them...
SimpleCmd uses a "Pot" component that is specific to the
mica (NOT mica2 or micaz, _mica_) platform. You may be able
to just go edit out
roberto pagliari wrote:
I wonder if someone can explain me the following
split-phase calls do not tie up stack memory while they are
executing.
Synchronous, or "get it done before doing anything else" code is still
interruptable. The stack is used to store state when interrupted, so it can
On Dec 17, 2007, at 6:55 AM, Greg Hackmann wrote:
[EMAIL PROTECTED] wrote:
Hi
when I post a task, for instance the example in the
tutorials\BlinkTask\BlinkTaskC,
post toggle() implicitly uses an instance of the TaskBasic interface,
but in the SchedulerBasicP component,TaskBasic.postTask comma
Michael Schippling wrote:
> In my humble, humbling, and limited experience with academically
> driven software, upgrading to the new-improved version of something
> generally exposes one to the Latest Software Engineering Paradigms,
> since such software is generally developed by grad-students who
On Dec 15, 2007, at 4:26 PM, Kevin Klues wrote:
I like the idea of using a %C directive as a shorthand for finding
the contrib directory. Given that contrib is starting in its
number of users, having such a feature would be nice. To make this
happen, we first need to decide on a standar
On Dec 16, 2007, at 3:39 PM, Michael Schippling wrote:
So, aside from applying my rusty hermeneutic skills to the TEPS,
is there someplace I can find a good description of the advantages
of re-experiencing the TOS learning cliff under T2?
http://www.tinyos.net/tinyos-2.x/doc/html/overview.htm
> First, split-phase calls do not tie up stack memory while they are
> executing.
This is perhaps poorly worded... of course stack memory is tied up while
the code is executing. However, split phase code does not tie up stack
memory in between phases. In other wirds, the call stack for phase 1
I'm not clear on what is improved:
a) the demo apps are better written;
b) there's no way to include platform specific code at the app level;
c) there's no more head-banging required.
???
MS
ps...Agreed. Some new-fangled enginnering ideas are probably
good (in the long run) AND advantageous (
>
> I do. Why should contrib -- a social construction that happens to be
> the way it is mostly due to sourceforge licensing and CVS checkout
> structure -- determine parameters to the compiler? If contrib were in
> tinyos-2.x (as it is in 1.x), then this would not be necessary.
Why even have the
Excellent...thank you...
A couple questions...
One of my projects relies on ATMEGA Timers1&3 for PWM output and
time capture. Have these been preempted by internals or can I
still use them with impunity?
The same project also uses PortC and all the ADC's, round robin
sampling on a 1ms Timer[] (wh
static building: meaning a link phase so you can include
regular 'C' code without hoop-jumping? or...?
thx
MS
John Griessen wrote:
> Michael Schippling wrote:
>> In my humble, humbling, and limited experience with academically
>> driven software, upgrading to the new-improved version of somethin
Great papers...have these been in stealth mode or did I just miss
the announcement? Are they linked in to the new improved TOSdoc wiki?
MS
Vlado Handziski wrote:
...
I would not say that the relation between T2 and T1 can be characterized
by "almost-the-same--except-oh-yeah-we-forgot-that-ver
On Dec 17, 2007, at 9:45 AM, Kevin Klues wrote:
Why even have the %T then? You can always use $TOSDIR or
explicitly write out the path each time you want to reference it.
Its there purely for convenience (its not in fact a 'parameter' to
the compiler in the sense of a command line parame
> Someone please correct me if I'm wrong, but one major motivation for %
> T was .platform, where you can't apply make variable substitution.
This discussion started while talking about .platform files for platforms
developed inside contrib (see subject) and how to most easily reference the
direc
Along these lines...is there a doc that describes the structure of
the TOS devel trees and their position dependencies? I've discovered
by wanton experimentation that I can set TOSDIR/TOSROOT (but, hmm,
which one, and using which (cygwin-hack C:/opt) syntax?) in order to
use different T1 version t
Hi all,
I have 2 questions related to the timing in TinyOS:
1. I implemented a TDMA MAC protocol in TinyOS 1.x. When executed in
the nodes (Im using a MSP430 microcontroller and a nRF2401 radio chip), the
protocol performed without any problem. But when I tried this protocol in
TOSSIM
On Dec 17, 2007 10:08 AM, Kevin Klues <[EMAIL PROTECTED]> wrote:
>
>
> > Someone please correct me if I'm wrong, but one major motivation for %
> > T was .platform, where you can't apply make variable substitution.
>
> This discussion started while talking about .platform files for platforms
> deve
maybe I should read the appropriate TEP, btw what do you mean by
"The point here is that there is just one stack in a TinyOS-based system,
so all execution is LIFO" ?
Roberto
On Dec 17, 2007 12:30 PM, John Regehr <[EMAIL PROTECTED]> wrote:
> > First, split-phase calls do not tie up stack memory
> maybe I should read the appropriate TEP, btw what do you mean by
> "The point here is that there is just one stack in a TinyOS-based system,
> so all execution is LIFO" ?
All tasks and interrupts execute on a single stack.
John
___
Tinyos-help mailing
no, mine is tinyos 1.x, Do you know where to get the sample code suitable to
telosb platform in tinyos 1.x??
thansk
Sam
Philip Levis <[EMAIL PROTECTED]> 写道：
On Dec 16, 2007, at 9:35 AM, Michael Schippling wrote:
> Well, isn't this nice... "portable" TOS demo apps have
> some platform depen
hi, Michael,
to your opinion a) teh demo apps are better written,
where is the demo apps??
thanks
Sam
Michael Schippling <[EMAIL PROTECTED]> 写道：
I'm not clear on what is improved:
a) the demo apps are better written;
b) there's no way to include platform specific code at the app level;
In my opinion I don't know if the demos are better,
that's what I was asking Phil...Folks seem to think
they are, so maybe your best approach is to just go
directly to T2 and don't pass Go.
On the other hand, trying to get T1 apps working is
a good learning exercise...heh
MS
Renee Azhen wrote:
>
Philip Levis wrote:
>I'd be all for a mechanism that can solve the general case, but am leery of
>adding a special case like this.
Phil
==
Kevin Klues wrote:
> Add this environment variable to the .profile file (or wherever environment
> variables are set up):
> export TOSCONTRIB=/pat
Michael Schippling wrote:
..Folks seem to think
> they are, so maybe your best approach is to just go
> directly to T2 and don't pass Go.
>
> On the other hand, trying to get T1 apps working is
> a good learning exercise...heh
>
> MS
And Michael's about the only one left for help with T1, and n
On Dec 17, 2007 2:16 PM, John Griessen <[EMAIL PROTECTED]> wrote:
> What makes the .platform file necessary separately from the ecosens1.target
> file? Could the ecosens1.target do it all somehow?
The .platform file is for ncc (and mig and ncg). The .target file is
something used by the Makefile-
thanks to Michael's stikcing to help newer on Tinyos 1.x.
if he turned to TS 2, I am afraid nobody will be on T1:)
Cheers
Sam
John Griessen <[EMAIL PROTECTED]> 写道：
Michael Schippling wrote:
..Folks seem to think
> they are, so maybe your best approach is to just go
> directly to T2
I'll be an Army of .666...
MS
Renee Azhen wrote:
> thanks to Michael's stikcing to help newer on Tinyos 1.x.
> if he turned to TS 2, I am afraid nobody will be on T1:)
>
> Cheers
> Sam
>
>
> */John Griessen <[EMAIL PROTECTED]>/* 写道：
>
> Michael Schippling wrote:
> ..Folks seem to thi
On Dec 17, 2007 11:49 PM, David Gay <[EMAIL PROTECTED]> wrote:
> On Dec 17, 2007 2:16 PM, John Griessen <[EMAIL PROTECTED]> wrote:
> > What makes the .platform file necessary separately from the
> ecosens1.target
> > file? Could the ecosens1.target do it all somehow?
>
> The .platform file is for
33 matches
Mail list logo
