CC2500 Radio Library

[alvarop 14]

I'm still on the early stages, but I've documented what I have so far here: blog.alvarop.com

 

I wrote my own radio libraries for the cc2500 to avoid using simpliciTI. They're fairly limited(64-byte packets, 250kbps), but good enough for what I need.

 

The code is on github right now, but it needs a lot of work. I also have the libraries written to work with msp430-gcc, but those were for my thesis work using the ez430-rf2500.

[bluehash 1,581]

Hello alvarop, I've moved your post to the code vault, since it belong here. I also fixed your link.

Very good work on the board. Make sure you create a project thread with your new board to get more exposure.

 

I love the time lapses!

[alvarop 14]

Thanks! I'll be sure to do that then.

[alvarop 14]

I did a major update to the CC2500 library today.

It's currently used to control an RGB LED light strip wirelessly, but should be easy enough to modify for other stuff. I hope the code is clear-ish and makes sense.

 

Code: https://github.com/alvarop/msp430-cc2500

 

Example of RGB LED use: http://blog.alvarop.com/2012/01/cc2500-project-part-6-reorganizing.html

[larsie 121]

Hi, I have some code for the CC1101 on https://github.com/mobilars/LarsRF/

 

Would this be pretty much the same code? I think it might be based on the same TI library? Does the code run interchangeably on the CC1101 and CC2500 or are there code differences?

[alvarop 14]

Yes, I'm basing mine off the same slaa325a library.

 

My main problem with it was having to create new hardware_board.h files and also having to modify include.h for every device you want to use. My goal is to eventually make the radio code hardware independent. I want to be able to use the same libraries across different devices with minimal changes. It would be pretty cool to be able to use the same code on an MSP430, Beagleboard, C2000, ATMega, CortexM3 etc...

 

Like you said, the SPI interface should be the same for all CCxxxx devices.

You'll just have to change the #defines in case there are different radio registers along with the writeRFSettings() function for the configuration.

[greeeg 460]

This should be extremely handy to implement on the chronos watch.

IMHO simpliciti seems better suited to multi node sensor networks rather than a watch, especially when all you want to do is talk to a single access point to sync the time, simpliciti seems over kill and takes up alot of code space.

[gwdeveloper 275]

The slaa325a library is really easy to adjust for different radios. Use SmartRF 7 and you can select the "RF settings HAL" template when exporting the registers. Then it's simple to add that to the CC1100-CC2500.c.

 

I do like the uart logging that Larsie has added with his library.

 

In defense of SimpliciTI, it is a much more advanced library -more than just the hardware initialization. I've been working with TI wireless for a while now and made the decision to use SimpliciTI a while ago due to it being a complete wireless solution all rolled into one application. Yes, the code size is bigger but as it's really designed for bigger mcu with more RAM. It squeezes itself onto a G2553 and will work great but try to add an LCD display you're out.

[alvarop 14]

That's true, there is a place for both SimpliciTI and slaa325a.

I mostly avoided SimpliciTI because the project I was working on required extremely precise packet timing. It was quicker to use the most basic libraries than to figure out how simpliciTI worked and modifying it.

 

Most of what I do right now is with the smaller devices, so simple packets are 'good enough'. It has also been a great learning experience.