Hi!

The old version of Deluge T2 made some assumptions about the images which are probably related with this problem.

I just committed a fix which allows non-Deluge images before Deluge. The test I did was using this:

        <volume_table>
          <volume name="TEST" size="65536"/>
          <volume name="GOLDENIMAGE" size="65536" base="983040" />
          <volume name="DELUGE1" size="65536"/>
          <volume name="DELUGE2" size="65536"/>
          <volume name="DELUGE3" size="65536"/>
        </volume_table>

--
Razvan ME

On Tue, 15 Jan 2008, David wrote:

Hi. Since I can't test the CVS version at the moment, I'm testing the
Ubuntu-installed tinyos-2.x at the moment.

One thing I've just seen which didn't come up before, is the mote
stops accepting tos-deluge communication after a few injects (or
immediately) if you setup your XML file so that DELUGE slots are in an
unusual place.

For instance, with the Blink deluge test app
(/opt/tinyos-2.x/apps/tests/deluge/Blink), if you add a new line to
the start of volumes-stm25p.xml, then tos-deluge -i will start
misbehaving.

Here's my new volumes-stm25p.xml:

<volume_table>
 <volume name="TEST" size="65536"/>
 <volume name="DELUGE0" size="65536"/>
 <volume name="DELUGE1" size="65536"/>
</volume_table>

After running a make install, inject no longer works. "Pinging node
..." just freezes.

When I broke the above (Ctrl+C), and tried it again, it got further,
but froze a bit later:

=== OUTPUT STARTS ===

Pinging node ...
Connected to Deluge nodes.
--------------------------------------------------
Stored image 1
 Prog Name:   OmnipoAppC
 Compiled On: Thu Jan 10 11:05:35 2008
 Platform:    telosb
 User ID:     david
 Host Name:   lnxdavid
 User Hash:   0xB4CD1E4CL
 Num Pages:   32/32

 Size:        35344
 UID:         3280566561
 Version:     1
--------------------------------------------------
Ihex read complete:
 Total bytes = 28520
 Sections = 2
--------------------------------------------------
[-%        25%         50%         75%         100%]
ERROR: Unable to send the last serial packet (file offset: 22)

=== OUTPUT ENDS ===

After the above error, tos-deluge -i keeps getting this error:

Pinging node ...
ERROR: Unable to retrieve image information over serial

The only way to restore the mote is to re-run 'make telosb install'.
Following that, the next error I get from 'tos-deluge -i' (when it
starts running without freezing) is:

"WARNING: Invalid image format detected". Then it freezes near the
start of the transfer, like above.

This is unfortunate, as I now don't have a way to store config
information to flash without either causing Deluge to bomb out, or my
config data to be invalidated by Deluge :-(

Please look into this problem (or help me with the CVS problem, see
earlier mail, so I can use that version instead). Thanks

David.

_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to