I don't see why you weren't getting a warning about atomic reads
if there were non-atomic reads in the code. Maybe they were hidden by
the previous build settings? It's not the end of the world to have
non-atomic reads, although you should probably fix those.
As far as the message length, did you try a "make clean"?
You will also have to rebuild the java code.
I have been using telosb code with my tmotes under Tos2 without
problems.
Eric
On Fri, Aug 15, 2008 at 2:16 PM, MITTAL,ASHISH <[EMAIL PROTECTED]> wrote:
>
> I am working on a sensor networks project where the nodes measure
> wind pressures during hurricanes. I have a board which has a
> pressure sensor and other conditioning stuff to amplify that
> signal. I use this voltage from the board and put it on the ADC of
> the tmote. I sample this ADC from tmote to transmit data to the
> receiver.
>
> Now since tmote has been discontinued I have ordered telosb from
> crossbow technologies. I was wondering if I could burn the same
> code on them without any changes (except for specifying the target
> for burning as telosb instead of tmote). I tried it and am getting
> some warnings saying atomic reads and writes or something. The
> packet size does not change even on changing the Oscope.h file (I
> used the Oscilloscope and modified it a bit for my ADC sampling).
> Can anyone help please?
>
> --
> MITTAL,ASHISH
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
