[Tinyos-help] Logger works on some micaz's and not on others(all have same code)

[Giri Baleri]

Hi All,

The symptom sounds very similar to an issue uncovered on some MICAz OEM modules. This was posted to Crossbow's knowledgebase along with the work-around that can be reviewed from
http://www.xbow.com/Support/wobjectDetail.aspx?id=50160000000KQJ8AAO&type=Solution&page=0

Please try the updated "HPLFlash.nc" file from the attachment and see if that alleviates the problem.

Regards,
Giri Baleri
Crossbow Tehcnology, Inc


-----Original Message-----
From: tinyos-help-bounces at Millennium.Berkeley.EDU on behalf of Michael Schippling
Sent: Fri 10/12/2007 3:38 PM
To: Nick Soldner
Cc: TinyOS Help (E-mail)
Subject: Re: [Tinyos-help] Logger works on some micaz's and not on others(all	have same code)
 
I wonder if you have a timing race condition in your init code?
Just an idea, probably nothing useful...
MS


Nick Soldner wrote:
> I posted earlier on this however now I have a bit more intuition as to 
> the nature of my problem. I have an application which writes data to the 
> micaz's 512KB flash EEPROM through the logger component. My code first 
> resets the write pointer whenever the mote is power cycled using 
> LoggerWrite.resetPointer(), I then issue the LoggerWrite.append(ptr) 
> command in six second intervals to write data to the EEPROM. I have an 
> led setup to toggle whenever the LoggerWrite.writedone event fires which 
> indicates a successful write operation.
> 
> After installing this program on multiple motes I find that some motes 
> successfully write to the EEPROM while others return FAIL. Given that 
> I'm installing the exact same program on many identical micaz motes I 
> would expect all motes to act the same; not the case it seems. On the 
> motes that do successfully write to the EEPROM I have verified that the 
> write pointer is indeed reset and that the data written is correct.
> 
> I have an intuition that the motes which don't successfully write to the 
> EEPROM have write pointers that point to protected space although the 
> shouldn't after resetPointer() is called. In theory since I always 
> execute LoggerWrite.resetPointer() once before I start to write data 
> there should be no issue trying to write in protected space. 
> Additionally the pointers are stored in the program code (LoggerM) so 
> each time I upload the code to a mote they should all have the same 
> pointers.
> 
> The ONLY thing I see that is different is the date codes of my micaz 
> motes, the ones with date codes of 11-20-06 work fine and the ones with 
> date codes of 03-13-07 don't work. Is there a way to change the newer 
> motes to mimic the old ones?
> 
> Any advice on how to troubleshoot this?
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Tinyos-help mailing list
> Tinyos-help at Millennium.Berkeley.EDU
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

-- 
Platform: WinXP/Cygwin
TinyOS version: 1.x, Boomerang
Programmer: MIB510
Device(s): Mica2, MicaZ, Tmote
Sensor board: homebrew

_______________________________________________
Tinyos-help mailing list
Tinyos-help at Millennium.Berkeley.EDU
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20071013/4c760f52/attachment.html