[Tinyos-devel] ATmega128 UartByte Broken

[David Moss]

Yes, the test code is available in tinyos-2.x-contrib:

http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x-contrib/tunit/tests/tiny
os-2.x/tos/lib/serial/TestUartByte/

It relies on the DirectSerialAMSenderC library to send packets over the
UartByte interface, found here:

http://tinyos.cvs.sourceforge.net/tinyos/tinyos-2.x-contrib/tunit/tos/lib/di
rectserial/

The test code itself is pretty simple.  Upon receiving the command to run
over the regular serial interface from the java side of TUnit, the test
creates the equivalent of a TUnit "test passed" message and sends the
message to the computer over DirectSerialAMSenderC.  If the computer
receives the message, the test really did pass which demonstrates that the
UartByte interface worked inside of the DirectSerialAMSenderC component.

So there is some overlap here - I've tested the DirectSerialAMSenderC
component with the MSP430 to ensure the test is not failing within that
functionality.

-David




-----Original Message-----
From: Philip Levis [mailto:pal at cs.stanford.edu] 
Sent: Tuesday, November 27, 2007 12:13 PM
To: David Moss
Cc: 'Alec Woo'; 'Tinyos-devel list'; 'Jonathan Hui'
Subject: Re: [Tinyos-devel] ATmega128 UartByte Broken


On Nov 27, 2007, at 10:36 AM, David Moss wrote:

> All my test can do is say whether or not the interface works as  
> expected by
> plugging in some bytes and evaluating what comes out the other side.
>
> It can't give any more information than that at the level it's  
> written.
> Being a unit test for a hardware driver, it's more of a black box  
> test than
> a white box test, so underlying details of why the driver is broken  
> are
> inherently masked.

Is the test source code in the tree? If not, can you send it to me?

Phil