I wish to report a problem that we are currently encountering: we did some tests on 17 waspmotes with Digi 802.15.4 transceiver modules (XBee 802.15.4 PRO S1) by sending and executing firmwares through OTA. All motes could successfully receive the firmware sent from a gateway and save the received firmware into SD card (all motes were configured by the same setting). However, 5 motes got stuck after restarted the new program (by -start_new_program command) and no longer gave response to any furthermore OTA command. The phenomenon is the same as what I reported before in a previous topic "Problem of OTA with the use of SD Functions"viewtopic.php?f=19&t=7801
The difference is that removing the bottom/top battery does not work for them. Furthermore, all the 5 improperly-working motes have very similar product serial numbers which are something like 3030-0005-xxx while the other 12 working motes have different numbers (3030-0004-xxx or 3030-0008-xxx ). Therefore, I suppose it is due to the bootloader.
Since all the 17 motes were purchased at the same time (mid of August 2011), they are supposed to have the latest version of bootloader (v003) but I do not know why the 5 motes are different.
I have ordered an AVR ISP programmer but the waspmote does not have an individual ISP socket (the UART0 is shared with USB/Xbee). Could anyone give suggestion to sort out this problem?
Furthermore, I was told that all motes manufactured after May 2011 should have the reset function available (it is a hardware implementation). However, I did not find the reset command works for our case, could anyone let me know how to better verify the if the function works or not?