Gsoc midterm evaluations pass last week, and there’s some good news about the status of my project, since the close relation between Openembedded and Poky I extend the support for Xilinx platforms to Poky which is faster than OE to build the rootfs for the reason that are far less recipes to parse and some others features. While Poky support for virtex5 platforms resolves my thesis problem to provide a graphical desktop, it also makes easier the software development for new users by using the Poky Anjuta plug-in although in can be used with OE.
Microblaze support still needs some work, but I’m close to complete it there’s no major changes
that I need to add to OE just resolve some issues with gcc and binutils related on shared libraries
linkage, there was reported a similar problem in OE mailing list, and going to start looking on that
And since Gsoc program is approaching to the end, I’m considering to start looking on labor
market, but first I need to complete my thesis and unfortunately this means a two month slip
:(, at the moment I’m having some hard to track issues on a hardware bridge from the system
bus to a simple peripheral and requires to learn how to use chip-scope (virtual logic analyzer)
to track the signals in order to validate its behavior. Thank fully there are some channels on
YouTube where I can learn in a simple and pain less way thanks to several Indian Technology
Institutes for having lectures online.
Listo, now the next step is to configure the plug-in to start development with Anjuta,
In Anjuta go toEdit->Preferences
Enable the plug-in:
Configure the toolchain path: /usr/local/poky/eabi-glibc/arm/
At the moment we will leave the Target options as shown in further post I will deal with this.
Close the preferences dialog; Create a New Project File->New->Project
Select an C GTK+ type.
Run Autogenerate… Build->Run Autogenerate…
You will see messages like:
checking for arm-poky-linux-gnueabi-strip… arm-poky-linux-gnueabi-strip
checking whether to enable maintainer-specific portions of Makefiles… yes
checking for style of include used by make… GNU
checking for arm-poky-linux-gnueabi-gcc… arm-poky-linux-gnueabi-gcc
checking for C compiler default output file name… a.out
checking whether the C compiler works… yes
checking whether we are cross compiling… yes
If not then you are not setting correctly the toolchain root path or you misspell the toolchain prefix.
That would place a binary your src directory.
On my next post I will go through procedure of running the previous example on Quemu as target platform, while you can start designing and coding : )