You are here: start » projects » gpio-bb

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
projects:gpio-bb [2017/01/12 22:44] – external edit 127.0.0.1projects:gpio-bb [2024/05/16 10:54] (current) – [GPIO bit-bang driver for Linux] darron
Line 7: Line 7:
 GPIO bit-bang is well suited to PICMicro ICSP but not exclusively. GPIO bit-bang is well suited to PICMicro ICSP but not exclusively.
  
-=== Raspbian for Raspberry Pi ===+WARNING: The underlying kernel API this module uses may have been removed from your running kernel. 
 +=== Build ===
  
-First install development tools and the kernel headers.+This module is built out of kernel and depends on the header files and tools found locally or may be cross compiled. 
 + 
 +For cross compilation, an example Makefile named `cross-compile.mk' is provided which should work for Raspberry PI OS as explained [[:tools:raspbian#kernel|here]]. 
 + 
 +If the linux source directory was cross compiled and then copied to the target system to build the module, `scripts.sh' is provided to rebuild certain kernel header scripts locally. This is needed because some scripts are actually binary files on the foreign architecture. 
 + 
 + 
 + 
 +=== Raspberry Pi OS=== 
 + 
 +First install development tools and the kernel headers when using a regular kernel.
 <code> <code>
 apt-get install raspberrypi-kernel-headers apt-get install raspberrypi-kernel-headers
 </code> </code>
  
-Now install the kernel module. +If you updated the kernel with rpi-update, install [[https://github.com/RPi-Distro/rpi-source|rpi-source]]
-<code> +
-hg clone http://hg.kewl.org/pub/gpio-bb +
-cd gpio-bb +
-make +
-make install +
-</code> +
- +
-=== Void Linux for Raspberry Pi ===+
  
-First install development tools and the kernel headers.+Now install headers for kernel installed with rpi-update.
 <code> <code>
-xbps-install mercurial make gcc rpi-kernel-headers +rpi-source --skip-space
 </code> </code>
  
Line 33: Line 36:
 hg clone http://hg.kewl.org/pub/gpio-bb hg clone http://hg.kewl.org/pub/gpio-bb
 cd gpio-bb cd gpio-bb
-./rpi-void.sh+make 
 +make install
 </code> </code>
  
-=== Bananian for Banana Pi ===+=== Armbian ===
  
-Install development tools and the kernel headers and then install the kernel module. +==BPI==
- +
-<code> +
-hg clone http://hg.kewl.org/pub/gpio-bb +
-cd gpio-bb +
-./bpi-bananian.sh +
-</code> +
- +
-=== Armbian for Orange Pi Zero === +
- +
-Install development tools and then install the kernel module.+
  
 <code> <code>
 +apt install linux-headers-current-sunxi
 hg clone http://hg.kewl.org/pub/gpio-bb hg clone http://hg.kewl.org/pub/gpio-bb
 cd gpio-bb cd gpio-bb
Line 67: Line 62:
 </code> </code>
  
-=== OpenWRT === +=== Obsolete documentation === 
-[[projects:gpio-bb:openwrt|GPIO bit-bang driver for OpenWRT]] +[[projects:gpio-bb:armbian|Armbian]] 
- +[[projects:gpio-bb:bananian|Bananian]] 
-=== Raspbian for Raspberry Pi (obsolete) === +[[projects:gpio-bb:openwrt|OpenWRT]] 
-[[projects:gpio-bb:raspbian|GPIO bit-bang driver for Raspbian]]+[[projects:gpio-bb:raspbian|Raspbian]]
  
 === Troubleshooting === === Troubleshooting ===
  
-gpio-bb uses the kernel API to access pins, this API demands +gpio-bb uses the kernel API to access pins, this API demands exclusive access to a pin per process. This means you cannot use gpio-bb and sysfs export simultaneously for a single pin.
-exclusive access to a pin per process. This means you cannot use +
-gpio-bb and sysfs export simultaneously for a single pin.+
  
 === Resources === === Resources ===
  
-[[https://www.pedalpc.com/blog/posts/how-to-program-a-pic-microcontroller-using-a-raspberry-pi-or-orange-pi-plus-2|Using gpio-bb on the Orange Pi]]+[[https://www.pedalpc.com/blog/program-pic-raspberry-pi/#gpio-bb|Using gpio-bb]]