It's pretty straight-forward, if you know most or all of the TOS tricks...
octavetech.com used to have a nice page explaining it but it seems to have
gone missing. Using the T1 TOS_Msg struct from tos/types/AM.h and the
afore-mentioned tricks:
7e | 42 | ff ff ff ff | 04 | 7d 5d | 08 |
00 00 00 00 00 00 00 01 | 52 ca | 7e
sync | mtype | addr | group | length |
data | crc | sync
Note that group is "escaped" so takes two bytes and your length
is 8 bytes so you must be sending an int32 value of 1. Normally
one doesn't see the sync and mtype (system message type) bytes
or the crc field in a message buffer delivered from the lower
level TOS Java code. I think you may have used ListenRaw rather
than Listen to get this data?
MS
trilok i wrote:
> hi all,
>
> Can anyone explain how to analyse the below packet. I have enabled
> TinySec and captured packet using /opt/tinyos-1.x/tools/src/listen with
> mode = TINYSEC_AUTH_ONLY.
> My data is 01 . And what about other fields?
>
> 7e 42 ff ff ff ff 04 7d 5d 08 00 00 00 00 00 00 00 01 52 ca 7e
>
>
> ------------------------------------------------------------------------
> Get easy photo sharing with Windows Live™ Photos. Drag n’ drop
> <http://www.microsoft.com/india/windows/windowslive/photos.aspx>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Tinyos-help mailing list
> [email protected]
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
