Tag Archives: xburst

Virtual Appliance with Debian Squeeze and OpenWRT-XBurst Development Tools for Qi Hardware’s Ben Nanonote

This post is about a Virtual Appliance with Debian Squeeze and OpenWRT-XBurst Development Tools installed, which would allow immediately compiling OpenWRT packages for the Nanonote without going through the painful process of setting up the development environment yourself.

As a non-developer, I found a working development environment to be the single most confusing part of porting to the Nanonote, even more confusing than OpenWRT’s Makefiles. Granted, this could be my personal lack of talent or skill, but it left me thinking removing this “steppingstone” for some of the less experienced users might open more doors, faster, for beginning Nanonote enthusiasts. The instructions at http://en.qi-hardware.com/wiki/Building_OpenWRT_on_Debian_6 are great, but might slightly intimidate less experienced Linux users. They are also slightly daunting to follow if the need arises frequently (if reinstalling OS, royally screwed something up, or other scenarios I’m sure you ran into).

The easiest way to get around this I could come up with was creating a Virtual Appliance which contains the basics for compiling for the Nanonote, using the wiki instructions for Debian Squeeze. Such an appliance can be run in VirtualBox (free and open source) or VMWare Player (free as in beer), even on Windows hosts. The result is a single 2.4 GB file with a ready toolchain which is ready to “accept” package Makefiles and compile them. Debian was installed, the toolchain was compiled, the locales and paths were set. I gave it a quick test compiling Pem (and a load of Perl dependencies) and it seemed to work.

The Virtual Appliance is currently unimaginatively called “Debian Squeeze with OpenWRT-XBurst Development Tools 2011-08-27” and comes as a single .OVA file. See details below:

1. Install VirtualBox.
2. Download Virtual Appliance .OVA file (links below)
3. In VirtualBox click on “Machine” > “Import” and select the .OVA file.

I’ve added a brief section under the Building on … Debian Squeeze wiki page.

Hope someone finds this helpful.

2011-08-27 Release:

Virtual Appliance Download Page on 1fichier.com:  http://4pp1qh.1fichier.com/en/
.OVA file MD5 sum:  3ad6e2aa9379336c10746a3062538d32
user:  build
password:  gongshow
root password:  gongshow
QR Image:

2011-02-23 Release:

Virtual Appliance Download Page on 1fichier.com:  http://0tqstz.1fichier.com/en/
.OVA file MD5 sum:  f9ebe1b0cfe63ae1aa584ddff7b222ed
user:  build
password:  gongshow
root password:  gongshow
QR Image:


— Ernest Kugel


1 Comment

Filed under Ben Nanonote

Qi’s XBurst Tools from source

This post will provide a quick how to on setting up Qi’s XBurst Tools from source, needed to flash their Nanonote. The kind folks from Qi got the source from Ingenic, and with it the lovely toolkit used for USB booting the Nanonote, which in turn allows to flash it.

Now, it’s worth mentioning this is not normally needed, because Qi provide binaries and Debian packages.

If you do wish to go from source, here’s what you’ll need: Linux with a build environment, libusb-dev and libconfuse-dev

My distro (Slackware13  64) had the first 2 in place. I only had to get libconfuse and build it from source. It worked as advertised.

Then, I got the source from the Qi repository. It too worked as advertised. (read: downloaded, compiled and installed).

However, despite having successfully built USBBOOT I could not actually boot the Nanonote, because my AMD64 targeted Slackware’s GCC had not MIPS support. So while it could compile the toolkit, it could not, by definition, compile the target boot image for the XBurst. The only way currently to circumvent this is to get the files from another machine (the boot images contain 2 stages, which you may just download here: xburst_stage1.bin and xburst_stage2.bin), or from the Debian package, as the submitted Debian bug suggests . They should be placed in /usr/local/share/xburst-tools . Currently, those are the only 2 pieces that can’t be built from source on your average Linux desktop, but as you’ve just seen, the best solution is quick and dirty.

1 Comment

Filed under Ben Nanonote