Is there any way to instantiate a component more than once?
I wrote a program that instantiated a TimerC component and connected
application components to it's Timer interfaces. The program also
used the networking stack. The app didn't work because the networking
stack used the same Timer
That's where you use parameterized interfaces i.e.
components TimerC;
implementation {
MyApp.FirstTimer - TimerC.Timer[unique(Timer)];
MyApp.SecondTimer - TimerC.Timer[unique(Timer)];
}
Note that all interfaces aren't parameterized, and you can't choose any
string for unique. In
Hi, I am also working on first step of tinydb. Just try to download the tinyos-1.1.11 packet. That works for me at least. Although I can compile with make mica2, it finally cannot get value from sensor. I guess we can share some information about this. We have to add new platform to tinydb.Anyone
hi, everybody: I want to set up a fake data in sever mica2 motes and then query these mote from base to receive these data. But now I don't know how to program tinydb to set up the fake data in flash of the motes? Can anyone give me some suggestion? Thanks a lot. Best sazure
Chalermphol,
You are right. With your help, I can now get a
multi-hop network running, and it also solves the
problems with Surge View and Mote View that I had
before.
Thanks a lot for your help.
- Liangping
--- Chalermphol Thammapalerd [EMAIL PROTECTED]
wrote:
Hi Liangping,
You need
On Thu, 2006-02-23 at 13:53 +, Helios Aliaga wrote:
Hello
When simulating Surge application with TOSSIM-packet I get
Segmentation fault (core dumped)
after the simulation runs for a few seconds.
When using bit-level TOSSIM all work fine. Does anybody know what can
be the problem
Quoting Philip Levis [EMAIL PROTECTED]:
I used TOSSIM packet and found out to my surprise that even after sendDone
method is called, if I modify the contents of the packet (e.g. to reuse it)
these changes are visible to the receiving node! May be I'm using an outdated
implementation.
dasarath
Thanks for your reply and sorry about the blank email before.
The segfault doesn't seem to happen in any place in concrete.
I've run other applications without problems. I've also run Surge in
different computers with different TinyOS versions, and the segfault
is still there.
Do you think that
On 2/23/06, Dasarath Weeratunge [EMAIL PROTECTED] wrote:
Quoting Nat Pryce [EMAIL PROTECTED]:
Check out parameterized interfaces.
and nesC 1.2 (well, 1.2.4 now), which has instantiatable components
(they are more template-like, FWIW).
David Gay
___
On Thu, 2006-02-23 at 22:04 +, Helios Aliaga wrote:
Thanks for your reply and sorry about the blank email before.
The segfault doesn't seem to happen in any place in concrete.
I've run other applications without problems.
By definition, a particular CPU instruction has to cause the
Hi,1. In the module file write module xM { ... uses{ interface Timer as Timer1; interface Timer as Timer2; interface Timer as TimerN; //and so on } } implementation { //for each timer u use write its associated event handler event result_t TimeN.fired() {
11 matches
Mail list logo
