Hello Markus, thank you for your reply.
However I meant with ONLY one of those resources (and well-known/core). For instance: LEDS and well-known/core = works Voltage and well-known/core = doesn't work Temperature and well-known/core = doesn't work and so on... Regards, -- Francesco Ficarola Department of Computer and System Sciences Sapienza, University of Rome Via Ariosto 25, room B112 00185, Rome Phone: (+39) 0677274119 Skype: francesco.ficarola DIS email: ficarola_at_dis.uniroma1_dot_it Nexse email: francesco.ficarola_at_nexse_dot_com Home email: francesco.ficarola_at_gmail_dot_com GPG KeyID: 0xDBA99D92 On 04/30/2012 09:22 AM, Markus Becker wrote: >> Hello everybody, >> >> I've been trying the CoapBlip application for a while (TinyOS-2.1.2-rc1 >> and TinyOS-trunk), it works pretty fine with telosb nodes... but, if you >> enable the well-known/core, it ONLY works (and not always) if the >> available resource is LEDs. With the other resources (Temp, Hum, Volt, >> Routing, and so on), the application looks like freezed... The node >> responds to ping6 requests, but the CoAP protocol doesn't work. > > CoAP is not able to allocate RAM dynamically if too many resources (with well- > known/core = more than the LED resource) are enabled. Currently there is > nothing I can do about it. > > Markus > >> Is that a known bug? >> >> Regards, > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
