janhauer [Mon, 25 Jun 2007 13:44:49 +0000 (13:44 +0000)]
Added a generic that generates a nesC warning if someone wired to RefVolt arbiter
but forgot to wire the AdcConfigure interface (the component does not generate
any code).
rincon [Sat, 23 Jun 2007 05:14:40 +0000 (05:14 +0000)]
First, we'll pull the new FifoQueue component out of the baseline for now so its interface is not permanently cast into TinyOS. Then, we'll define some broad, useful Queue interface to support many the types of behavior, including the ones you are mentioning. Finally, we (anybody) can implement various Queues using the unified Queue interfaces.
rincon [Tue, 19 Jun 2007 17:30:08 +0000 (17:30 +0000)]
Updated the ActiveMessageAddress interface after discovering issues with calling setAmGroup() and setAmAddress() separately and having the radio try to split-phase sync() with each one of those.
rincon [Mon, 18 Jun 2007 20:36:36 +0000 (20:36 +0000)]
Added a -no-output and null renderer option for deployable applications that only want serial forwarder running completely in the background. Have yet to regenerat/commit the baseline .jar that corresponds to this addition.
idgay [Wed, 6 Jun 2007 22:40:17 +0000 (22:40 +0000)]
build both 32 and 64-bit versions of the JNI code so as to support both
32 and 64-bit JDKs
install the appropriate JNI version depending on whether the JDK is 32 or 64-bit
rincon [Thu, 24 May 2007 19:55:12 +0000 (19:55 +0000)]
Previous problem: The EventDispatcher is stuck on the function waitForEvent() while we are attempting to close. Closing NativeSerial while the driver is still in the function waitForEvent() will crash everything. Calling cancelWait() in win32 does let waitForEvent() return until some event actually occurs, which is not the behavior I was expecting. The serial driver itself could be fixed to let cancelWait() actually force waitForEvent() to return false, but I don't want to touch it.
Solution: Force waitForEvent() to generate an event by adding a notification for OUTPUT_EMPTY. When we want to close the serial source, send a 0x7E byte to the serial port and wait for that OUTPUT_EMPTY event to get signaled. At that point, the EventDispatcher thread can continue execution and will cancelWait() properly. We aren't stuck in waitForEvent(), and only then can we shut down NativeSerial with confidence.
One other issue remaining is the fact that sometimes you can't reconnect to the source very quickly after a disconnect. Adding in a hacky wait(500) fixes the problem on disconnect, but I haven't included that anywhere because I haven't figured out exactly what is causing us to need to wait for a short period of time after a disconnect before reconnecting again.
razvanm [Tue, 22 May 2007 20:34:19 +0000 (20:34 +0000)]
Initial commit of the Deluge T2. Some notes:
- TOSBoot includes some code to allow the MicaZ version to compile but it's not support for it it's not done yet.
- tools/tinyos/misc/Makefile.am is not updated yet so the new tools will not be installed by default.
scipio [Mon, 21 May 2007 21:35:54 +0000 (21:35 +0000)]
Improved accuracy of acknowledgement delivery by considering SNR
curves. Currently, ack reception is based on the same SNR/PRR curve
as packet delivery. This is pessimistic, due to the fact that acks
are shorter than packets. I need to measure the ARR/SNR curve to
put it something more accurate. Also, currently TOSSIM does not model
false positives, something I will be adding shortly.
rincon [Fri, 18 May 2007 18:27:03 +0000 (18:27 +0000)]
Previously, the serial forwarder would only release the COM port on exit. Now it provides the ability to temporarily release or reconnect to the COM port when you close/open your source. The SF GUI demonstrates this ability when you connect to your mote, stop the server and verify you can reprogram your mote at that time, restart the sf server and verify you can continue communicating with that mote... all without closing down your serial forwarder.