Difference between revisions of "CC1100/CC2500 Recent Updates"
(→January 22, 2008) |
(→January 22, 2008) |
||
| Line 20: | Line 20: | ||
* Isolation test created for SplitControlManager in a new ''blaze/tos/chips/ccxx00/'' directory in TUnit: ''blaze/tos/chips/ccxx00/isolation/SplitControlManager''. | * Isolation test created for SplitControlManager in a new ''blaze/tos/chips/ccxx00/'' directory in TUnit: ''blaze/tos/chips/ccxx00/isolation/SplitControlManager''. | ||
* Integration test for BlazeInit SplitControl interface - duty cycle the power on and off. | * Integration test for BlazeInit SplitControl interface - duty cycle the power on and off. | ||
| + | ** Test passed on a tmote2500 platform | ||
== January 21, 2008 == | == January 21, 2008 == | ||
Revision as of 15:56, 22 January 2008
The CCxx00 radio stack is getting some new architecture. The last stable working version may be checked out from CVS using a special update by date, on or before January 20, 2008.
January 22, 2008
Status
- NON-OPERATIONAL: In a state of flux, dividing the prototype Blaze radio stack (blazeradio) into a new ccxx00 directory which will contain the final CCxx00 radio stack architecture.
Updates
- Updated all .platform files to point to the new ccxx00 directory
- Created a SplitControlManager component to reside just underneath the RadioSelect module.
- Isolation unit tested the SplitControlManager. All tests pass.
- Removed SplitControl functionality from RadioSelect module. The RadioSelect module is now entirely responsible for converting the non-parameterized Send and Receive interfaces it provides into parameterized Send and Receive interfaces it uses.
- Wired SplitControlManager into CC2500ControlP and CC1100ControlP to prevent Configuration commits to the radio registers when the radio is off.
- Removed SplitControl managing functionality from BlazeInit.
- Removed the BlazePower interface, replaced it with internal functions in BlazeInitP. The SplitControl and BlazeCommit interfaces are the only interfaces that should be interacting with the hardware. Also removed BlazePower connections from CC2500ControlC and CC1100ControlC.
Tests
- Isolation test created for SplitControlManager in a new blaze/tos/chips/ccxx00/ directory in TUnit: blaze/tos/chips/ccxx00/isolation/SplitControlManager.
- Integration test for BlazeInit SplitControl interface - duty cycle the power on and off.
- Test passed on a tmote2500 platform
January 21, 2008
Status
- NON-OPERATIONAL: implementing better SplitControl architecture.
Updates
- Reduced the number of SPI register burst init elements from 39 to 25, decreasing the time it takes for init.
- Added the RadioReset interface and HplRadioResetC/P modules to allow the driver to check the SO line to see that the radio has been automatically powered up on reset.
- Removed RfResource and PriorityQueue from the radio stack.
- Removed while-loop hack functionality in BlazeInitP - this still needs to be tested with various hardware
Tests
- Created AutomaticPor test to test the RadioReset interface, which I have implemented for the MSP430-based platforms
January 20, 2008
Status
- OPERATIONAL. Stable on the MSP430. Full of hacks to try to get the hardware working. The radio typically refuses to go into TX mode on Atmega128 platforms.
