Difference between revisions of "CC1100/CC2500 Recent Updates"
(→January 21, 2008) |
|||
Line 12: | Line 12: | ||
''Tests'' | ''Tests'' | ||
* Created AutomaticPor test to test the RadioReset interface, which I have implemented for the MSP430-based platforms | * Created AutomaticPor test to test the RadioReset interface, which I have implemented for the MSP430-based platforms | ||
− | |||
− | |||
− | |||
− | |||
== January 20, 2008 == | == January 20, 2008 == | ||
Line 21: | Line 17: | ||
''Status'' | ''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. | * 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. | ||
+ | |||
+ | = See Also = | ||
+ | |||
+ | * [[CC1100/CC2500|CC1100/CC2500 Radio Stack]] |
Revision as of 07:41, 22 January 2008
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.