About Libraries
|
I'm receiving many mails about the libraries I've developed and I'm sharing. I just can't answer all the mails and provide support for all the specific cases. Some even post their issues on Twitter!
|
Plug-and-Play
|
The libraries are plug-and-play as I'm using them in my projects. However, they are designed for a specific configuration. For example, a SD-card library requires a minimum of 512 bytes of RAM as this is the size of a sector. So it won't work on the MSP430G2553.
With so many LaunchPads, BoosterPacks and components possible combinations, the one-fits-all approach is just impossible. It would end with lengthy and hard to read code with many pre-processing statements. For example, changing the pins names for the pins numbers improves the portability of the library across the LaunchPad range of boards. |
Obsolescence
|
Even if the library works out of the box, they are provided as examples and require some work from the user. This is the best way for learning. The user should read and understand them, and then customise them so they can match his/her exact needs.
With new hardware and software releases coming out, a library may suffer from obsolescence. It used to work with a prior version but no longer works with the new one. For example, each new release of Energia or CCS adds new features and sometimes modifies others in order to ensure compatibility across the whole range. |
Help Back!
|
A good place to discuss about the libraries is the 43oh forum.
Improve and share back the libraries with the community by contributing to the GitHub repositories. |
