[Tinyos-help] Development wanted for Deluge T2

[David]

> >
> > Do you have a suggestion for how long to wait before calls to
> > tos-deluge so there won't be errors? I'm using 5s now without errors,
> > but I'm not sure how safe that is, or if it is too long (as fast as
> > possible is nice for testing).
>
> I just committed a fix that should allow the erase/inject to work without
> any additional delays. Let me know if it works well for you.
>

Hi, thanks, it looks like that is fixed :-)

However, it looks like an earlier bug is back, where if you boot into
an image, then that UID is not shown as the currently-executing image
afterwards.

For instance:

(After re-compiling the Blink test deluge app and injecting once for
every slot).

tos-deluge /dev/ttyUSB0 telosb -p 3
Pinging node ...
--------------------------------------------------
Currently Executing:
  Prog Name:   BlinkAppC
  UID:         0x50E978D4
  Compiled On: Fri Jan 18 12:20:17 2008
  Node ID:     0

Stored image 3
  Prog Name:   BlinkAppC
  UID:         0xFA5179D2
  Compiled On: Fri Jan 18 12:23:22 2008
  Platform:    telosb
  User ID:     david
  Host Name:   lnxdavid
  User Hash:   0xB4CD1E4C
  Size:        33504
  Num Pages:   30
--------------------------------------------------

telosb -b 3
error: 0 data: []
Command sent

(At this point the mode flashes on all 3 leds on, then they dissappear
one by one, and then the program starts up. I assume this means a
successful reprogram. I haven't checked with different colored LEDs in
BlinkApp yet).

telosb -p 3
Pinging node ...
--------------------------------------------------
Currently Executing:
  Prog Name:   BlinkAppC
  UID:         0x50E978D4
  Compiled On: Fri Jan 18 12:20:17 2008
  Node ID:     0

Stored image 3
  Prog Name:   BlinkAppC
  UID:         0xFA5179D2
  Compiled On: Fri Jan 18 12:23:22 2008
  Platform:    telosb
  User ID:     david
  Host Name:   lnxdavid
  User Hash:   0xB4CD1E4C
  Size:        33504
  Num Pages:   30
--------------------------------------------------

Currently Executing UID should be "0xFA5179D2" at this point, but it's
still on the old value.

David.