Paulo Rogerio, Most probably, your micaz motes have the same version of the flash chip as the iris motes. The quick fix would be the following: Modify the file tinyos-2.x/tos/platforms/micaz/.platform by inserting the line %T/platforms/iris/chips/at45db before the line %T/platforms/mica2/chips/at45db
After making this change, you can verify that HplAt45dbIOC.nc and HplAt45dbIOP.nc get pulled in from platforms/iris/chips/at45db by adding PFLAGS+=-v to the Makefile of an app that uses the flash. Obviously, I can't test it, but there is a good chance that it will work. Janos -----Original Message----- From: Paulo Rogerio Barreiros d'Almeida Pereira [mailto:[EMAIL PROTECTED] Sent: Thursday, July 24, 2008 8:17 AM To: Janos Sallai Subject: potential micaz flash issues Hi, We have bought 10 MicaZ motes that we received in April 2007. We just found out that the flash applications do not work in most of them. I fetched the latest TinyOS2 version from the CVS repository and the same happens: the flash applications do not work at all. For instance: tinyos-2.x/apps/tutorials/BlinkConfig or tinyos-2.x/apps/tests/storage/Config do not light any led at all. These applications work for other older MicaZ motes we have. Would it be possible to get a working version of TinyOS for the newer MicaZ motes? By when? Best regards, Paulo Rogério Pereira > Philip Levis: >>On Mar 5, 2008, at 10:38 AM, Janos Sallai wrote: >> >>> I have recently learned that newer micaz motes and OEM modules use >>> a newer version of the at45db, which is not fully backwards >>> compatible with the old version. >>> >>> >>> >>> From my experiences with the iris mote, which has the new version >>> (at45db041d), the micaz code would not work with the new chip. >>> Could anybody verify this by running the flash test apps on a >>> recently purchased micaz? >>> >> >>Is there any way for software to detect which chip a node has? >>This is going to be pretty hairy, if you have to include both chip >>implementations and switch between then at runtime. Or are the >>differences trivial? It would be nice to avoid the 433/900MHz mica2 >>debacle. > > Yes, it is possible to programmatically detect which chip the mote has. > I've just skimmed the manuals, and it appears that it is possible to > come up with a single piece of code that works on both revisions, so we > wouldn't need to branch based on the chip ID. > > The problem is that with the older version it was possible to check if > the chip is ready by toggling the clock and checking a pin. This feature > was removed from the at45db041d from revision G (after February, 2007). > I think that checking for ready can be done by reading the status > register on all at45db versions. > > Before touching the code, could somebody check if this problem exists at > all? > > Phil _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
