I too was working on a similar approach....The 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 <[email protected]> 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 >> <[email protected]> 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 >>>> [email protected] >>>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>> >>> > > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
