Home Software Development Pre-built Images

Pre-Built Images

E-mail Print PDF
User Rating: / 16
PoorBest 

In addition to the software packages available via the opkg package manager, Gumstix provides pre-built bootloaders, Linux kernels and root file systems.

It is highly recommend that customers who just received a Gumstix COM in a recent order update that COM to the latest tested and stable image. The image pre-loaded on that COM could be several weeks or even a few months old due to manufacturing logistics.

Images for Overo Series

Pre-built images are available for the Angstrom distribution in stable and development flavours. Be sure to download a matching set of bootloaders, kernels, modules, and root file systems.

 

Tested, Stable Images

Pre-built factory images·are available·here for customers wanting to install a tested, stable image on their Overo COM. Factory images are taken from the prebuilt desktop-nand image and booted once to eliminate all the set-up that happens on the first boot. ·The directory name indicates the original development image used; typically these images would be used during the build process of Gumstix COMs shortly after this date.

 

Development Images

Development images for the Overo series are available·here. These images are recent builds from the top of the Overo OpenEmbedded build tree.

Note: The desktop images may appear to hang the first time they are booted, displaying only a blinking cursor on screen, or "configuring xxx" on the debug console. This is normal and the system should complete booting if left for an hour.

 

Instructions to Update the Images on your Overo COM

To update the u-boot, Linux kernel and root file system images on your Overo COM, you'll need to update the NAND. To do this, start with a bootable microSD card and follow the instructions in this·Write Images to FLASH article. If you need to create your own bootable microSD card, follow these instructions to Create a bootable microSD card article.

You can also use these images to boot from NAND  When writing to NAND, keep in mind the size limitations of the NAND roofs partition. In particular you will need to use omap3-desktop-nand-image rather than omap3-desktop-image.

Note, if you just want to add some more software to your current image, check out our tutorial on the opkg package manager instead.

 

Images for the Verdex Pro Series

Images for verdex pro, verdex, connex, and basix COMs are available here. You will find three subdirectories at this location: u-boot, archive, current. The u-boot subdirectory contains the bootloader binaries for each of these product lines. The filenames are of the form: u-boot-{family}-{clock speed}-{revision}.bin.

verdex pro COMs will boot directly from a properly prepared microSD card. Follow the instructions posted here to create a bootable microSD card.

Basix users should use a connex image which matches their motherboard clock rate. Archive stored previous builds where the subdirectory name indicates the source code revision and the target library used for the build.  Again, Basix users should use the Connex images.  The current directory contains the most recent build from Archive.