All,
I am frustrated with the organization of the CC2530 and CC2531 firmware libraries. They seem to be designed only for the application examples provided in the package, and not for general code development that use the code examples. For example, just to make an LED blink on a CC2531 dongle, I find myself adding all kinds of new files with USB support, etc. All I want to do is use the libraries to blink an LED, yet the include dependencies in the firmware libraries seem to drill endlessly into supporting every feature possible with the hardware. Am I doing something wrong? Is there another "library package" that I should be using? Do I need to write my own libraries and headers to get away from this problem?
Secondly, the CC2531 uses MRFI libraries for radio communications, but the CC2530 uses basic_rf. If you use the library for the CC2531, it doesn't even include directories for basic_rf components, and if you use the CC2530, there is no included files for MRFI. Once again, shouldn't there just be a library directory structure where developers can add what they need? Both chips should support the same radio functionality. Am I missing something here?