Skip to main content

[RTEMS/QEMU] Emulation with RTEMS on Qemu (realview_pbx_a9_qemu bsp)

Although I have a similar article last year and play around with Raspberry Pi before, now I pick up this QEMU emulation with RTEMS again for my research. Thanks for anonymous people who give me suggestions. Again I wrote down the complete flow again to backup/summarize the information I need here. Hopefully it could also aid you. Enjoy it!

From Alan's Tech Notes and official guide, to have a totally new environment for RTEMS:
  1. I strongly recommend to use RTEMS source builder so-called RSB to prepare all the essential stuffs. Before digging into the details, Ubuntu prerequisties should be somehow in your system. (refer to Alan's note):
    2. $ sudo apt-get install build-essential
$ sudo apt-get install git
$ sudo apt-get install python-dev
$ sudo apt-get build-dep binutils gcc g++ gdb unzip git
  2. First make a specific folder for the source code of rtems-source-builder:
    $ cd
$ mkdir -p development/rtems/rsb
$ cd development/rtems/rsb
$ git clone git://git.rtems.org/rtems-source-builder.git
$ cd rtems-source-builder
$ cd rtems
  3. Under the source-builder folder, type the following command:
    $ ../source-builder/sb-check
    to check if the environment and essential tools are prepared properly.
  4. Then (Please note, now the latest version is 4.12)
    $ ../source-builder/sb-set-builder \
         --log=build-log.txt \
         --prefix=$HOME/development/rtems/compiler/4.12 \
          4.12/rtems-arm
  5. It will spend quite a long time, just leave the terminal there...
After all, the environment involved cross-compiler and the other toolchains are all there.
Don't forget to add the path in your .profile or .bashrc:

PATH=[whatever place that has RTEMS toolchain]:$PATH

------------------ Now talk about QEMU:

In fact I planned to play with Gem5 before, however it still doesn't work yet.
Instead, QEMU is still a viable solution to us to demonstrate RTEMS's features.
To know how to compile the example in RTEMS source code, please refer to my previous article.

At first, download the source tree from RTEMS git 
git clone https://github.com/RTEMS/rtems.git
To build up all the auto generated makefile and configuration 
./bootstrap
Do the configuration:
The following commands are implicitly pointing to the bsp and the options I use for uniprocessor. 
../rtems-gpio/configure --target=arm-rtems4.12 \
 --enable-rtemsbsp=realview_pbx_a9_qemu \
 --enable-tests=samples --enable-networking \
 --enable-posix --prefix=$HOME/development/rtems/4.12
For SMP (including all the testsuites):
../rtems-smp/configure --target=arm-rtems4.12 \
--enable-rtemsbsp=realview_pbx_a9_qemu_smp --enable-smp \
--enable-tests=yes --prefix=$HOME/development/rtems/compiler/4.12

After this, follow the standard way to compile the source tree 
make install
If we consider to run helloworld.exe kernel directly on qemu (assume you are now in the build tree/helloworld), type the following commands:
qemu-system-arm -no-reboot -nographic -M realview-pbx-a9 -m 256M -kernel \
hello.exe 
For SMP:
qemu-system-arm -no-reboot -nographic -M realview-pbx-a9 -m 256M -kernel \
hello.exe -smp 4
For debugging, please refer to http://wiki.osdev.org/Kernel_Debugging

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