Skip to main content

[RTEMS/RASP] GPIO/Pibrella/Display-Module on RTEMS

This quest is for the one who is seeking how to use GPIO on RTEMS.
I have tested that Pibrella Rev3 (popular all-in-one collection) and Raspberry Pi® Display-Modul 1115 (LCD+Keypad) both can work well.



Thanks for André Marques, now GPIO library is feasible on RTEMS.
Consider https://github.com/asuol/RTEMS_rpi_testing github:
Below find more detail information after this article.
Andrésaid he is still updating the file system, we look forward the official release in RTEMS.


To adopt his contributions, I clone over his branch (GPIO_API) and rebuild my RTEMS again.
Under the source directory (rtems-gpio), ./bootstrap, e.g. /home/khchen/development/rtems-gpio/, and then go to the build directory:

Makefile.am and configure.ac all need to be changed accordingly, i.e., the name of library and the path of sample.
Please note, due to ./bootstrap script, all the Makefile.am will be complied to Makefile.in in each directory.
Then we change to the directory of build and configure the building information.
../rtems-gpio/configure --target=arm-rtems4.11 \
--enable-rtemsbsp=raspberrypi \
--enable-tests=samples \
--enable-networking \
--enable-posix \
--prefix=$HOME/development/rtems/4.11

And then:

make install
Or, go in to the .../testsuites/samples/:

make install

If you find an error message like this:
"undefined reference to `gpio_get_val!!"
It's that the name of function gpio_get_val now is changed to gpio_get_value;

Hooray! Now you can find the complied file of example named LIBGPIO_TEST under testsuites/samples/

Therefore, we use the arm toolchain to wrap the executable file as image:

arm-rtems4.11-objcopy -Obinary $HOME/development/build-rtems-rpi-gpio/arm-rtems4.11/c/raspberrypi/testsuites/samples/LIBGPIO_TEST/LIBGPIO_TEST.exe kernel.img


----------------------------------------------------------------------

I also build two cases into the samples:
One is for LCD+Keypad:
It is important that the keypad has PULL_UP resistor.
  
https://github.com/c0066c/rtems-gpio/tree/Keypad_test/testsuites/samples/GPIO_KEYPAD

arm-rtems4.11-objcopy -Obinary /home/khchen/development/build-rtems-rpi-gpio/arm-rtems4.11/c/raspberrypi/testsuites/samples/GPIO_KEYPAD/GPIO_KEYPAD.exe kernel.img

Another is for Pibrella:
It is also really important that the button on Pibrella has PULL_DOWN resistor.

https://github.com/c0066c/rtems-gpio/tree/Keypad_test/testsuites/samples/GPIO_Pibrella

arm-rtems4.11-objcopy -Obinary /home/khchen/development/build-rtems-rpi-gpio/arm-rtems4.11/c/raspberrypi/testsuites/samples/GPIO_Pibrella/GPIO_Pibrella.exe kernel.img

When you press button, don't let the circuit short...
Otherwise YOU WILL CONFUSE YOURSELF!!


Resource:
https://www.raspberrypi.org/documentation/usage/gpio-plus-and-raspi2/README.md
https://devel.rtems.org/wiki/GSoC/2013/Raspberry_Pi_BSP_Peripherals
blog https://asuolgsoc2014.wordpress.com/2014/06/
Display+Keypadhttp://www.conrad.de/ce/de/product/1070528/Raspberry-Pi-Display-Modul-1115 

Comments

Post a Comment

Popular posts from this blog

RSB+RTEMS 5/6 with QEMU-SMP (ARM realview_pbx_a9_qemu as example)

Since I got a request regarding this blog  written in 2016, summarizing again the complete flow with the latest version of RTEMS could be a good idea. Prepare a suitable workspace according to the adopted operating system on your host ( https://docs.rtems.org/branches/master/user/hosts/index.html ):  sudo apt-get build-dep build-essential gcc-defaults g++ gdb git unzip pax bison flex texinfo unzip python3-dev libpython-dev libncurses5-dev zlib1g-dev Checkout RSB and build: git clone git://git.rtems.org/rtems-source-builder.git rsb change directory to rsb/rtems/ and type ../source-builder/sb-set-builder --prefix=<the path you like to store the built toolchains> <the name of bsp> For example, to use QEMU, I need toolchains for ARM, so: ../source-builder/sb-set-builder --prefix=/home/kh.chen/respository/build/. 6/rtems-arm This will take a while. Please ensure your connection is reliable. Add the built folder into your PATH. For example, you can add one line in ~/.bas...
Post a Comment
Read more

[LEGO nxt] Install the Enhanced NXT firmware and Upload the OSEK excutable file with Ubuntu 64bits 14.04 in 2015

This tutorial is referred from Install the Enhanced NXT firmware on NXT . I think this is the critical part to capture the idea from the tutorial for Windows. I have tried many ways to conquer the problem of libnxt3.0, however, I still have some problems on the compilation of fwflash or something else. Though the tutorial for Windows is doable, my preference is to build up everything with Linux environment. Fortunately, I notice that NxTTool in the tutorial for Windows is really powerful. We can handle the firmware updating by using NxTTool in Linux as well! I also refer to this Japanese Blog , which inspire me a lot. As usual, install the required packages: sudo apt-get install libusb-dev:i386 libusb-0.1-4 subversion fpc Please note, here is the case for 64bits user that I change libusb-dev to libusb-dev:i386 comparing to the original tutorial. Instead of using libnxt to do the uploading, here I follow that JP Blog to get the latest version of bricxcc: (The url in blog i...
Post a Comment
Read more

Virtualenv experience or alternatives

Today I have a project which requires several packages on my python. However, due to whatever reason, I have a lot of different versions of python. Before I thought, it was fine to just install and maintain each by each. Maybe it is time to learn how to use virtualenv. (alternatively, you can use module). I first got some quick ideas from here: https://stackoverflow.com/questions/10763440/how-to-install-python3-version-of-package-via-pip-on-ubuntu The magic virtualenv does is that, it copies a series of your python binaries, include, pip, etc., into a folder. The prepared activate script does that, add the export folder into the general variable PATH at its beginning. By doing so, the targeted version of python will be the first target that will be executed. To enable virtualenv, source the position of the above folder/bin/activate To leave the virtualenv, just type deactivate, as it is defined when you load the activate script. For example, I call virtualenv in my home ...
Post a Comment
Read more