Thanks. I got this working (had some problems, will detail below). The gesture and the extra deluge slots appear to be working, as well as the extra status line for the currently-executing mote. Thanks.
I had the following problems: * Kept getting "No such file or directory: '/home/david/dev/internet/tinyos/tinyos2/cvs_checkout/tinyos-2.x/tos/lib/tosboot/build/telosb/main.ihex'" errors when trying to install the newly-built images. I fixed this by changing to the tos/lib/tosboot directory and running "make telosb". "make all" didn't create this file. But it was included in the ubuntu installers. * Your instructions installed tos-deluge etc under $HOME/local/bin which wasn't under my path. I fixed this by running: export PATH=/home/david/local/bin/:$PATH I found a few more issues with Deluge while testing your updates: * Only image 1 can be disseminated. I understand about image 0, for protection of the Golden Image (Section 5.2 from tinyos-1.x/doc/deluge-manual.pdf), but images 2 and 3 should be able to disseminate. I reprogrammed both of my testing motes with the updated GoldenImage, erased the 4 slots, injected the blink deluge test into slot 0 on the basestation, and attempted to disseminate. It only works on Deluge slot 1. I tried this a few times (erasing images 0-4 from both testing motes, then reinstalling the Blink testing deluge app on both and retrying dissemination). One thing I notice (on the deb-installed version) is that I can fix mote dissemination (after being interrupted and refusing to resume), by re-injecting on the basestation and re-trying the disseminate (so it is possible to "unbrick" updating, but it still is a problem for our needs). Also, the original version can disseminate both slots, not just #1. * I can't build the GoldenImage or other Deluge apps with the "sim" option to test under TOSSIM. Is this currently unsupported? (I usually use telosb, but the tutorial says that only micaz is supported under tinyos-2.x) [EMAIL PROTECTED]:~/dev/internet/tinyos/tinyos2/cvs_checkout/tinyos-2.x/apps/tests/deluge/GoldenImage$ make micaz sim mkdir -p build/micaz placing object files in build/micaz writing XML schema to app.xml compiling GoldenImageC to object file sim.o ncc -c -shared -fPIC -o build/micaz/sim.o -g -O0 -tossim -fnesc-nido-tosnodes=1000 -fnesc-simulate -fnesc-nido-motenumber=sim_node\(\) -Wall -Wshadow -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb -finline-limit=100000 -Ibuild/micaz -DDELUGE_BASESTATION -DDELUGE -I/home/david/dev/internet/tinyos/tinyos2/cvs_checkout/tinyos-2.x/tos/lib/net -I/home/david/dev/internet/tinyos/tinyos2/cvs_checkout/tinyos-2.x/tos/lib/net/drip -I/home/david/dev/internet/tinyos/tinyos2/cvs_checkout/tinyos-2.x/tos/lib/net/Deluge -I/home/david/dev/internet/tinyos/tinyos2/cvs_checkout/tinyos-2.x/tos/lib/net/Deluge/FlashVolumeManager -I/home/david/dev/internet/tinyos/tinyos2/cvs_checkout/tinyos-2.x/tos/lib/net/Deluge/extra -I/home/david/dev/internet/tinyos/tinyos2/cvs_checkout/tinyos-2.x/tos/lib/net/Deluge/extra/avr -I/home/david/dev/internet/tinyos/tinyos2/cvs_checkout/tinyos-2.x/tos/lib/net/Deluge/extra/micaz -I/home/david/dev/internet/tinyos/tinyos2/cvs_checkout/tinyos-2.x/tos/lib/net/Deluge/extra/mica2 -DIDENT_PROGRAM_NAME=\"GoldenImageC\" -DIDENT_USER_ID=\"david\" -DIDENT_HOSTNAME=\"lnxdavid\" -DIDENT_USER_HASH=0xb4cd1e4cL -DIDENT_UNIX_TIME=0x476b75e9L -DIDENT_UID_HASH=0xb19a3410L -Wno-nesc-data-race GoldenImageC.nc -fnesc-dump=components -fnesc-dump=variables -fnesc-dump=constants -fnesc-dump=typedefs -fnesc-dump=interfacedefs -fnesc-dump=tags -fnesc-dumpfile=app.xml /home/david/dev/internet/tinyos/tinyos2/cvs_checkout/tinyos-2.x/tos/lib/net/Deluge/DelugeC.nc:28:28: error: StorageVolumes.h: No such file or directory In component `GoldenImageC': GoldenImageC.nc:31: failed to preprocess /home/david/dev/internet/tinyos/tinyos2/cvs_checkout/tinyos-2.x/tos/lib/net/Deluge/DelugeC.nc make: *** [sim-exe] Error 1 That syntax does however work for non-deluge apps (eg: basic Blink demo). Even if it gets a lot of compile warnings. * Currently-executing UID can be incorrect if you programmed the mote via "make install" instead of through Deluge. This is not serious, but it could be confusing. Could also be related to the next point: * "Currently Executing" always shows slot 1 UID, regardless of what image you've actually booted the basestation into. You should be able to reproduce this problem by: 1) Rebuild the blink deluge test app (to get a new UID) 2) Inject into slot 0 3) Repeat above for slots 1-3 4) Reboot basestation into slot 0 5) Ping slot 0, compare "currently executing UID" with the slot UID 6) Repeat 4-5 for slots 1-3 * And finally, a few questions about Deluge slots. How do you customize the number of slots? (I see your XML updates, but don't see where you changed wiring). Is it safe to change your slot config after your motes already "know" (in their currently-installed deluge setup) that they have a certain # of slots with specific sizes etc? I can't find this info in the docs. There may be other problems, but I haven't tested much further than the above. David. On Dec 20, 2007 11:29 PM, Razvan Musaloiu-E. <[EMAIL PROTECTED]> wrote: > Hi! > > On Thu, 20 Dec 2007, Razvan Musaloiu-E. wrote: > > > Hi! > > > > On Thu, 20 Dec 2007, David wrote: > > > >> See my reply below yours. > >> > >>> 1.) Initially, the plan was to write a new storage manager for Deluge > >>> T2. Unfortunately, it never got completed, and Deluge T2 is still > >>> using a simple storage manager. > >>> > >>> 2.) Yes, this is not in the current Deluge T2. > >>> > >>> 3.) To add more image volumes, just update the volume XML file and a > >>> wiring file. It is hard to determine the number and the size of > >>> volumes each person really needs, so we just put two volumes as an > >>> example. > >>> > >>> 4.) This one is related to the first comment. > >>> > >>> Thank you > >>> > >>> Mike > >>> > >> > >> Thanks for your reply. > >> > >> Do you think that Deluge T2 will be developed further in the near > >> future by the tinyos devs? From your reply I gather that it isn't a > >> priority at the moment. > > > > We just committed a fix for the rollback gesture and we increase the total > > number of images to 4. It would be great if you can give it a try can give > > us > > some feedback. > > > > We are investigating now how to fix 1) and 4). We'll send an email when we > > make more progress. :-) > > I just committed a fix for 4). The information that is published about the > current application is the UID. > > -- > Razvan ME > _______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
