[Tinyos-devel] ATmega128 UartByte Broken

[David Moss]

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.

-David


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


On Nov 13, 2007, at 3:02 PM, David Moss wrote:

> Alec -
>
> I checked out the Atm128UartP.nc and HplAtm128UartP.nc from that  
> branch and
> verified the version numbers.  After replacing my local files with  
> those, I
> compiled and installed the TestSerial application.
>
> In doing this, I was able to read messages on the computer side,  
> but could
> not send messages from the computer to the mote. No led's lit up,  
> and the
> console was stuck at "Sending packet 0". I haven't looked into it  
> any deeper
> than that at the moment.
>
> This new error prevents the unit test framework from running the  
> original
> UartByte test because the framework itself is dependent upon  
> sending packets
> to the mote to kick off each test.

It looks like the newer (Alec's in -devel) version is incorrectly  
leaving RX interrupts disabled on start.

I don't know what the issue in the main tree version is. David, can  
you give more detailed info on how it is failing the test?

Phil