[LEGO nxt] Set up OSEK build tree on Ubuntu 64bits 14.04 in 2015

As we have the ARM cross compiler in the previous quest, now we can set up the environment of OSEK build tree.

I take a reference from Set up nxtOSEK, and update some out-date information.
All the concepts are repeatable in VirtualBox with same environment.

First, install the wine:

sudo apt-get install wine

Then, download nxtOSEK from here http://sourceforge.net/projects/lejos-osek/files/nxtOSEK/
nxtOSEK_v218.zip is the latest version currently.
And a patch from TOPPERS:

wget http://www.toppers.jp/download.cgi/osek_os-1.1.lzh

Merge them accordingly.

Under ecrobot directory, update tool_gcc.mak file to specify with the variable GNUARM_ROOT the path to the installed GNU ARM directory.

# specify GNU-ARM root directory
 ifndef GNUARM_ROOT
 GNUARM_ROOT = /[absolute path to parent directory of gnuarm]/gnuarm
 endif

Then we can change directory to nxtOSEK/samples_c/helloworld directory and build binary executables of helloworld sample with the following commands:

~$ cd ./nxtOSEK/samples_c/helloworld 
~$ make all

If everything goes well, you can find out the executable and some upload programs there.

HOTFIX:
ecrobot.mak and ecrobot++.mak in 218 have some new codes related to detecting the operating system. However it doesn't work for Linux (so far). Please get the nxtOSEK files from some previous version, e.g., 214.

Comments

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...

[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...

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 ...

Adventure Journey on ES / RTOS

Search This Blog