A quick look at TOSBase reveals no CRC checking, but I could be wrong.
The Packetizer.java code does check the crc on host side receives
so I'd bet that TB just passes everything along like you want.
Just whack the crc code out of Packetizer...
nesc -v shows more detail of what is being done curing a compile.
All the TOS code that an app uses is compiled and uploaded each time.
There is some nesc doc in the T1 tree, or a quick google search should
come up with the white-paper docs.
MS
Adnan Iqbal wrote:
hi
Scenario:
using two micaz motes
mote1 broadcasts packets,
mote 2 is runninf TOSBase and simply forwards those packets to UART
Listen is getting packets
Problem:
we want to disable CRC checking for received packets at mote 2
(TOSBase), because we want to receive all packets even if they are in
partial error
question 1: how to disable crc checksum
question 2: how can i know exact process of compilation/install
in TinyOS, i mean what happens when we use a command like "make micaz
install, COM1". I know roughly that first it compiles .nc files than
makes .srec and i hex files and then uploads them. Questions are does
TinyOS for mote is recompiled every time and uploaded to mote every time
OR there is some version of OS built into mote and only application code
is uploaded.
question 3: if TinyOS for mote does not compile every time, how to do that?
Regards
Adnan
------------------------------------------------------------------------
_______________________________________________
Tinyos-help mailing list
[EMAIL PROTECTED]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
_______________________________________________
Tinyos-help mailing list
[EMAIL PROTECTED]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
