meghs94 / tinyos-main

Automatically exported from code.google.com/p/tinyos-main
1 stars 0 forks source link

[patch] RF212 frame receive doesn't always complete SPI transfer #63

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Receive a frame which gets rejected by the RadioReceive.header() check.
2. Attempt to receive another frame.
3. Note how the frame is not actually received, as downloadMessage() does not 
get called, as the previous SPI transfer has not been properly finished.

What is the expected output? What do you see instead?
A received frame in (2).

What version of the product are you using? On what operating system?
TinyOS-2.x trunk

Please provide any additional information below.

To properly finalize the SPI transfer, a FastSpiByte.read() has to be called. 
In the call path where RadioReceive.header(msg) returns false, this does not 
happen, which screws up the next receive.

Original issue reported on code.google.com by jmatts...@dius.com.au on 7 Sep 2011 at 4:38

Attachments:

GoogleCodeExporter commented 8 years ago

Original comment by philip.l...@gmail.com on 12 Sep 2011 at 12:38

GoogleCodeExporter commented 8 years ago
The patch is applied (the same problem is also fixed for RF230)

Original comment by mmar...@gmail.com on 13 Sep 2011 at 10:01