On Mon, Dec 17, 2012 at 8:08 AM, Enrico Scopelliti <erics...@hotmail.it>wrote:
> Thanks to all for replies and informations. > > Is this the link for the msp430-int branch of the tinyprod fork? > https://github.com/tinyprod/prod/tree/msp430-int > It is but it has been integrated into the tinyprod mainline so you actually want to work off gh:tp-freeforall/prod(tp-master) <https://github.com/tp-freeforall/prod> = https://github.com/tp-freeforall/prod, tp-master branch. Instructions for contributing can be found at https://github.com/tp-freeforall/prod/blob/tp-master/00d_Contribution_Process Reading other documents at the top level is also not a bad idea. thanks for your interest. > > > Stay tuned for updates and to contribute ( if i can ). > > Sorry for the lack of prompt response. > > Regards, > > Enrico. > > Did you find the usage of string identifiers to be rather verbose? > Meaning, don't they take up a lot of code space? > > Yes, they do. True. We are limited with the number of CoAP resources to > include on one particular device. Having human-readable description has its > advantages though. > > > That seems to me to be a problem in a resource constrained environment like > the msp430s. Even the large code space puppies. We don't have an > official 20 bit development enviornment yet. > > On Sat, Dec 1, 2012 at 2:27 AM, Markus Becker <m...@comnets.uni- > > bremen.de>wrote: > > Hi, > > a similar problem is solved by IPSO Application Framework [1] for CoAP. > We have implemented some part of its /dev resource for coap-12 (which is > not yet > in the SVN). This is limited to the CoAP application, and not every > general TinyOS application. Those CoAP resources could be rebased onto > PlatformConfig, > though. > > -- > Markus > > > [1] http://www.ipso-alliance.org/downloads/Application+Framework > > I've started defining what I'm calling the Platorm interface that this > would be logically part of. PlatfromConfig. > > The Platform code itself is coming in on the msp430-int branch of the > tinyprod fork. Happening this week. > > So you'll be able to look at its gestation. > > On Fri, Nov 30, 2012 at 10:47 AM, Antonio Linan <ali...@zolertia.com> > <ali...@zolertia.com> > > wrote: > > I use something similar as I include default serial/RF commands in > projects for debugging/maintenance, but feeding this info it is > rather manual in command line/.h file, for an upcoming project I > will try to fill the holes by taking the information from > compilation time, when I have something I'll be happy to share. > > --Antonio > > On Fri, Nov 30, 2012 at 6:16 PM, Eric Decker <cire...@gmail.com> > <cire...@gmail.com> > > wrote: > > You'd have to write this stuff. > > There isn't by default (code doesn't exist) to obtain this > information programatically. > > This is the kind of information one would want in a > production/deployment kind of envrionment. And hasn't been done. > > If you want to work on creating this, I'd be happy to help define > it. I will at some point need this kind of thing for what I'm doing > (production motes) but am not there yet. But do have a vested > interest. > > On Fri, Nov 30, 2012 at 3:14 AM, Enrico Scopelliti > > <erics...@hotmail.it> <erics...@hotmail.it>wrote: > > Hi to TinyOS's developers, > > I would like to know if exists a way to get a SW/HW node's > > description > > > after the deployment. > I'll explain. > For example, there is a mote with TinyOS installed and I want to > > know: > > - what is the application that is currently running; > - what is the installed version of TinyOS; > - what are the TinyOS modules deployed on the mote; > - what are the hardware features of the board. > > Is there a way to get these informations or a part of them? > > Any help appreciated. > > Regards, > > Enrico Scopelliti > > > _______________________________________________ > Tinyos-help mailing listtinyos-h...@millennium.berkeley.edu > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-hel > > p > > -- > Eric B. Decker > Senior (over 50 :-) Researcher > > > > _______________________________________________ > Tinyos-help mailing listtinyos-h...@millennium.berkeley.edu > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > > -- > -- > Antonio Liñan Colina > R+D+I Engineer > @: ali...@advancare.com > @: ali...@zolertia.com > ------------------------------ > Advancare > T: +34 93 582 02 > 70http://www.advancare.comhttp://www.zolertia.comhttp://zolertia.sourceforge.nethttp://webshop.zolertia.com > > ------------------------------------------------ > > | Dipl.-Ing. Markus Becker > | Communication Networks > | TZI - Center for Computing Technologies > | University Bremen > | Germany > > ------------------------------------------------ > > | web: http://www.comnets.uni-bremen.de/~mab/ > | mailto: m...@comnets.uni-bremen.de > | telephone: +49 421 218 62379 > | building: NW1 room: N2260 > > ------------------------------------------------ > > ------------------------------------------------ > | Dipl.-Ing. Markus Becker > | Communication Networks > | TZI - Center for Computing Technologies > | University Bremen > | Germany > ------------------------------------------------ > | web: http://www.comnets.uni-bremen.de/~mab/ > | mailto: m...@comnets.uni-bremen.de > | telephone: +49 421 218 62379 > | building: NW1 room: N2260 > ------------------------------------------------ > > > > > -- Eric B. Decker Senior (over 50 :-) Researcher
_______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
