[Tinyos-help] Deluge invalidating non-deluge flash volumes?

[David]

I have un-CC'd Jonathan Hui, since this seems to be a Deluge problem
rather than a storage issue (other than that the storage does not do
bounds checking).

> >
> > For now I'll keep all my volumes before Deluge's, but please (to the
> > tinyos devs in general) look into this.
> >
> > Btw, what is the best way to force Deluge volumes to go to the end of
> > the flash memory instead of the start? I would like to disrupt Deluge
> > as little as possible when I add new volumes for my app. Probably
> > "offset", but what values should I use?
> >

I initially tried an xml file, where deluge volumes were at the end
(by creating RESERVED slots first), but Deluge didn't like that.
tos-deluge kept freezing while trying to ping those slots. Please
check that.

For your reference, here is the xml file I tried using:

<volume_table>
  <volume name="CONFIG"  size="131072"/>
  <volume name="RESERVED2" size="65536"/>
  <volume name="RESERVED3" size="65536"/>
  <volume name="RESERVED4" size="65536"/>
  <volume name="RESERVED5" size="65536"/>
  <volume name="RESERVED6" size="65536"/>
  <volume name="RESERVED7" size="65536"/>
  <volume name="RESERVED8" size="65536"/>
  <volume name="RESERVED9" size="65536"/>
  <volume name="RESERVED10" size="65536"/>
  <volume name="RESERVED11" size="65536"/>
  <volume name="RESERVED12" size="65536"/>
  <volume name="RESERVED13" size="65536"/>
  <volume name="DELUGE0" size="65536"/>
  <volume name="DELUGE1" size="65536"/>
</volume_table>

For that one, DELUGE0 can be accessed (through tos-deluge), but not
DELUGE1. The "ping" part of tos-deluge always stalls.

I also tried a variation, in case deluge needs some room after the
last deluge slot to be able to work (ie, to work around it's bug, but
to still keep deluge at the end of the flash memory):

<volume_table>
  <volume name="CONFIG"  size="131072"/>
  <volume name="RESERVED2" size="65536"/>
  <volume name="RESERVED3" size="65536"/>
  <volume name="RESERVED4" size="65536"/>
  <volume name="RESERVED5" size="65536"/>
  <volume name="RESERVED6" size="65536"/>
  <volume name="RESERVED7" size="65536"/>
  <volume name="RESERVED8" size="65536"/>
  <volume name="RESERVED9" size="65536"/>
  <volume name="RESERVED10" size="65536"/>
  <volume name="RESERVED11" size="65536"/>
  <volume name="RESERVED12" size="65536"/>
  <volume name="DELUGE0" size="65536"/>
  <volume name="DELUGE1" size="65536"/>
  <volume name="DELUGE_CORRUPTED_VOLUME" size="65536"/>
</volume_table>

But for some reason tos-deluge could no longer ping *any* slots.
Please investigate these problems.

I also tried an XML file like this:

<volume_table>
  <volume name="DELUGE0" size="65536"/>
  <volume name="DELUGE1" size="65536"/>
  <volume name="DELUGE_CORRUPTED" size="65536"/>
  <volume name="CONFIG"  size="131072"/>
</volume_table>

However, CONFIG is still being invalidated. It looks like the only
safe way to prevent invalidation is to move CONFIG to the start.

David.