2007/8/19, Kevin Klues <[EMAIL PROTECTED]>: > On 8/18/07, Luca Briggi <[EMAIL PROTECTED]> wrote: > > I'don't understand what happen when reading from permanent storage > > when using BlockRead.read on data erased but not written (it return > > immediately invalid (EINVAL) or it will signal a readDone with FAIL in > > error_t?). > > > > In ConfigStorage (interface form small objects) a commit makes data > > valid; there is a way to make a small object invalid? > > Take a look at TEP 103 for detailed information on each of these > components and interfaces. > > http://tinyos.cvs.sourceforge.net/*checkout*/tinyos/tinyos-2.x/doc/html/tep103.html > > -- > ~Kevin > On this tep there is no answer to my questions. i've also looked at the comment in the code of the interfaces with the same result. On tep128 (about VolumeSetting interface) is written that usual fill byte is 0xFF (all ones) so i suppose that a read after an erase returns all ones (in terms of bit). If i need to know at mote power-up if there is valid data (previously sync) on a BlockStorage how can i do?
Thanks for the attention. _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
