direct all comments, questions, and concerns to me.
I will collect all feedback and forward to the authors of the TEP in
about 3 weeks.
Thanks!
Matt Welsh
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.e
It doesn't matter to me who hosts the wiki; I was hoping to host it
behind a generic DNS name so its physical location could be moved
whenever.
On Mon, 2007-08-13 at 12:51 -0700, Joe Polastre wrote:
> > Our goal was that the wiki would be hosted at Harvard. The tinyos.net
> > site is hosted by Be
in to the tree!
Matt Welsh
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
I agree with Kevin here. Phil's example of putting printf's between two
points in the program isn't guaranteed to do the "correct" thing on
UNIX, either.
Anyone using printf in that way is writing incorrect code.
On Fri, 2007-09-21 at 20:47 -0700, Kevin Klues wrote:
> I guess saying that "printf
While I like this idea, are we going through a TEP vetting process
before adding new calls in the radio stack interface? I could think of
a lot of things that one might want to add to the CC2420 radio stack
but I thought the idea of the TEP process was to air these ideas
through feature ext
One of the interesting aspects of NesC is that it doesn't enforce any
specific kind of encapsulation of interfaces. That is, an application
component can "poke through" the various layers below it to get at an
interface provided by a deeper underlying component. In this case you
propose to
The timer ticks in binary milliseconds. So you need
TIMER_INTERVAL=10240 to represent 10 seconds.
On Mar 7, 2008, at 7:50 PM, Iñigo Urteaga wrote:
Hi,
I'm trying to synchronize a simulation in TOSSIM with an application
running a PDE model. I have timers (using Timer) firing every
10 second
This seems like an unnecessarily large swath of the AM address space
for one small working group. It would be better to justify this in
terms of your actual needs, rather than projected. How many AM IDs do
the net2 protocols currently need and can we estimate the growth in
the protocol spac
e could move to
16-bit AM IDs.
Matt
On Apr 29, 2008, at 10:59 PM, Philip Levis wrote:
>
> On Apr 29, 2008, at 7:41 PM, Matt Welsh wrote:
>> This seems like an unnecessarily large swath of the AM address space
>> for one small working group. It would be better to justify this in
onsider an AM ID assignment as a
revokable lease, rather than a permanent guarantee. That way the net2
WG can reclaim unused/stale AM IDs if needed.
On Apr 30, 2008, at 12:11 PM, Philip Levis wrote:
>
> On Apr 30, 2008, at 6:02 AM, Matt Welsh wrote:
>> That makes a lot more sense
OK, this is fine enough, though I guess it means that the net2 WG is
the gatekeeper for all protocols in TinyOS. It wasn't clear to me that
this was the case...
>> For the protocols that are distributed with the core (lib/net), it is
>> clear that we want ID allocation and they MUST not confli
Hi all:
I have searched the archives and have not found much information
about running TinyOS on MacOS machines (Intel in my case).
There is some information here:
http://www.allthingsalceste.com/tinyos-on-mac-os-x/
However, there are a few details missing on this page, such as how
to get
I'm not sure if this is what you are looking for, but I did a port
of *most* of the functionality of the Java tools to C#:
http://www.eecs.harvard.edu/~mdw/private/csharp.tar.gz
Most of it is automatically converted from the Java code,
with various tweaks and hacks. There is an example program
i
Quick update:
I have checked in a small change to tools/src/sf/sfsource.c
that allows the C-based Serial Forwarder to work on MacOS.
Onto getting the Java tools to talk to it (possibly by excising
the dependency on javax.comm). Has anyone tried TOSComm on MacOS?
> I don't know a good answer to
gt; I know that there many other folks like me. If you could
> kindly post
> your experiences, that would be great! I will give it an
> another try
> :-)
>
> Thanks and good luck,
>
> - Vinayak
>
Folks,
I quickly threw together a web page with all the steps (I think!)
that I used to get TinyOS working on Mac OS X on Intel:
http://www.eecs.harvard.edu/~mdw/proj/tinyos-macos
This supports both programming motes and using serialforwarder
on Intel Macs. There are a few steps I am not 100% su
it's a total hack, but it appears that it creates valid
binaries. I've can compile various apps in $TOSROOT/apps and
$MOTEIV_DIR/apps with success. Moteiv's Trawler and Oscilloscope apps
both appear to produce valid results.
Regards,
Robert
On 5/3/06, Matt Welsh <[EMAIL PRO
17 matches
Mail list logo
