Re: [Tinyos-help] Deluge T2 on Shimmer2r plataform
Sending again from my tinyos-help subscribed address. On Mon, Apr 7, 2014 at 6:51 PM, András Bíró andras.b...@unicomp.hu wrote: Hi Emanual, Yes, I did port deluge to some atm128rfa1/stm25p platform, but I'm not familiar with msp430. I think shimmer2r doesn't have any integrated flash, just the optional SD card, which is unsupported by both deluge and tosboot, and the drivers present in tinyos is far from the best (a friend of mine complained about it a lot). That meens, that first you need to write an sd card driver which supports BlockRead/BlockWrite in tinyos, then an other SD card driver for tosboot, which supports reading. This is way too much work to get deluge working, if you ask me. But, if you want to dig yourself in deluge code, here's an advice: there's a lot of duplacated code in tos/lib/tosboot and tos/lib/net/Deluge/extra. tos/lib/net/Deluge/extra is rearly used if you copy some files to tosboot, it will work without it, with much less confusion. Best, Andris On Mon, Apr 7, 2014 at 6:15 PM, Emanuel Lima Lima emanuelrl...@hotmail.com wrote: Hi András Bíró, I'm trying to put Deluge T2 to work with the Shimmer2r platform and i saw that you make the same to other platforms, perhaps for the Shimmer platform too. Is that the case? If not, could you give me some tips where do i start? Any help would be helpfull. Thanks very much, Emanuel Lima https://www.mail-archive.com/search?l=tinyos-help@millennium.berkeley.eduq=from:%22Andr%C3%A1s+B%C3%ADr%C3%B3%22 ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 multiplataform
Hello. On Fri, 4 Apr 2014, Emanuel Lima Lima wrote: I'm currently working with Deluge T2 and this protocol is only available for a group of platforms. I came ask, if someone tried to put Deluge T2 to work with a platform that doesn't belong to this group, like Shimmer2r for example? The help will be much appreciated. I added my platform (wserial (avr1281+at45db from DELUGE point of view) with this patch https://github.com/mcerveny/tinyos-main/commit/891e03cee2dd2285bcb4badf851d3bda87de66f7 (You do not need all changes, the patch also resolve non-power-of-2 page format of at45db (264 bytes page instead of 256 bytes page).) I do not known platform Shimmer2r (msp430) and how self programming (tosboot) is working on this platform. Probably you can replicate all from tinynode platform (makefiles, ifdefs, addons directories ...). Regards, Martin Cerveny ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 Tutorial Help Couldn't execute msp430-gcc
On Wed, Feb 13, 2013 at 10:46:29PM +0500, Muhammad Tayyeb wrote: Hi, I am new to TinyOS and implementing the tutorials. I am on Deluge T2 at the moment. When I run the command ./burn serial@/dev/ttyUSB0:115200 telosb I get the following error xubuntos@xubuntos-tinyos:/opt/tinyos-2.x/apps/tests/deluge/Blink$ ./burn serial@/dev/ttyUSB0:115200 telosb rm -rf build rm: cannot remove `build/telosb/ident_flags.txt': Permission denied rm: cannot remove `build/telosb/StorageVolumes.h': Permission denied make: *** [clean] Error 1 Compile and load Blink mkdir -p build/telosb /bin/sh: cannot create build/telosb/ident_flags.txt: Permission denied You should copy the whole tinyos-2.x directory to somewhere in your user's $HOME if you want to build stuff. Your help will be much appreciated on the error Couldn't execute msp430-gcc error. msp430-gss exe is present in its folder. You probably need to install additional packages. Search your package manager for msp430 or so. -- O ascii ribbon campaign - stop html mail - www.asciiribbon.org pgpoIq6IfiV1F.pgp Description: PGP signature ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 Tutorial Help Couldn't execute msp430-gcc
This is actually for Muhammad but I only have Robin email directly. On Wed, Feb 13, 2013 at 12:42 PM, Robin Martinjak r...@rmartinjak.de wrote: On Wed, Feb 13, 2013 at 10:46:29PM +0500, Muhammad Tayyeb wrote: Hi, I am new to TinyOS and implementing the tutorials. I am on Deluge T2 at the moment. I am guessing that you are on cygwin. It would have been really helpful if you had told us what system you are hosting your development environment on. When I run the command ./burn serial@/dev/ttyUSB0:115200 telosb I get the following error xubuntos@xubuntos-tinyos:/opt/tinyos-2.x/apps/tests/deluge/Blink$ ./burn serial@/dev/ttyUSB0:115200 telosb rm -rf build rm: cannot remove `build/telosb/ident_flags.txt': Permission denied rm: cannot remove `build/telosb/StorageVolumes.h': Permission denied what do the permissions look like for the install? make: *** [clean] Error 1 Compile and load Blink mkdir -p build/telosb /bin/sh: cannot create build/telosb/ident_flags.txt: Permission denied You should copy the whole tinyos-2.x directory to somewhere in your user's $HOME if you want to build stuff. Gag. We haven't updated the install instructions but the new improved mechansims to get the release are as follows: cd ~ mkdir -p w cd w git clone git://github.com/tinyos/tinyos-release.git The above will put the current tinyos release (2.1.2) into the directory ~/w/tinyos-release you will have to tweak your environment variable appropriately. you will also need git, apt-get install git-core should do the trick But I am assuming that you are on Linux and I suspect that isn't true. Currently, we don't have cygwin rpms for the 4.6.3 buildsSo if you are on cygwin, I'm not sure what you can do. The problem you will also run into is 2.1.2 needs 4.6.3. I would strongly encourage you to switch over to a Linux box (Debian or Ubuntu). I originally started TinyOS development using a Cygwin host and found it to be quite painful as well as problematic. At some point I got fed up and switched over to Linux and haven't looked back. I do much of the packaging for toolchains and tinyos and do not support the cygwin rpms. I support the debian archives. Also the TinyOS repository at Stanford is no longer actively maintained so am hosting my work at tinyprod.net. See below. Your help will be much appreciated on the error Couldn't execute msp430-gcc error. msp430-gss exe is present in its folder. running commands as root isn't recommended, you can really do damage if you screw something up. did you install the msp430 toolchain (you need 4.6.3 which you can get from http://tinyprod.net/repos/debian/ you should be able to execute the command msp430gcc --version to make sure that You probably need to install additional packages. Search your package manager for msp430 or so. -- O ascii ribbon campaign - stop html mail - www.asciiribbon.org ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Eric B. Decker Senior (over 50 :-) Researcher ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge t2 issues
Hi Sadun, On Mon, Dec 10, 2012 at 5:18 PM, sadun silva silva.sa...@gmail.com wrote: Hi all, I have been working with deluge for couple of days now. I checked out the tree from google code. (so a stable version). But I ran in to following problems. 1. I do not have any way to erase the volumes. -e switch does not work. I tried installing an all new blink application thinking it will erase the entire flash. But still the mote has the image which i injected earlier. Do you guys know how to cleanly erase the flash so that the mote is unaware of any deluge components? You mean, you did run tos-deluge serial... -i imagenum image twice, and you still have the earlier image on the basestation? I never head problem with that, I didn' even know that there's a -e argument, because -i always overwrote the earlier image. 2. I tried -d switch to disseminate after that tried to use -r switch. It simply does not work. When -dr switch is used it works flawlessly. Do you guys have any idea why is this? Yeah, that's kind of stupid -r only reprogram the basestation, which doesn't make any sense, because you probably always want to use a deluge basestation. However, -dr will reprogram everything BUT the basestation, and it won't disseminate the image, if it's already done. Andras Biro Software Engineer Unicomp Ltd. http://ucmote.com Thanks any help is appreciated. Sadun ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 and iris motes
Hi all, I think I have solved my issues with deluge T2 and iris motes with Ubuntu 11.04. I used the git repository (checked out on July 13th 2012) and all the latest versions of avr tools (locally recompiled with gcc4.6.1). I found 2 bugs in this version of the database/tools compiled for IRIS target. They are all related to the external flash (AT45DB) having pages of 264 bytes instead of 256 bytes: - the function StorageMap.getPhysicalAddress() in tos/lib/net/Deluge/BlockStorageManagerP.nc is obviously written for AT45DB with 256-bytes pages. - the function ExtFlash.startRead() in tos/lib/tosboot/at45db does not work for 264-bytes pages. I think the root of all evil lies in function multiplageContinue() in chips/at45db/BlockStorageP.nc. The version that is used in the Xubuntu vmware image (which does work), is written for 256-bytes pages while the version in the git repository is designed for 264-bytes pages. I guess we should either revert back to the old version of multiplageContinue(), or update StorageMap.getPhysicalAddress() and ExtFlash.startRead(). I would be glad to submit/discuss my corrections with an official maintainer of tinyOS/Deluge or anybody with needs them. Regards, Yann On 07/10/2012 09:54 PM, András Bíró wrote: Hi Guys, It's seems there is a bunch of deluge related problem recently, and altough I don't really know the source of your problems, Deluge T2 certainly works. I didn't use it on memsic motes for quite a long time (although I could test it on irises if you wish), but I've ported it to the motes our company manufactures, and recently I programmed about 150 motes with it (all of them in the same room). By the way, I'm using Arch linux, and the newest python2 package on it for tinyos python scripts, I never had any problem with the tos-deluge - mote connection. Debugging a deluge related problem is really painful, since it's quite complex protocol, handling awful lot of data. Some issues I had problems with: -TOSH_DATA_LENGTH _must_ be the same on all motes. If the receiver's TOSH_DATA_LENGTH is bigger than the sender's, the receiver fills the remaining data with garbage, and that will cause crc error in the bootloader. That means it will restart with the old image, redownload the new, reboots, detects the crc error and so on. -Deluge doesn't like if there's serious communication in the area. It really slows down the downloading of the image (from two minutes to fifteen-thirty), and worst of all, it also causes image crc errors (not sure why, but at first we could only reprogram about 50 of the 150 motes. Fortunately, we could disable almost all communication on the motes). -Image 0 is the golden image (1; 2 and 3 are general purpose images), but it's not well designed. You have to inject the golden image yourself, but at some point deluge will stop you to use it as the other images, and I think that point is the dissemination. Therefor, you have to inject it with serial on all motes (but I'm not sure, I didn't really cared this issue) -You also have to be extramly unfortunate, if you encounter a mote automaticly programs itself with golden image. Tosboot only incrases the gesture counter (which counts to 3, and when reaches 3, tosboot will program the golden image) if ther was some problem during copying a page from the external flash to the internal, but I never had such problem. It does not protect your mote from redownloading a crc error image again and again, which happens quite often however. Andris On Tue, Jul 10, 2012 at 4:54 PM, Yann Le Corre yann.leco...@uni.lu wrote: Hi, It looks similar to what I have here. I (almost) gave up and I tried the xubuntu VMWare from tinyOS wiki. Everything seems to be working fine now. I can disseminate and execute. It seems that Deluge T2 has issues with ubuntu 11.10 and 12.04 LS. I would be glad to help to solve them if anybody could give me some clues. Regards, Yann On 07/10/2012 05:20 PM, Hamid Rafiei Karkvandi wrote: Hi, I have been having no success in using Deluge T2 with IRIS and MIB520. First I failed even to install Deluge correctly on Cygwin so I migrated to Ubuntu 12.04 LS and I installed the recent updated version of Tinyos. Deluge T2 runs on the mote, I inject the image and I read the flash successfully and even mine doesn't give the error you mentioned (is it base station or not ... ) but still after dissemination I can see other motes start to get the image and write it down on their flash (the green LED blinks fast) but after all no one reboots and execute the new image ... I kinda gave up on it, but if anyone has a similar experience and knows how to solve these issues with IRIS and Deluge T2, I appreciate ... Regards, Hamid Rafiei Karkvandi On Tue, Jul 10, 2012 at 7:40 AM, Yann Le Corre yann.leco...@uni.lu wrote: Hi All, I try to get Deluge T2 working on my Iris motes but with no success so far. Starting
Re: [Tinyos-help] Deluge T2 and iris motes
Yann, Thanks for reporting this issue. A quick recap, just for the record: a recent change to chips/at45db/BlockStorageP.nc that allowed for non-power-of-two page sizes broke deluge/tosboot on the iris and micaz (probably other platforms, too), because deluge and tosboot were expecting the page size to be 256. For now, I reverted back to the old chips/at45db/BlockStorageP.nc, which assumes that the page size is a power of 2. Deluge/tosboot needs to be fixed post 2.1.2. I'm posting a google code issue, as well. Janos On Fri, Jul 27, 2012 at 8:54 AM, Yann Le Corre yann.leco...@uni.lu wrote: Hi all, I think I have solved my issues with deluge T2 and iris motes with Ubuntu 11.04. I used the git repository (checked out on July 13th 2012) and all the latest versions of avr tools (locally recompiled with gcc4.6.1). I found 2 bugs in this version of the database/tools compiled for IRIS target. They are all related to the external flash (AT45DB) having pages of 264 bytes instead of 256 bytes: - the function StorageMap.getPhysicalAddress() in tos/lib/net/Deluge/BlockStorageManagerP.nc is obviously written for AT45DB with 256-bytes pages. - the function ExtFlash.startRead() in tos/lib/tosboot/at45db does not work for 264-bytes pages. I think the root of all evil lies in function multiplageContinue() in chips/at45db/BlockStorageP.nc. The version that is used in the Xubuntu vmware image (which does work), is written for 256-bytes pages while the version in the git repository is designed for 264-bytes pages. I guess we should either revert back to the old version of multiplageContinue(), or update StorageMap.getPhysicalAddress() and ExtFlash.startRead(). I would be glad to submit/discuss my corrections with an official maintainer of tinyOS/Deluge or anybody with needs them. Regards, Yann On 07/10/2012 09:54 PM, András Bíró wrote: Hi Guys, It's seems there is a bunch of deluge related problem recently, and altough I don't really know the source of your problems, Deluge T2 certainly works. I didn't use it on memsic motes for quite a long time (although I could test it on irises if you wish), but I've ported it to the motes our company manufactures, and recently I programmed about 150 motes with it (all of them in the same room). By the way, I'm using Arch linux, and the newest python2 package on it for tinyos python scripts, I never had any problem with the tos-deluge - mote connection. Debugging a deluge related problem is really painful, since it's quite complex protocol, handling awful lot of data. Some issues I had problems with: -TOSH_DATA_LENGTH _must_ be the same on all motes. If the receiver's TOSH_DATA_LENGTH is bigger than the sender's, the receiver fills the remaining data with garbage, and that will cause crc error in the bootloader. That means it will restart with the old image, redownload the new, reboots, detects the crc error and so on. -Deluge doesn't like if there's serious communication in the area. It really slows down the downloading of the image (from two minutes to fifteen-thirty), and worst of all, it also causes image crc errors (not sure why, but at first we could only reprogram about 50 of the 150 motes. Fortunately, we could disable almost all communication on the motes). -Image 0 is the golden image (1; 2 and 3 are general purpose images), but it's not well designed. You have to inject the golden image yourself, but at some point deluge will stop you to use it as the other images, and I think that point is the dissemination. Therefor, you have to inject it with serial on all motes (but I'm not sure, I didn't really cared this issue) -You also have to be extramly unfortunate, if you encounter a mote automaticly programs itself with golden image. Tosboot only incrases the gesture counter (which counts to 3, and when reaches 3, tosboot will program the golden image) if ther was some problem during copying a page from the external flash to the internal, but I never had such problem. It does not protect your mote from redownloading a crc error image again and again, which happens quite often however. Andris On Tue, Jul 10, 2012 at 4:54 PM, Yann Le Corre yann.leco...@uni.lu wrote: Hi, It looks similar to what I have here. I (almost) gave up and I tried the xubuntu VMWare from tinyOS wiki. Everything seems to be working fine now. I can disseminate and execute. It seems that Deluge T2 has issues with ubuntu 11.10 and 12.04 LS. I would be glad to help to solve them if anybody could give me some clues. Regards, Yann On 07/10/2012 05:20 PM, Hamid Rafiei Karkvandi wrote: Hi, I have been having no success in using Deluge T2 with IRIS and MIB520. First I failed even to install Deluge correctly on Cygwin so I migrated to Ubuntu 12.04 LS and I installed the recent updated version of Tinyos. Deluge T2 runs on the mote, I inject the image and I read the flash successfully and even mine doesn't give
Re: [Tinyos-help] Deluge T2 and iris motes
Hi, I have been having no success in using Deluge T2 with IRIS and MIB520. First I failed even to install Deluge correctly on Cygwin so I migrated to Ubuntu 12.04 LS and I installed the recent updated version of Tinyos. Deluge T2 runs on the mote, I inject the image and I read the flash successfully and even mine doesn't give the error you mentioned (is it base station or not ... ) but still after dissemination I can see other motes start to get the image and write it down on their flash (the green LED blinks fast) but after all no one reboots and execute the new image ... I kinda gave up on it, but if anyone has a similar experience and knows how to solve these issues with IRIS and Deluge T2, I appreciate ... Regards, Hamid Rafiei Karkvandi On Tue, Jul 10, 2012 at 7:40 AM, Yann Le Corre yann.leco...@uni.lu wrote: Hi All, I try to get Deluge T2 working on my Iris motes but with no success so far. Starting with only one mote connected to the PC with a mib520, I tried the following steps: 1. compile and install apps/test/deluge/Basestation 2. tos-deluge serial@/dev/ttyUSB1:57600 -p 0 == I can read the flash content, everything seems OK 3. compile and install apps/test/deluge/Blink == led0 is blinking 4. tos-deluge serial@/dev/ttyUSB1:57600 -p 0 == ERROR: Timeout. Is the node a Deluge T2 base station? My PC is running Ubuntu 11.10 with avr-gcc 4.63, avr binutils 2.22, nescc 1.3.3 and tinyOS tree from CVS. CFLAGS always contains -DDELUGE_BASE_STATION or -DDELUGE_LIGHT_BASE_STATION. After a lot of trials and errors, it appears that I can make deluge/Blink answer to the tos-deluge -p if I change the -DIDENT_APPNAME flag. Actually, what seems to matter is the length of the application name. For example -DIDENT_APPNAME=\BlinkAppC\ will not work while -DIDENT_APPNAME=\BlinkAppC__\ does work. I know it sounds weird. It makes me think about alignment issues in the FLASH... Then, I tried to run the demo further. I checked that I can run the blink and reverse-blink demos and that I can ping them with tos-deluge -p. Injecting an application with tos-deluge -i seems to be working. But the mote never reboots and executes the injected application (i.e., the burn script does not work). Is Deluge T2 supposed to be working on iris motes ? Does somebody already bumped into similar issues ? Thanks, Regards, yann -- Yann Le Corre Laboratory of Algorithmics, Cryptology and Security (LACS) FSTC/CSC UNIVERSITE DU LUXEMBOURG CAMPUS KIRCHBERG, E206 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg T: +352 46 66 44 5795 yann.leco...@uni.lu www.uni.lu www.uni.lu ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 and iris motes
Hi, It looks similar to what I have here. I (almost) gave up and I tried the xubuntu VMWare from tinyOS wiki. Everything seems to be working fine now. I can disseminate and execute. It seems that Deluge T2 has issues with ubuntu 11.10 and 12.04 LS. I would be glad to help to solve them if anybody could give me some clues. Regards, Yann On 07/10/2012 05:20 PM, Hamid Rafiei Karkvandi wrote: Hi, I have been having no success in using Deluge T2 with IRIS and MIB520. First I failed even to install Deluge correctly on Cygwin so I migrated to Ubuntu 12.04 LS and I installed the recent updated version of Tinyos. Deluge T2 runs on the mote, I inject the image and I read the flash successfully and even mine doesn't give the error you mentioned (is it base station or not ... ) but still after dissemination I can see other motes start to get the image and write it down on their flash (the green LED blinks fast) but after all no one reboots and execute the new image ... I kinda gave up on it, but if anyone has a similar experience and knows how to solve these issues with IRIS and Deluge T2, I appreciate ... Regards, Hamid Rafiei Karkvandi On Tue, Jul 10, 2012 at 7:40 AM, Yann Le Corre yann.leco...@uni.lu mailto:yann.leco...@uni.lu wrote: Hi All, I try to get Deluge T2 working on my Iris motes but with no success so far. Starting with only one mote connected to the PC with a mib520, I tried the following steps: 1. compile and install apps/test/deluge/Basestation 2. tos-deluge serial@/dev/ttyUSB1:57600 -p 0 == I can read the flash content, everything seems OK 3. compile and install apps/test/deluge/Blink == led0 is blinking 4. tos-deluge serial@/dev/ttyUSB1:57600 -p 0 == ERROR: Timeout. Is the node a Deluge T2 base station? My PC is running Ubuntu 11.10 with avr-gcc 4.63, avr binutils 2.22, nescc 1.3.3 and tinyOS tree from CVS. CFLAGS always contains -DDELUGE_BASE_STATION or -DDELUGE_LIGHT_BASE_STATION. After a lot of trials and errors, it appears that I can make deluge/Blink answer to the tos-deluge -p if I change the -DIDENT_APPNAME flag. Actually, what seems to matter is the length of the application name. For example -DIDENT_APPNAME=\BlinkAppC\ will not work while -DIDENT_APPNAME=\BlinkAppC__\ does work. I know it sounds weird. It makes me think about alignment issues in the FLASH... Then, I tried to run the demo further. I checked that I can run the blink and reverse-blink demos and that I can ping them with tos-deluge -p. Injecting an application with tos-deluge -i seems to be working. But the mote never reboots and executes the injected application (i.e., the burn script does not work). Is Deluge T2 supposed to be working on iris motes ? Does somebody already bumped into similar issues ? Thanks, Regards, yann -- Yann Le Corre Laboratory of Algorithmics, Cryptology and Security (LACS) FSTC/CSC UNIVERSITE DU LUXEMBOURG CAMPUS KIRCHBERG, E206 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg T: +352 46 66 44 5795 yann.leco...@uni.lu mailto:yann.leco...@uni.lu www.uni.lu http://www.uni.lu www.uni.lu http://www.uni.lu ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu mailto:Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Yann Le Corre Laboratory of Algorithmics, Cryptology and Security (LACS) FSTC/CSC UNIVERSITE DU LUXEMBOURG CAMPUS KIRCHBERG, E206 6, rue Richard Coudenhove-Kalergi L-1359 Luxembourg T: +352 46 66 44 5795 yann.leco...@uni.lu www.uni.lu www.uni.lu ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 and iris motes
Hi Guys, It's seems there is a bunch of deluge related problem recently, and altough I don't really know the source of your problems, Deluge T2 certainly works. I didn't use it on memsic motes for quite a long time (although I could test it on irises if you wish), but I've ported it to the motes our company manufactures, and recently I programmed about 150 motes with it (all of them in the same room). By the way, I'm using Arch linux, and the newest python2 package on it for tinyos python scripts, I never had any problem with the tos-deluge - mote connection. Debugging a deluge related problem is really painful, since it's quite complex protocol, handling awful lot of data. Some issues I had problems with: -TOSH_DATA_LENGTH _must_ be the same on all motes. If the receiver's TOSH_DATA_LENGTH is bigger than the sender's, the receiver fills the remaining data with garbage, and that will cause crc error in the bootloader. That means it will restart with the old image, redownload the new, reboots, detects the crc error and so on. -Deluge doesn't like if there's serious communication in the area. It really slows down the downloading of the image (from two minutes to fifteen-thirty), and worst of all, it also causes image crc errors (not sure why, but at first we could only reprogram about 50 of the 150 motes. Fortunately, we could disable almost all communication on the motes). -Image 0 is the golden image (1; 2 and 3 are general purpose images), but it's not well designed. You have to inject the golden image yourself, but at some point deluge will stop you to use it as the other images, and I think that point is the dissemination. Therefor, you have to inject it with serial on all motes (but I'm not sure, I didn't really cared this issue) -You also have to be extramly unfortunate, if you encounter a mote automaticly programs itself with golden image. Tosboot only incrases the gesture counter (which counts to 3, and when reaches 3, tosboot will program the golden image) if ther was some problem during copying a page from the external flash to the internal, but I never had such problem. It does not protect your mote from redownloading a crc error image again and again, which happens quite often however. Andris On Tue, Jul 10, 2012 at 4:54 PM, Yann Le Corre yann.leco...@uni.lu wrote: Hi, It looks similar to what I have here. I (almost) gave up and I tried the xubuntu VMWare from tinyOS wiki. Everything seems to be working fine now. I can disseminate and execute. It seems that Deluge T2 has issues with ubuntu 11.10 and 12.04 LS. I would be glad to help to solve them if anybody could give me some clues. Regards, Yann On 07/10/2012 05:20 PM, Hamid Rafiei Karkvandi wrote: Hi, I have been having no success in using Deluge T2 with IRIS and MIB520. First I failed even to install Deluge correctly on Cygwin so I migrated to Ubuntu 12.04 LS and I installed the recent updated version of Tinyos. Deluge T2 runs on the mote, I inject the image and I read the flash successfully and even mine doesn't give the error you mentioned (is it base station or not ... ) but still after dissemination I can see other motes start to get the image and write it down on their flash (the green LED blinks fast) but after all no one reboots and execute the new image ... I kinda gave up on it, but if anyone has a similar experience and knows how to solve these issues with IRIS and Deluge T2, I appreciate ... Regards, Hamid Rafiei Karkvandi On Tue, Jul 10, 2012 at 7:40 AM, Yann Le Corre yann.leco...@uni.lu wrote: Hi All, I try to get Deluge T2 working on my Iris motes but with no success so far. Starting with only one mote connected to the PC with a mib520, I tried the following steps: 1. compile and install apps/test/deluge/Basestation 2. tos-deluge serial@/dev/ttyUSB1:57600 -p 0 == I can read the flash content, everything seems OK 3. compile and install apps/test/deluge/Blink == led0 is blinking 4. tos-deluge serial@/dev/ttyUSB1:57600 -p 0 == ERROR: Timeout. Is the node a Deluge T2 base station? My PC is running Ubuntu 11.10 with avr-gcc 4.63, avr binutils 2.22, nescc 1.3.3 and tinyOS tree from CVS. CFLAGS always contains -DDELUGE_BASE_STATION or -DDELUGE_LIGHT_BASE_STATION. After a lot of trials and errors, it appears that I can make deluge/Blink answer to the tos-deluge -p if I change the -DIDENT_APPNAME flag. Actually, what seems to matter is the length of the application name. For example -DIDENT_APPNAME=\BlinkAppC\ will not work while -DIDENT_APPNAME=\BlinkAppC__\ does work. I know it sounds weird. It makes me think about alignment issues in the FLASH... Then, I tried to run the demo further. I checked that I can run the blink and reverse-blink demos and that I can ping them with tos-deluge -p. Injecting an application with tos-deluge -i seems to be working. But the mote never reboots and executes the injected application (i.e., the burn script does not
Re: [Tinyos-help] Deluge T2 problem
Hi everybody, I am getting the problem while compiling for Tossim [gags@gags RadioCountToLeds]$ make micaz sim [gags@gags RadioCountToLeds]$ make micaz sim mkdir -p simbuild/micaz mig python -target=micaz -DIDENT_APPNAME=\RadioCountToLed\ -DIDENT_USERNAME=\gags\ -DIDENT_HOSTNAME=\gags\ -DIDENT_USERHASH=0x7c2a7f59L -DIDENT_TIMESTAMP=0x4fbe9008L -DIDENT_UIDHASH=0x86ba7359L -python-classname=RadioCountMsg RadioCountToLeds.h radio_count_msg -o RadioCountMsg.py two source files specified (PLATFORM_MICAZ and IDENT_APPNAME=RadioCountToLed) failed to parse message file RadioCountToLeds.h make: *** [RadioCountMsg.py] Error 1 Regards, Gagan On Thu, May 24, 2012 at 10:36 PM, Hamid Rafiei Karkvandi hamid.raf...@gmail.com wrote: Hello Everyone, I have got a problem with Deluge protocol. After a tough day I successfully installed and configured Deluge using these scripts: ./Bootstrap ./configure and then make; make install for tools/tinyos/misc as the Tutorial suggested and everything successfully installed, I am working on IRIS platform. I installed the Basestation program on IRIS using make iris install,0 mib520,com3, successfully installed. but when I try to inject an image on this mote I get the following lines and errors: $ tos-deluge serial@com4:57600 -i 1 $TOSROOT/apps/Blink/build/iris/tos_image.xm l Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 441, in module inject(imgNum, sys.argv[4]) File /usr/local/bin/tos-deluge, line 316, in inject i = getIdent(imgNum) File /usr/local/bin/tos-deluge, line 276, in getIdent r = read(imgNum, DELUGE_IDENT_OFFSET, DELUGE_IDENT_SIZE) File /usr/local/bin/tos-deluge, line 180, in read reply = SerialReplyPacket(packet.data) AttributeError: 'NoneType' object has no attribute 'data' I cannot trace what the problem is, I have seen couple of other posts similar to mine but no satisfactory solution was found. I have updated my tinyOS to R5949 at the time. I appreciate if anyone can guide me through this, Regards, Hamid Rafiei Karkvandi ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 problem
hi, if you are using GCC in Linux, your gcc version may be 4.6, refer to http://sourceforge.net/tracker/?func=detailaid=3153727group_id=56288atid=480036for any suggestion. 2012/5/25 Gagandeep Singh gagandeep.s.dhin...@gmail.com Hi everybody, I am getting the problem while compiling for Tossim [gags@gags RadioCountToLeds]$ make micaz sim [gags@gags RadioCountToLeds]$ make micaz sim mkdir -p simbuild/micaz mig python -target=micaz -DIDENT_APPNAME=\RadioCountToLed\ -DIDENT_USERNAME=\gags\ -DIDENT_HOSTNAME=\gags\ -DIDENT_USERHASH=0x7c2a7f59L -DIDENT_TIMESTAMP=0x4fbe9008L -DIDENT_UIDHASH=0x86ba7359L -python-classname=RadioCountMsg RadioCountToLeds.h radio_count_msg -o RadioCountMsg.py two source files specified (PLATFORM_MICAZ and IDENT_APPNAME=RadioCountToLed) failed to parse message file RadioCountToLeds.h make: *** [RadioCountMsg.py] Error 1 Regards, Gagan On Thu, May 24, 2012 at 10:36 PM, Hamid Rafiei Karkvandi hamid.raf...@gmail.com wrote: Hello Everyone, I have got a problem with Deluge protocol. After a tough day I successfully installed and configured Deluge using these scripts: ./Bootstrap ./configure and then make; make install for tools/tinyos/misc as the Tutorial suggested and everything successfully installed, I am working on IRIS platform. I installed the Basestation program on IRIS using make iris install,0 mib520,com3, successfully installed. but when I try to inject an image on this mote I get the following lines and errors: $ tos-deluge serial@com4:57600 -i 1 $TOSROOT/apps/Blink/build/iris/tos_image.xm l Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 441, in module inject(imgNum, sys.argv[4]) File /usr/local/bin/tos-deluge, line 316, in inject i = getIdent(imgNum) File /usr/local/bin/tos-deluge, line 276, in getIdent r = read(imgNum, DELUGE_IDENT_OFFSET, DELUGE_IDENT_SIZE) File /usr/local/bin/tos-deluge, line 180, in read reply = SerialReplyPacket(packet.data) AttributeError: 'NoneType' object has no attribute 'data' I cannot trace what the problem is, I have seen couple of other posts similar to mine but no satisfactory solution was found. I have updated my tinyOS to R5949 at the time. I appreciate if anyone can guide me through this, Regards, Hamid Rafiei Karkvandi ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Cyan Phoenix ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 problem
Hi, I would like to add some new information to my post, it seems the error: - AttributeError: 'NoneType' object has no attribute 'data' is generated by Python engine. I am not that skilled in Python yet, but after doing some search, I found out that the problem should be mainly because getIdent() function in tos-deluge is not returning a valid value and it should be None which is not accepted by Python, I also tried to install the Blink in apps/tests/deluge/Blink by: $ ./burn mib520,com3 serial@com4:57600 iris it perfectly works as intended but when I try to ping the node: $ tos-deluge serial@com4:57600 -p 0 Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... -- Currently Executing: Prog Name: BlinkAppC UID: 0xA8160D04 Compiled On: Thu May 24 12:16:54 2012 Node ID: 1 Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 437, in module ping(imgNum) File /usr/local/bin/tos-deluge, line 353, in ping i = getIdent(imgNum) File /usr/local/bin/tos-deluge, line 276, in getIdent r = read(imgNum, DELUGE_IDENT_OFFSET, DELUGE_IDENT_SIZE) File /usr/local/bin/tos-deluge, line 180, in read reply = SerialReplyPacket(packet.data) AttributeError: 'NoneType' object has no attribute 'data' I appreciate your help beforehand, Regards, Hamid Rafiei Karkvandi On Thu, May 24, 2012 at 11:06 AM, Hamid Rafiei Karkvandi hamid.raf...@gmail.com wrote: Hello Everyone, I have got a problem with Deluge protocol. After a tough day I successfully installed and configured Deluge using these scripts: ./Bootstrap ./configure and then make; make install for tools/tinyos/misc as the Tutorial suggested and everything successfully installed, I am working on IRIS platform. I installed the Basestation program on IRIS using make iris install,0 mib520,com3, successfully installed. but when I try to inject an image on this mote I get the following lines and errors: $ tos-deluge serial@com4:57600 -i 1 $TOSROOT/apps/Blink/build/iris/tos_image.xm l Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 441, in module inject(imgNum, sys.argv[4]) File /usr/local/bin/tos-deluge, line 316, in inject i = getIdent(imgNum) File /usr/local/bin/tos-deluge, line 276, in getIdent r = read(imgNum, DELUGE_IDENT_OFFSET, DELUGE_IDENT_SIZE) File /usr/local/bin/tos-deluge, line 180, in read reply = SerialReplyPacket(packet.data) AttributeError: 'NoneType' object has no attribute 'data' I cannot trace what the problem is, I have seen couple of other posts similar to mine but no satisfactory solution was found. I have updated my tinyOS to R5949 at the time. I appreciate if anyone can guide me through this, Regards, Hamid Rafiei Karkvandi ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 problem
Ok, after some investigation I found out that when I am trying to ping or inject an image to the mote, the following error occurs in the read function of tos-deluge file: def read(imgNum, offset, length): r = [] sreqpkt = FMReqPacket((FM_CMD_READ, imgNum, offset, length, [])) hamtemp=0 while True: if sreqpkt.length SERIAL_DATA_LENGTH: sreqpkt.length = SERIAL_DATA_LENGTH if am.write(sreqpkt, FM_AMID): packet = am.read() reply = SerialReplyPacket(packet.data) if reply.error == ERROR_SUCCESS: r.extend(reply.data) else: r = None break else: r = None break sreqpkt.offset += sreqpkt.length if sreqpkt.offset = (offset + length): break sreqpkt.length = (offset + length) - sreqpkt.offset return r The problem is that in that While loop, first time that packet=am.read() is executed packet is valid, for the second time, still packet is received and valid, but for the third time, packet=am.read() returns None for packet, whcih later messes the reply=SerialReplyPacket(packet.data) because there is no data attribute. I have no idea why packet is not being received from am, I tried to increase the timeout of read function for am to 5 (packet=am.read(timeout=5) but still nothing was received, I appreciate if anyone can help, I really need to get Deluge on the IRIS mote to save hours later for programming the motes, Thanks, Hamid Rafiei Karkvandi On Thu, May 24, 2012 at 12:55 PM, Hamid Rafiei Karkvandi hamid.raf...@gmail.com wrote: Hi, I would like to add some new information to my post, it seems the error: - AttributeError: 'NoneType' object has no attribute 'data' is generated by Python engine. I am not that skilled in Python yet, but after doing some search, I found out that the problem should be mainly because getIdent() function in tos-deluge is not returning a valid value and it should be None which is not accepted by Python, I also tried to install the Blink in apps/tests/deluge/Blink by: $ ./burn mib520,com3 serial@com4:57600 iris it perfectly works as intended but when I try to ping the node: $ tos-deluge serial@com4:57600 -p 0 Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... -- Currently Executing: Prog Name: BlinkAppC UID: 0xA8160D04 Compiled On: Thu May 24 12:16:54 2012 Node ID: 1 Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 437, in module ping(imgNum) File /usr/local/bin/tos-deluge, line 353, in ping i = getIdent(imgNum) File /usr/local/bin/tos-deluge, line 276, in getIdent r = read(imgNum, DELUGE_IDENT_OFFSET, DELUGE_IDENT_SIZE) File /usr/local/bin/tos-deluge, line 180, in read reply = SerialReplyPacket(packet.data) AttributeError: 'NoneType' object has no attribute 'data' I appreciate your help beforehand, Regards, Hamid Rafiei Karkvandi On Thu, May 24, 2012 at 11:06 AM, Hamid Rafiei Karkvandi hamid.raf...@gmail.com wrote: Hello Everyone, I have got a problem with Deluge protocol. After a tough day I successfully installed and configured Deluge using these scripts: ./Bootstrap ./configure and then make; make install for tools/tinyos/misc as the Tutorial suggested and everything successfully installed, I am working on IRIS platform. I installed the Basestation program on IRIS using make iris install,0 mib520,com3, successfully installed. but when I try to inject an image on this mote I get the following lines and errors: $ tos-deluge serial@com4:57600 -i 1 $TOSROOT/apps/Blink/build/iris/tos_image.xm l Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 441, in module inject(imgNum, sys.argv[4]) File /usr/local/bin/tos-deluge, line 316, in inject i = getIdent(imgNum) File /usr/local/bin/tos-deluge, line 276, in getIdent r = read(imgNum, DELUGE_IDENT_OFFSET, DELUGE_IDENT_SIZE) File /usr/local/bin/tos-deluge, line 180, in read reply = SerialReplyPacket(packet.data) AttributeError: 'NoneType' object has no attribute 'data' I cannot trace what the problem is, I have seen couple of other posts similar to mine but no satisfactory solution was found. I have updated my tinyOS to R5949 at the time. I appreciate if anyone can guide me through this, Regards, Hamid Rafiei Karkvandi ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 Rollback Gesture on Iris
Hi Guys, I'm currently porting deluge to some of our platforms, and I think the rollback function isn't that easy as it should be based on the documentation. First of all, the golden image should be injected with tos-deluge serial -i 0 image xml. It can probably disseminated with -d, but I'm not sure. Second, the guesture counter is only incrased if there was a programming error (e.g. CRC error), pressing the reset button is not enough. Andris On Fri, Mar 9, 2012 at 6:24 PM, Augusto Soares soares.augus...@gmail.com wrote: Augusto Soares wrote: Hi Fabrice, i have the same problem as you, i'm using telosb mote. i also do the same thing by pressing the reset button for a few times but the mote doesn't rollback the golden image. Have you solved the problem? i have been searching the forums but i found nothing. Regards, Augusto Fabrice Dossin wrote: Hi, I have read the Deluge 2.0 manual and some posts on the mailing list. It said that 4/5 resets should take the mote back to the GoldenImage image. But when I try this on my Iris mote it stays on the last image (in my case selected from the basestation with tos-deluge serial@/dev/ttyUSB1:57600 -dr 1 command). I just see the leds blink 3 times before shutting down as usual. Has the rollback gesture changed for Deluge T2 or for Iris motes ? Kind regards, Fabrice Dossin ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- View this message in context: http://old.nabble.com/Deluge-T2-Rollback-Gesture-on-Iris-tp29395590p33473281.html Sent from the TinyOS - Help mailing list archive at Nabble.com. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 Rollback Gesture on Iris
Hi Fabrice, i have the same problem as you, i'm using telosb mote. i also do the same thing by pressing the reset button for a few times but the mote doesn't rollback the golden image. Have solved the problem? i have been searching the forums but i found nothing. Regards, Augusto Fabrice Dossin wrote: Hi, I have read the Deluge 2.0 manual and some posts on the mailing list. It said that 4/5 resets should take the mote back to the GoldenImage image. But when I try this on my Iris mote it stays on the last image (in my case selected from the basestation with tos-deluge serial@/dev/ttyUSB1:57600 -dr 1 command). I just see the leds blink 3 times before shutting down as usual. Has the rollback gesture changed for Deluge T2 or for Iris motes ? Kind regards, Fabrice Dossin ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- View this message in context: http://old.nabble.com/Deluge-T2-Rollback-Gesture-on-Iris-tp29395590p33473059.html Sent from the TinyOS - Help mailing list archive at Nabble.com. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 Rollback Gesture on Iris
Augusto Soares wrote: Hi Fabrice, i have the same problem as you, i'm using telosb mote. i also do the same thing by pressing the reset button for a few times but the mote doesn't rollback the golden image. Have you solved the problem? i have been searching the forums but i found nothing. Regards, Augusto Fabrice Dossin wrote: Hi, I have read the Deluge 2.0 manual and some posts on the mailing list. It said that 4/5 resets should take the mote back to the GoldenImage image. But when I try this on my Iris mote it stays on the last image (in my case selected from the basestation with tos-deluge serial@/dev/ttyUSB1:57600 -dr 1 command). I just see the leds blink 3 times before shutting down as usual. Has the rollback gesture changed for Deluge T2 or for Iris motes ? Kind regards, Fabrice Dossin ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- View this message in context: http://old.nabble.com/Deluge-T2-Rollback-Gesture-on-Iris-tp29395590p33473281.html Sent from the TinyOS - Help mailing list archive at Nabble.com. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge t2 Error: Timeout. Is the node a Deluge T2 base station?
Hi! Some questions: what version of tinyos are you using (latest SVN version should work properly)? Also note that USB MIB boards expose two USB ports (one of them is dedicated for reprogramming). -- Razvan ME On Mon, 16 Jan 2012, #YONG HUI RU DORANCE# wrote: Hi all, I am trying to run Deluge T2 Quick Start. I followed the steps given on: http://docs.tinyos.net/tinywiki/index.php/Deluge_T2 . In directory tinyos-2.x/tos/lib/tosboot, $ make micaz In directory tinyos-2.x/apps/tests/deluge/Blink, $ ./burn mib510,/dev/ttyS7 serial@/dev/ttyS7:57600 micaz After executing the steps above, I was met with the problem described below: = Upload the image == Flushing the serial port.. Checking of node is a Deluge T2 base station ... ERROR: Timeout. Is the node a Deluge T2 base station? The same error occurs when I try to carry out the section Reprogramming a network Injecting a new image. Please assist me on this if you have any idea what the problem could be. Thank you! Regards, Dorance Yong ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] deluge T2 problem
Can you please follow the instructions from here: http://tinyprod.net/razvanm/debian/ It compiles properly with them on my system. -- Razvan ME On Mon, Dec 5, 2011 at 6:00 PM, sadun silva silva.sa...@gmail.com wrote: hi, when i try to compile the GoldenImage it gives me the following error. tos/lib/net/Deluge/DelugePageTransferP.nc: In function `DelugePageTransferP__BlockWrite__writeDone': /opt/tinyos-main-read-only/tos/lib/net/Deluge/DelugePageTransferP.nc:455: Internal compiler error in gen_lowpart, at emit-rtl.c:1197 looks like a compiler issue. but i think i have the latest version which is the msp430-gcc-tinyos 3.2.3 do you know what is wrong here? thanks silva On Thu, Dec 1, 2011 at 1:54 PM, sadun silva silva.sa...@gmail.com wrote: thanks a lot! solved! i got it to work. i did not have automake installed on my system. silva On Thu, Dec 1, 2011 at 1:40 PM, sadun silva silva.sa...@gmail.comwrote: hi, Thanks a lot for the prompt reply. it is not the latest svn. But when i tried to follow the instructions (in the Deluge T2 wiki) with the latest version (after an svn checkout from googlecode) it gives the following set of errors. when i go to /tools type ./Bootstrap + aclocal ./Bootstrap: 1: aclocal: not found + set -x + cd platforms/mica/uisp + ./bootstrap ./bootstrap: 1: aclocal: not found ./bootstrap: 2: autoheader: not found ./bootstrap: 3: autoconf: not found ./bootstrap: 5: automake: not found + rm -f config.cache src/config.cache do you have any idea what is wrong here? thanks for the help silva On Wed, Nov 30, 2011 at 5:46 PM, Razvan Musaloiu-E. raz...@musaloiu.com wrote: Quick question: is the latest SVN? If not, can you try that? :-) -- Razvan ME On Wed, Nov 30, 2011 at 4:19 PM, sadun silva silva.sa...@gmail.comwrote: hi all, i'm trying to get deluge to work. i installed the base station program in /tests/deluge/BaseStation using make telosb install,0 bsl,/dev/ttyUSB0 this mote id is 0 it is connected to the USB after that i tried to execute tos-deluge serial@/dev/ttyUSB0:115200 -p 0 just to ping the mote. but it gives the following msg. File /usr/local/bin/tos-deluge, line 425, in module am = tos.AM() TypeError: __init__() takes exactly 2 arguments (1 given) can someone please help in this? am i doing something wrong here? i'm stuck in here for days now. thanks silva ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] deluge T2 problem
thanks a lot! solved! i got it to work. i did not have automake installed on my system. silva On Thu, Dec 1, 2011 at 1:40 PM, sadun silva silva.sa...@gmail.com wrote: hi, Thanks a lot for the prompt reply. it is not the latest svn. But when i tried to follow the instructions (in the Deluge T2 wiki) with the latest version (after an svn checkout from googlecode) it gives the following set of errors. when i go to /tools type ./Bootstrap + aclocal ./Bootstrap: 1: aclocal: not found + set -x + cd platforms/mica/uisp + ./bootstrap ./bootstrap: 1: aclocal: not found ./bootstrap: 2: autoheader: not found ./bootstrap: 3: autoconf: not found ./bootstrap: 5: automake: not found + rm -f config.cache src/config.cache do you have any idea what is wrong here? thanks for the help silva On Wed, Nov 30, 2011 at 5:46 PM, Razvan Musaloiu-E. raz...@musaloiu.comwrote: Quick question: is the latest SVN? If not, can you try that? :-) -- Razvan ME On Wed, Nov 30, 2011 at 4:19 PM, sadun silva silva.sa...@gmail.comwrote: hi all, i'm trying to get deluge to work. i installed the base station program in /tests/deluge/BaseStation using make telosb install,0 bsl,/dev/ttyUSB0 this mote id is 0 it is connected to the USB after that i tried to execute tos-deluge serial@/dev/ttyUSB0:115200 -p 0 just to ping the mote. but it gives the following msg. File /usr/local/bin/tos-deluge, line 425, in module am = tos.AM() TypeError: __init__() takes exactly 2 arguments (1 given) can someone please help in this? am i doing something wrong here? i'm stuck in here for days now. thanks silva ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] deluge T2 problem
hi, Thanks a lot for the prompt reply. it is not the latest svn. But when i tried to follow the instructions (in the Deluge T2 wiki) with the latest version (after an svn checkout from googlecode) it gives the following set of errors. when i go to /tools type ./Bootstrap + aclocal ./Bootstrap: 1: aclocal: not found + set -x + cd platforms/mica/uisp + ./bootstrap ./bootstrap: 1: aclocal: not found ./bootstrap: 2: autoheader: not found ./bootstrap: 3: autoconf: not found ./bootstrap: 5: automake: not found + rm -f config.cache src/config.cache do you have any idea what is wrong here? thanks for the help silva On Wed, Nov 30, 2011 at 5:46 PM, Razvan Musaloiu-E. raz...@musaloiu.comwrote: Quick question: is the latest SVN? If not, can you try that? :-) -- Razvan ME On Wed, Nov 30, 2011 at 4:19 PM, sadun silva silva.sa...@gmail.comwrote: hi all, i'm trying to get deluge to work. i installed the base station program in /tests/deluge/BaseStation using make telosb install,0 bsl,/dev/ttyUSB0 this mote id is 0 it is connected to the USB after that i tried to execute tos-deluge serial@/dev/ttyUSB0:115200 -p 0 just to ping the mote. but it gives the following msg. File /usr/local/bin/tos-deluge, line 425, in module am = tos.AM() TypeError: __init__() takes exactly 2 arguments (1 given) can someone please help in this? am i doing something wrong here? i'm stuck in here for days now. thanks silva ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] deluge T2 problem
hi, when i try to compile the GoldenImage it gives me the following error. tos/lib/net/Deluge/DelugePageTransferP.nc: In function `DelugePageTransferP__BlockWrite__writeDone': /opt/tinyos-main-read-only/tos/lib/net/Deluge/DelugePageTransferP.nc:455: Internal compiler error in gen_lowpart, at emit-rtl.c:1197 looks like a compiler issue. but i think i have the latest version which is the msp430-gcc-tinyos 3.2.3 do you know what is wrong here? thanks silva On Thu, Dec 1, 2011 at 1:54 PM, sadun silva silva.sa...@gmail.com wrote: thanks a lot! solved! i got it to work. i did not have automake installed on my system. silva On Thu, Dec 1, 2011 at 1:40 PM, sadun silva silva.sa...@gmail.com wrote: hi, Thanks a lot for the prompt reply. it is not the latest svn. But when i tried to follow the instructions (in the Deluge T2 wiki) with the latest version (after an svn checkout from googlecode) it gives the following set of errors. when i go to /tools type ./Bootstrap + aclocal ./Bootstrap: 1: aclocal: not found + set -x + cd platforms/mica/uisp + ./bootstrap ./bootstrap: 1: aclocal: not found ./bootstrap: 2: autoheader: not found ./bootstrap: 3: autoconf: not found ./bootstrap: 5: automake: not found + rm -f config.cache src/config.cache do you have any idea what is wrong here? thanks for the help silva On Wed, Nov 30, 2011 at 5:46 PM, Razvan Musaloiu-E. raz...@musaloiu.comwrote: Quick question: is the latest SVN? If not, can you try that? :-) -- Razvan ME On Wed, Nov 30, 2011 at 4:19 PM, sadun silva silva.sa...@gmail.comwrote: hi all, i'm trying to get deluge to work. i installed the base station program in /tests/deluge/BaseStation using make telosb install,0 bsl,/dev/ttyUSB0 this mote id is 0 it is connected to the USB after that i tried to execute tos-deluge serial@/dev/ttyUSB0:115200 -p 0 just to ping the mote. but it gives the following msg. File /usr/local/bin/tos-deluge, line 425, in module am = tos.AM() TypeError: __init__() takes exactly 2 arguments (1 given) can someone please help in this? am i doing something wrong here? i'm stuck in here for days now. thanks silva ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] deluge T2 problem
Quick question: is the latest SVN? If not, can you try that? :-) -- Razvan ME On Wed, Nov 30, 2011 at 4:19 PM, sadun silva silva.sa...@gmail.com wrote: hi all, i'm trying to get deluge to work. i installed the base station program in /tests/deluge/BaseStation using make telosb install,0 bsl,/dev/ttyUSB0 this mote id is 0 it is connected to the USB after that i tried to execute tos-deluge serial@/dev/ttyUSB0:115200 -p 0 just to ping the mote. but it gives the following msg. File /usr/local/bin/tos-deluge, line 425, in module am = tos.AM() TypeError: __init__() takes exactly 2 arguments (1 given) can someone please help in this? am i doing something wrong here? i'm stuck in here for days now. thanks silva ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 on ubuntu Lucid Lynx
Hi! What errors do you get? Can you try the latest SVN version (that's the one that the wiki is usually suppose to document)? -- Razvan ME On Sat, 10 Sep 2011, Rafael de Oliveira Costa wrote: Hi, I've installed the tinyos-2.1.1 from http://tinyos.stanford.edu/ to ubuntu Lucid Lynx and i want to use Deluge for reprogramming micaz motes. I'm following Deluge T2 Tutorial ( http://docs.tinyos.net/tinywiki/index.php/Deluge_T2) but occurs errors when i execute some scripts. Someone has successfully follow this tutorial ? Rafael de Oliveira Costa M.Sc. Student PPGI / DCC - iNCE/ UFRJ Rio de Janeiro, RJ, Brazil The first step to getting the things you want out of life is this : decide what you want Ben Stein ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 + netbsl
I've tried it in another computer and now it works: $ CFLAGS=-DDELUGE_BASESTATION make telosb install netbsl,192.168.1.100:10001 First it loads the tosboot and then loads the main program without erase memory. * I've the netbsl.extra file modified on line #29: $(BOOTLOADER) - $(BOOTLOADER_IMG). __ El 14/01/2011 16:52, José A. Tarifa escribió: Hi to all! I've a Tmote Connect unit, and a Tmote Sky mote connected to it. I can install a normal program through netbsl command. For example, the Blink app (previously compiled): [cygwin] $ make telosb reinstall netbsl,192.168.1.100:10001 cp build/telosb/main.ihex build/telosb/main.ihex.out installing telosb binary using netbsl /opt/tinyos-2.x/support/make/msp/netbsl 192.168.1.100:10001 build/telosb/main.ihex.out --telosb -r -e -I -p Using mote on port /dev/ttyUSB0. Mass erase. Invoking BSL. BSL version 1.61, MCU device id f16c. Changing to 38400 baud. Program image /tmp/_dev_ttyUSB0, 2648 bytes. Invoking BSL. BSL version 1.61, MCU device id f16c. Changing to 38400 baud. Program. Programmed 2680 bytes. Reset rm -f build/telosb/main.exe.out build/telosb/main.ihex.out [cygwin] It works OK. Then, I try the test/deluge/Blink app in a mote which is connected directly to the USB (COM15) of my PC: [cygwin] $ CFLAGS=-DDELUGE_BASESTATION make telosb reinstall bsl,14 cp build/telosb/main.ihex build/telosb/main.ihex.out installing telosb bootloader using bsl tos-bsl --telosb -c 14 -r -e -I -p C:/cygwin/opt/tinyos-2.x/tos/lib/tosboot/build/telosb/main.ihex MSP430 Bootstrap Loader Version: 1.39-telos-8 Mass Erase... Transmit default password ... Invoking BSL... Transmit default password ... Current bootstrap loader version: 1.61 (Device ID: f16c) Changing baudrate to 38400 ... Program ... 2118 bytes programmed. Reset device ... installing telosb binary using bsl (without mass erase) tos-bsl --telosb -c 14 -r -I -p build/telosb/main.ihex.out MSP430 Bootstrap Loader Version: 1.39-telos-8 Invoking BSL... Transmit default password ... Current bootstrap loader version: 1.61 (Device ID: f16c) Changing baudrate to 38400 ... Program ... 39616 bytes programmed. Reset device ... rm -f build/telosb/main.exe.out build/telosb/main.ihex.out [cygwin] It works OK too. (The three leds are on and then only the red one blinks). I want to program (via Ethernet) a mote conected to the Tmote Connect device. [cygwin] $ CFLAGS=-DDELUGE_BASESTATION make telosb reinstall netbsl,192.168.1.100:10001 cp build/telosb/main.ihex build/telosb/main.ihex.out installing telosb bootloader using netbsl /opt/tinyos-2.x/support/make/msp/netbsl 192.168.1.100:10001 C:/cygwin/opt/tinyos-2.x/tos/lib/tosboot/build/tel osb/main.ihex --telosb -r -e -I -p Using mote on port /dev/ttyUSB0. Mass erase. Invoking BSL. BSL version 1.61, MCU device id f16c. Changing to 38400 baud. Program image /tmp/_dev_ttyUSB0, 2118 bytes. Invoking BSL. BSL version 1.61, MCU device id f16c. Changing to 38400 baud. Program. Programmed 2118 bytes. Reset installing telosb binary using netbsl (without mass erase) /opt/tinyos-2.x/support/make/msp/netbsl 192.168.1.100:10001 build/telosb/main.ihex.out --telosb -r -I -p Using mote on port /dev/ttyUSB0. Program image /tmp/_dev_ttyUSB0, 39584 bytes. Invoking BSL. BSL version 1.61, MCU device id f16c. Changing to 38400 baud. Program. Programmed 39616 bytes. Reset rm -f build/telosb/main.exe.out build/telosb/main.ihex.out [cygwin] When I reboot the mote (by pressing the RESET button), the three leds are on, but afterwards no led blinks. Is there any way to program a remote sensor (via Tmote Connect) using Deluge protocol? Thank you very much!! Regards, Jose A. P.D. netbsl and netbsl.extra files I'm using: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20110107/9e927f2d/attachment.obj https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20110107/9e927f2d/attachment-0001.obj I've changed line#29 of netbsl.extra from $(BOOTLOADER) -- $(BOOTLOADER_IMG) -- Jose A. Seville, Spain ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help -- Jose A. Seville, Spain attachment: jostargal.vcf___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 app maximum size
Hi Jose, This is not the problem of Deluge, but the fact that Tmote Sky Flash is only 48K. When you included the DelugeC component, it bumped up the ROM usage. Thank you Mike On Dec 31, 2010, at 9:54 AM, jostar...@alum.us.es jostar...@alum.us.es wrote: Hi all! I'm working with Deluge T2 in Tmote Sky (telosb) under Cygwin. I wonder what's the maximum size of a tos image that work OK with Deluge dissemination. I've an app with 38000B in ROM and 4000B in RAM, and when I compile (make telosb) with DelugeC component, I get memory problems (overlapping memory areas). The Tmote Sky Flash memory I think is 48K... Thanks!! Regards, Jose A. ╔══╗ ║José A. Tarifa Galisteo ║ ║ Estudiante Ingeniería de Telecomunicación ║ Escuela Superior de Ingenieros - U. Sevilla ║ http://alumno.us.es/j/jostargal/ ╚══╝ ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge on new platform
I'm working on Deluge T2 since a few days ago... and I don't understand it at all ... Have you tested the burn script included in apps\tests\deluge\Blink ? You can open it and see the different steps. Regards, Jose A. - Mensaje original - De: Devasenapathy s.devasenapa...@student.tudelft.nl Fecha: Jueves, Diciembre 30, 2010 8:59 ombr Asunto: [Tinyos-help] Deluge on new platform A: tinyos-help@millennium.berkeley.edu Hello All I have an exact replica of a tmote-sky on which I need to use deluge. I have the following issue with this: I followed the instructions in the Deluge T2 page: http://docs.tinyos.net/index.php/Deluge_T2 as is and see that the expected response is seen on tmotes. So I know that my toolchain and environment are correct. However, I do not see this on the tmote replica. A make telosb install.1 in $TOSROOT/apps/tests/deluge/Blink executes without errors, the startupsequence leds glow as expected, but the periodic LED blink after this is not seen. I tried fusing the code for a basestation with CFLAGS=- DDELUGE_BASESTATION to see if there is a response to the tos- deluge ping command. The response is: Flushing the serial port.. Checking if node is a Deluge T2 base station ... ERROR: Timeout. Is the node a Deluge T2 base station? I) I tried splitting the commands that follow as a result of the make telosb reinstall command : tos-set-symbols --objcopy msp430-objcopy --objdump msp430- objdump --target ihex build/telosb/main.ihex build/telosb/main.ihex.out-1 TOS_NODE_ID=1 ActiveMessageAddressC__addr=1 tos-bsl --telosb -c /dev/ttyUSB0 -r -e -I -p /opt/tinyos- 2.1.1/tos/lib/tosboot/build/telosb/main.ihex tos-bsl --telosb -c /dev/ttyUSB0 -r -I -p build/telosb/main.ihex.out-1 But this time included option --force-BSL-download into 1)the first tos-bsl commands 2) the second one and 3) both commands. There was no change in operation. II) I tried the second tos-bsl command with the -e option that does a mass erase before reprogramming the mote. With this I see the periodic blink. With the basestation cflags, my mote can work perfectly as a basestation and can program tmotes over the air. As a non-basestation mote, I see the indication that a page has been received (second led blinks when the page is received) but the switch between images does not happen. This is obvious because the bootloader has been erased . III) I tried the tos-bsl commands with a -D option and see that the bootloader and the blink application get loaded at different memory locations. I have come to the conclusion that the bootloader and the blink application get fused onto the mote at different memory locations but cannot work together. Can anyone help me with this ? Any help would be appreciated. Thanks, Devasenapathy ╔══╗ ║José A. Tarifa Galisteo ║ ║ Estudiante Ingeniería de Telecomunicación ║ Escuela Superior de Ingenieros - U. Sevilla ║ http://alumno.us.es/j/jostargal/ ╚══╝ ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge sample
$TOSROOT is a shell variable pointing to the root of your TinyOS directory. You probably have already set it up during installation. Mike On Oct 31, 2010, at 12:28 PM, Puya Ghazizadeh wrote: I have tinyos 2.1.0. I want to run Deluge sample on iris motes. Base on manual in http://docs.tinyos.net/index.php/Deluge_T2 first step is: % cd $TOSROOT/tools % ./Bootstrap ... % ./configure ... % cd tinyos/misc % make ; make install but I can find $TOSROOT folder in my tinyos folder! Where is that folder? Thanks, Puya ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge Post-Dissemination Reboot Problem
Hi, Try out the sequence of commands given below. This is what I use. Also it is not clear which program you are using to test dissemination. 1. cd $TOSROOT/apps/tests/deluge/GoldenImage 2. make telosb install,52 bsl,/dev/ttyUSB1-with CFLAGS+=-DELUGE_BASESTATION 3. make telosb install,XXX bsl,/dev/ttyUSB2-with CFLAGS+=-DELUGE_LIGHT_BASESTATION Now all the nodes have Golden image in them with proper ids. Next the application program, say Blink has to be disseminated to all the nodes from the Basestation. It is not required that they be connected to the same system. They just need to be powered. One important thing here is that the application code must contain deluge. Take a look at BlinkAppC.nc. cd $TOSROOT/apps/tests/deluge/Blink Take a look at BlinkAppC.nc. 4. Include CFLAGS+=-DELUGE_LIGHT_BASESTATION in Makefile. This is because you have to first inject to BS and disseminate the code specific to non-BS motes. 5. /usr/bin/tos-deluge /dev/ttyUSB0 telosb -i 1 build/telosb/tos_image.xml 6. /usr/bin/tos-deluge /dev/ttyUSB0 telosb -d 1 - this command will only disseminated the code to non-BS motes. You can also use /usr/bin/tos-deluge /dev/ttyUSB0 telosb -dr 1 - which will disseminate the code and all the non-BS motes will reboot with this and so you should be able to see the nodes blinking. 7. Include CFLAGS+=-DELUGE_BASESTATION in the Makefile. 8. /usr/bin/tos-deluge /dev/ttyUSB0 telosb -i 1 build/telosb/tos_image.xml 9. Here you should be a little careful. If you used command in step 6, then 10. /usr/bin/tos-deluge /dev/ttyUSB0 telosb -dr 1 - we only disseminated the code before so now reboot the motes to run blink prog. 11. /usr/bin/tos-deluge /dev/ttyUSB0 telosb -r 1 - reboot BS with blink. else, 10. The non-BS motes are already in blink prog so just boot BS with the same. /usr/bin/tos-deluge /dev/ttyUSB0 telosb -r 1 I suggest you use the second command in step 6 so that you can straight away solve your problem of not being able to reboot with new code. From: eced...@ece.iisc.ernet.in From my experience with deluge, if you opt for 'disseminate and reboot' option, the program gets disseminated and all the nodes now reboot with this code. You can verify this by ping command and find the name in the Currently Executing: part. Could you tell me the exact sequence of the commands that you are using here? And also a flag in the Makefile has to be changed for basestation and non-basestation motes. Hi, First, thanks for your help. This is the method I have used: cd to tosboot directory make telosb cd $TOSROOT/apps/tests/deluge/Basestation make telosb install,52 bsl,/dev/ttyUSB1 tos-deluge serial@/dev/ttyUSB1:115200 -i 0 build/telosb/tos_image.xml cd $TOSROOT/apps/tests/deluge/GoldenImage make telosb install,XXX bsl,/dev/ttyUSB2 tos-deluge serial@/dev/ttyUSB2:115200 -i 0 build/telosb/tos_image.xml Repeat previous two commands for each node. To test dissemination: make telosb tos-deluge serial@/dev/ttyUSB1:115200 -i 1 build/telosb/tos_image.xml tos-deluge serial@/dev/ttyUSB1:115200 -dr 1 Result with CVS version: Code disseminates, nodes reprograms, node requires tap on reset button to start up. Result with new version: No code dissemination occurs: no nodes overhear data exchange. The main problem I would really like to solve, even if I have to code it myself, is to have the nodes properly reset at the end so that they do not need to be reset using the button. I'm assuming that Basestation and GoldenImage do not require CFLAGS+=-DELUGE_LIGHT_BASESTATION or whatever to be included on the command line since this appears in the Makefile. Any help appreciated! -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. --Deeksha -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge Post-Dissemination Reboot Problem
From: eced...@ece.iisc.ernet.in From my experience with deluge, if you opt for 'disseminate and reboot' option, the program gets disseminated and all the nodes now reboot with this code. You can verify this by ping command and find the name in the Currently Executing: part. Could you tell me the exact sequence of the commands that you are using here? And also a flag in the Makefile has to be changed for basestation and non-basestation motes. Hi, First, thanks for your help. This is the method I have used: cd to tosboot directory make telosb cd $TOSROOT/apps/tests/deluge/Basestation make telosb install,52 bsl,/dev/ttyUSB1 tos-deluge serial@/dev/ttyUSB1:115200 -i 0 build/telosb/tos_image.xml cd $TOSROOT/apps/tests/deluge/GoldenImage make telosb install,XXX bsl,/dev/ttyUSB2 tos-deluge serial@/dev/ttyUSB2:115200 -i 0 build/telosb/tos_image.xml Repeat previous two commands for each node. To test dissemination: make telosb tos-deluge serial@/dev/ttyUSB1:115200 -i 1 build/telosb/tos_image.xml tos-deluge serial@/dev/ttyUSB1:115200 -dr 1 Result with CVS version: Code disseminates, nodes reprograms, node requires tap on reset button to start up. Result with new version: No code dissemination occurs: no nodes overhear data exchange. The main problem I would really like to solve, even if I have to code it myself, is to have the nodes properly reset at the end so that they do not need to be reset using the button. I'm assuming that Basestation and GoldenImage do not require CFLAGS+=-DELUGE_LIGHT_BASESTATION or whatever to be included on the command line since this appears in the Makefile. Any help appreciated! ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge Post-Dissemination Reboot Problem
I am assuming you are using MSP430. Have you tried the latest version from the official TinyOS SVN repository? Do example Deluge apps in tinyos-2.x/apps/tests/deluge (such as the burn script in tinyos-2.x/apps/tests/deluge/Blink) work for you? Thanks Mike On Oct 20, 2010, at 3:49 PM, Sensors Project wrote: Hi, I am using TinyOS 2.1 from the CVS. I have a problem with the Deluge reprogramming system. I have Deluge working OK, with a basestation and a number of nodes. The code correctly disseminates around the network, and appears to flash to the nodes as indicated by the fast flashing Leds. However, once this process is complete, the Leds fade down and then the node needs to be reset before it will run the program. If I reset the node manually, it will however successfully load the program... At first I wondered if this was a result of the reboot mechanism built into Deluge that sets up the watchdog timer of the MSP430 in order to force a reset. But when I tested this mechanism in my own code (which uses the same Deluge boot program, but obviously no change to the program at the reboot), the reset is successful. Is anybody aware of a reason for this? Do I need to consider an alternative reboot mechanism in the netprog_reboot() function? Or is this function not being called at all? (i.e. the reprogramming is occurring outside of the bootloader and no reboot even occurred to begin with.) Or is this a problem with the bootloader itself, in that it reprograms OK but is then unable to load the new program? Any help would be appreciated, otherwise I face another 10 hours of walking around manually resetting nodes... ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge Post-Dissemination Reboot Problem
Subject: Re: [Tinyos-help] Deluge Post-Dissemination Reboot Problem From: clia...@cs.jhu.edu I am assuming you are using MSP430. Have you tried the latest version from the official TinyOS SVN repository? Do example Deluge apps in tinyos-2.x/apps/tests/deluge (such as the burn script in tinyos-2.x/apps/tests/deluge/Blink) work for you? Thanks for this suggestion, but it isn't working for me - in fact it is worse... Last time I checked these scripts, they do exactly the same thing that I am doing anyway. Unless preparation is not building the code, installing it on the nodes, then ensuring each node has a fallback image in slot 0 -- and programming the network is not building the application, writing it into the basestation's slot 1, then issuing a disseminate-and-reboot command? I just obtained the SVN copy from Google code, rebuilt tosboot, installed Basestation on the PC node, put the code also into slot 0 and finally installed GoldenImage on all other nodes - with the code also flashed into slot 0. I assume this means all the code involved is updated to the latest version. This setup allows me to upload code into slot 1 of the basestation, but issuing the dissemination or 'disseminate and reboot' command results in zero network traffic and no flashing LEDs. (The command is accepted by the base, and the green LED lights momentarily. The code is written correctly to the basestation, since a ping shows this.) Trying to reset the nodes to their golden images using the reset gesture failed on some nodes due to the voltage detection problem on these nodes, so I modified both tosboot and the NetProg programs to remove the detection code (forcing the return of TRUE in the okToProgram functions etc). I Rebuilt tosboot and repeated all the steps again: same result, except the reset gestures now work. So I guess I'm back to square one, or possibly square minus one ;-) I'm tempted to switch back to my CVS checkout, since that seemed to work. But I still don't understand why the nodes will not reset properly after a disseminate-and-reprogram command. Presumably if this was fixed, some problem was found. Anybody know what? Could it have been a failure to reset the WDT in certain circumstances or perhaps more than one method to get a software reset? If somebody can give me a hint where in the code the actual reprogramming occurs in this scenario, I can investigate further. Is it in tosboot, or is it part of Deluge? I can then try to trace the problem and possibly force the node to reboot with different code. I see some code that interacts with flash before calling netprog_reboot(), but I'm unsure if this is the end of the problem. Some other forums suggest the WDT reset can result in infinite resets if the WDT is not disabled immediately on reboot. The suggestions for a replacement seem to be either writing an incorrect flash password or disabling interrupts followed by a program branch to zero. Any ideas or suggestions? ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge Post-Dissemination Reboot Problem
Hi, From my experience with deluge, if you opt for 'disseminate and reboot' option, the program gets disseminated and all the nodes now reboot with this code in the current working direc Hi, I am using TinyOS 2.1 from the CVS. I have a problem with the Deluge reprogramming system. I have Deluge working OK, with a basestation and a number of nodes. The code correctly disseminates around the network, and appears to flash to the nodes as indicated by the fast flashing Leds. However, once this process is complete, the Leds fade down and then the node needs to be reset before it will run the program. If I reset the node manually, it will however successfully load the program... At first I wondered if this was a result of the reboot mechanism built into Deluge that sets up the watchdog timer of the MSP430 in order to force a reset. But when I tested this mechanism in my own code (which uses the same Deluge boot program, but obviously no change to the program at the reboot), the reset is successful. Is anybody aware of a reason for this? Do I need to consider an alternative reboot mechanism in the netprog_reboot() function? Or is this function not being called at all? (i.e. the reprogramming is occurring outside of the bootloader and no reboot even occurred to begin with.) Or is this a problem with the bootloader itself, in that it reprograms OK but is then unable to load the new program? Any help would be appreciated, otherwise I face another 10 hours of walking around manually resetting nodes... -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help --Deeksha -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 with CTP
2010/10/19 白惠文 lancey...@hotmail.com: Can someone tell me whether Deluge T2 works correctly with CTP in tinyos-2.1 now? I'm using the most recent tinyos from CVS. However, I still observe weird behaviors when using Deluge with CTP. I know there were bugs before, but they should have been fixed. If someone is currently using Deluge + CTP, I'll appreciate it if you would tell me about your experience. Please use the version in Google code (SVN). - om_p ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 ERROR: Unable to erase the flash volume
I need to correct something. I realized that switching to another USB port was not the real reason that erasing worked. It worked because the node reset after being plugged in to another USB port. Now I'm still having the same erasing error as mentioned before. However, it start to work again if I press the reset button on the node. Anyone can think of an explanation? I have another problem with Deluge though. The tutorial says TOSBoot installs the Golden Image when the count of repeated resets exceeds a specified threshold. I tried this (resetting 6 times. Golden Image has been downloaded via serial port) but it didn't work. Can someone tell me what the threshold is? BTW, I'm using TelosB with the most recent tinyos version from CVS. Thanks, Lan From: lancey...@hotmail.com To: tinyos-help@millennium.berkeley.edu Date: Sat, 2 Oct 2010 11:21:07 +0800 Subject: [Tinyos-help] Deluge T2 ERROR: Unable to erase the flash volume Hi, I'm having some trouble with Deluge T2. When I try to erase or reprogram some already programmed flash volume on the basestation node, it says ERROR: Unable to erase the flash volume error: 1 data: [ ]. After debugging tos-deluge, I found that this error rooted in handleResponse function in tos-deluge. The packet type I got is 83. It seems 100 should be the correct result. Does anyone know what might went wrong? The other functionalities of deluge worked fine with a 3-node network. I can disseminate multiple programs to the network, and let the nodes reboot to any program. I am using the most recent tinyos version from CVS. Thanks in advance for your help. Lan ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 ERROR: Unable to erase the flash volume
What mote platform are you using? Mike On Oct 1, 2010, at 11:21 PM, 白惠文 wrote: Hi, I'm having some trouble with Deluge T2. When I try to erase or reprogram some already programmed flash volume on the basestation node, it says ERROR: Unable to erase the flash volume error: 1 data: [ ]. After debugging tos-deluge, I found that this error rooted in handleResponse function in tos-deluge. The packet type I got is 83. It seems 100 should be the correct result. Does anyone know what might went wrong? The other functionalities of deluge worked fine with a 3-node network. I can disseminate multiple programs to the network, and let the nodes reboot to any program. I am using the most recent tinyos version from CVS. Thanks in advance for your help. Lan ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 strange boot behavior
I've committed the fix. Thanks, Fabrice.
Janos
On Tue, Aug 24, 2010 at 10:40 AM, Fabrice Dossin
fabrice.dos...@gmail.com wrote:
Hi,
Ok, I have finally found it (bug report) !
The problem was into Deluge initialization process. One of the first
task that Deluge does is to check if the images are valid.
It is checked by computing the CRC of each page and comparing it to
the transmitted CRCs.
In DelugeMetadataP module, on line 127, there is a call to
BlockRead.computeCrc.
call BlockRead.computeCrc[currentVolume](calcPageAddr(),
DELUGE_BYTES_PER_PAGE, 0);
This call was returning an EINVAL error and without any error code
verification the Deluge module was just stopped into the CRC check
loop and storageReady event was never sent, neither the radio
initialized.
The EINVAL is caused by the calcPageAddr() in the same module on line 75 :
uint32_t calcPageAddr()
{
return DELUGE_IDENT_SIZE + DELUGE_CRC_BLOCK_SIZE + currentPage *
DELUGE_BYTES_PER_PAGE;
}
The calculation of this sum is cast to an Integer since
DELUGE_BYTES_PER_PAGE is an integer.
When my current page equal to 30, there is an integer overflow and the
method returns 0x82E0 instead of 0x82E0.
A working fix for this could be casting DELUGE_BYTES_PER_PAGE to
uint32_t but there is maybe a cleaner fix (I am kind a beginner in C
and embedded systems).
uint32_t calcPageAddr()
{
return DELUGE_IDENT_SIZE + DELUGE_CRC_BLOCK_SIZE + currentPage *
(uint32_t)DELUGE_BYTES_PER_PAGE;
}
Regards,
Fabrice Dossin
On 23 August 2010 10:14, Fabrice Dossin fabrice.dos...@gmail.com wrote:
Yes, it is. As a proof when I flash my app on the mote as the golden image
it works like a charm...
I just need this to link it to my app, no ?
components DelugeC;
DelugeC.Leds - LedsC;
Regards,
Fabrice
On 21 August 2010 03:33, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote:
Hi,
Is your Blink app wired to DelugeC component?
Mike
On Aug 20, 2010, at 10:32 AM, Fabrice Dossin wrote:
Hi,
I am currently investigating for integrating Deluge T2 into my app.
I have a strange behavior :
When I program the motes with my program as the golden image it does boot
correctly and I can propagate a Blink image or another to the mesh.
But when I flash the mote with Blink and propagate my app trough the air,
my app never start...
The Boot.booted event is sent but I never receive the startDone event
from ActiveMessageC that is automatically started by Deluge.
The program is blocked somewhere between these.
If I manually activate ActiveMessage, Deluge never take my propagated
images so it should be freezed somewhere into the deluge initialization
process.
Does someone have a clue for me on where to search ?
I am developing on IRIS motes.
Kind regards,
Fabrice
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 strange boot behavior
Hi,
Ok, I have finally found it (bug report) !
The problem was into Deluge initialization process. One of the first
task that Deluge does is to check if the images are valid.
It is checked by computing the CRC of each page and comparing it to
the transmitted CRCs.
In DelugeMetadataP module, on line 127, there is a call to
BlockRead.computeCrc.
call BlockRead.computeCrc[currentVolume](calcPageAddr(),
DELUGE_BYTES_PER_PAGE, 0);
This call was returning an EINVAL error and without any error code
verification the Deluge module was just stopped into the CRC check
loop and storageReady event was never sent, neither the radio
initialized.
The EINVAL is caused by the calcPageAddr() in the same module on line 75 :
uint32_t calcPageAddr()
{
return DELUGE_IDENT_SIZE + DELUGE_CRC_BLOCK_SIZE + currentPage *
DELUGE_BYTES_PER_PAGE;
}
The calculation of this sum is cast to an Integer since
DELUGE_BYTES_PER_PAGE is an integer.
When my current page equal to 30, there is an integer overflow and the
method returns 0x82E0 instead of 0x82E0.
A working fix for this could be casting DELUGE_BYTES_PER_PAGE to
uint32_t but there is maybe a cleaner fix (I am kind a beginner in C
and embedded systems).
uint32_t calcPageAddr()
{
return DELUGE_IDENT_SIZE + DELUGE_CRC_BLOCK_SIZE + currentPage *
(uint32_t)DELUGE_BYTES_PER_PAGE;
}
Regards,
Fabrice Dossin
On 23 August 2010 10:14, Fabrice Dossin fabrice.dos...@gmail.com wrote:
Yes, it is. As a proof when I flash my app on the mote as the golden image it
works like a charm...
I just need this to link it to my app, no ?
components DelugeC;
DelugeC.Leds - LedsC;
Regards,
Fabrice
On 21 August 2010 03:33, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote:
Hi,
Is your Blink app wired to DelugeC component?
Mike
On Aug 20, 2010, at 10:32 AM, Fabrice Dossin wrote:
Hi,
I am currently investigating for integrating Deluge T2 into my app.
I have a strange behavior :
When I program the motes with my program as the golden image it does boot
correctly and I can propagate a Blink image or another to the mesh.
But when I flash the mote with Blink and propagate my app trough the air,
my app never start...
The Boot.booted event is sent but I never receive the startDone event from
ActiveMessageC that is automatically started by Deluge.
The program is blocked somewhere between these.
If I manually activate ActiveMessage, Deluge never take my propagated
images so it should be freezed somewhere into the deluge initialization
process.
Does someone have a clue for me on where to search ?
I am developing on IRIS motes.
Kind regards,
Fabrice
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 strange boot behavior
Yes, it is. As a proof when I flash my app on the mote as the golden image it works like a charm... I just need this to link it to my app, no ? components DelugeC; DelugeC.Leds - LedsC; Regards, Fabrice On 21 August 2010 03:33, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote: Hi, Is your Blink app wired to DelugeC component? Mike On Aug 20, 2010, at 10:32 AM, Fabrice Dossin wrote: Hi, I am currently investigating for integrating Deluge T2 into my app. I have a strange behavior : When I program the motes with my program as the golden image it does boot correctly and I can propagate a Blink image or another to the mesh. But when I flash the mote with Blink and propagate my app trough the air, my app never start... The Boot.booted event is sent but I never receive the startDone event from ActiveMessageC that is automatically started by Deluge. The program is blocked somewhere between these. If I manually activate ActiveMessage, Deluge never take my propagated images so it should be freezed somewhere into the deluge initialization process. Does someone have a clue for me on where to search ? I am developing on IRIS motes. Kind regards, Fabrice ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 strange boot behavior
Hi, Is your Blink app wired to DelugeC component? Mike On Aug 20, 2010, at 10:32 AM, Fabrice Dossin wrote: Hi, I am currently investigating for integrating Deluge T2 into my app. I have a strange behavior : When I program the motes with my program as the golden image it does boot correctly and I can propagate a Blink image or another to the mesh. But when I flash the mote with Blink and propagate my app trough the air, my app never start... The Boot.booted event is sent but I never receive the startDone event from ActiveMessageC that is automatically started by Deluge. The program is blocked somewhere between these. If I manually activate ActiveMessage, Deluge never take my propagated images so it should be freezed somewhere into the deluge initialization process. Does someone have a clue for me on where to search ? I am developing on IRIS motes. Kind regards, Fabrice ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 BaseStation problems
Hi! Sorry for answering so slow. On Mon, 22 Feb 2010, Ryan Emerson wrote: I have recently being trying to use Deluge T2 and have been following this manual: http://www.tinyos.net/tinyos-2.x/doc/html/deluge-t2-manual.html The latest documentation is on wiki: http://docs.tinyos.net/index.php/Deluge_T2 I can sucessfully run the following commands in the GoldenImage directory: CFLAGS=-DDELUGE_BASESTATION make micaz install,0 mib510,/dev/ttyS2 However when I then try to communicate using tos-deluge or try to install an application using: ./burn /dev/ttyS2 /dev/ttyS2 micaz I receive the following errors: Flushing the serial port.. Checking if node is a Deluge T2 base station ... ERROR: Timeout. Is the node a Deluge T2 base station? I have also read on various posts that people use a tests/deluge/BaseStation folder. However my installation doesn't have this. Is this necessary and if so how can I get it. I think you are running a very old version. Can you please update to the latest CVS/GIT? You can find the the way to do it here: http://docs.tinyos.net/index.php/Installing_from_CVS/GIT All the best! Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2
It is for Deluge to blink the leds to indicate status. It is exposed to the user applications because users can decide whether they want Deluge to use leds for this purpose or not. Mike On Jan 25, 2010, at 1:54 PM, David Guillén wrote: Hi all, I was looking at the file BlinkAppC.nc and I don't know what is DelugeC.Leds - LedsC; Does somebody know why we make this wiring?? Regards, David ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2
Thanks Mike. If I wanted to create an application that works with Deluge T2, shall I know something else apart from what it is said in Deluge T2 manual? I have tried to make a new Deluge application taking an old one and adding: components DelugeC; in the AppC.nc BOOTLOADER=tosboot in the Makefile I have no problems compiling it and the base station disseminates it properly, but when the nodes reboot they don't change to the new image. In addition when my application is running on a node, this does not hear the dissemination-reprogramming command. Any suggestion like including more lines in the files or update the CVS repository?? Regards, David On Mon, Jan 25, 2010 at 8:40 PM, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote: It is for Deluge to blink the leds to indicate status. It is exposed to the user applications because users can decide whether they want Deluge to use leds for this purpose or not. Mike On Jan 25, 2010, at 1:54 PM, David Guillén wrote: Hi all, I was looking at the file BlinkAppC.nc and I don't know what is DelugeC.Leds - LedsC; Does somebody know why we make this wiring?? Regards, David ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 problem for new entry in volumes-at45db.xml (MICAz motes)
Steps to reproduce the Deluge problem for MICAz motes. 1. First program all the client motes with the golden image application under apps/tests/deluge. Every mote having a unique ID. 2. Program one mote with the base station application. 3. Inject a new image in the basestation: % tos-deluge serial@/dev/ttyS0:57600 -i 1 apps/Blink/build/micaz/tos_image.xml 4. Disseminate this image from the basestation to the client motes. % tos-deluge serial@/dev/ttyS0:57600 -d 1 % tos-deluge serial@/dev/ttyS0:57600 -dr 1 5. The client motes get reprogrammed and start working fine as per the new program image. Now. Repeat steps 3 to 4 for a new My application image. This application has the following volumesxxx.xml file. volume_table volume name=GOLDENIMAGE size=65536 base=0 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ volume name=DYMODATA size=131072 / /volume_table After step no 4, the client motes get reprogrammed and start working fine as per the new My application program image. Now, repeat steps 3 and 4 for any other application. This time, the step 4 is not able to reprogram the client motes. Thats where the problem is. Thanks Vikram On Mon, Jan 25, 2010 at 12:50 AM, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote: Can you give the steps (commands) to reproduce this problem? Mike On Jan 23, 2010, at 6:17 AM, Vikram vik76 wrote: Hello, I have an additional entry in the volumes-at45db.xml file for my application. volume_table volume name=GOLDENIMAGE size=65536 base=0 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ volume name=DYMODATA size=131072 / /volume_table Initially, I programmed the motes with the GoldenImage in apps/tests/deluge/GoldenImage and used the Blink application for testing. It worked fine. After reprogramming the MICAz motes with a new image created using the above XML file, it works fine for my application. But the problem is after doing this, I am not able to reprogram again the second time for the same application. Regards Vikram ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 problem for new entry in volumes-at45db.xml (MICAz motes)
I would like to verify a theory. Can you please try the following volume XML file? volume_table volume name=GOLDENIMAGE size=65536 base=0/ volume name=DELUGE1 size=65536 base=65536/ volume name=DELUGE2 size=65536 base=131072/ volume name=DELUGE3 size=65536 base=196608/ volume name=DYMODATA size=131072 base=327680/ /volume_table Thanks Mike On Jan 25, 2010, at 10:22 PM, Vikram vik76 wrote: Steps to reproduce the Deluge problem for MICAz motes. 1. First program all the client motes with the golden image application under apps/tests/deluge. Every mote having a unique ID. 2. Program one mote with the base station application. 3. Inject a new image in the basestation: % tos-deluge serial@/dev/ttyS0:57600 -i 1 apps/Blink/build/micaz/tos_image.xml 4. Disseminate this image from the basestation to the client motes. % tos-deluge serial@/dev/ttyS0:57600 -d 1 % tos-deluge serial@/dev/ttyS0:57600 -dr 1 5. The client motes get reprogrammed and start working fine as per the new program image. Now. Repeat steps 3 to 4 for a new My application image. This application has the following volumesxxx.xml file. volume_table volume name=GOLDENIMAGE size=65536 base=0 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ volume name=DYMODATA size=131072 / /volume_table After step no 4, the client motes get reprogrammed and start working fine as per the new My application program image. Now, repeat steps 3 and 4 for any other application. This time, the step 4 is not able to reprogram the client motes. Thats where the problem is. Thanks Vikram On Mon, Jan 25, 2010 at 12:50 AM, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote: Can you give the steps (commands) to reproduce this problem? Mike On Jan 23, 2010, at 6:17 AM, Vikram vik76 wrote: Hello, I have an additional entry in the volumes-at45db.xml file for my application. volume_table volume name=GOLDENIMAGE size=65536 base=0 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ volume name=DYMODATA size=131072 / /volume_table Initially, I programmed the motes with the GoldenImage in apps/tests/deluge/GoldenImage and used the Blink application for testing. It worked fine. After reprogramming the MICAz motes with a new image created using the above XML file, it works fine for my application. But the problem is after doing this, I am not able to reprogram again the second time for the same application. Regards Vikram ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 problem for new entry in volumes-at45db.xml (MICAz motes)
I too was working on a similar approachThe following was the XML file for MICAz motes. volume_table volume name=DYMODATA size=131072 / volume name=GOLDENIMAGE size=65536 base=327680 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ /volume_table The above seemed to be working...but couldn't verify completely. I'll perform multiple tests. What would be the reason behind this? I couldn't understand. I got the clue from the XML for telosb motes where we need to specify the base for GOLDENIMAGE. Also please tell me the requirement of GOLDENIMAGE volume. Thanks Vikram On Tue, Jan 26, 2010 at 9:34 AM, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote: I would like to verify a theory. Can you please try the following volume XML file? volume_table volume name=GOLDENIMAGE size=65536 base=0/ volume name=DELUGE1 size=65536 base=65536/ volume name=DELUGE2 size=65536 base=131072/ volume name=DELUGE3 size=65536 base=196608/ volume name=DYMODATA size=131072 base=327680/ /volume_table Thanks Mike On Jan 25, 2010, at 10:22 PM, Vikram vik76 wrote: Steps to reproduce the Deluge problem for MICAz motes. 1. First program all the client motes with the golden image application under apps/tests/deluge. Every mote having a unique ID. 2. Program one mote with the base station application. 3. Inject a new image in the basestation: % tos-deluge serial@/dev/ttyS0:57600 -i 1 apps/Blink/build/micaz/tos_image.xml 4. Disseminate this image from the basestation to the client motes. % tos-deluge serial@/dev/ttyS0:57600 -d 1 % tos-deluge serial@/dev/ttyS0:57600 -dr 1 5. The client motes get reprogrammed and start working fine as per the new program image. Now. Repeat steps 3 to 4 for a new My application image. This application has the following volumesxxx.xml file. volume_table volume name=GOLDENIMAGE size=65536 base=0 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ volume name=DYMODATA size=131072 / /volume_table After step no 4, the client motes get reprogrammed and start working fine as per the new My application program image. Now, repeat steps 3 and 4 for any other application. This time, the step 4 is not able to reprogram the client motes. Thats where the problem is. Thanks Vikram On Mon, Jan 25, 2010 at 12:50 AM, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote: Can you give the steps (commands) to reproduce this problem? Mike On Jan 23, 2010, at 6:17 AM, Vikram vik76 wrote: Hello, I have an additional entry in the volumes-at45db.xml file for my application. volume_table volume name=GOLDENIMAGE size=65536 base=0 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ volume name=DYMODATA size=131072 / /volume_table Initially, I programmed the motes with the GoldenImage in apps/tests/deluge/GoldenImage and used the Blink application for testing. It worked fine. After reprogramming the MICAz motes with a new image created using the above XML file, it works fine for my application. But the problem is after doing this, I am not able to reprogram again the second time for the same application. Regards Vikram ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 problem for new entry in volumes-at45db.xml (MICAz motes)
It is in the way TOS generates the volume XML for at45db. There is a notion of unmovable (with the base attribute) volume. Deluge volumes should be unmovable. This way, when we refer to image x, it will always be pointing to the same volume. Mike On Jan 25, 2010, at 11:14 PM, Vikram vik76 wrote: I too was working on a similar approachThe following was the XML file for MICAz motes. volume_table volume name=DYMODATA size=131072 / volume name=GOLDENIMAGE size=65536 base=327680 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ /volume_table The above seemed to be working...but couldn't verify completely. I'll perform multiple tests. What would be the reason behind this? I couldn't understand. I got the clue from the XML for telosb motes where we need to specify the base for GOLDENIMAGE. Also please tell me the requirement of GOLDENIMAGE volume. Thanks Vikram On Tue, Jan 26, 2010 at 9:34 AM, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote: I would like to verify a theory. Can you please try the following volume XML file? volume_table volume name=GOLDENIMAGE size=65536 base=0/ volume name=DELUGE1 size=65536 base=65536/ volume name=DELUGE2 size=65536 base=131072/ volume name=DELUGE3 size=65536 base=196608/ volume name=DYMODATA size=131072 base=327680/ /volume_table Thanks Mike On Jan 25, 2010, at 10:22 PM, Vikram vik76 wrote: Steps to reproduce the Deluge problem for MICAz motes. 1. First program all the client motes with the golden image application under apps/tests/deluge. Every mote having a unique ID. 2. Program one mote with the base station application. 3. Inject a new image in the basestation: % tos-deluge serial@/dev/ttyS0:57600 -i 1 apps/Blink/build/micaz/tos_image.xml 4. Disseminate this image from the basestation to the client motes. % tos-deluge serial@/dev/ttyS0:57600 -d 1 % tos-deluge serial@/dev/ttyS0:57600 -dr 1 5. The client motes get reprogrammed and start working fine as per the new program image. Now. Repeat steps 3 to 4 for a new My application image. This application has the following volumesxxx.xml file. volume_table volume name=GOLDENIMAGE size=65536 base=0 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ volume name=DYMODATA size=131072 / /volume_table After step no 4, the client motes get reprogrammed and start working fine as per the new My application program image. Now, repeat steps 3 and 4 for any other application. This time, the step 4 is not able to reprogram the client motes. Thats where the problem is. Thanks Vikram On Mon, Jan 25, 2010 at 12:50 AM, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote: Can you give the steps (commands) to reproduce this problem? Mike On Jan 23, 2010, at 6:17 AM, Vikram vik76 wrote: Hello, I have an additional entry in the volumes-at45db.xml file for my application. volume_table volume name=GOLDENIMAGE size=65536 base=0 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ volume name=DYMODATA size=131072 / /volume_table Initially, I programmed the motes with the GoldenImage in apps/tests/deluge/GoldenImage and used the Blink application for testing. It worked fine. After reprogramming the MICAz motes with a new image created using the above XML file, it works fine for my application. But the problem is after doing this, I am not able to reprogram again the second time for the same application. Regards Vikram ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 problem for new entry in volumes-at45db.xml (MICAz motes)
I would specify the base attribute for all deluge volumes. Gold image is a guaranteed-to-work image with minimal support for network programming. It allows for node recovery in the worst case. Deluge expects the first volume to contain the gold image (hence base=0). Mike On Jan 25, 2010, at 11:31 PM, Vikram vik76 wrote: Ok, so its safe to always specify the base for all the volumes. Why do we require GOLDENIMAGE volume for DELUGE? Vikram. On Tue, Jan 26, 2010 at 9:53 AM, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote: It is in the way TOS generates the volume XML for at45db. There is a notion of unmovable (with the base attribute) volume. Deluge volumes should be unmovable. This way, when we refer to image x, it will always be pointing to the same volume. Mike On Jan 25, 2010, at 11:14 PM, Vikram vik76 wrote: I too was working on a similar approachThe following was the XML file for MICAz motes. volume_table volume name=DYMODATA size=131072 / volume name=GOLDENIMAGE size=65536 base=327680 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ /volume_table The above seemed to be working...but couldn't verify completely. I'll perform multiple tests. What would be the reason behind this? I couldn't understand. I got the clue from the XML for telosb motes where we need to specify the base for GOLDENIMAGE. Also please tell me the requirement of GOLDENIMAGE volume. Thanks Vikram On Tue, Jan 26, 2010 at 9:34 AM, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote: I would like to verify a theory. Can you please try the following volume XML file? volume_table volume name=GOLDENIMAGE size=65536 base=0/ volume name=DELUGE1 size=65536 base=65536/ volume name=DELUGE2 size=65536 base=131072/ volume name=DELUGE3 size=65536 base=196608/ volume name=DYMODATA size=131072 base=327680/ /volume_table Thanks Mike On Jan 25, 2010, at 10:22 PM, Vikram vik76 wrote: Steps to reproduce the Deluge problem for MICAz motes. 1. First program all the client motes with the golden image application under apps/tests/deluge. Every mote having a unique ID. 2. Program one mote with the base station application. 3. Inject a new image in the basestation: % tos-deluge serial@/dev/ttyS0:57600 -i 1 apps/Blink/build/micaz/tos_image.xml 4. Disseminate this image from the basestation to the client motes. % tos-deluge serial@/dev/ttyS0:57600 -d 1 % tos-deluge serial@/dev/ttyS0:57600 -dr 1 5. The client motes get reprogrammed and start working fine as per the new program image. Now. Repeat steps 3 to 4 for a new My application image. This application has the following volumesxxx.xml file. volume_table volume name=GOLDENIMAGE size=65536 base=0 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ volume name=DYMODATA size=131072 / /volume_table After step no 4, the client motes get reprogrammed and start working fine as per the new My application program image. Now, repeat steps 3 and 4 for any other application. This time, the step 4 is not able to reprogram the client motes. Thats where the problem is. Thanks Vikram On Mon, Jan 25, 2010 at 12:50 AM, Chieh-Jan (Mike) Liang clia...@cs.jhu.edu wrote: Can you give the steps (commands) to reproduce this problem? Mike On Jan 23, 2010, at 6:17 AM, Vikram vik76 wrote: Hello, I have an additional entry in the volumes-at45db.xml file for my application. volume_table volume name=GOLDENIMAGE size=65536 base=0 / volume name=DELUGE1 size=65536/ volume name=DELUGE2 size=65536/ volume name=DELUGE3 size=65536/ volume name=DYMODATA size=131072 / /volume_table Initially, I programmed the motes with the GoldenImage in apps/tests/deluge/GoldenImage and used the Blink application for testing. It worked fine. After reprogramming the MICAz motes with a new image created using the above XML file, it works fine for my application. But the problem is after doing this, I am not able to reprogram again the second time for the same application. Regards Vikram ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 erase command and overwriting images
Hi! On Fri, 22 Jan 2010, Erwing Sánchez wrote: Thank you Razvan, it works impeccably with the latest update. Great! :-) -- Razvan ME On Thu, Jan 21, 2010 at 6:07 PM, Razvan Musaloiu-E. razv...@cs.jhu.eduwrote: Hi! Can you please make sure you are running la latest CVS/GIT? In my attempt to fix some issues with micaz I managed to break telos. Now it should be fine. The commit that restores the proper behavior is this one: http://hinrg.cs.jhu.edu/git/?p=tinyos-2.x.git;a=commit;h=809036bc77a8366b0f9aa2d78cdcacdcc4dc1379 -- Razvan ME On Thu, 21 Jan 2010, Erwing Sánchez wrote: Hi, is the erase command implemented for Deluge T2? it is possible to overwrite an image and disseminate it? I'm working with telosb nodes in linux., and I'm having problems replacing an existing image. If I use the erase command for erasing the first image, I get the expected answer, but the image doesn't seem to be erased since the ping command is able to find it, e.g.: $ tos-deluge serial@/dev/ttyUSB0:115200 -e 1 Flushing the serial port.. Checking if node is a Deluge T2 base station ... Image number 1 erased $ tos-deluge serial@/dev/ttyUSB0:115200 -p 1 Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... -- Currently Executing: Prog Name: BasestationAppC UID: 0x701A61FE Compiled On: Thu Jan 21 17:30:07 2010 Node ID: 0 Stored image 1 Prog Name: BlinkAppC UID: 0xA606F84D Compiled On: Thu Jan 01 01:00:00 1970 Platform: User ID: erH Host Name: User Hash: 0x Size:33504 Num Pages: 30 -- If, after, I try to write a new image in volume 1, tos-deluge tries to replace the image, but in the summary the Prog Name is wrong and a subsequent ping command shows that there isn't a valid image in the volume. $ tos-deluge serial@/dev/ttyUSB0:115200 -i 1 build/telosb/tos_image.xml Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... Connected to Deluge nodes. -- Stored image 1 Prog Name: BlinkAppC UID: 0xA606F84D Compiled On: Thu Jan 01 01:00:00 1970 Platform: User ID: erH Host Name: User Hash: 0x Size:33504 Num Pages: 30 -- Create image: /usr/local/bin/tos-build-deluge-image -i 1 build/telosb/tos_image.xml Ihex read complete: 39418 bytes starting at 0x4A00 32 bytes starting at 0xFFE0 39450 bytes in 2 sections CRCs: 0xB6B9 0xDA78 0xA4F7 0x3489 0x4A40 0xBA10 0x11BD 0xAF51 0x24A5 0x9846 0x785A 0x5E7B 0x3274 0x0910 0x7757 0x3564 0x8F06 0x9BF2 0xECAD 0x2747 0x0B75 0x72C0 0x78AD 0x3A03 0xBE0B 0x0B15 0x3388 0x204D 0xA156 0xC5C3 0x006C 0xA446 0xF9CD 0x9B7E 0x821E 0xF380 -- 40128 bytes in 29.10 seconds (1378.8893 bytes/s) -- Replace image with: Prog Name: b`...@`pa UID: 0x2002604C Compiled On: Thu Jan 01 01:00:00 1970 Platform: User ID: erH Host Name: User Hash: 0x Size:32960 Num Pages: 4 -- $ tos-deluge serial@/dev/ttyUSB0:115200 -p 1 Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... -- Currently Executing: Prog Name: BasestationAppC UID: 0x701A61FE Compiled On: Thu Jan 21 17:30:07 2010 Node ID: 0 No valid image was detected. -- Any ideas for solving this behavior? thanks, Erwing ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 erase command and overwriting images
Hi! Can you please make sure you are running la latest CVS/GIT? In my attempt to fix some issues with micaz I managed to break telos. Now it should be fine. The commit that restores the proper behavior is this one: http://hinrg.cs.jhu.edu/git/?p=tinyos-2.x.git;a=commit;h=809036bc77a8366b0f9aa2d78cdcacdcc4dc1379 -- Razvan ME On Thu, 21 Jan 2010, Erwing Sánchez wrote: Hi, is the erase command implemented for Deluge T2? it is possible to overwrite an image and disseminate it? I'm working with telosb nodes in linux., and I'm having problems replacing an existing image. If I use the erase command for erasing the first image, I get the expected answer, but the image doesn't seem to be erased since the ping command is able to find it, e.g.: $ tos-deluge serial@/dev/ttyUSB0:115200 -e 1 Flushing the serial port.. Checking if node is a Deluge T2 base station ... Image number 1 erased $ tos-deluge serial@/dev/ttyUSB0:115200 -p 1 Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... -- Currently Executing: Prog Name: BasestationAppC UID: 0x701A61FE Compiled On: Thu Jan 21 17:30:07 2010 Node ID: 0 Stored image 1 Prog Name: BlinkAppC UID: 0xA606F84D Compiled On: Thu Jan 01 01:00:00 1970 Platform: User ID: erH Host Name: User Hash: 0x Size:33504 Num Pages: 30 -- If, after, I try to write a new image in volume 1, tos-deluge tries to replace the image, but in the summary the Prog Name is wrong and a subsequent ping command shows that there isn't a valid image in the volume. $ tos-deluge serial@/dev/ttyUSB0:115200 -i 1 build/telosb/tos_image.xml Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... Connected to Deluge nodes. -- Stored image 1 Prog Name: BlinkAppC UID: 0xA606F84D Compiled On: Thu Jan 01 01:00:00 1970 Platform: User ID: erH Host Name: User Hash: 0x Size:33504 Num Pages: 30 -- Create image: /usr/local/bin/tos-build-deluge-image -i 1 build/telosb/tos_image.xml Ihex read complete: 39418 bytes starting at 0x4A00 32 bytes starting at 0xFFE0 39450 bytes in 2 sections CRCs: 0xB6B9 0xDA78 0xA4F7 0x3489 0x4A40 0xBA10 0x11BD 0xAF51 0x24A5 0x9846 0x785A 0x5E7B 0x3274 0x0910 0x7757 0x3564 0x8F06 0x9BF2 0xECAD 0x2747 0x0B75 0x72C0 0x78AD 0x3A03 0xBE0B 0x0B15 0x3388 0x204D 0xA156 0xC5C3 0x006C 0xA446 0xF9CD 0x9B7E 0x821E 0xF380 -- 40128 bytes in 29.10 seconds (1378.8893 bytes/s) -- Replace image with: Prog Name: b`...@`pa UID: 0x2002604C Compiled On: Thu Jan 01 01:00:00 1970 Platform: User ID: erH Host Name: User Hash: 0x Size:32960 Num Pages: 4 -- $ tos-deluge serial@/dev/ttyUSB0:115200 -p 1 Flushing the serial port.. Checking if node is a Deluge T2 base station ... Pinging node ... -- Currently Executing: Prog Name: BasestationAppC UID: 0x701A61FE Compiled On: Thu Jan 21 17:30:07 2010 Node ID: 0 No valid image was detected. -- Any ideas for solving this behavior? thanks, Erwing ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge tutorial
http://docs.tinyos.net/index.php/Deluge_T2 Mike On Jan 13, 2010, at 2:39 PM, Geetha S wrote: Hello, I am looking for a proper working tutorial on Tiny OS DELUGE for Fedora 9. I will appreciate if you can forward it to me. Thanks a ton. SG ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 problem for MICAz motes
Hi! On Tue, 12 Jan 2010, Vikram vik76 wrote: Hello, I am trying to use Deluge T2 for MICAz motes. I use the command as per the Deluge T2 tutorial at http://docs.tinyos.net/index.php/Deluge_T2 ./burn mib510,/dev/ttyS0 serial@/dev/ttyS0:57600 micaz I get the following error during the Upload image process: === Upload the image === Flushing the serial port... Checking if node is a Deluge T2 base station ... It hangs at this position of Checking. I have connected the micaz mote using a programming board connected using a serial cable. Are you using the latest CVS? That's what I testes a few days ago and it was working fine. Note: The similar thing works for tmote sky motes when I change micaz to telosb in the burn command. Strange. Can you test if the serial communication works fine? Therefore, is it possible that I use a tmote sky mote as basestation and then reprogram the micaz motes as clients in the network? I haven't tested this but it should work. -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 problem for MICAz motes
Hi, Therefore, is it possible that I use a tmote sky mote as basestation and then reprogram the micaz motes as clients in the network? I haven't tested this but it should work. I have tested it with TelosB and MICAz motes as TelosB base-station a long time ago. It works fine. Be sure to inject the image builded for MICAz (remote-mote) into the TelosB(base-station mote) flash. -- Mehmet Akif Antepli On Wed, Jan 13, 2010 at 9:08 AM, Razvan Musaloiu-E. razv...@cs.jhu.eduwrote: Hi! On Tue, 12 Jan 2010, Vikram vik76 wrote: Hello, I am trying to use Deluge T2 for MICAz motes. I use the command as per the Deluge T2 tutorial at http://docs.tinyos.net/index.php/Deluge_T2 ./burn mib510,/dev/ttyS0 serial@/dev/ttyS0:57600 micaz I get the following error during the Upload image process: === Upload the image === Flushing the serial port... Checking if node is a Deluge T2 base station ... It hangs at this position of Checking. I have connected the micaz mote using a programming board connected using a serial cable. Are you using the latest CVS? That's what I testes a few days ago and it was working fine. Note: The similar thing works for tmote sky motes when I change micaz to telosb in the burn command. Strange. Can you test if the serial communication works fine? Therefore, is it possible that I use a tmote sky mote as basestation and then reprogram the micaz motes as clients in the network? I haven't tested this but it should work. -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] deluge T2 problem (buffer overflow warning, incomplete dissemination)
Hi! On Tue, 24 Nov 2009, Ning Martin Xu wrote: Dear all, I've been playing with Deluge T2 in TinyOS 2.1 under Ubuntu 8.04 LTS. The motes I'm using are Crossbow Micaz. I had these problems recently. Sometimes, in the process of injecting a program image into the mote connected to MIB510, it kept showing Warning: Buffer overflow while printing -- the progress bar. I know it is the python support in TinyOS that prints this message. I don't know what caused it, or how to fix it. There's another problem. I included Deluge component in MViz, and it was working fine at first. I issued the tos-deluge -d command to disseminate the program and -dr when all motes have their yellow LED on (program received). They all reprogrammed. Now, what happened was, around 1 minute after the dissemination started, the closest motes turned on all three LEDs, and then they turned off, as in a regular start up. After this, I don't see them resume receiving the program (the green LED doesn't flicker), nor respond to a new -d command. Would somebody be nice to shed some light. Thanks a lot. Can you please try the latest CVS and let me know if you see the same behavior? -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge compilation on micaz
Hi Razvan, When I typed echo $PYTHONPATH, the computer didn't show me anything. What do you think? I will try it tomorrow at office and let you know. Thanks. Regards, Bai On Wed, Sep 9, 2009 at 3:22 PM, Razvan Musaloiu-E. razv...@cs.jhu.eduwrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: On Wed, Sep 9, 2009 at 2:43 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, That is the manual I am using. All the stuffs are latest. Not too sure where it went wrong. I tried the command you suggested already. No luck. Have you tried it on micaz since it is updated to the latest CVS? I don't have a micaz at hand but I just retested with a telosb and it works fine. I think your python is searching for the tos.py in the wrong place. Is your PYTHONPATH is using including the $TOSROOT/support/sdk/python? Where I can or what command I can use to check out if my pytho using th ecorrect path? From the bash shell you can print the PYTHONPATH with the following command: echo $PYTHONPATH Same as for PATH basically. :-) You can check the path my running python and the type: import tos help(tos) And then look at the FILES sections. In my case it says: FILE /home/lpl/local/src/tinyos-2.x/support/sdk/python/tos.py Which is correct because that is where my local installation is. Am I doing it right as you suggested? I got the following errors. I guess the Python path is not correct? administra...@jujumao /opt/tinyos-2.x/apps/tests/deluge/blink $ python Python 2.5.1 (r251:54863, May 18 2007, 16:56:43) [GCC 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)] on cygwin Type help, copyright, credits or license for more information. import tos Traceback (most recent call last): File stdin, line 1, in module ImportError: No module named tos import tos.py Traceback (most recent call last): File stdin, line 1, in module ImportError: No module named tos.py help(tos) Traceback (most recent call last): File stdin, line 1, in module NameError: name 'tos' is not defined This is strange. If you don't have tos.py in your path then the tos-deluge should fail in a different way. -- Razvan ME One more thing: the correct baudrate for micaz is 57600 and not 115200. Thanks -- Razvan ME On Wed, Sep 9, 2009 at 2:13 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, Since Deluge manual doesn't provide any micaz install command. It could be something wrong with the command I typed. But i tried different combination. It still had the same error. So I reckon it has nothing to do with this command. What manual are you reading? The current one is this one: http://docs.tinyos.net/index.php/Deluge_T2 One thing to note is that the first parameter needs to ser...@port :SPEED for serial ports. -- Razvan ME On Wed, Sep 9, 2009 at 2:03 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, I have followed the intructions from the Deulge tutorial and also installed pyserial tools as required. I met the following error when i tried to inject blink image to micaz administra...@jujumao /opt/tinyos-2.x/apps/tests/deluge/Blink $ tos-deluge /dev/ttyS5:115200 -i 1 build/micaz/tos-image.xml Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 401, in module am = tos.AM() TypeError: __init__() takes exactly 2 arguments (1 given) It is the latest CVS. What could cause this problem? Can you run tos-deluge and see if the output is like this? $ tos-deluge Usage: /home/lpl/local/bin/tos-deluge source -p|-i|-r|-d|-e|-s image_number [options] source can be: ser...@port:SPEED Serial ports netw...@host:PORT MIB600 -p --pingProvide status of the image in the external flash -i --inject Inject a compiled TinyOS application [options]: tos_image.xml file path -e --erase Erase an image in the external flash -b --bootForce a reboot of the mote -r --reprogram Reprogram the mote -d --disseminate Disseminate the image in the external flash to the network -dr --disseminate-and-reprogram -s --stopStop the dissemination -ls --local-stop Stop the dissemination only on the local mote If it's not then you are not running the latest CVS. :-) -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge compilation on micaz
Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi Razvan, When I typed echo $PYTHONPATH, the computer didn't show me anything. What do you think? You can set it by adding: export PYTHONPATH=$TOSROOT/support/sdk/python:$PYTHONPATH to your ~/.bashrc or ~/.bash_profile. -- Razvan ME I will try it tomorrow at office and let you know. Thanks. Regards, Bai On Wed, Sep 9, 2009 at 3:22 PM, Razvan Musaloiu-E. razv...@cs.jhu.eduwrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: On Wed, Sep 9, 2009 at 2:43 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, That is the manual I am using. All the stuffs are latest. Not too sure where it went wrong. I tried the command you suggested already. No luck. Have you tried it on micaz since it is updated to the latest CVS? I don't have a micaz at hand but I just retested with a telosb and it works fine. I think your python is searching for the tos.py in the wrong place. Is your PYTHONPATH is using including the $TOSROOT/support/sdk/python? Where I can or what command I can use to check out if my pytho using th ecorrect path? From the bash shell you can print the PYTHONPATH with the following command: echo $PYTHONPATH Same as for PATH basically. :-) You can check the path my running python and the type: import tos help(tos) And then look at the FILES sections. In my case it says: FILE /home/lpl/local/src/tinyos-2.x/support/sdk/python/tos.py Which is correct because that is where my local installation is. Am I doing it right as you suggested? I got the following errors. I guess the Python path is not correct? administra...@jujumao /opt/tinyos-2.x/apps/tests/deluge/blink $ python Python 2.5.1 (r251:54863, May 18 2007, 16:56:43) [GCC 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)] on cygwin Type help, copyright, credits or license for more information. import tos Traceback (most recent call last): File stdin, line 1, in module ImportError: No module named tos import tos.py Traceback (most recent call last): File stdin, line 1, in module ImportError: No module named tos.py help(tos) Traceback (most recent call last): File stdin, line 1, in module NameError: name 'tos' is not defined This is strange. If you don't have tos.py in your path then the tos-deluge should fail in a different way. -- Razvan ME One more thing: the correct baudrate for micaz is 57600 and not 115200. Thanks -- Razvan ME On Wed, Sep 9, 2009 at 2:13 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, Since Deluge manual doesn't provide any micaz install command. It could be something wrong with the command I typed. But i tried different combination. It still had the same error. So I reckon it has nothing to do with this command. What manual are you reading? The current one is this one: http://docs.tinyos.net/index.php/Deluge_T2 One thing to note is that the first parameter needs to ser...@port:SPEED for serial ports. -- Razvan ME On Wed, Sep 9, 2009 at 2:03 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, I have followed the intructions from the Deulge tutorial and also installed pyserial tools as required. I met the following error when i tried to inject blink image to micaz administra...@jujumao /opt/tinyos-2.x/apps/tests/deluge/Blink $ tos-deluge /dev/ttyS5:115200 -i 1 build/micaz/tos-image.xml Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 401, in module am = tos.AM() TypeError: __init__() takes exactly 2 arguments (1 given) It is the latest CVS. What could cause this problem? Can you run tos-deluge and see if the output is like this? $ tos-deluge Usage: /home/lpl/local/bin/tos-deluge source -p|-i|-r|-d|-e|-s image_number [options] source can be: ser...@port:SPEED Serial ports netw...@host:PORT MIB600 -p --pingProvide status of the image in the external flash -i --inject Inject a compiled TinyOS application [options]: tos_image.xml file path -e --erase Erase an image in the external flash -b --bootForce a reboot of the mote -r --reprogram Reprogram the mote -d --disseminate Disseminate the image in the external flash to the network -dr --disseminate-and-reprogram -s --stopStop the dissemination -ls --local-stop Stop the dissemination only on the local mote If it's not then you are not running the latest CVS. :-) -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge compilation on micaz
Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, I have followed the intructions from the Deulge tutorial and also installed pyserial tools as required. I met the following error when i tried to inject blink image to micaz administra...@jujumao /opt/tinyos-2.x/apps/tests/deluge/Blink $ tos-deluge /dev/ttyS5:115200 -i 1 build/micaz/tos-image.xml Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 401, in module am = tos.AM() TypeError: __init__() takes exactly 2 arguments (1 given) It is the latest CVS. What could cause this problem? Can you run tos-deluge and see if the output is like this? $ tos-deluge Usage: /home/lpl/local/bin/tos-deluge source -p|-i|-r|-d|-e|-s image_number [options] source can be: ser...@port:SPEED Serial ports netw...@host:PORT MIB600 -p --pingProvide status of the image in the external flash -i --inject Inject a compiled TinyOS application [options]: tos_image.xml file path -e --erase Erase an image in the external flash -b --bootForce a reboot of the mote -r --reprogram Reprogram the mote -d --disseminate Disseminate the image in the external flash to the network -dr --disseminate-and-reprogram -s --stopStop the dissemination -ls --local-stop Stop the dissemination only on the local mote If it's not then you are not running the latest CVS. :-) -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge compilation on micaz
Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, Since Deluge manual doesn't provide any micaz install command. It could be something wrong with the command I typed. But i tried different combination. It still had the same error. So I reckon it has nothing to do with this command. What manual are you reading? The current one is this one: http://docs.tinyos.net/index.php/Deluge_T2 One thing to note is that the first parameter needs to ser...@port:SPEED for serial ports. -- Razvan ME On Wed, Sep 9, 2009 at 2:03 PM, Razvan Musaloiu-E. razv...@cs.jhu.eduwrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, I have followed the intructions from the Deulge tutorial and also installed pyserial tools as required. I met the following error when i tried to inject blink image to micaz administra...@jujumao /opt/tinyos-2.x/apps/tests/deluge/Blink $ tos-deluge /dev/ttyS5:115200 -i 1 build/micaz/tos-image.xml Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 401, in module am = tos.AM() TypeError: __init__() takes exactly 2 arguments (1 given) It is the latest CVS. What could cause this problem? Can you run tos-deluge and see if the output is like this? $ tos-deluge Usage: /home/lpl/local/bin/tos-deluge source -p|-i|-r|-d|-e|-s image_number [options] source can be: ser...@port:SPEED Serial ports netw...@host:PORT MIB600 -p --pingProvide status of the image in the external flash -i --inject Inject a compiled TinyOS application [options]: tos_image.xml file path -e --erase Erase an image in the external flash -b --bootForce a reboot of the mote -r --reprogram Reprogram the mote -d --disseminate Disseminate the image in the external flash to the network -dr --disseminate-and-reprogram -s --stopStop the dissemination -ls --local-stop Stop the dissemination only on the local mote If it's not then you are not running the latest CVS. :-) -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge compilation on micaz
Hi, That is the manual I am using. All the stuffs are latest. Not too sure where it went wrong. I tried the command you suggested already. No luck. Have you tried it on micaz since it is updated to the latest CVS? Regards, Bai On Wed, Sep 9, 2009 at 2:13 PM, Razvan Musaloiu-E. razv...@cs.jhu.eduwrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, Since Deluge manual doesn't provide any micaz install command. It could be something wrong with the command I typed. But i tried different combination. It still had the same error. So I reckon it has nothing to do with this command. What manual are you reading? The current one is this one: http://docs.tinyos.net/index.php/Deluge_T2 One thing to note is that the first parameter needs to ser...@port:SPEED for serial ports. -- Razvan ME On Wed, Sep 9, 2009 at 2:03 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, I have followed the intructions from the Deulge tutorial and also installed pyserial tools as required. I met the following error when i tried to inject blink image to micaz administra...@jujumao /opt/tinyos-2.x/apps/tests/deluge/Blink $ tos-deluge /dev/ttyS5:115200 -i 1 build/micaz/tos-image.xml Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 401, in module am = tos.AM() TypeError: __init__() takes exactly 2 arguments (1 given) It is the latest CVS. What could cause this problem? Can you run tos-deluge and see if the output is like this? $ tos-deluge Usage: /home/lpl/local/bin/tos-deluge source -p|-i|-r|-d|-e|-s image_number [options] source can be: ser...@port:SPEED Serial ports netw...@host:PORT MIB600 -p --pingProvide status of the image in the external flash -i --inject Inject a compiled TinyOS application [options]: tos_image.xml file path -e --erase Erase an image in the external flash -b --bootForce a reboot of the mote -r --reprogram Reprogram the mote -d --disseminate Disseminate the image in the external flash to the network -dr --disseminate-and-reprogram -s --stopStop the dissemination -ls --local-stop Stop the dissemination only on the local mote If it's not then you are not running the latest CVS. :-) -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge compilation on micaz
Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, That is the manual I am using. All the stuffs are latest. Not too sure where it went wrong. I tried the command you suggested already. No luck. Have you tried it on micaz since it is updated to the latest CVS? I don't have a micaz at hand but I just retested with a telosb and it works fine. I think your python is searching for the tos.py in the wrong place. Is your PYTHONPATH is using including the $TOSROOT/support/sdk/python? You can check the path my running python and the type: import tos help(tos) And then look at the FILES sections. In my case it says: FILE /home/lpl/local/src/tinyos-2.x/support/sdk/python/tos.py Which is correct because that is where my local installation is. One more thing: the correct baudrate for micaz is 57600 and not 115200. -- Razvan ME On Wed, Sep 9, 2009 at 2:13 PM, Razvan Musaloiu-E. razv...@cs.jhu.eduwrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, Since Deluge manual doesn't provide any micaz install command. It could be something wrong with the command I typed. But i tried different combination. It still had the same error. So I reckon it has nothing to do with this command. What manual are you reading? The current one is this one: http://docs.tinyos.net/index.php/Deluge_T2 One thing to note is that the first parameter needs to ser...@port:SPEED for serial ports. -- Razvan ME On Wed, Sep 9, 2009 at 2:03 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, I have followed the intructions from the Deulge tutorial and also installed pyserial tools as required. I met the following error when i tried to inject blink image to micaz administra...@jujumao /opt/tinyos-2.x/apps/tests/deluge/Blink $ tos-deluge /dev/ttyS5:115200 -i 1 build/micaz/tos-image.xml Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 401, in module am = tos.AM() TypeError: __init__() takes exactly 2 arguments (1 given) It is the latest CVS. What could cause this problem? Can you run tos-deluge and see if the output is like this? $ tos-deluge Usage: /home/lpl/local/bin/tos-deluge source -p|-i|-r|-d|-e|-s image_number [options] source can be: ser...@port:SPEED Serial ports netw...@host:PORT MIB600 -p --pingProvide status of the image in the external flash -i --inject Inject a compiled TinyOS application [options]: tos_image.xml file path -e --erase Erase an image in the external flash -b --bootForce a reboot of the mote -r --reprogram Reprogram the mote -d --disseminate Disseminate the image in the external flash to the network -dr --disseminate-and-reprogram -s --stopStop the dissemination -ls --local-stop Stop the dissemination only on the local mote If it's not then you are not running the latest CVS. :-) -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge compilation on micaz
On Wed, Sep 9, 2009 at 2:43 PM, Razvan Musaloiu-E. razv...@cs.jhu.eduwrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, That is the manual I am using. All the stuffs are latest. Not too sure where it went wrong. I tried the command you suggested already. No luck. Have you tried it on micaz since it is updated to the latest CVS? I don't have a micaz at hand but I just retested with a telosb and it works fine. I think your python is searching for the tos.py in the wrong place. Is your PYTHONPATH is using including the $TOSROOT/support/sdk/python? Where I can or what command I can use to check out if my pytho using th ecorrect path? You can check the path my running python and the type: import tos help(tos) And then look at the FILES sections. In my case it says: FILE /home/lpl/local/src/tinyos-2.x/support/sdk/python/tos.py Which is correct because that is where my local installation is. Am I doing it right as you suggested? I got the following errors. I guess the Python path is not correct? administra...@jujumao /opt/tinyos-2.x/apps/tests/deluge/blink $ python Python 2.5.1 (r251:54863, May 18 2007, 16:56:43) [GCC 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)] on cygwin Type help, copyright, credits or license for more information. import tos Traceback (most recent call last): File stdin, line 1, in module ImportError: No module named tos import tos.py Traceback (most recent call last): File stdin, line 1, in module ImportError: No module named tos.py help(tos) Traceback (most recent call last): File stdin, line 1, in module NameError: name 'tos' is not defined One more thing: the correct baudrate for micaz is 57600 and not 115200. Thanks -- Razvan ME On Wed, Sep 9, 2009 at 2:13 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, Since Deluge manual doesn't provide any micaz install command. It could be something wrong with the command I typed. But i tried different combination. It still had the same error. So I reckon it has nothing to do with this command. What manual are you reading? The current one is this one: http://docs.tinyos.net/index.php/Deluge_T2 One thing to note is that the first parameter needs to ser...@port:SPEED for serial ports. -- Razvan ME On Wed, Sep 9, 2009 at 2:03 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Wed, 9 Sep 2009, BAI LI wrote: Hi, I have followed the intructions from the Deulge tutorial and also installed pyserial tools as required. I met the following error when i tried to inject blink image to micaz administra...@jujumao /opt/tinyos-2.x/apps/tests/deluge/Blink $ tos-deluge /dev/ttyS5:115200 -i 1 build/micaz/tos-image.xml Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 401, in module am = tos.AM() TypeError: __init__() takes exactly 2 arguments (1 given) It is the latest CVS. What could cause this problem? Can you run tos-deluge and see if the output is like this? $ tos-deluge Usage: /home/lpl/local/bin/tos-deluge source -p|-i|-r|-d|-e|-s image_number [options] source can be: ser...@port:SPEED Serial ports netw...@host:PORT MIB600 -p --pingProvide status of the image in the external flash -i --inject Inject a compiled TinyOS application [options]: tos_image.xml file path -e --erase Erase an image in the external flash -b --bootForce a reboot of the mote -r --reprogram Reprogram the mote -d --disseminate Disseminate the image in the external flash to the network -dr --disseminate-and-reprogram -s --stopStop the dissemination -ls --local-stop Stop the dissemination only on the local mote If it's not then you are not running the latest CVS. :-) -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 on Iris (Mac OS X): ERROR: Unable to retrieve the ident.
Hi Razvan, Thanks for the help. While I got the latest CVS version, I didn't think of updating the tools. Now it works. Cheers, Urs Razvan Musaloiu-E. wrote: Hi! On Mon, 17 Aug 2009, Urs Hunkeler wrote: Hi, I managed to get almost everything running for Deluge T2 on the Mac. I have the impression that the Deluge communication does not properly work. I use the mib520 programming board and I did check that I use the right port for the communication (ie. the port ending in a 'B' is the comm port, while the port ending in a 'A' is the programming port). [..] Any ideas what might be wrong? Can you please try the latest CVS version? The new tos.py is using the ser...@... syntax and it should work fine in Mac OS. Make sure you recompile the tools in order to get the new tos-deluge. :-) -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] DELUGE + CTP: Problem with TOS_AM_ADDRESS TOS_NODE_ID
Hi!
On Sun, 9 Aug 2009, Mehmet Akif Antepli wrote:
Hi,
I want to use deluge for my T2 applicaiton which uses CTP.
When i build and install my application into micaz motes, CTP works. During
installation, i assign mote id and it sets both TOS_NODE_ID and
TOS_AM_ADDRESS and they become equal. (in the avr.rules file)
CTP uses TOS_AM_ADDRESS as link layer address (in the CtpRoutingEngineP
with the variable my_ll_addr) but at the application layer, TOS_NODE_ID is
used for root selection.
In the following, I tried injecting my applicaiton into base station mote
and rebooting it from that application;
1-) Build and install BaseStation application
(/opt/tinyos-2.1.0/apps/tests/deluge/BaseStation) with mote id 0 into the
base-station micaz mote.
2-) Build my application with the flag CFLAGS+= -DDELUGE_BASESTATION, and
inject it as 1st image into micaz's flash memory.
3-) Reboot micaz from that image.
Then my application works but parent_id is set to 1 (at the application
layer). *I have a root node with node id 0 but having a parent node with id
1!*
**
**
The problem is that, TOS_AM_ADDRESS is always equals to 1 in the AM.h.
CtpRoutingEngineP component sets my_ll_addr variable during software
initialization as;
my_ll_addr = call AMPacket.address();
which is TOS_AM_ADDRESS=1
In NetProgM.nc from tos/lib/net/Deluge/extra there a Init.init in which
the the local address is properly restore:
53command error_t Init.init()
54{
55 BootArgs bootArgs;
56 call IFlash.read(TCAST(uint8_t*
COUNT(sizeof(bootArgs)),TOSBOOT_ARGS_ADDR), bootArgs, sizeof(bootArgs));
57
58 // Update the local node ID
59 if (bootArgs.address != 0x) {
60TOS_NODE_ID = bootArgs.address;
61call setAmAddress(bootArgs.address);
62 }
63 call CC2420Config.setShortAddr(bootArgs.address);
64 call CC2420Config.sync();
65
66 return SUCCESS;
67}
The problem is the my_ll_addr also initialized in a Init.init so they will
execute in arbitrary order. If you move that line in StdControl.start
things should start working normally. Can you give it a try? :-)
--
Razvan ME
It seems that i can't build my application once and disseminate it
over-the-air (while using CTP) because TOS_AM_ADDRESS is a constant and
assigned at compile time. Because, all the network will reboot with the same
AM address then. Although at mote level, it can be changed using the
interface ActiveMessageAddress at run-time, CtpRoutingEngineP initializes
my_ll_address variable at software initialization.
I tried using ActiveMessageAddress and providing Init interfaces at the
application level,
command error_t Init.init() {
call ActiveMessageAddress.setAddress(call ActiveMessageAddress.amGroup(),
TOS_NODE_ID);
return SUCCESS;
}
but it doesn't work,
Any suggestions?
Thanks in advance,
--
Mehmet Akif Antepli
Grad. Student
Dept. of EEE
Middle East Technical University
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge
Thanks for the reply, I did figure it out after a while. I misread the code
initially. But for some reason the mote was reporting that the supply
voltage was too low and did not want to reboot. I thought that this was not
possible as the mote was plugged into a USB port. Until I physically
measured the voltage and found that it was indeed below the threshold
voltage. When run from batteries everything seems fine.
Leon
2009/6/11 Razvan Musaloiu-E. razv...@cs.jhu.edu
Hi!
On Fri, 8 May 2009, Leon Steenkamp wrote:
In tos\lib\net\Deluge\extra\NetProgM.nc there is the following:
--SNIP--
command error_t NetProg.programImageAndReboot(uint32_t imgAddr)
{
reprogramImgAddr = imgAddr;
return call ReprogramGuard.okToProgram();
}
event void ReprogramGuard.okToProgramDone(bool ok)
{
BootArgs bootArgs;
if (!ok) {
// The voltage is too low. Nothing to do.
return;
}
atomic {
call IFlash.read(TCAST(uint8_t*
COUNT(sizeof(bootArgs)),TOSBOOT_ARGS_ADDR), bootArgs, sizeof(bootArgs));
bootArgs.imageAddr = reprogramImgAddr;
bootArgs.gestureCount = 0xff;
bootArgs.noReprogram = FALSE;
bootArgs.address = TOS_NODE_ID;
call IFlash.write(TCAST(uint8_t*
COUNT(sizeof(bootArgs)),TOSBOOT_ARGS_ADDR), bootArgs, sizeof(bootArgs));
// reboot
netprog_reboot();
}
}
--SNIP--
I am using TelosB platform and when NetProg.programImageAndReboot is
called
not much happens and I guess its because ReprogramGuard.okToProgram() is
called with no argument.
ReprogramGuard.okToProgram() is called without any argument because it's a
split phase command. The response is the ReprogramGuard.okToProgramDone
event. If the ok is false it means the battery voltage is too low so the
mote will not reboot. There is another voltage check in the bootloader
(tosboot) so if you ignore the ok and initiate a reboot the mote will not
reprogram (and you can enter in a loop if you keep rebooting asking for a
reprogramming).
Sorry for delay. I didn't notice this message until now. :-(
Razvan ME
And if (!ok) is always true.
Am I missing something? or is there a problem with the code? I changed the
if (!ok) to if (ok), the node now reboots but it does not seem to be
reprogrammed.
Leon
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge
Hi!
On Fri, 8 May 2009, Leon Steenkamp wrote:
In tos\lib\net\Deluge\extra\NetProgM.nc there is the following:
--SNIP--
command error_t NetProg.programImageAndReboot(uint32_t imgAddr)
{
reprogramImgAddr = imgAddr;
return call ReprogramGuard.okToProgram();
}
event void ReprogramGuard.okToProgramDone(bool ok)
{
BootArgs bootArgs;
if (!ok) {
// The voltage is too low. Nothing to do.
return;
}
atomic {
call IFlash.read(TCAST(uint8_t*
COUNT(sizeof(bootArgs)),TOSBOOT_ARGS_ADDR), bootArgs, sizeof(bootArgs));
bootArgs.imageAddr = reprogramImgAddr;
bootArgs.gestureCount = 0xff;
bootArgs.noReprogram = FALSE;
bootArgs.address = TOS_NODE_ID;
call IFlash.write(TCAST(uint8_t*
COUNT(sizeof(bootArgs)),TOSBOOT_ARGS_ADDR), bootArgs, sizeof(bootArgs));
// reboot
netprog_reboot();
}
}
--SNIP--
I am using TelosB platform and when NetProg.programImageAndReboot is called
not much happens and I guess its because ReprogramGuard.okToProgram() is
called with no argument.
ReprogramGuard.okToProgram() is called without any argument because it's a
split phase command. The response is the ReprogramGuard.okToProgramDone
event. If the ok is false it means the battery voltage is too low so the
mote will not reboot. There is another voltage check in the bootloader
(tosboot) so if you ignore the ok and initiate a reboot the mote will not
reprogram (and you can enter in a loop if you keep rebooting asking for a
reprogramming).
Sorry for delay. I didn't notice this message until now. :-(
Razvan ME
And if (!ok) is always true.
Am I missing something? or is there a problem with the code? I changed the
if (!ok) to if (ok), the node now reboots but it does not seem to be
reprogrammed.
Leon
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 BaseStation compilation error
Thank you for the reply. I’m running the latest CVS. (I followed the instructions at sourceforge). But I updated it again but still gives the same problem. What might be the reason for this error? I configured /opt/tinyos-2.x/tools according to the tutorial. But when I compile BaseStation program it gives me the error. Component DelugeC not found. please help me Thank you. R.Fernando Date: Tue, 26 May 2009 20:03:53 -0400 From: razv...@cs.jhu.edu To: ranalferna...@live.com CC: tinyos-help@millennium.berkeley.edu Subject: Re: [Tinyos-help] Deluge T2 BaseStation compilation error Hi! On Tue, 26 May 2009, ranal fernando wrote: Dear all, Iʼm trying to use Deluge for T2, I could continue according to the Deluge T2 tutorial but when I encounter the compilation of BaseStation app it gives me an error. Component deluge not found When I give $ TINYOS_NP=BNP make telosb it gives me lot of errors. I went thru TOS help for bnp.extra. I have bnp.extra version bnp.extra,v 1.3 2007/07/11 00:42:54 razvanm Exp $ I tried to download a new bnp.extra but it is not available for download at sourceforge as well as at Razvanʼs location. I think this is a path problem. Are you running the latest CVS? If you are not, can you please give a try? :-) Note: the 'TINYOS_NP=BNP' was replaces by 'BOOTLOADER=tosboot'. -- Razvan ME I really want some help in this. Thanks in advance. R.Fernando _ Hotmail® goes with you. http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 BaseStation compilation error
Hi! On Wed, 27 May 2009, ranal fernando wrote: Thank you for the reply. I’m running the latest CVS. (I followed the instructions at sourceforge). But I updated it again but still gives the same problem. What might be the reason for this error? I configured /opt/tinyos-2.x/tools according to the tutorial. But when I compile BaseStation program it gives me the error. Component DelugeC not found. Can you please check the if the MAKERULES points to the place where you put the CVS version? If it points to the old you might get this error. -- Razvan ME Date: Tue, 26 May 2009 20:03:53 -0400 From: razv...@cs.jhu.edu To: ranalferna...@live.com CC: tinyos-help@millennium.berkeley.edu Subject: Re: [Tinyos-help] Deluge T2 BaseStation compilation error Hi! On Tue, 26 May 2009, ranal fernando wrote: Dear all, Iʼm trying to use Deluge for T2, I could continue according to the Deluge T2 tutorial but when I encounter the compilation of BaseStation app it gives me an error. Component deluge not found When I give $ TINYOS_NP=BNP make telosb it gives me lot of errors. I went thru TOS help for bnp.extra. I have bnp.extra version bnp.extra,v 1.3 2007/07/11 00:42:54 razvanm Exp $ I tried to download a new bnp.extra but it is not available for download at sourceforge as well as at Razvanʼs location. I think this is a path problem. Are you running the latest CVS? If you are not, can you please give a try? :-) Note: the 'TINYOS_NP=BNP' was replaces by 'BOOTLOADER=tosboot'. -- Razvan ME I really want some help in this. Thanks in advance. R.Fernando _ Hotmail® goes with you. http://windowslive.com/Tutorial/Hotmail/Mobile?ocid=TXT_TAGLM_WL_HM_Tutorial_Mobile1_052009___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 BaseStation compilation error
Hi! On Tue, 26 May 2009, ranal fernando wrote: Dear all, I’m trying to use Deluge for T2, I could continue according to the Deluge T2 tutorial but when I encounter the compilation of BaseStation app it gives me an error. Component deluge not found When I give $ TINYOS_NP=BNP make telosb it gives me lot of errors. I went thru TOS help for bnp.extra. I have bnp.extra version bnp.extra,v 1.3 2007/07/11 00:42:54 razvanm Exp $ I tried to download a new bnp.extra but it is not available for download at sourceforge as well as at Razvan’s location. I think this is a path problem. Are you running the latest CVS? If you are not, can you please give a try? :-) Note: the 'TINYOS_NP=BNP' was replaces by 'BOOTLOADER=tosboot'. -- Razvan ME I really want some help in this. Thanks in advance. R.Fernando ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge without a basestation
Hi! On Mon, 20 Apr 2009, Angela Perez wrote: Hi, Is the following possible using Deluge T2: I want a mote (say mote X) to re-program a selected neighbor in the network (say mote Y), without X being a base station connected to a serial port. Re-programming will take place when some condition specific to my app is true. If X has an image stored that can be used to reprogram Y, how can this be achieved? Is there any documentation - apart from the simple Deluge Tutorial - that explains Deluge in more detail? The tutorial doesn't go into these details. Here is a few pointers. The component that is implementing the basestation behavior is called DelugeManagerC. The code that triggers the dissemination and starts the object publishing is in DelugeManagerP. The function of interests are SerialAMReceiver.receive and DelugeMetadata.readDone. The code that deals with what happens on the client side is in DelugeP.nc. The most interesting things happen in DisseminationValue.changed and ObjectTransfer.receiveDone. Note: DelugeManagerP.nc and DelugeP.nc are in tos/lib/net/Deluge. -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] deluge Simulation using tossim
It's very easy. Go to the folder /build/pc export DBG=usr1 ./main.exe 2 2 is the number of motes you want to simulate. usr1 is the debug output you want to check. Tehsinullah khan wrote: I have compiled the DelugeBasic code with make pc. but now i don't know how to run the simulation.I am using tinyos-1.1.15. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] deluge Simulation using tossim
Thank you for your kind reply.. DelugeBasic was not compiling by make pc but then i make changes in bnp.extra in tools/make.Now the code is compiled with some warning. I run the simulation with java net.tinyos.sim.SimDriver -gui -run build/pc/main.exe 4 the graphical gui is displayed but i dont understand the result of the simulation. I have run the TestTinyViz using SimDiver .Now i want to reprogram these nodes (TestTinyViz ) to blink. Plz guide me through the simulation process. Secondly The FormatEEPROM in TestDeluge is giving error.The FormatC.nc is missing the summary of this error. kindly help me !!! regards, On 4/1/09, Yu Liu yu...@siu.edu wrote: It's very easy. Go to the folder /build/pc export DBG=usr1 ./main.exe 2 2 is the number of motes you want to simulate. usr1 is the debug output you want to check. Tehsinullah khan wrote: I have compiled the DelugeBasic code with make pc. but now i don't know how to run the simulation.I am using tinyos-1.1.15. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 problem on a NEW platform
Hi!
On Mon, 16 Feb 2009, Mehmet Akif Antepli wrote:
Hi Razvan,
I examined the files under tos/lib/tosboot, especially;
tos/lib/tosboot/TOSBootM.nc
tos/lib/tosboot/stm25p/ExtFlashC.nc
tos/lib/tosboot/stm25p/ExtFlashM.nc
the files under tos/lib/tosboot/telosb.
I made the following observations:
--
*1-) *In TOSBootM.nc there is the following line:
209 void startupSequence() {
.
.
253// give user some time and count down LEDs
254 startupLeds();
.
.
}
The startupSequence() function is called in the main function. So, Leds
should unconditionally have been glowing due to startupLeds() function but
it does not.!
This is an indication that the bootloader is not on the mote. The
bootloader is written on the mote before the program. Here is the sequence
of commands for telosb:
Writing the bootloader:
tos-bsl --telosb -c /dev/ttyUSB0 -r -e -I -p
/home/tinyos2/local/src/tinyos-2.x/tos/lib/tosboot/build/telosb/main.ihex
MSP430 Bootstrap Loader Version: 1.39-telos-8
Mass Erase...
Transmit default password ...
Invoking BSL...
Transmit default password ...
Current bootstrap loader version: 1.61 (Device ID: f16c)
Changing baudrate to 38400 ...
Program ...
2112 bytes programmed.
Reset device ...
installing telosb binary using bsl (without mass erase)
Writing the program:
tos-bsl --telosb -c /dev/ttyUSB0 -r -I -p build/telosb/main.ihex.out
MSP430 Bootstrap Loader Version: 1.39-telos-8
Invoking BSL...
Transmit default password ...
Current bootstrap loader version: 1.61 (Device ID: f16c)
Changing baudrate to 38400 ...
Program ...
37702 bytes programmed.
Reset device ...
When i ping the 'Sensenode' it seems that Blink application is loaded into
its flash. But during the following command;
5-) reprogram 'Sensenode' with the following command:
tos-deluge /dev/ttyUSB0 telosb -r 1
none of the leds glow, flash or set! Reboot command does not make the code
in TOSBootM.nc to work.
*2-) *If i did the reverse, that is, programming telosb over-the-air by
installing Blink (/opt/tinyos-2.1.0/apps/tests/deluge/Blink) image into
'Sensenode's flash, disseminate reboot Telosb form that image, then TelosB
blinks. So, the reverse operation works.
*3-) *As a reminder, if i program 'Sensenode' with Blink application (build
for TelosB) under opt/tinyos-2.1.0/apps/tests/deluge/Blink, it runs on
'Sensenode 'as it runs on TelosB. Also, both motes use the same flash chip
ST M25P80.
*4-)* i copied the hardware.h file of Sensenode under
/opt/tinyos-2.1.0/tos/platforms/sensenode/ in the following. It seems to
be the same with that of TelosB.
#ifndef _H_hardware_h
#define _H_hardware_h
#include msp430hardware.h
//#include MSP430ADC12.h
//#include CC2420Const.h
//#include AM.h
// LEDs
TOSH_ASSIGN_PIN(RED_LED, 5, 5);
TOSH_ASSIGN_PIN(GREEN_LED, 5, 4);
TOSH_ASSIGN_PIN(YELLOW_LED, 5, 6);
// CC2420 RADIO #defines
TOSH_ASSIGN_PIN(RADIO_CSN, 4, 2);
TOSH_ASSIGN_PIN(RADIO_VREF, 4, 5);
TOSH_ASSIGN_PIN(RADIO_RESET, 4, 6);
TOSH_ASSIGN_PIN(RADIO_FIFOP, 1, 0);
TOSH_ASSIGN_PIN(RADIO_SFD, 4, 1);
TOSH_ASSIGN_PIN(RADIO_GIO0, 1, 3);
TOSH_ASSIGN_PIN(RADIO_FIFO, 1, 3);
TOSH_ASSIGN_PIN(RADIO_GIO1, 1, 4);
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
TOSH_ASSIGN_PIN(CC_FIFOP, 1, 0);
TOSH_ASSIGN_PIN(CC_FIFO, 1, 3);
TOSH_ASSIGN_PIN(CC_SFD, 4, 1);
TOSH_ASSIGN_PIN(CC_VREN, 4, 5);
TOSH_ASSIGN_PIN(CC_RSTN, 4, 6);
// UART pins
TOSH_ASSIGN_PIN(SOMI0, 3, 2);
TOSH_ASSIGN_PIN(SIMO0, 3, 1);
TOSH_ASSIGN_PIN(UCLK0, 3, 3);
TOSH_ASSIGN_PIN(UTXD0, 3, 4);
TOSH_ASSIGN_PIN(URXD0, 3, 5);
TOSH_ASSIGN_PIN(UTXD1, 3, 6);
TOSH_ASSIGN_PIN(URXD1, 3, 7);
TOSH_ASSIGN_PIN(UCLK1, 5, 3);
TOSH_ASSIGN_PIN(SOMI1, 5, 2);
TOSH_ASSIGN_PIN(SIMO1, 5, 1);
// ADC
TOSH_ASSIGN_PIN(ADC0, 6, 0);
TOSH_ASSIGN_PIN(ADC1, 6, 1);
TOSH_ASSIGN_PIN(ADC2, 6, 2);
TOSH_ASSIGN_PIN(ADC3, 6, 3);
// GIO pins
TOSH_ASSIGN_PIN(GIO0, 2, 0);
TOSH_ASSIGN_PIN(GIO1, 2, 1);
TOSH_ASSIGN_PIN(GIO2, 2, 3);
TOSH_ASSIGN_PIN(GIO3, 2, 6);
// FLASH
TOSH_ASSIGN_PIN(FLASH_PWR, 4, 3);
TOSH_ASSIGN_PIN(FLASH_CS, 4, 4);
TOSH_ASSIGN_PIN(FLASH_HOLD, 4, 7);
// PROGRAMMING PINS (tri-state)
//TOSH_ASSIGN_PIN(TCK, );
TOSH_ASSIGN_PIN(PROG_RX, 1, 1);
TOSH_ASSIGN_PIN(PROG_TX, 2, 2);
// need to undef atomic inside header files or nesC ignores the directive
#undef atomic
#endif // _H_hardware_h
As a result, after writing into 'Sensenode's flash, somehow it can't reboot
it with program image although pinging shows that the program image was
loaded.
Which component calls TOSBootM.nc? I don't know the mechanism that how
bootloader works.
TOSBootM.nc is the main code of the bootloader. It's the first code that
the mote runs when it powers up. The bootloader is the one that will give
Re: [Tinyos-help] Deluge T2 problem on a NEW platform
Hi Razvan,
I examined the files under tos/lib/tosboot, especially;
tos/lib/tosboot/TOSBootM.nc
tos/lib/tosboot/stm25p/ExtFlashC.nc
tos/lib/tosboot/stm25p/ExtFlashM.nc
the files under tos/lib/tosboot/telosb.
I made the following observations:
--
*1-) *In TOSBootM.nc there is the following line:
209 void startupSequence() {
.
.
253// give user some time and count down LEDs
254 startupLeds();
.
.
}
The startupSequence() function is called in the main function. So, Leds
should unconditionally have been glowing due to startupLeds() function but
it does not.!
When i ping the 'Sensenode' it seems that Blink application is loaded into
its flash. But during the following command;
5-) reprogram 'Sensenode' with the following command:
tos-deluge /dev/ttyUSB0 telosb -r 1
none of the leds glow, flash or set! Reboot command does not make the code
in TOSBootM.nc to work.
*2-) *If i did the reverse, that is, programming telosb over-the-air by
installing Blink (/opt/tinyos-2.1.0/apps/tests/deluge/Blink) image into
'Sensenode's flash, disseminate reboot Telosb form that image, then TelosB
blinks. So, the reverse operation works.
*3-) *As a reminder, if i program 'Sensenode' with Blink application (build
for TelosB) under opt/tinyos-2.1.0/apps/tests/deluge/Blink, it runs on
'Sensenode 'as it runs on TelosB. Also, both motes use the same flash chip
ST M25P80.
*4-)* i copied the hardware.h file of Sensenode under
/opt/tinyos-2.1.0/tos/platforms/sensenode/ in the following. It seems to
be the same with that of TelosB.
#ifndef _H_hardware_h
#define _H_hardware_h
#include msp430hardware.h
//#include MSP430ADC12.h
//#include CC2420Const.h
//#include AM.h
// LEDs
TOSH_ASSIGN_PIN(RED_LED, 5, 5);
TOSH_ASSIGN_PIN(GREEN_LED, 5, 4);
TOSH_ASSIGN_PIN(YELLOW_LED, 5, 6);
// CC2420 RADIO #defines
TOSH_ASSIGN_PIN(RADIO_CSN, 4, 2);
TOSH_ASSIGN_PIN(RADIO_VREF, 4, 5);
TOSH_ASSIGN_PIN(RADIO_RESET, 4, 6);
TOSH_ASSIGN_PIN(RADIO_FIFOP, 1, 0);
TOSH_ASSIGN_PIN(RADIO_SFD, 4, 1);
TOSH_ASSIGN_PIN(RADIO_GIO0, 1, 3);
TOSH_ASSIGN_PIN(RADIO_FIFO, 1, 3);
TOSH_ASSIGN_PIN(RADIO_GIO1, 1, 4);
TOSH_ASSIGN_PIN(RADIO_CCA, 1, 4);
TOSH_ASSIGN_PIN(CC_FIFOP, 1, 0);
TOSH_ASSIGN_PIN(CC_FIFO, 1, 3);
TOSH_ASSIGN_PIN(CC_SFD, 4, 1);
TOSH_ASSIGN_PIN(CC_VREN, 4, 5);
TOSH_ASSIGN_PIN(CC_RSTN, 4, 6);
// UART pins
TOSH_ASSIGN_PIN(SOMI0, 3, 2);
TOSH_ASSIGN_PIN(SIMO0, 3, 1);
TOSH_ASSIGN_PIN(UCLK0, 3, 3);
TOSH_ASSIGN_PIN(UTXD0, 3, 4);
TOSH_ASSIGN_PIN(URXD0, 3, 5);
TOSH_ASSIGN_PIN(UTXD1, 3, 6);
TOSH_ASSIGN_PIN(URXD1, 3, 7);
TOSH_ASSIGN_PIN(UCLK1, 5, 3);
TOSH_ASSIGN_PIN(SOMI1, 5, 2);
TOSH_ASSIGN_PIN(SIMO1, 5, 1);
// ADC
TOSH_ASSIGN_PIN(ADC0, 6, 0);
TOSH_ASSIGN_PIN(ADC1, 6, 1);
TOSH_ASSIGN_PIN(ADC2, 6, 2);
TOSH_ASSIGN_PIN(ADC3, 6, 3);
// GIO pins
TOSH_ASSIGN_PIN(GIO0, 2, 0);
TOSH_ASSIGN_PIN(GIO1, 2, 1);
TOSH_ASSIGN_PIN(GIO2, 2, 3);
TOSH_ASSIGN_PIN(GIO3, 2, 6);
// FLASH
TOSH_ASSIGN_PIN(FLASH_PWR, 4, 3);
TOSH_ASSIGN_PIN(FLASH_CS, 4, 4);
TOSH_ASSIGN_PIN(FLASH_HOLD, 4, 7);
// PROGRAMMING PINS (tri-state)
//TOSH_ASSIGN_PIN(TCK, );
TOSH_ASSIGN_PIN(PROG_RX, 1, 1);
TOSH_ASSIGN_PIN(PROG_TX, 2, 2);
// need to undef atomic inside header files or nesC ignores the directive
#undef atomic
#endif // _H_hardware_h
As a result, after writing into 'Sensenode's flash, somehow it can't reboot
it with program image although pinging shows that the program image was
loaded.
Which component calls TOSBootM.nc? I don't know the mechanism that how
bootloader works.
I run the command make telosb docs for GoldenImage component and i didn't
see any component using TOSBootM.nc.
Can there be a problem with the enums in TOSBoot_platform.h under
/opt/tinyos-2.1.0/tos/lib/tosboot/telosb file?
What do you think about that? Where do i make mistake?
Thanks in advance,
Mehmet Akif Antepli
Graduate Student
Dept. of Electrical-Electronics Eng.
METU
On Sat, Feb 14, 2009 at 12:00 AM, Mehmet Akif Antepli akifante...@gmail.com
wrote:
Hi Razvan,
First of all, thanks for your reply and suggestion.
On Fri, Feb 13, 2009 at 10:40 PM, Razvan Musaloiu-E.
razv...@cs.jhu.eduwrote:
Quick question: for Sensenode do you upload the image doing 'make telosb
install'?
Actually, the command;
make telosb install
does not work. Thus, I used the following command to load GoldenImage into
'Sensenode':
/usr/local/msp430/bin/msp430-bsl -r -e -I --invert-reset --invert-test -c
/dev/ttyUSB0 -p
/opt/tinyos-2.1.0/apps/tests/deluge/GoldenImage/build/telosb/main.ihex
Note: if you run the latest CVS (highly recommended :D) you should use the
apps/tests/deluge/Basestation.
I work with XubunTOS-2.1.0 and i want to use tinyos-tools in XubunTOS-2.1.0
in order to not to make things complicated. Otherwise, after installing
XubunTOS-2.1.0, i should download tinyos-2.x from CVS, then configure the
system... What i want is to establish
Re: [Tinyos-help] Deluge T2 problem on a NEW platform
Hello Razvan,
Besides TelosB and MICAz, I have some custom motes called 'Sensenode'.
Actually, it is completely the same as TelosB but has an extra sensor board
on it. (Sensenode has the same MCU, Flash, Radio... with that of TelosB).
When i load a program image which is build for TelosB into Sensenode, it
works as well.
Now, I want to use Deluge T2 for 'Sensenode' as i can use it for TelosB and
MICAz motes.
First of all, i tried to load some images into the flash of 'Sensenode' and
then reprogram it from those images. i took the following steps;
1-) Build GoldenImage with the following command;
CFLAGS=-DDELUGE_BASESTATION make telosb
and then load the image into 'Sensenode'.
2-) Build /op/tinyos-2.1.0/apps/tests/deluge/Blink with the following
command;
make Telosb
3-) Inject Blink application image into the flash of 'Sensenode' with the
following command:
/usr/bin/tos-deluge /dev/ttyUSB0 telosb -i 1
/opt/tinyos-2.1.0/apps/tests/deluge/Blink/build/telosb/tos_image.xml
4-) Ping 'Sensenode' with the following command:
tos-deluge /dev/ttyUSB0 telosb -p 1
and i see that 'Sensenode' is loaded with GoldenImage and Blink application
image is on its flash as the 1st image.
5-) reprogram 'Sensenode' with the following command:
tos-deluge /dev/ttyUSB0 telosb -r 1
*Then nothing happens on the 'Sensenode'! *
**
*Before those steps; in order to make sure that 'Sensenode' could run
/opt/tinyos-2.1.0/apps/tests/deluge/Blink application, i loaded it into
'Sensenode' (after building for TelosB) and i saw that the mote blinks!*
**
*There seems a problem with the flash but i could'nt figure it out.*
**
*i checked hardware.h files for both platforms ('Sensenode' and TelosB) but
everything is the same.*
**
*i also checked * *the files and folders under
/opt/tinyos-2.1.0/tos/lib/net/deluge, i found that 5 or 6 files are
dependent on TelosB platform but as far as i saw, those files are related to
baud rate and flash specs which is the same for 'Sensenode'.*
**
*Actually, i want to ask which files should i check for compatible operation
of flah on the 'Sensenode' with the one on the TelosB. What could be the
difference? Which does Deluge T2 need for TelosB in terms of flash so that i
can check for them for 'Sensenode'?*
**
*Any suggestions?*
*Thanks in advence,*
Mehmet Akif Antepli
Graduate Student
Dept. of Electrical-Electronics Eng.
METU
On Sat, Feb 7, 2009 at 12:30 AM, Razvan Musaloiu-E. razv...@cs.jhu.eduwrote:
Hi!
On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote:
Hi Razvan,
I did all the five steps that i mentioned previously with your comment on
'-' for the first two steps as follows;
1-) CFLAGS=-DDELUGE_BASESTATION make micaz install,0 mib520,/dev/ttyUSB0
2-) CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install bsl,/dev/ttyUSB2
Then i *succeeded* to disseminate Blink and now, TelosB blinks :)
Thus, cross-platform issue is ok for MICAz and TelosB motes!
Great! :-)
However, after i run the last command
/usr/bin/tos-deluge /dev/ttyUSB1 micaz -dr 1
it took about *45* *seconds *to reboot TelosB itself. Does it normal?
That sounds about right.
--
Razvan ME
Thanks in advance,
Mehmet Akif Antepli
Graduate Student
Dept. of Electrical-Electronics Eng.
METU
On Fri, Feb 6, 2009 at 8:37 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu
wrote:
Hi!
On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote:
Hi Razvan,
Btw: make sure you don't forget the '-' in 'CFLAGS=-DDELUGE_BASESTATION'
and
'CFLAGS+=-DDELUGE_LIGHT_BASESTATION'. I presume it was a typo in your
original message. :-)
While writing the e-mail, actually I couldn't remember whether i used
'-' or not :-). But, i did not get any errors, that's for sure!
Anyhow, i don't remember the '-' thing for now, but this evening i
have a chance to go to lab and test it.
Thanks for your reply Razvan,
By the way, is there a mistake in the tos-deluge python script under
tinyos-2.x/tools/tinyos/misc?
Actually, I use TinyOS-2.1.0 in XubunTOS-2.1.0 but, I also downloaded
tinyos-2.x form CVS
to use python scripts related to tinyos-2.x/tools (altough they are
installled in Tinyos-2.1.0 under usr/bin). In the Deluge T2 document
(http://docs.tinyos.net/index.php/Deluge_T2) it says that;
Tools Installation
Deluge T2 requires a few Python scripts that not yet included in the
official tinyos-tools RPM package. On the CVS, the scripts are located
in tinyos-2.x/tools/tinyos/misc. The steps to install them are the
following:
% cd $TOSROOT/tools
% ./Bootstrap
...
% ./configure
...
% cd tinyos/misc
% make ; make install
...
For TinyOS-2.1.0, tos-deluge python script is in usr/bin
After i do those steps above, i have a second tos-deluge python script
but this time under usr/local/bin.Then, i do the 5 steps that i wrote
previously to implement application image dissemination, (but this
time by calling /usr/local/bin/tos-deluge).
If you don't give the '--prefix=...' to the ./configure
Re: [Tinyos-help] Deluge T2 problem on a NEW platform
Hi!
On Fri, 13 Feb 2009, Mehmet Akif Antepli wrote:
Hello Razvan,
Besides TelosB and MICAz, I have some custom motes called 'Sensenode'.
Actually, it is completely the same as TelosB but has an extra sensor board
on it. (Sensenode has the same MCU, Flash, Radio... with that of TelosB).
When i load a program image which is build for TelosB into Sensenode, it
works as well.
Quick question: for Sensenode do you upload the image doing 'make telosb
install'?
Now, I want to use Deluge T2 for 'Sensenode' as i can use it for TelosB and
MICAz motes.
First of all, i tried to load some images into the flash of 'Sensenode' and
then reprogram it from those images. i took the following steps;
1-) Build GoldenImage with the following command;
CFLAGS=-DDELUGE_BASESTATION make telosb
and then load the image into 'Sensenode'.
Note: if you run the latest CVS (highly recommended :D) you should use the
apps/tests/deluge/Basestation.
2-) Build /op/tinyos-2.1.0/apps/tests/deluge/Blink with the following
command;
make Telosb
3-) Inject Blink application image into the flash of 'Sensenode' with the
following command:
/usr/bin/tos-deluge /dev/ttyUSB0 telosb -i 1
/opt/tinyos-2.1.0/apps/tests/deluge/Blink/build/telosb/tos_image.xml
4-) Ping 'Sensenode' with the following command:
tos-deluge /dev/ttyUSB0 telosb -p 1
and i see that 'Sensenode' is loaded with GoldenImage and Blink application
image is on its flash as the 1st image.
5-) reprogram 'Sensenode' with the following command:
tos-deluge /dev/ttyUSB0 telosb -r 1
*Then nothing happens on the 'Sensenode'! *
**
*Before those steps; in order to make sure that 'Sensenode' could run
/opt/tinyos-2.1.0/apps/tests/deluge/Blink application, i loaded it into
'Sensenode' (after building for TelosB) and i saw that the mote blinks!*
**
*There seems a problem with the flash but i could'nt figure it out.*
**
*i checked hardware.h files for both platforms ('Sensenode' and TelosB) but
everything is the same.*
**
*i also checked * *the files and folders under
/opt/tinyos-2.1.0/tos/lib/net/deluge, i found that 5 or 6 files are
dependent on TelosB platform but as far as i saw, those files are related to
baud rate and flash specs which is the same for 'Sensenode'.*
**
*Actually, i want to ask which files should i check for compatible operation
of flah on the 'Sensenode' with the one on the TelosB. What could be the
difference? Which does Deluge T2 need for TelosB in terms of flash so that i
can check for them for 'Sensenode'?*
**
*Any suggestions?*
I think the problem might be in the tosboot (tos/lib/tosboot). There there
is some code that is responsible with reading stuff the external flash and
write it on the internal one. The code responsible with this is in
tos/lib/tosboot/stm25p for telos. The main component for tosboot is
TOSBootM.nc. I usually debug it using the leds.
All the best!
Razvan ME
On Sat, Feb 7, 2009 at 12:30 AM, Razvan Musaloiu-E. razv...@cs.jhu.eduwrote:
Hi!
On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote:
Hi Razvan,
I did all the five steps that i mentioned previously with your comment on
'-' for the first two steps as follows;
1-) CFLAGS=-DDELUGE_BASESTATION make micaz install,0 mib520,/dev/ttyUSB0
2-) CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install bsl,/dev/ttyUSB2
Then i *succeeded* to disseminate Blink and now, TelosB blinks :)
Thus, cross-platform issue is ok for MICAz and TelosB motes!
Great! :-)
However, after i run the last command
/usr/bin/tos-deluge /dev/ttyUSB1 micaz -dr 1
it took about *45* *seconds *to reboot TelosB itself. Does it normal?
That sounds about right.
--
Razvan ME
Thanks in advance,
Mehmet Akif Antepli
Graduate Student
Dept. of Electrical-Electronics Eng.
METU
On Fri, Feb 6, 2009 at 8:37 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu
wrote:
Hi!
On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote:
Hi Razvan,
Btw: make sure you don't forget the '-' in 'CFLAGS=-DDELUGE_BASESTATION'
and
'CFLAGS+=-DDELUGE_LIGHT_BASESTATION'. I presume it was a typo in your
original message. :-)
While writing the e-mail, actually I couldn't remember whether i used
'-' or not :-). But, i did not get any errors, that's for sure!
Anyhow, i don't remember the '-' thing for now, but this evening i
have a chance to go to lab and test it.
Thanks for your reply Razvan,
By the way, is there a mistake in the tos-deluge python script under
tinyos-2.x/tools/tinyos/misc?
Actually, I use TinyOS-2.1.0 in XubunTOS-2.1.0 but, I also downloaded
tinyos-2.x form CVS
to use python scripts related to tinyos-2.x/tools (altough they are
installled in Tinyos-2.1.0 under usr/bin). In the Deluge T2 document
(http://docs.tinyos.net/index.php/Deluge_T2) it says that;
Tools Installation
Deluge T2 requires a few Python scripts that not yet included in the
official tinyos-tools RPM package. On the CVS, the scripts are located
in
Re: [Tinyos-help] Deluge T2 problem on a NEW platform
Hobbs, do you know if maria will stay in our campsite or how many they
are? I think we still should have some space left.
Thomas
On 2/13/09, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote:
Hi!
On Fri, 13 Feb 2009, Mehmet Akif Antepli wrote:
Hello Razvan,
Besides TelosB and MICAz, I have some custom motes called 'Sensenode'.
Actually, it is completely the same as TelosB but has an extra sensor
board
on it. (Sensenode has the same MCU, Flash, Radio... with that of TelosB).
When i load a program image which is build for TelosB into Sensenode, it
works as well.
Quick question: for Sensenode do you upload the image doing 'make telosb
install'?
Now, I want to use Deluge T2 for 'Sensenode' as i can use it for TelosB
and
MICAz motes.
First of all, i tried to load some images into the flash of 'Sensenode'
and
then reprogram it from those images. i took the following steps;
1-) Build GoldenImage with the following command;
CFLAGS=-DDELUGE_BASESTATION make telosb
and then load the image into 'Sensenode'.
Note: if you run the latest CVS (highly recommended :D) you should use the
apps/tests/deluge/Basestation.
2-) Build /op/tinyos-2.1.0/apps/tests/deluge/Blink with the following
command;
make Telosb
3-) Inject Blink application image into the flash of 'Sensenode' with the
following command:
/usr/bin/tos-deluge /dev/ttyUSB0 telosb -i 1
/opt/tinyos-2.1.0/apps/tests/deluge/Blink/build/telosb/tos_image.xml
4-) Ping 'Sensenode' with the following command:
tos-deluge /dev/ttyUSB0 telosb -p 1
and i see that 'Sensenode' is loaded with GoldenImage and Blink
application
image is on its flash as the 1st image.
5-) reprogram 'Sensenode' with the following command:
tos-deluge /dev/ttyUSB0 telosb -r 1
*Then nothing happens on the 'Sensenode'! *
**
*Before those steps; in order to make sure that 'Sensenode' could run
/opt/tinyos-2.1.0/apps/tests/deluge/Blink application, i loaded it into
'Sensenode' (after building for TelosB) and i saw that the mote blinks!*
**
*There seems a problem with the flash but i could'nt figure it out.*
**
*i checked hardware.h files for both platforms ('Sensenode' and TelosB)
but
everything is the same.*
**
*i also checked * *the files and folders under
/opt/tinyos-2.1.0/tos/lib/net/deluge, i found that 5 or 6 files are
dependent on TelosB platform but as far as i saw, those files are related
to
baud rate and flash specs which is the same for 'Sensenode'.*
**
*Actually, i want to ask which files should i check for compatible
operation
of flah on the 'Sensenode' with the one on the TelosB. What could be the
difference? Which does Deluge T2 need for TelosB in terms of flash so that
i
can check for them for 'Sensenode'?*
**
*Any suggestions?*
I think the problem might be in the tosboot (tos/lib/tosboot). There there
is some code that is responsible with reading stuff the external flash and
write it on the internal one. The code responsible with this is in
tos/lib/tosboot/stm25p for telos. The main component for tosboot is
TOSBootM.nc. I usually debug it using the leds.
All the best!
Razvan ME
On Sat, Feb 7, 2009 at 12:30 AM, Razvan Musaloiu-E.
razv...@cs.jhu.eduwrote:
Hi!
On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote:
Hi Razvan,
I did all the five steps that i mentioned previously with your comment
on
'-' for the first two steps as follows;
1-) CFLAGS=-DDELUGE_BASESTATION make micaz install,0 mib520,/dev/ttyUSB0
2-) CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install
bsl,/dev/ttyUSB2
Then i *succeeded* to disseminate Blink and now, TelosB blinks :)
Thus, cross-platform issue is ok for MICAz and TelosB motes!
Great! :-)
However, after i run the last command
/usr/bin/tos-deluge /dev/ttyUSB1 micaz -dr 1
it took about *45* *seconds *to reboot TelosB itself. Does it normal?
That sounds about right.
--
Razvan ME
Thanks in advance,
Mehmet Akif Antepli
Graduate Student
Dept. of Electrical-Electronics Eng.
METU
On Fri, Feb 6, 2009 at 8:37 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu
wrote:
Hi!
On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote:
Hi Razvan,
Btw: make sure you don't forget the '-' in
'CFLAGS=-DDELUGE_BASESTATION' and
'CFLAGS+=-DDELUGE_LIGHT_BASESTATION'. I presume it was a typo in your
original message. :-)
While writing the e-mail, actually I couldn't remember whether i used
'-' or not :-). But, i did not get any errors, that's for sure!
Anyhow, i don't remember the '-' thing for now, but this evening i
have a chance to go to lab and test it.
Thanks for your reply Razvan,
By the way, is there a mistake in the tos-deluge python script under
tinyos-2.x/tools/tinyos/misc?
Actually, I use TinyOS-2.1.0 in XubunTOS-2.1.0 but, I also downloaded
tinyos-2.x form CVS
to use python scripts related to tinyos-2.x/tools (altough they are
installled in Tinyos-2.1.0 under usr/bin). In the Deluge T2 document
Re: [Tinyos-help] Deluge T2 problem on a NEW platform
Hi Razvan, First of all, thanks for your reply and suggestion. On Fri, Feb 13, 2009 at 10:40 PM, Razvan Musaloiu-E. razv...@cs.jhu.eduwrote: Quick question: for Sensenode do you upload the image doing 'make telosb install'? Actually, the command; make telosb install does not work. Thus, I used the following command to load GoldenImage into 'Sensenode': /usr/local/msp430/bin/msp430-bsl -r -e -I --invert-reset --invert-test -c /dev/ttyUSB0 -p /opt/tinyos-2.1.0/apps/tests/deluge/GoldenImage/build/telosb/main.ihex Note: if you run the latest CVS (highly recommended :D) you should use the apps/tests/deluge/Basestation. I work with XubunTOS-2.1.0 and i want to use tinyos-tools in XubunTOS-2.1.0 in order to not to make things complicated. Otherwise, after installing XubunTOS-2.1.0, i should download tinyos-2.x from CVS, then configure the system... What i want is to establish development environment in one step (maybe two :-)). But it seems that even XubunTOS-2.1.0 lacks the whole capability. If it doesn't work with tinyos-tools in XubunTOS-2.1.0, i promise i will try the latest CVS :-) I think the problem might be in the tosboot (tos/lib/tosboot). There there is some code that is responsible with reading stuff the external flash and write it on the internal one. The code responsible with this is in tos/lib/tosboot/stm25p for telos. The main component for tosboot is TOSBootM.nc. I usually debug it using the leds. I will look the files you mentioned above, it seems to be a good hint. Thanks for your help, All the best! Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 dissemination problem on XubunTOS-2.1.0
Hi! Sorry for delay, I just noticed this thread. On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote: Hi Bai, Thanks for your reply. I flaged TelosB with Light_Base_Station since i want to ping TelosB, also. Therefore, i included this CFLAGS+=DDELUGE_LIGHT_BASESTATION in the 2nd step. It's not a mistake to use -DDELUGE_LIGHT_BASESTATION without any errors. I never test the cross-platform operation of Deluge T2 but I'll do it tomorrow. Btw: make sure you don't forget the '-' in 'CFLAGS=-DDELUGE_BASESTATION' and 'CFLAGS+=-DDELUGE_LIGHT_BASESTATION'. I presume it was a typo in your original message. :-) -- Razvan ME Anyhow, i will do the 2nd step without CFLAGS+=DDELUGE_LIGHT_BASESTATION again and see whether it works or not. Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU On Fri, Feb 6, 2009 at 2:15 AM, BAI LI libai0...@gmail.com wrote: Hi, I think your second step was not correct. You should not flag the telosb with base station since your micaz was working as base station now. you can normally install Goldimage on telosb with an id. Regards, Bai ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 dissemination problem on XubunTOS-2.1.0
Hi Razvan, Btw: make sure you don't forget the '-' in 'CFLAGS=-DDELUGE_BASESTATION' and 'CFLAGS+=-DDELUGE_LIGHT_BASESTATION'. I presume it was a typo in your original message. :-) While writing the e-mail, actually I couldn't remember whether i used '-' or not :-). But, i did not get any errors, that's for sure! Anyhow, i don't remember the '-' thing for now, but this evening i have a chance to go to lab and test it. Thanks for your reply Razvan, By the way, is there a mistake in the tos-deluge python script under tinyos-2.x/tools/tinyos/misc? Actually, I use TinyOS-2.1.0 in XubunTOS-2.1.0 but, I also downloaded tinyos-2.x form CVS to use python scripts related to tinyos-2.x/tools (altough they are installled in Tinyos-2.1.0 under usr/bin). In the Deluge T2 document (http://docs.tinyos.net/index.php/Deluge_T2) it says that; Tools Installation Deluge T2 requires a few Python scripts that not yet included in the official tinyos-tools RPM package. On the CVS, the scripts are located in tinyos-2.x/tools/tinyos/misc. The steps to install them are the following: % cd $TOSROOT/tools % ./Bootstrap ... % ./configure ... % cd tinyos/misc % make ; make install ... For TinyOS-2.1.0, tos-deluge python script is in usr/bin After i do those steps above, i have a second tos-deluge python script but this time under usr/local/bin.Then, i do the 5 steps that i wrote previously to implement application image dissemination, (but this time by calling /usr/local/bin/tos-deluge). However, i got an error related to tos.AM(), about missing parameters where in the code below (code in the /usr/local/bin/tos-deluge), there is not any argument for tos.AM(); 398 # MAIN # 399 if len(sys.argv) = 3: 400 401 am = tos.AM() what do you think about that? Have you ever been faced with that kind of an error, or i messed up everything relating to tinyos-tools? Note that: The first error event that i have been faced with, has nothing to do with that new error event becasue when i failed in the former, i tried the latter hoping to run dissemination! Thanks in advance, Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU On Fri, Feb 6, 2009 at 10:57 AM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! Sorry for delay, I just noticed this thread. On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote: Hi Bai, Thanks for your reply. I flaged TelosB with Light_Base_Station since i want to ping TelosB, also. Therefore, i included this CFLAGS+=DDELUGE_LIGHT_BASESTATION in the 2nd step. It's not a mistake to use -DDELUGE_LIGHT_BASESTATION without any errors. I never test the cross-platform operation of Deluge T2 but I'll do it tomorrow. Btw: make sure you don't forget the '-' in 'CFLAGS=-DDELUGE_BASESTATION' and 'CFLAGS+=-DDELUGE_LIGHT_BASESTATION'. I presume it was a typo in your original message. :-) -- Razvan ME Anyhow, i will do the 2nd step without CFLAGS+=DDELUGE_LIGHT_BASESTATION again and see whether it works or not. Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU On Fri, Feb 6, 2009 at 2:15 AM, BAI LI libai0...@gmail.com wrote: Hi, I think your second step was not correct. You should not flag the telosb with base station since your micaz was working as base station now. you can normally install Goldimage on telosb with an id. Regards, Bai ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 dissemination problem on XubunTOS-2.1.0
Hi! On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote: Hi Razvan, Btw: make sure you don't forget the '-' in 'CFLAGS=-DDELUGE_BASESTATION' and 'CFLAGS+=-DDELUGE_LIGHT_BASESTATION'. I presume it was a typo in your original message. :-) While writing the e-mail, actually I couldn't remember whether i used '-' or not :-). But, i did not get any errors, that's for sure! Anyhow, i don't remember the '-' thing for now, but this evening i have a chance to go to lab and test it. Thanks for your reply Razvan, By the way, is there a mistake in the tos-deluge python script under tinyos-2.x/tools/tinyos/misc? Actually, I use TinyOS-2.1.0 in XubunTOS-2.1.0 but, I also downloaded tinyos-2.x form CVS to use python scripts related to tinyos-2.x/tools (altough they are installled in Tinyos-2.1.0 under usr/bin). In the Deluge T2 document (http://docs.tinyos.net/index.php/Deluge_T2) it says that; Tools Installation Deluge T2 requires a few Python scripts that not yet included in the official tinyos-tools RPM package. On the CVS, the scripts are located in tinyos-2.x/tools/tinyos/misc. The steps to install them are the following: % cd $TOSROOT/tools % ./Bootstrap ... % ./configure ... % cd tinyos/misc % make ; make install ... For TinyOS-2.1.0, tos-deluge python script is in usr/bin After i do those steps above, i have a second tos-deluge python script but this time under usr/local/bin.Then, i do the 5 steps that i wrote previously to implement application image dissemination, (but this time by calling /usr/local/bin/tos-deluge). If you don't give the '--prefix=...' to the ./configure script then the default install path is /urs/local. The text from the wiki manual says this: By default, the files will be installed in /usr/local/bin. If desired, the --prefix parameter from configure can be used to indicate a different path. However, i got an error related to tos.AM(), about missing parameters where in the code below (code in the /usr/local/bin/tos-deluge), there is not any argument for tos.AM(); 398 # MAIN # 399 if len(sys.argv) = 3: 400 401 am = tos.AM() what do you think about that? Have you ever been faced with that kind of an error, or i messed up everything relating to tinyos-tools? The place of tos.py, the Python library used by the tos-deluge, changed from 2.1 and now is in $TOSDIR/support/sdk/python. In you case the tos-deluge might pick-up by mistake the old one from 2.1 -- Razvan ME Note that: The first error event that i have been faced with, has nothing to do with that new error event becasue when i failed in the former, i tried the latter hoping to run dissemination! Thanks in advance, Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU On Fri, Feb 6, 2009 at 10:57 AM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! Sorry for delay, I just noticed this thread. On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote: Hi Bai, Thanks for your reply. I flaged TelosB with Light_Base_Station since i want to ping TelosB, also. Therefore, i included this CFLAGS+=DDELUGE_LIGHT_BASESTATION in the 2nd step. It's not a mistake to use -DDELUGE_LIGHT_BASESTATION without any errors. I never test the cross-platform operation of Deluge T2 but I'll do it tomorrow. Btw: make sure you don't forget the '-' in 'CFLAGS=-DDELUGE_BASESTATION' and 'CFLAGS+=-DDELUGE_LIGHT_BASESTATION'. I presume it was a typo in your original message. :-) -- Razvan ME Anyhow, i will do the 2nd step without CFLAGS+=DDELUGE_LIGHT_BASESTATION again and see whether it works or not. Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU On Fri, Feb 6, 2009 at 2:15 AM, BAI LI libai0...@gmail.com wrote: Hi, I think your second step was not correct. You should not flag the telosb with base station since your micaz was working as base station now. you can normally install Goldimage on telosb with an id. Regards, Bai ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 dissemination problem on XubunTOS-2.1.0
Hi Razvan, I did all the five steps that i mentioned previously with your comment on '-' for the first two steps as follows; 1-) CFLAGS=-DDELUGE_BASESTATION make micaz install,0 mib520,/dev/ttyUSB0 2-) CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install bsl,/dev/ttyUSB2 Then i *succeeded* to disseminate Blink and now, TelosB blinks :) Thus, cross-platform issue is ok for MICAz and TelosB motes! However, after i run the last command /usr/bin/tos-deluge /dev/ttyUSB1 micaz -dr 1 it took about *45* *seconds *to reboot TelosB itself. Does it normal? Thanks in advance, Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU On Fri, Feb 6, 2009 at 8:37 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote: Hi Razvan, Btw: make sure you don't forget the '-' in 'CFLAGS=-DDELUGE_BASESTATION' and 'CFLAGS+=-DDELUGE_LIGHT_BASESTATION'. I presume it was a typo in your original message. :-) While writing the e-mail, actually I couldn't remember whether i used '-' or not :-). But, i did not get any errors, that's for sure! Anyhow, i don't remember the '-' thing for now, but this evening i have a chance to go to lab and test it. Thanks for your reply Razvan, By the way, is there a mistake in the tos-deluge python script under tinyos-2.x/tools/tinyos/misc? Actually, I use TinyOS-2.1.0 in XubunTOS-2.1.0 but, I also downloaded tinyos-2.x form CVS to use python scripts related to tinyos-2.x/tools (altough they are installled in Tinyos-2.1.0 under usr/bin). In the Deluge T2 document (http://docs.tinyos.net/index.php/Deluge_T2) it says that; Tools Installation Deluge T2 requires a few Python scripts that not yet included in the official tinyos-tools RPM package. On the CVS, the scripts are located in tinyos-2.x/tools/tinyos/misc. The steps to install them are the following: % cd $TOSROOT/tools % ./Bootstrap ... % ./configure ... % cd tinyos/misc % make ; make install ... For TinyOS-2.1.0, tos-deluge python script is in usr/bin After i do those steps above, i have a second tos-deluge python script but this time under usr/local/bin.Then, i do the 5 steps that i wrote previously to implement application image dissemination, (but this time by calling /usr/local/bin/tos-deluge). If you don't give the '--prefix=...' to the ./configure script then the default install path is /urs/local. The text from the wiki manual says this: By default, the files will be installed in /usr/local/bin. If desired, the --prefix parameter from configure can be used to indicate a different path. However, i got an error related to tos.AM(), about missing parameters where in the code below (code in the /usr/local/bin/tos-deluge), there is not any argument for tos.AM(); 398 # MAIN # 399 if len(sys.argv) = 3: 400 401 am = tos.AM() what do you think about that? Have you ever been faced with that kind of an error, or i messed up everything relating to tinyos-tools? The place of tos.py, the Python library used by the tos-deluge, changed from 2.1 and now is in $TOSDIR/support/sdk/python. In you case the tos-deluge might pick-up by mistake the old one from 2.1 -- Razvan ME Note that: The first error event that i have been faced with, has nothing to do with that new error event becasue when i failed in the former, i tried the latter hoping to run dissemination! Thanks in advance, Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU On Fri, Feb 6, 2009 at 10:57 AM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! Sorry for delay, I just noticed this thread. On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote: Hi Bai, Thanks for your reply. I flaged TelosB with Light_Base_Station since i want to ping TelosB, also. Therefore, i included this CFLAGS+=DDELUGE_LIGHT_BASESTATION in the 2nd step. It's not a mistake to use -DDELUGE_LIGHT_BASESTATION without any errors. I never test the cross-platform operation of Deluge T2 but I'll do it tomorrow. Btw: make sure you don't forget the '-' in 'CFLAGS=-DDELUGE_BASESTATION' and 'CFLAGS+=-DDELUGE_LIGHT_BASESTATION'. I presume it was a typo in your original message. :-) -- Razvan ME Anyhow, i will do the 2nd step without CFLAGS+=DDELUGE_LIGHT_BASESTATION again and see whether it works or not. Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU On Fri, Feb 6, 2009 at 2:15 AM, BAI LI libai0...@gmail.com wrote: Hi, I think your second step was not correct. You should not flag the telosb with base station since your micaz was working as base station now. you can normally install Goldimage on telosb with an id. Regards, Bai ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 dissemination problem on XubunTOS-2.1.0
Hi! On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote: Hi Razvan, I did all the five steps that i mentioned previously with your comment on '-' for the first two steps as follows; 1-) CFLAGS=-DDELUGE_BASESTATION make micaz install,0 mib520,/dev/ttyUSB0 2-) CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install bsl,/dev/ttyUSB2 Then i *succeeded* to disseminate Blink and now, TelosB blinks :) Thus, cross-platform issue is ok for MICAz and TelosB motes! Great! :-) However, after i run the last command /usr/bin/tos-deluge /dev/ttyUSB1 micaz -dr 1 it took about *45* *seconds *to reboot TelosB itself. Does it normal? That sounds about right. -- Razvan ME Thanks in advance, Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU On Fri, Feb 6, 2009 at 8:37 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote: Hi Razvan, Btw: make sure you don't forget the '-' in 'CFLAGS=-DDELUGE_BASESTATION' and 'CFLAGS+=-DDELUGE_LIGHT_BASESTATION'. I presume it was a typo in your original message. :-) While writing the e-mail, actually I couldn't remember whether i used '-' or not :-). But, i did not get any errors, that's for sure! Anyhow, i don't remember the '-' thing for now, but this evening i have a chance to go to lab and test it. Thanks for your reply Razvan, By the way, is there a mistake in the tos-deluge python script under tinyos-2.x/tools/tinyos/misc? Actually, I use TinyOS-2.1.0 in XubunTOS-2.1.0 but, I also downloaded tinyos-2.x form CVS to use python scripts related to tinyos-2.x/tools (altough they are installled in Tinyos-2.1.0 under usr/bin). In the Deluge T2 document (http://docs.tinyos.net/index.php/Deluge_T2) it says that; Tools Installation Deluge T2 requires a few Python scripts that not yet included in the official tinyos-tools RPM package. On the CVS, the scripts are located in tinyos-2.x/tools/tinyos/misc. The steps to install them are the following: % cd $TOSROOT/tools % ./Bootstrap ... % ./configure ... % cd tinyos/misc % make ; make install ... For TinyOS-2.1.0, tos-deluge python script is in usr/bin After i do those steps above, i have a second tos-deluge python script but this time under usr/local/bin.Then, i do the 5 steps that i wrote previously to implement application image dissemination, (but this time by calling /usr/local/bin/tos-deluge). If you don't give the '--prefix=...' to the ./configure script then the default install path is /urs/local. The text from the wiki manual says this: By default, the files will be installed in /usr/local/bin. If desired, the --prefix parameter from configure can be used to indicate a different path. However, i got an error related to tos.AM(), about missing parameters where in the code below (code in the /usr/local/bin/tos-deluge), there is not any argument for tos.AM(); 398 # MAIN # 399 if len(sys.argv) = 3: 400 401 am = tos.AM() what do you think about that? Have you ever been faced with that kind of an error, or i messed up everything relating to tinyos-tools? The place of tos.py, the Python library used by the tos-deluge, changed from 2.1 and now is in $TOSDIR/support/sdk/python. In you case the tos-deluge might pick-up by mistake the old one from 2.1 -- Razvan ME Note that: The first error event that i have been faced with, has nothing to do with that new error event becasue when i failed in the former, i tried the latter hoping to run dissemination! Thanks in advance, Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU On Fri, Feb 6, 2009 at 10:57 AM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! Sorry for delay, I just noticed this thread. On Fri, 6 Feb 2009, Mehmet Akif Antepli wrote: Hi Bai, Thanks for your reply. I flaged TelosB with Light_Base_Station since i want to ping TelosB, also. Therefore, i included this CFLAGS+=DDELUGE_LIGHT_BASESTATION in the 2nd step. It's not a mistake to use -DDELUGE_LIGHT_BASESTATION without any errors. I never test the cross-platform operation of Deluge T2 but I'll do it tomorrow. Btw: make sure you don't forget the '-' in 'CFLAGS=-DDELUGE_BASESTATION' and 'CFLAGS+=-DDELUGE_LIGHT_BASESTATION'. I presume it was a typo in your original message. :-) -- Razvan ME Anyhow, i will do the 2nd step without CFLAGS+=DDELUGE_LIGHT_BASESTATION again and see whether it works or not. Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU On Fri, Feb 6, 2009 at 2:15 AM, BAI LI libai0...@gmail.com wrote: Hi, I think your second step was not correct. You should not flag the telosb with base station since your micaz was working as base station now. you can normally install Goldimage on telosb with an id. Regards, Bai ___ Tinyos-help mailing
Re: [Tinyos-help] Deluge T2 dissemination problem on XubunTOS-2.1.0
Hi, I think your second step was not correct. You should not flag the telosb with base station since your micaz was working as base station now. you can normally install Goldimage on telosb with an id. Regards, Bai ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 dissemination problem on XubunTOS-2.1.0
Hi Bai, Thanks for your reply. I flaged TelosB with Light_Base_Station since i want to ping TelosB, also. Therefore, i included this CFLAGS+=DDELUGE_LIGHT_BASESTATION in the 2nd step. Anyhow, i will do the 2nd step without CFLAGS+=DDELUGE_LIGHT_BASESTATION again and see whether it works or not. Mehmet Akif Antepli Graduate Student Dept. of Electrical-Electronics Eng. METU On Fri, Feb 6, 2009 at 2:15 AM, BAI LI libai0...@gmail.com wrote: Hi, I think your second step was not correct. You should not flag the telosb with base station since your micaz was working as base station now. you can normally install Goldimage on telosb with an id. Regards, Bai ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge t2 dessimination problem
Hi! On Mon, 19 Jan 2009, Pratik Gupte wrote: Hi, Even I'm facing the same problem with both telosb and micaz motes as per instructions on http://docs.tinyos.net/index.php/Deluge_T2 and unfortunately there were no replies to this post. Also while going through the tinyos mailing list archives on problem on dissemination of deluge T2 http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026270.html, I tried to reproduce the steps in the archive, replacing appropriately commands for micaz and mib520 board - I face the same problem (as the problem in the archive)- Base Station has Version 1, but after dissemination the node in air still has version 0. I'm a little confused about what doesn't work. What does node in air means? :-) Also: do you have the problem in Windows or Linux? I'll retest tomorrow the burn and burn-net. -- Razvan ME On Mon, Jan 5, 2009 at 6:09 PM, d...@student.dei.uc.pt wrote: Hey everyone, I've been following the deluge t2 tutorial in wiki, and when i'm trying to disseminate, this problem occurs: Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 405, in module ident(timeout=5) File /usr/local/bin/tos-deluge, line 153, in ident if am.write(sreqpkt, FM_AMID, timeout=timeout): File C:\cygwin\opt\tinyos-2.x/support/sdk/python/tos.py, line 440, in write r = super(AM, self).write(packet, amId, timeout, blocking) File C:\cygwin\opt\tinyos-2.x/support/sdk/python/tos.py, line 398, in write return ack.seqno == self.seqno UnboundLocalError: local variable 'ack' referenced before assignment Even though the Windows path have the slashes backwards it still reads the files. I'm using micaz motes, gateway mib520. Cheers, Daniel ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge t2 dessimination problem
Hi Razvan, Sorry for the confusion. I'm using the latest version of deluge and TinyOS 2.x from the tinyos CVS on linux (Ubuntu 8.04). I'm re-writing down exactly whatever I have tried: Setting up the basestation (mote 0) /opt/tinyos-2.x/apps/tests/deluge/Basestation make telosb install,0 bsl,/dev/ttyUSB0 Similarly I setup the client node (mote 1) with the Golden Image. Then I again connect mote 0 and transfer a Blink app with DelugeC component and the Makefile with BOOTLOADER=tosboot then make telosb then I transfer the above image to mote 0 using tos-deluge serial@/dev/ttyUSB0:115200 -i 1 build/telosb/tos_image.xml Everything works fine and even tos-deluge serial@/dev/ttyUSB0:115200 -p 1 shows the Currently running BaseStationAppC and BlinkAppC (stored image 1) as the other volume I power on mote 1 now with batteries and type the following command tos-deluge serial@/dev/ttyUSB0:115200 -dr 1 Command Sent Mote 1 does nothing and it doesn't boot up with the Blink app. Just to check what Mote 1 has I repeated the above steps and compiled the GoldenImage with CFLAGS=-DDELUGE_BASESTATION for Mote 1 also and finally the command tos-deluge serial@/dev/ttyUSB0:115200 -p 1 shows only the GoldenImage on Mote 1. 2nd Attempt on the steps on the mail archive http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026204.html Replicating the above steps appropriately, I get the same error as in the above mail and as described as above, i.e. Mote 1 does not receive the new version. By node in air I meant about the nodes connected through batteries and expecting the disseminated code from the base station. Regards, Pratik On Mon, Jan 19, 2009 at 1:49 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Mon, 19 Jan 2009, Pratik Gupte wrote: Hi, Even I'm facing the same problem with both telosb and micaz motes as per instructions on http://docs.tinyos.net/index.php/Deluge_T2 and unfortunately there were no replies to this post. Also while going through the tinyos mailing list archives on problem on dissemination of deluge T2 http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026270.html, I tried to reproduce the steps in the archive, replacing appropriately commands for micaz and mib520 board - I face the same problem (as the problem in the archive)- Base Station has Version 1, but after dissemination the node in air still has version 0. I'm a little confused about what doesn't work. What does node in air means? :-) Also: do you have the problem in Windows or Linux? I'll retest tomorrow the burn and burn-net. -- Razvan ME On Mon, Jan 5, 2009 at 6:09 PM, d...@student.dei.uc.pt wrote: Hey everyone, I've been following the deluge t2 tutorial in wiki, and when i'm trying to disseminate, this problem occurs: Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 405, in module ident(timeout=5) File /usr/local/bin/tos-deluge, line 153, in ident if am.write(sreqpkt, FM_AMID, timeout=timeout): File C:\cygwin\opt\tinyos-2.x/support/sdk/python/tos.py, line 440, in write r = super(AM, self).write(packet, amId, timeout, blocking) File C:\cygwin\opt\tinyos-2.x/support/sdk/python/tos.py, line 398, in write return ack.seqno == self.seqno UnboundLocalError: local variable 'ack' referenced before assignment Even though the Windows path have the slashes backwards it still reads the files. I'm using micaz motes, gateway mib520. Cheers, Daniel ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge t2 dessimination problem
Hi! On Mon, 19 Jan 2009, Pratik Gupte wrote: Hi Razvan, Sorry for the confusion. I'm using the latest version of deluge and TinyOS 2.x from the tinyos CVS on linux (Ubuntu 8.04). I'm re-writing down exactly whatever I have tried: Setting up the basestation (mote 0) /opt/tinyos-2.x/apps/tests/deluge/Basestation make telosb install,0 bsl,/dev/ttyUSB0 Similarly I setup the client node (mote 1) with the Golden Image. The DELUGE_LIGHT_BASESTATION is disabled in the Makefile from GoldenImage so you will not be able to ping the node. Then I again connect mote 0 and transfer a Blink app with DelugeC component and the Makefile with BOOTLOADER=tosboot then make telosb The Blink from apps/tests/deluge also has the DELUGE_LIGHT_BASESTATION disabled in the Makefile so the mote that will reboot in this image will not respond to ping. then I transfer the above image to mote 0 using tos-deluge serial@/dev/ttyUSB0:115200 -i 1 build/telosb/tos_image.xml Everything works fine and even tos-deluge serial@/dev/ttyUSB0:115200 -p 1 shows the Currently running BaseStationAppC and BlinkAppC (stored image 1) as the other volume I power on mote 1 now with batteries and type the following command tos-deluge serial@/dev/ttyUSB0:115200 -dr 1 Command Sent Mote 1 does nothing and it doesn't boot up with the Blink app. I just verify that the node id works fine. Here is the manual steps: - plug a mote in ttyUSB0 and burn the deluge/Basestation on it: make telosb install,0 - plug another mote in ttyUSB1 and burn the deluge/GoldenImage with the DELUGE_LIGHT_BASESTATION enabled: CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install,10 bsl,/dev/ttyUSB1 - compile deluge/Blink with DELUGE_LIGHT_BASESTATION enabled: CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install - upload the deluge/Blink to Basestation: tos-deluge serial@/dev/ttyUSB0:115200 -i 1 build/telosb/tos_image.xml - start the dissemination-and-reboot: tos-deluge serial@/dev/ttyUSB0:115200 -dr 1 - after the dissemination is over the mote on ttyUSB1 will blink. To make sure it has the expected node id you have to ping it: tos-deluge serial@/dev/ttyUSB1:115200 -p 1 Just to check what Mote 1 has I repeated the above steps and compiled the GoldenImage with CFLAGS=-DDELUGE_BASESTATION for Mote 1 also and finally the command A mote with DELUGE_BASESTATION will behave as a client. tos-deluge serial@/dev/ttyUSB0:115200 -p 1 shows only the GoldenImage on Mote 1. 2nd Attempt on the steps on the mail archive http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026204.html Replicating the above steps appropriately, I get the same error as in the above mail and as described as above, i.e. Mote 1 does not receive the new version. The error you indicate will happen when you try to ping a mote that is not compiled with DELUGE_BASESTATION or DELUGE_LIGHT_BASESTATION. I'll add some code to print a better message for this. By node in air I meant about the nodes connected through batteries and expecting the disseminated code from the base station. One more thing: make sure the voltage of the batteries is above 2.7V. A mote will not reboot if the voltage is lower than that. And one last thing: the GoldenImage doesn't have any leds enabled so the progress of Deluge will not be indicated in any way. You can enabled them by adding the following lines to the GoldenImageAppC.nc: components LedsC; DelugeC.Leds - LedsC; All the best! Razvan ME On Mon, Jan 19, 2009 at 1:49 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Mon, 19 Jan 2009, Pratik Gupte wrote: Hi, Even I'm facing the same problem with both telosb and micaz motes as per instructions on http://docs.tinyos.net/index.php/Deluge_T2 and unfortunately there were no replies to this post. Also while going through the tinyos mailing list archives on problem on dissemination of deluge T2 http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026270.html, I tried to reproduce the steps in the archive, replacing appropriately commands for micaz and mib520 board - I face the same problem (as the problem in the archive)- Base Station has Version 1, but after dissemination the node in air still has version 0. I'm a little confused about what doesn't work. What does node in air means? :-) Also: do you have the problem in Windows or Linux? I'll retest tomorrow the burn and burn-net. -- Razvan ME On Mon, Jan 5, 2009 at 6:09 PM, d...@student.dei.uc.pt wrote: Hey everyone, I've been following the deluge t2 tutorial in wiki, and when i'm trying to disseminate, this problem occurs: Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 405, in module ident(timeout=5) File /usr/local/bin/tos-deluge, line 153, in ident if am.write(sreqpkt, FM_AMID, timeout=timeout): File
Re: [Tinyos-help] Deluge t2 dessimination problem
Hey, I also will try your solution Razvan. Although i think that, some of this information should be on wiki: -battery level -CFLAGS=-DDELUGE_LIGHT_BASESTATION with GoldenImage (maybe its there but i didn't realized at that time) -components LedsC; DelugeC.Leds - LedsC; Thanks for your support, Daniel. Hi! On Mon, 19 Jan 2009, Pratik Gupte wrote: Hi Razvan, Sorry for the confusion. I'm using the latest version of deluge and TinyOS 2.x from the tinyos CVS on linux (Ubuntu 8.04). I'm re-writing down exactly whatever I have tried: Setting up the basestation (mote 0) /opt/tinyos-2.x/apps/tests/deluge/Basestation make telosb install,0 bsl,/dev/ttyUSB0 Similarly I setup the client node (mote 1) with the Golden Image. The DELUGE_LIGHT_BASESTATION is disabled in the Makefile from GoldenImage so you will not be able to ping the node. Then I again connect mote 0 and transfer a Blink app with DelugeC component and the Makefile with BOOTLOADER=tosboot then make telosb The Blink from apps/tests/deluge also has the DELUGE_LIGHT_BASESTATION disabled in the Makefile so the mote that will reboot in this image will not respond to ping. then I transfer the above image to mote 0 using tos-deluge serial@/dev/ttyUSB0:115200 -i 1 build/telosb/tos_image.xml Everything works fine and even tos-deluge serial@/dev/ttyUSB0:115200 -p 1 shows the Currently running BaseStationAppC and BlinkAppC (stored image 1) as the other volume I power on mote 1 now with batteries and type the following command tos-deluge serial@/dev/ttyUSB0:115200 -dr 1 Command Sent Mote 1 does nothing and it doesn't boot up with the Blink app. I just verify that the node id works fine. Here is the manual steps: - plug a mote in ttyUSB0 and burn the deluge/Basestation on it: make telosb install,0 - plug another mote in ttyUSB1 and burn the deluge/GoldenImage with the DELUGE_LIGHT_BASESTATION enabled: CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install,10 bsl,/dev/ttyUSB1 - compile deluge/Blink with DELUGE_LIGHT_BASESTATION enabled: CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install - upload the deluge/Blink to Basestation: tos-deluge serial@/dev/ttyUSB0:115200 -i 1 build/telosb/tos_image.xml - start the dissemination-and-reboot: tos-deluge serial@/dev/ttyUSB0:115200 -dr 1 - after the dissemination is over the mote on ttyUSB1 will blink. To make sure it has the expected node id you have to ping it: tos-deluge serial@/dev/ttyUSB1:115200 -p 1 Just to check what Mote 1 has I repeated the above steps and compiled the GoldenImage with CFLAGS=-DDELUGE_BASESTATION for Mote 1 also and finally the command A mote with DELUGE_BASESTATION will behave as a client. tos-deluge serial@/dev/ttyUSB0:115200 -p 1 shows only the GoldenImage on Mote 1. 2nd Attempt on the steps on the mail archive http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026204.html Replicating the above steps appropriately, I get the same error as in the above mail and as described as above, i.e. Mote 1 does not receive the new version. The error you indicate will happen when you try to ping a mote that is not compiled with DELUGE_BASESTATION or DELUGE_LIGHT_BASESTATION. I'll add some code to print a better message for this. By node in air I meant about the nodes connected through batteries and expecting the disseminated code from the base station. One more thing: make sure the voltage of the batteries is above 2.7V. A mote will not reboot if the voltage is lower than that. And one last thing: the GoldenImage doesn't have any leds enabled so the progress of Deluge will not be indicated in any way. You can enabled them by adding the following lines to the GoldenImageAppC.nc: components LedsC; DelugeC.Leds - LedsC; All the best! Razvan ME On Mon, Jan 19, 2009 at 1:49 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Mon, 19 Jan 2009, Pratik Gupte wrote: Hi, Even I'm facing the same problem with both telosb and micaz motes as per instructions on http://docs.tinyos.net/index.php/Deluge_T2 and unfortunately there were no replies to this post. Also while going through the tinyos mailing list archives on problem on dissemination of deluge T2 http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026270.html, I tried to reproduce the steps in the archive, replacing appropriately commands for micaz and mib520 board - I face the same problem (as the problem in the archive)- Base Station has Version 1, but after dissemination the node in air still has version 0. I'm a little confused about what doesn't work. What does node in air means? :-) Also: do you have the problem in Windows or Linux? I'll retest tomorrow the burn and burn-net. -- Razvan ME On Mon, Jan 5,
Re: [Tinyos-help] Deluge t2 dessimination problem
Hi! On Mon, 19 Jan 2009, d...@student.dei.uc.pt wrote: Hey, I also will try your solution Razvan. Although i think that, some of this information should be on wiki: -battery level I added this to the wiki. -CFLAGS=-DDELUGE_LIGHT_BASESTATION with GoldenImage (maybe its there but i didn't realized at that time) -components LedsC; DelugeC.Leds - LedsC; I committed these changes in the tree. :-) All the best! Razvan ME Hi! On Mon, 19 Jan 2009, Pratik Gupte wrote: Hi Razvan, Sorry for the confusion. I'm using the latest version of deluge and TinyOS 2.x from the tinyos CVS on linux (Ubuntu 8.04). I'm re-writing down exactly whatever I have tried: Setting up the basestation (mote 0) /opt/tinyos-2.x/apps/tests/deluge/Basestation make telosb install,0 bsl,/dev/ttyUSB0 Similarly I setup the client node (mote 1) with the Golden Image. The DELUGE_LIGHT_BASESTATION is disabled in the Makefile from GoldenImage so you will not be able to ping the node. Then I again connect mote 0 and transfer a Blink app with DelugeC component and the Makefile with BOOTLOADER=tosboot then make telosb The Blink from apps/tests/deluge also has the DELUGE_LIGHT_BASESTATION disabled in the Makefile so the mote that will reboot in this image will not respond to ping. then I transfer the above image to mote 0 using tos-deluge serial@/dev/ttyUSB0:115200 -i 1 build/telosb/tos_image.xml Everything works fine and even tos-deluge serial@/dev/ttyUSB0:115200 -p 1 shows the Currently running BaseStationAppC and BlinkAppC (stored image 1) as the other volume I power on mote 1 now with batteries and type the following command tos-deluge serial@/dev/ttyUSB0:115200 -dr 1 Command Sent Mote 1 does nothing and it doesn't boot up with the Blink app. I just verify that the node id works fine. Here is the manual steps: - plug a mote in ttyUSB0 and burn the deluge/Basestation on it: make telosb install,0 - plug another mote in ttyUSB1 and burn the deluge/GoldenImage with the DELUGE_LIGHT_BASESTATION enabled: CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install,10 bsl,/dev/ttyUSB1 - compile deluge/Blink with DELUGE_LIGHT_BASESTATION enabled: CFLAGS=-DDELUGE_LIGHT_BASESTATION make telosb install - upload the deluge/Blink to Basestation: tos-deluge serial@/dev/ttyUSB0:115200 -i 1 build/telosb/tos_image.xml - start the dissemination-and-reboot: tos-deluge serial@/dev/ttyUSB0:115200 -dr 1 - after the dissemination is over the mote on ttyUSB1 will blink. To make sure it has the expected node id you have to ping it: tos-deluge serial@/dev/ttyUSB1:115200 -p 1 Just to check what Mote 1 has I repeated the above steps and compiled the GoldenImage with CFLAGS=-DDELUGE_BASESTATION for Mote 1 also and finally the command A mote with DELUGE_BASESTATION will behave as a client. tos-deluge serial@/dev/ttyUSB0:115200 -p 1 shows only the GoldenImage on Mote 1. 2nd Attempt on the steps on the mail archive http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026204.html Replicating the above steps appropriately, I get the same error as in the above mail and as described as above, i.e. Mote 1 does not receive the new version. The error you indicate will happen when you try to ping a mote that is not compiled with DELUGE_BASESTATION or DELUGE_LIGHT_BASESTATION. I'll add some code to print a better message for this. By node in air I meant about the nodes connected through batteries and expecting the disseminated code from the base station. One more thing: make sure the voltage of the batteries is above 2.7V. A mote will not reboot if the voltage is lower than that. And one last thing: the GoldenImage doesn't have any leds enabled so the progress of Deluge will not be indicated in any way. You can enabled them by adding the following lines to the GoldenImageAppC.nc: components LedsC; DelugeC.Leds - LedsC; All the best! Razvan ME On Mon, Jan 19, 2009 at 1:49 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: Hi! On Mon, 19 Jan 2009, Pratik Gupte wrote: Hi, Even I'm facing the same problem with both telosb and micaz motes as per instructions on http://docs.tinyos.net/index.php/Deluge_T2 and unfortunately there were no replies to this post. Also while going through the tinyos mailing list archives on problem on dissemination of deluge T2 http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026270.html, I tried to reproduce the steps in the archive, replacing appropriately commands for micaz and mib520 board - I face the same problem (as the problem in the archive)- Base Station has Version 1, but after dissemination the node in air still has version 0. I'm a little confused about what doesn't work. What does node in air means? :-) Also: do you have the problem in Windows or Linux? I'll retest tomorrow the burn and burn-net.
Re: [Tinyos-help] Deluge t2 dessimination problem
Hi, The voltage level for reboot can be changed right? Where can I find the file defined and change it? Thanks Regards, Bai ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge t2 dessimination problem
Hi! On Tue, 20 Jan 2009, BAI LI wrote: Hi, The voltage level for reboot can be changed right? Where can I find the file defined and change it? Look for ReprogramGuardP.nc in lib/net/Deluge/extra and for VoltageC.nc in lib/net/tosboot. -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge t2 dessimination problem
Hi, Even I'm facing the same problem with both telosb and micaz motes as per instructions on http://docs.tinyos.net/index.php/Deluge_T2 and unfortunately there were no replies to this post. Also while going through the tinyos mailing list archives on problem on dissemination of deluge T2 http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2007-June/026270.html, I tried to reproduce the steps in the archive, replacing appropriately commands for micaz and mib520 board - I face the same problem (as the problem in the archive)- Base Station has Version 1, but after dissemination the node in air still has version 0. Regards, Pratik On Mon, Jan 5, 2009 at 6:09 PM, d...@student.dei.uc.pt wrote: Hey everyone, I've been following the deluge t2 tutorial in wiki, and when i'm trying to disseminate, this problem occurs: Traceback (most recent call last): File /usr/local/bin/tos-deluge, line 405, in module ident(timeout=5) File /usr/local/bin/tos-deluge, line 153, in ident if am.write(sreqpkt, FM_AMID, timeout=timeout): File C:\cygwin\opt\tinyos-2.x/support/sdk/python/tos.py, line 440, in write r = super(AM, self).write(packet, amId, timeout, blocking) File C:\cygwin\opt\tinyos-2.x/support/sdk/python/tos.py, line 398, in write return ack.seqno == self.seqno UnboundLocalError: local variable 'ack' referenced before assignment Even though the Windows path have the slashes backwards it still reads the files. I'm using micaz motes, gateway mib520. Cheers, Daniel This message was sent using IMP, the Internet Messaging Program. ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge: unable to initialize the port connection
Hi! On Mon, 29 Dec 2008, BAI LI wrote: Hi, I have a question regarding to the Deluge. Normally when the port ID is less than 10, I can install the application with base station flag and inject the program later. But when the port number become bigger, i still can install the application with base station flag but fail to inject the new image. the following is the error i captured i don't understand. Is there any restriction on port id? Thanks in advance. e...@wsn /opt/tinyos-2.x/apps/Blink1 $ tos-deluge /dev/ttyS26 telosb -p 0 ERROR: Unable to initialize serial port connection to /dev/ttyS26 You try clean up the Windows's knowledge about the FTDI ports using the FTClean from here: http://www.ftdichip.com/Resources/Utilities.htm I have a Windows box and when it will go beyond 10 I'll try to see if I can make it behave better. :-) -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 and TOS_NODE_ID
Hi! On Fri, 19 Dec 2008, Jamie Macbeth wrote: Hi, Razvan, I just did a simple test of the restoration of TOS_NODE_ID on the iris. Now it seems to work properly! I think earlier I was using a stale app image in which DelugeC wasn't properly wired in. Sorry for troubling you. By the way, I was required to copy over the volumes-*.xml files in order for the iris image to build with DelugeC wired in and with BOOTLOADER=tosboot in the Makefile. It may be worthwhile to add this to the instructions in the Deluge T2 Wiki or elsewhere. The BOOTLOADER=tosboot was already in the manual. I also added the instruction about volumes-*.xml. Thanks for catching this problem! :-) -- Razvan ME DelugeC.nc doesn't build without the volumes-*.xml files, and that caused me to attempt to disseminate images without it, which, I think, in the end, caused my trouble with TOS_NODE_ID. Much thanks, Jamie On Mon, Dec 15, 2008 at 4:08 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: The TOS_NODE_ID is hard-coded on the app.c but upon boot the DelugeC is restoring it. The code that is doing this for IRIS is the Init.init from tos/lib/net/Deluge/extra/iris/NetProgM.nc. I'll check tomorrow on MicaZ to see if everything works as it should. I just tested MicaZ and it works fine. The TOS_NODE_ID is properly restored after a -dr command. Janos, can you confirm this result for IRIS? :-) -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 and TOS_NODE_ID
Hi, Rasvan, I just did a simple test of the restoration of TOS_NODE_ID on the iris. Now it seems to work properly! I think earlier I was using a stale app image in which DelugeC wasn't properly wired in. Sorry for troubling you. By the way, I was required to copy over the volumes-*.xml files in order for the iris image to build with DelugeC wired in and with BOOTLOADER=tosboot in the Makefile. It may be worthwhile to add this to the instructions in the Deluge T2 Wiki or elsewhere. DelugeC.nc doesn't build without the volumes-*.xml files, and that caused me to attempt to disseminate images without it, which, I think, in the end, caused my trouble with TOS_NODE_ID. Much thanks, Jamie On Mon, Dec 15, 2008 at 4:08 PM, Razvan Musaloiu-E. razv...@cs.jhu.edu wrote: The TOS_NODE_ID is hard-coded on the app.c but upon boot the DelugeC is restoring it. The code that is doing this for IRIS is the Init.init from tos/lib/net/Deluge/extra/iris/NetProgM.nc. I'll check tomorrow on MicaZ to see if everything works as it should. I just tested MicaZ and it works fine. The TOS_NODE_ID is properly restored after a -dr command. Janos, can you confirm this result for IRIS? :-) -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 and TOS_NODE_ID
Hi! On Sun, 14 Dec 2008, Jamie Macbeth wrote: I'm running Tinyos-2.x from CVS on iris motes. I'm trying run Deluge T2, and in my application every node needs to know its ID. Dissemination and reboot seem to work properly for all of the Deluge connected nodes, but TOS_NODE_ID is identical for all nodes when I use it in my app. With some searching I felt assured that TOS_NODE_ID is being hard-coded in the c source created in the build process (build/iris/app.c). So I guess that TOS_NODE_ID isn't supposed to work with Deluge. When I Deluge-ping nodes connected via serial they seem to know their node ids... I assume that they are being read from storage. How can I ID in tinyos applications that are disseminated through Deluge? The TOS_NODE_ID is hard-coded on the app.c but upon boot the DelugeC is restoring it. The code that is doing this for IRIS is the Init.init from tos/lib/net/Deluge/extra/iris/NetProgM.nc. I'll check tomorrow on MicaZ to see if everything works as it should. -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge T2 and TOS_NODE_ID
Hi! On Mon, 15 Dec 2008, Razvan Musaloiu-E. wrote: Hi! On Sun, 14 Dec 2008, Jamie Macbeth wrote: I'm running Tinyos-2.x from CVS on iris motes. I'm trying run Deluge T2, and in my application every node needs to know its ID. Dissemination and reboot seem to work properly for all of the Deluge connected nodes, but TOS_NODE_ID is identical for all nodes when I use it in my app. With some searching I felt assured that TOS_NODE_ID is being hard-coded in the c source created in the build process (build/iris/app.c). So I guess that TOS_NODE_ID isn't supposed to work with Deluge. When I Deluge-ping nodes connected via serial they seem to know their node ids... I assume that they are being read from storage. How can I ID in tinyos applications that are disseminated through Deluge? The TOS_NODE_ID is hard-coded on the app.c but upon boot the DelugeC is restoring it. The code that is doing this for IRIS is the Init.init from tos/lib/net/Deluge/extra/iris/NetProgM.nc. I'll check tomorrow on MicaZ to see if everything works as it should. I just tested MicaZ and it works fine. The TOS_NODE_ID is properly restored after a -dr command. Janos, can you confirm this result for IRIS? :-) -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge Reference tinyos 2.x
Hi! On Wed, 29 Oct 2008, Gireesh P wrote: Hi , So if I want to rewrite a part of program memory, can you tell me what are the minimum steps I should take? ( For example memory location loc1 has to be modified and new value is stored in external flash. It should first read from flash, find the program memory to be modified and rewrite that and reboot) First of all I highly recommend a careful study of the MSP430 and the ATmega128 specs. The two architectures are quite different and they have different limitation. In tosboot the writing is done using a component called ProgFlashM.nc. There is one in tos/lib/tosboot/msp430 and another one in tos/lib/tosboot/avr. The function that is using it is the programImage from TOSBootM.nc from tos/lib/tosboot. -- Razvan ME On Tue, Oct 28, 2008 at 11:16 PM, Razvan Musaloiu-E. [EMAIL PROTECTED]wrote: Hi! On Tue, 28 Oct 2008, Gireesh P wrote: Dear TinyOS supporters, I would like to know 1)more about files used in deluge for tinyos 2.x. Basically I am looking at boot loader and flash rewriting part such as the files to be included/ functions to be used for this purpose The loading of the code from the external flash to the internal one takes place exclusively in tosboot. You can find it in tos/lib/tosboot. The communication with the tosboot is done using using some special regions of internal flash memories. The code that is doing the tinyos application is in NetProgM.nc from tos/lib/net/Deluge/extra. The format of the data that is passed to the bootloader is describe by the tosboot_args_t from TOSBoot.h from tos/lib/net/Deluge/extra. 2)Is there a working code of XNP for tinyos 2.x? I'm not aware of such a port. I agree that it would be useful to have an equivalent for it. :-) All the best! Razvan ME -- Thanks with regards Gireesh - Gireesan Namboothiri P MS(R) Student Dept of CSE IIT Madras ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge Reference tinyos 2.x
Hi! On Tue, 28 Oct 2008, Gireesh P wrote: Dear TinyOS supporters, I would like to know 1)more about files used in deluge for tinyos 2.x. Basically I am looking at boot loader and flash rewriting part such as the files to be included/ functions to be used for this purpose The loading of the code from the external flash to the internal one takes place exclusively in tosboot. You can find it in tos/lib/tosboot. The communication with the tosboot is done using using some special regions of internal flash memories. The code that is doing the tinyos application is in NetProgM.nc from tos/lib/net/Deluge/extra. The format of the data that is passed to the bootloader is describe by the tosboot_args_t from TOSBoot.h from tos/lib/net/Deluge/extra. 2)Is there a working code of XNP for tinyos 2.x? I'm not aware of such a port. I agree that it would be useful to have an equivalent for it. :-) All the best! Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
Re: [Tinyos-help] Deluge install problem
Hi! On Wed, 10 Sep 2008, [EMAIL PROTECTED] wrote: Hello, I am having trouble to load deluge into my Mica2 motes. The mote that I have is MIB510. I am using Cygwin with USB port (COM5). I got the no such file or directory error when I makeload the program into the mote. == make mica2 reinstall,19 mib510,COM5 set-mote-id build/mica2/main.srec build/mica2/main.srec.out-19 19 installing mica2 binary using mib510 uisp -dprog-mib510 -dserial=/dev/ttyS3 --wr_fuse_h=0xd8 -dpart=ATmega128 --wr_fuse_e=ff --erase --upload if=build/mica2/main.srec.out-19 Error: No such file or directory - /dev/ttyS3 make: *** [program] Error 1 == The following is my Makelocal file under /opt/tinyos-1.x/tools/make == DEFAULT_PROGRAM=mib510 MIB510=/dev/ttyS3 DEFAULT_LOCAL_GROUP=0x88 CFLAGS += -I%T/../contrib/xbow/tos/platform/mica2 -I%T/../contrib/xbow/tos/AXStack/mica2 -DCC1K_DEFAULT_FREQ=0x15 -DRADIO_XMIT_POWER=0xFF === If I change the MIB510=/dev/ttyS3 to MIB510=COM5 in Makelocal file, the compile process seems hang forever at the following line: ... ... uisp -dprog=mib510 -dserial=COM5 --wr_fuse_h=0xd8 -dpart=ATmega128 --wr_fuse_e=ff --erase --upload if=build/mica2/main.srec.out-19 Please help me fix this issue! Your response is appreciated! Can you try to use /dev/ttyS4 instead of COM5? The numbers for ttyS is one less than the one from the COM. :P -- Razvan ME ___ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
