[Tinyos-host-mote-wg] Re: [Tinyos-2.0wg] event signal "not connected" error

Kevin Klues klues at tkn.tu-berlin.de
Thu Apr 21 11:28:23 PDT 2005


Nevermind..... stupid mistake... forgot to implement the default event 
handler.... :)

Kevin

Kevin Klues wrote:

> What could be giving me the following error?
>
> In component `TestArbiterC.Arbiter':
> /home/klueska/TOS/sf/tinyos-2.x/tos/system/RoundRobinArbiter.nc: In 
> function `ReleasedTask.runTask':
> /home/klueska/TOS/sf/tinyos-2.x/tos/system/RoundRobinArbiter.nc(TestArbiterC.Arbiter):104: 
> Resource.released not connected
>
>
> RoundRobinArbiter is a generic module that provides the Resource 
> interface.
> TestArbiterC is an application that creates an instance of the 
> RoundRobinArbiter, and then wires 3 resources to it.
>
> Here are the wirings.....
>
> #define TEST_ARBITER_RESOURCE   "Test.Arbiter.Resource"
> configuration TestArbiterC{
> }
> implementation {
>  components Main
>     , TestArbiterM
>     , new RoundRobinArbiter( uniqueCount(TEST_ARBITER_RESOURCE) ) as 
> Arbiter
>     , LedsC
>     ;
>
>  TestArbiterM -> Main.Boot;
>  Main.SoftwareInit -> LedsC;
>  Main.SoftwareInit -> Arbiter;
>
>  TestArbiterM.ResourceUser -> Arbiter.ResourceUser; 
>  TestArbiterM.Resource0 -> 
> Arbiter.Resource[unique(TEST_ARBITER_RESOURCE)];
>  TestArbiterM.Resource1 -> 
> Arbiter.Resource[unique(TEST_ARBITER_RESOURCE)];
>  TestArbiterM.Resource2 -> 
> Arbiter.Resource[unique(TEST_ARBITER_RESOURCE)];
>
>  TestArbiterM.Leds -> LedsC;
> }
>
> Anyone had this problem before??
>
> Kevin
>
>
> _______________________________________________
> Tinyos-2.0wg mailing list
> Tinyos-2.0wg at Mail.Millennium.Berkeley.EDU
> http://Mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-2.0wg
>
>


_______________________________________________
Tinyos-2.0wg mailing list
Tinyos-2.0wg at Mail.Millennium.Berkeley.EDU
http://Mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-2.0wg


More information about the Tinyos-host-mote-wg mailing list