Sensor/Actuator repository for libmraa (v1.5.1)
Porting arduino libraries to libmraa as UPM libraries is usually fairly easy. The issues typically come from misunderstanding of how a non real time OS deals with interrupts and timers. It also highly depends on the sensor. A concrete example is explained in detail on Making a UPM module for MAX31855
By default you need a header called modulename.hpp and a C++ file called modulename.cxx. You can have multiple headers and source files. Only public headers need to be added to module_hpp and all source files need to be in module_src.
The easiest way to do this is to have a look at a similar sensor to yours. Typically create a class for your sensor with a constructor that defines the pins it is on. This constructor will create the mraa_*_context structs that are required to talk to the board's IO. An I2c sensor will create a mraa_i2c_context, keep it as a private member and require a bus number and slave address in it's constructor.
Typically in sensors a simple object->read() function is preferred, depending on your sensor/actuator this may or may not be easy or not even make sense. Most UPM APIs have a simple set of functions.
Your constructor is similar to the setup() function in arduino, you should initialise your IO the way you want it. This means initialising contexts (private members) and setting the correct modes for them.
See the mraa API documentation for exact API.
To build your module just follow Building UPM. By creating a folder and the CMakelists.txt file you have done all that is required to add your sensor to the UPM build system.
The last step is when you're happy with your module and it works send us a pull request! We'd love to include your sensor in our repository.
If you don't like github you can also send mihai.nosp@m..firstname.lastname@example.org@email@example.com@m.ntel..firstname.lastname@example.org a git formatted patch of your sensor. More details are on Contributing a module and on https://help.github.com/articles/creating-a-pull-request