{"id":1625,"date":"2016-03-30T20:30:20","date_gmt":"2016-03-31T03:30:20","guid":{"rendered":"http:\/\/visualgdb.com\/w\/?p=1625"},"modified":"2016-03-30T20:30:20","modified_gmt":"2016-03-31T03:30:20","slug":"creating-python-interfaces-for-c-libraries-on-raspberry-pi","status":"publish","type":"post","link":"https:\/\/visualgdb.com\/tutorials\/raspberry\/python\/","title":{"rendered":"Creating Python interfaces for C libraries on Raspberry Pi"},"content":{"rendered":"

This tutorial shows how to interface a C library to a Python script on Raspberry Pi with VisualGDB. We will create a Python module exporting some basic functionality from the wiringPi<\/a> library to the Python script and use it to control an LED connected to Raspberry Pi. Before you begin, install VisualGDB 5.1 or later.<\/p>\n

    \n
  1. Our first step will be to install the debug build of Python to Raspberry Pi. Connect to your board via SmarTTY<\/a> and run the following commands:\n
    sudo apt-get update\r\nsudo apt-get install python3.3-dev python3.3-dbg<\/pre>\n
    \"00b-python3-dbg\"<\/a><\/li>\n
  2. Then download, build and install the wiringPi library:\n
    sudo apt-get install git-core\r\ngit clone git:\/\/git.drogon.net\/wiringPi\r\ncd wiringPi\r\n.\/build<\/pre>\n
    \"00a-build\"<\/a><\/li>\n
  3. Now that both Python and wiringPi are installed on your Raspberry, we will create a Visual Studio project demonstrating how to export the wiringPi functionality to Python. Start Visual Studio and launch the VisualGDB Linux Project Wizard:\"01-projname\"<\/a><\/li>\n
  4. Select “Create a new project -> Python-based project”:\"02-module\"<\/a><\/li>\n
  5. Then select “Build the project locally with a cross-compiler”, pick the Raspberry Pi cross-toolchain (if it’s not installed, VisualGDB will download and install it automatically) and choose the connection to your Raspberry Pi (select “Create a new SSH connection” if it’s not in the list):\"03-target\"<\/a>Once you have selected the toolchain and the target, click “Synchronize headers and libraries”.<\/li>\n
  6. Proceed with the default synchronization directories (if you only installed Python and wiringPi since last sync, you can uncheck the \/opt directory to save some time):\"04-sync\"<\/a><\/li>\n
  7. Finally select your python executable. Raspberry Pi uses slightly different naming for Python directories from the Desktop Linux, so you will need to select the include folder (e.g. \/usr\/include\/python3.3dm) manually. Note that as you are using the debug build, you need to pick a directory containing the ‘d’ letter: \"06-python\"<\/a><\/li>\n
  8. Press “Finish” to generate the project. Before we add any wiringPi-specific code, quickly test that the project can be built and debugged. Set a breakpoint inside HelloMethod() and hit F5 to start debugging:\"07-dbgc\"<\/a><\/li>\n
  9. Once the breakpoint is triggered, use the Call Stack window to navigate to the <module> frame and verify that you can see the Python source as well:\"08-dbgpy\"<\/a><\/li>\n
  10. Now we will add the wiringPi support. Include the <wiringPi.h> file and replace the HelloMethod() together with the method table with the following code:\n
    template <int _Value> static PyObject *SetPin(PyObject *self, PyObject *args)\r\n{\r\n\u00a0\u00a0 \u00a0int pinNumber;\r\n\r\n\u00a0\u00a0 \u00a0if (!PyArg_ParseTuple(args, \"d\", &pinNumber))\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0return Py_BuildValue(\"0\", 1);\r\n\u00a0\u00a0 \u00a0\r\n\u00a0\u00a0\u00a0 digitalWrite(pinNumber, _Value);\r\n\u00a0\u00a0 \u00a0return Py_BuildValue(\"i\", 1);\r\n}\r\n\r\ntemplate <int _Value> static PyObject *SetMode(PyObject *self, PyObject *args)\r\n{\r\n\u00a0\u00a0\u00a0 int pinNumber;\r\n\r\n\u00a0\u00a0\u00a0 if (!PyArg_ParseTuple(args, \"d\", &pinNumber))\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 return Py_BuildValue(\"0\", 1);\r\n\u00a0\u00a0 \u00a0\r\n\u00a0\u00a0\u00a0 pinMode(pinNumber, _Value);\r\n\u00a0\u00a0\u00a0 return Py_BuildValue(\"i\", 1);\r\n}\r\n\r\nstatic PyMethodDef PythonWiringDemoMethods[] = \r\n{\r\n\u00a0\u00a0 \u00a0{\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\"sethigh\",\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0SetPin<HIGH>,\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0METH_VARARGS,\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\"Sets an output pin value to HIGH\" \r\n\u00a0\u00a0 \u00a0},\r\n\u00a0\u00a0 \u00a0\u00a0\u00a0 \u00a0\r\n\u00a0\u00a0\u00a0 {\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \"setlow\",\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SetPin<LOW>,\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 METH_VARARGS,\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \"Sets an output pin value to LOW\" \r\n\u00a0\u00a0\u00a0 },\r\n\u00a0\u00a0 \u00a0\r\n\u00a0\u00a0\u00a0 {\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \"makeoutput\",\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SetMode<OUTPUT>,\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 METH_VARARGS,\r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \"Configures a pin as output\" \r\n\u00a0\u00a0\u00a0 },\r\n\r\n{ NULL, NULL, 0, NULL }\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \/* End of list *\/\r\n};<\/pre>\n
    \"09-setpin\"<\/a><\/li>\n
  11. Insert a call to wiringPiSetupGpio() to the module initialization function:\"gpio\"<\/a><\/li>\n
  12. Finally go to VisualGDB Project Properties and add “pthread” and “wiringPi” to the library names so that your module is actually linked against the wiringPi library:\"11-libs\"<\/a><\/li>\n
  13. Now that we have added the sethigh(), setlow() and makeoutput() methods to our module, we will modify the Python script in the project to actually call them. However first we need to find a pin that we will control. According to the Raspberry Pi 2 pinout<\/a>, GPIO pin #3 is the lower pin in the 3rd row of the GPIO connector opposite to the ground pin:\"gpio\"<\/a><\/li>\n
  14. Connect an LED there and replace the contents of the Python script with the following code to make the LED on pin #3 blink:\n
    import PythonWiringDemo\r\nfrom time import sleep\r\npin_number = 3\r\nPythonWiringDemo.makeoutput(pin_number)\r\n\r\nwhile 1:\r\n\u00a0\u00a0\u00a0 PythonWiringDemo.setlow(pin_number)\r\n\u00a0\u00a0\u00a0 sleep(0.2)\r\n\u00a0\u00a0\u00a0 PythonWiringDemo.sethigh(pin_number)\r\n\u00a0\u00a0\u00a0 sleep(0.2)<\/pre>\n
    \"12-py\"<\/a><\/li>\n
  15. If you try running your program now, the program will exit immediately with a message stating that you need root privilege:\"13-noroot\"<\/a><\/li>\n
  16. Open VisualGDB Project Properties, go to the Debug Settings page and enable the “Run debugger as root” checkbox:\"14-root\"<\/a><\/li>\n
  17. Now you can press F5 to start debugging your program. The LED should now start blinking:\"led\"<\/a><\/li>\n
  18. Set a breakpoint at the call to PythonWiringDemo.sethigh() and wait for it to trigger:\"15-sethighpy\"<\/a><\/li>\n
  19. Stepping in would step into the Python’s code responsible for calling C functions, so instead set a breakpoint in the SetPin() function and press F5 to continue. See how our C++ wrapper gets called from the Python script and passes the pin number specified in the script to the digitalWrite()<\/strong> function provided by the wiringPi library:\"16-sethighcpp\"<\/a><\/li>\n<\/ol>\n
    You can use the technique described in this tutorial to interface any C\/C++ library to the your Python scripts. Simply create a Python module referencing the library, define your functions in the function table and call the functions from the Python side.<\/p>\n","protected":false},"excerpt":{"rendered":"
    This tutorial shows how to interface a C library to a Python script on Raspberry Pi with VisualGDB. We will<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[72,122,43],"_links":{"self":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/1625"}],"collection":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/comments?post=1625"}],"version-history":[{"count":1,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/1625\/revisions"}],"predecessor-version":[{"id":1646,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/posts\/1625\/revisions\/1646"}],"wp:attachment":[{"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/media?parent=1625"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/categories?post=1625"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/visualgdb.com\/w\/wp-json\/wp\/v2\/tags?post=1625"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}