Difference between revisions of "TUnit Known Issues"
(New page: == Pong Problem == Some users get the message "Didn't receive a pong from the mote". This issue has been observed on some linux platforms as well as some hardware platforms, like a MICAz...) |
(→Pong Problem) |
||
| Line 6: | Line 6: | ||
One thing we might try is disconnecting / reconnecting / pinging a few times. | One thing we might try is disconnecting / reconnecting / pinging a few times. | ||
| + | |||
| + | = TestCaseC not found = | ||
| + | |||
| + | NesC cannot find a path to your ''tinyos-2.x-contrib/tunit/tos/tunit'' directory. TUnit tacks this information into a temporary local file called testrunner.extra, and references it at compile time. Make sure your TOSMAKE_PATH environment variable says "./" so nesC can look in your local directory for .extra files. | ||
| + | |||
| + | In component `MyFirstTestC': | ||
| + | MyFirstTestC.nc:6: component TestCaseC not found | ||
| + | MyFirstTestC.nc:6: component `TestCaseC' is not generic | ||
| + | MyFirstTestP.nc:1:22: TestCase.h: No such file or directory | ||
| + | MyFirstTestC.nc:8: failed to preprocess MyFirstTestP.nc | ||
| + | |||
| + | export TOSMAKE_PATH="./" | ||
Latest revision as of 13:33, 16 January 2008
Pong Problem
Some users get the message "Didn't receive a pong from the mote". This issue has been observed on some linux platforms as well as some hardware platforms, like a MICAz + MIB520. It could be a serial driver issue. We're not sure where the problem lies, because it's below the level at which TUnit operates.
TUnit establishes a connection with the node using a serial forwarder on the computer side. To verify the connection has been established, TUnit sends a message through the serial forwarder (ping). It waits for some time before giving up.
One thing we might try is disconnecting / reconnecting / pinging a few times.
TestCaseC not found
NesC cannot find a path to your tinyos-2.x-contrib/tunit/tos/tunit directory. TUnit tacks this information into a temporary local file called testrunner.extra, and references it at compile time. Make sure your TOSMAKE_PATH environment variable says "./" so nesC can look in your local directory for .extra files.
In component `MyFirstTestC': MyFirstTestC.nc:6: component TestCaseC not found MyFirstTestC.nc:6: component `TestCaseC' is not generic MyFirstTestP.nc:1:22: TestCase.h: No such file or directory MyFirstTestC.nc:8: failed to preprocess MyFirstTestP.nc
export TOSMAKE_PATH="./"
