Dear all,

Now I am hunted by the the storage stuff.   I did the tutorial in the core
folder and the RssiSample in the contribution directory.  I found the

program has a common point that the receive data, write, read and report all
in one program.

I think the program I'd like to implement is getting them separated.  I can
delete the entry in AT45DB from a certain point and end with a

certain point,  receive data and write entry in it, and report (read) the
data via UART (Three separate programs). So I can control the

dataflow procedure.

So I need to know quite clear, what's on earth going on when I use the
volume. what the driver will do with it (the corresponding header file
created by the compiler)

 If I download a program with a type 1 .xml to define the volume and write
some data.  What will happen if I download another program

with type 2 .xml.  Will the previous data loss? I think it will not, but
what if I allocate more space than the chip really has by now  and I'm

still confused with the concept of the volume, what is this? This question
may be concerned with write and read/report programs.

And when I read the RssiSample program, I noticed that the write operation
is triggered when SPI(RSSI value) bus is available and all

record is deleted when the mote experience a power cycle, it does not inlude
the routine of read the data afterwards. As this application

can let the mote connectted to the computer. However we need the mote to
store the data when in a real network application.

I also noticed that there are a bunch of routines implemented by Rincon
company, however the Atmel1281 driver is different from Atmel128

in the UART part, this routine cannot be used.  I guess there should be many
groups using write, read, report routines, what do you guys

usually do when you want to store some data when want to survive power cycle
and read after?

sincerely
Peng
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to