On Friday 25 August 2006 09:59 am, David Gay wrote: > On 8/25/06, R. Steve McKown <[EMAIL PROTECTED]> wrote: > > What's the best practice for initially configuring the various > > Block/Log/Config storage components' volumes, especially in a moderate > > volume production setting? I'm currently thinking a separate program > > needs to do intitial setup before the main application is installed. > > I think it's too new for their to be a best practice yet... We assumed > you would consider your application's needs, flash chip > characteristics (erase size, etc), and pick accordingly (each kind of > flash chip has a separate configuration file for volumes).
I'm thinking more about initializing flash volumes for the various storage abstractions. Initialization would be an issue for new motes with "factory fresh" flash, or motes which have been reprogrammed after a change to the volume organization (volumes-<impl>.xml file). For sake of argument, I'm going to call these conditions "invalid volume", relative to the storage abstraction which is (to be) using the volume. If I read TEP 103 correctly, BlockStorageC and ConfigStorageC can detect an invalid volume, using BlockRead.verify and ConfigStorage.valid (after mount()), respectively. Is this correct? I can't find a similar mechanism for LogStorageC; is there one? TEP 103 doesn't say, but I'm assuming if LogStorageC has an invalid volume, LogWrite.erase() must first be called? Thanks for your patience. Steve _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
