klueska [Thu, 27 Mar 2008 00:52:02 +0000 (00:52 +0000)]
Update to allow header files to be processed via standard gcc and not have to run through ncc first (problem was in the usage of @combine, etc. in these files)
klueska [Tue, 11 Mar 2008 09:51:22 +0000 (09:51 +0000)]
Changed bsl.exra to search for the string between the commas and not short circuiting after seeing a digit when installing to some default tty device. Also added some more variables to the avr.rules and msp430.rules to allow more flexibility in the way the tos-storage-XXX scripts are invoked
klueska [Tue, 11 Mar 2008 09:34:13 +0000 (09:34 +0000)]
Changed bsl.exra to search for the string between the commas and not short circuiting after seeing a digit when installing to some default tty device. Also added some more variables to the avr.rules and msp430.rules to allow more flexibility in the way the tos-storage-XXX scripts are invoked
klueska [Tue, 11 Mar 2008 08:28:54 +0000 (08:28 +0000)]
Changed bsl.exra to search for the string between the commas and not short circuiting after seeing a digit when installing to some default tty device. Also added some more variables to the avr.rules and msp430.rules to allow more flexibility in the way the tos-storage-XXX scripts are invoked
janhauer [Wed, 5 Mar 2008 18:40:17 +0000 (18:40 +0000)]
Bugfix for a bug in the timer system that was first reported here:
http://sourceforge.net/tracker/index.php?func=detail&aid=1572439&group_id=28656&atid=393934
It showed up when you used two Timer interfaces (e.g. provided by two TimerMilliC() instances) and Timer2.startOneShot() was called withinTimer1.fired() and in addition (1) Timer2 had a higher internal interface ID (unique(UQ_TIMER_MILLI)) than Timer1 and (2) there was some (small) amount of time elapsed before the Timer2.startOneShot() was called in the fired eventhandler. Then, Timer2.fired() was signalled immediately independent of the "dt" parameter in startOneShot(uint32_t dt). This has been fixed now.
For more information see:
http://mail.millennium.berkeley.edu/pipermail/tinyos-devel/2008-March/002573.html
klueska [Mon, 3 Mar 2008 03:11:27 +0000 (03:11 +0000)]
Added README file explaining how the applicatin works, its organizational structure, and how to cinfigure it to work with other sensors as well as set the sampling intervals, etc.
rincon [Thu, 28 Feb 2008 17:28:12 +0000 (17:28 +0000)]
Roman Lim's fix:
"i noticed that my application (running on tmotes) using dma on spi does not go to the lowest possible sleep mode but only to LPM1.
i managed to find out, that in McusleepC when calculating the lowpower mode, ME1 had the USPIE bit set. this is, because in Msp430SpiDmaP the unconfigure command does nothing. I don't know, if this is done on purpose, but if not, the same code as in Msp430SpiNoDmaP would do the job (see follwing diff)
rincon [Mon, 4 Feb 2008 23:10:13 +0000 (23:10 +0000)]
Added the SendNotifier interface to support CTP + LPL integration.
Create and drop a module into your system that listens for the SendNotifier events for the AM types related to CTP or Dissemination, then have it call LowPowerListening.setRxSleepInterval(msg, 512);. Or capture the event for every AM type.
This can also be used to control other transmit parameters on a system-wide basis, like full duplex PA control on a per-destination basis, etc. If this hook works out, we can expand this into other radio stacks.
rincon [Thu, 31 Jan 2008 14:02:06 +0000 (14:02 +0000)]
Removal of cc1000_lpl. This LPL version is broken, and I have no plans on fixing it because I ran out of time a long time ago to work on it. Use the default CC1000 stack.