Skip to main content

RTEMS on Raspberry Pi

 Thanks for Michael Engel's help, I reach the point about the first run of example.
The board I used is the module A and USB to TTL Serial Cable(http://www.adafruit.com/products/954)


I also check on http://alanstechnotes.blogspot.de/2013/03/running-your-first-rtems-program-on.html to know how to place the file into SD card.

This is the way I generate the kernel by the example:
arm-rtems4.11-objcopy -Obinary /home/khchen/development/build-rtems-rpi/arm-rtems4.11/c/raspberrypi/testsuites/samples/ticker/ticker.exe kernel.img

However, I find that it is not that trivial to just copy kernel.img into the card!

We first have to format the SD card via the mkcard.txt script before copying the kernel.
(wget http://downloads.angstrom-distribution.org/demo/beaglebone/mkcard.txt)

"use dmesg | tail" to find out the removable disk label, e.g., sdb.
sudo ./mkcard.txt /dev/sdb (run it twice in my case)
First time, it will report this "the device apparently does not exist; did you specify it correctly?"


To build the SD card for Raspberry Pi kernel, the initial partition should be proper.
We can find the information from here : http://elinux.org/RPi_Advanced_Setup
(12.12.2017: the script is somehow not reliable. Please directly use the expert mode to partition the SD card. 7.4Mb for boot. )


We can observe that the connection of usb -> /dev/ttyUSB0 has a different group permission.
Therefore, we have to assign our account into this group, named diologout(20).
http://askubuntu.com/questions/40959/how-do-i-connect-to-tty-com-dev-ttyusb0

After all, we can use screen command to connect into the board with root bash:
sudo bash

screen /dev/ttyUSB0 115200
Also, with HDMI, we can see a colourful figure on the screen.
------------------------------------------------
(I find that I cannot use rsb to build my own toolchain due to the version conflict of python 2.7.10)

About the building of example:
Under the git folder (rtems-git), we do have to ./bootstrap
Then, go to the build folder, e.g.,  /home/khchen/development/build-rtems-rpi/
and run: 
../rtems-git/configure --target=arm-rtems4.11 \
--enable-rtemsbsp=raspberrypi \
--enable-tests=samples \
--enable-networking \
--enable-posix \
--prefix=$HOME/development/rtems/4.11 %I put the bsp file into the folder of toolchain.
and 
make install
We can also try the additional example released by RTEMS, under git folder (rtems-git)
git clone git://git.rtems.org/examples-v2.git examples-v2
cd examples-v2
export RTEMS_MAKEFILE_PATH=~/development/rtems/4.11/arm-rtems4.11/raspberrypi/
make

arm-rtems4.11-objcopy -Obinary $HOME/development/examples-v2/classic_api/triple_period/o-optimize/triple_period.exe kernel.img

Instead of examples-v2, all the others are listed on https://git.rtems.org/
git clone git://git.rtems.org/network-demo network-demo
cd examples-v2
export RTEMS_MAKEFILE_PATH=~/development/rtems/4.11/arm-rtems4.11/raspberrypi/
make
http://superuser.com/questions/674672/sdcard-dev-sdb2-is-apparently-in-use-by-the-system-will-not-make-a-filesystem

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