Gumstix User Wiki - User contributions [en]

Category:How to - Buildroot overo

2012-02-09T15:21:29Z

Trevor Woerner: Added more necessary adjustments for a successful image

Officially Gumstix only supports building images for Overo devices using OpenEmbedded. But there are other ways of producing a root filesystem for an Overo device, for example [http://buildroot.uclibc.org/ Buildroot]. Since OE is the only official build system, it remains the best, most up-to-date place to get your cross-development toolchain, kernel, bootloader, and MLO for Overo development.

For the remainder of this document I'm going to assume <tt>${OEBASE}</tt> is where you have checked out OE and <tt>${BRBASE}</tt> is the directory into which you have unpacked Buildroot.

* Start off by following the official instructions for preparing your build system and checking out the OE code at [http://www.gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html Using the Open Embedded Build System for Overo Series]. Follow those instructions right until the end but do not perform the last step (i.e. "<tt>$ bitbake omap3-console-image</tt>")

* Replace the last instruction ("<tt>$ bitbake omap3-console-image</tt>") with the following:
$ bitbake virtual/kernel
$ bitbake x-load
$ bitbake u-boot

With these commands OE has built a cross-development toolchain for you as well as a kernel, MLO, and u-boot bootloader. For the root filesystem we now make use of Buildroot.

* Go to the location where you have unpacked Buildroot and issue:
$ make menuconfig

(If you prefer you can use '<tt>$ make nconfig</tt>', '<tt>$ make xconfig</tt>', or '<tt>$ make gconfig</tt>' instead)

* Under 'Target Architecture'
* select 'arm'

* Under 'Target Architecture Variant'
select 'generic_arm'
further down there is a '<tt>cortex_a8</tt>' option but Buildroot says the <tt>cortex_a8</tt> and <tt>cortex_a9</tt> options require gcc > 4.4.x. Currently the OE toolchain is 4.3.x. '<tt>generic_arm</tt>' seems to work fine

* Under 'Toolchain'
** Toolchain Type
select 'External toolchain'
** Toolchain
'Custom toolchain'
** Toolchain path
enter '${OEBASE}/tmp/sysroots/x86_64-linux/usr/armv7a'
(obviously if your build system is not x86 64-bit this path won't exist, look around and find your equivalent)
** Toolchain prefix
enter 'arm-angstrom-linux-gnueabi'
** External toolchain C library
select 'glibc'
** Select
Toolchain has C++ support
* Under 'System configuration'
** Port to run a getty (login prompt) on
select 'ttyO2'
(NOTE: that is: "tee-tee-why-(capital)Oh-two")

You can leave everything else as-is, or browse around and find other things to tweak.

* Exit the Buildroot configuration system and
$ make

Now when you assemble your Qemu image or SD card you will find your bootloader, MLO, and x-boot as usual in <tt>${OEBASE}/tmp/deploy/glibc/images/overo</tt> but your root filesystem will be found in <tt>${BRBASE}/images</tt>.

By way of comparison a Qemu image created for the Overo converted to VDI format uses:
* 27MB for a buildroot-based image
* 272MB for a completely OE-based image

<pre style="background:black;color:white">
# qemu-system-arm.linaro -M overo -m 256 -clock unix -serial stdio -sd br.HDD

Texas Instruments X-Loader 1.5.1 (Nov 22 2011 - 09:58:25)
OMAP35XX-GP ES3.1
Board revision: 0
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2011.09 (Nov 22 2011 - 10:10:50)

OMAP35XX-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz
Gumstix Overo board + LPDDR/NAND
I2C: ready
DRAM: 256 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Board revision: 0
Direct connection on mmc2
No EEPROM on expansion board
Die ID #51454d5551454d555400000051454d55
Net: smc911x-0
Hit any key to stop autoboot: 0
reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **
reading uImage

3091316 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Angstrom/3.0/overo
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3091252 Bytes = 2.9 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
omap2_inth_read: Bad register 0x00000020
Linux version 3.0.0 (trevor@codei7) (gcc version 4.3.3 (GCC) ) #1 Mon Nov 21 17:37:48 EST 2011
CPU: ARMv7 Processor [412fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Gumstix Overo
Reserving 12582912 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.1 (iva sgx neon isp 720mhz )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x10000
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 61952
Kernel command line: console=ttyO2,115200n8 mpurate=500 vram=12M omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 244MB = 244MB total
Memory: 240900k/240900k available, 21244k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xd0800000 - 0xf8000000 ( 632 MB)
lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc003b000 ( 204 kB)
.text : 0xc003b000 - 0xc05ce764 (5710 kB)
.data : 0xc05d0000 - 0xc061ea10 ( 315 kB)
.bss : 0xc061ea34 - 0xc068291c ( 400 kB)
NR_IRQS:410
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP clockevent source: GPTIMER1 at 32768 Hz
sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
Console: colour dummy device 80x30
Calibrating delay loop... 435.38 BogoMIPS (lpj=1701888)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_hwmod: gpt12_fck: missing clockdomain for gpt12_fck.
omap_hwmod: am35x_otg_hs: cannot be enabled (3)
print_constraints: dummy:
NET: Registered protocol family 16
GPMC revision 5.0
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
omap_mux_init: Add partition: #1: core, flags: 0
Found NAND on CS0
Registering NAND on CS0
platform iva.0: Enabled OPP corresponding to 720MHz
hw-breakpoint: debug architecture 0x0 unsupported.
omap_device: omap-mcbsp.2: alias fck already exists
omap_device: omap-mcbsp.3: alias fck already exists
Switched to new clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
print_constraints: vads7846: 3300 mV
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
omap_i2c omap_i2c.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
print_constraints: VUSB1V5: 1500 mV normal standby
print_constraints: VUSB1V8: 1800 mV normal standby
print_constraints: VUSB3V1: 3100 mV normal standby
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
print_constraints: VMMC1: 1850 <--> 3150 mV at 3150 mV normal standby
print_constraints: VDAC: 1800 mV normal standby
print_constraints: VDVI: 1800 mV normal standby
omap_i2c omap_i2c.3: bus 3 rev3.12 at 400 kHz
Advanced Linux Sound Architecture Driver Version 1.0.24.
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
Switching to clocksource 32k_counter
Switched to NOHz mode on CPU #0
musb-hdrc: version 6.0, musb-dma, host
musb-hdrc musb-hdrc: MUSB HDRC host driver
musb-hdrc musb-hdrc: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 3.0.0 musb-hcd
usb usb1: SerialNumber: musb-hdrc
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc: USB Host mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
platform iva.0: Enabled OPP corresponding to 720MHz
omap-iommu omap-iommu.0: isp registered
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Registering unionfs 2.5.9.2 (for 3.0.0-rc4)
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 470
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
OMAP DSS rev 2.0
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP UART0
omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP UART2
console [ttyO2] enabled
brd: module loaded
loop: module loaded
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit)
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000080000 : "xloader"
0x000000080000-0x000000240000 : "uboot"
0x000000240000-0x000000280000 : "uboot environment"
0x000000280000-0x000000680000 : "linux"
0x000000680000-0x000010000000 : "rootfs"
smsc911x: Driver version 2008-10-21
smsc911x-mdio: probed
smsc911x smsc911x.0: eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1)
smsc911x smsc911x.0: eth0: MAC Address: 52:54:00:12:34:56
smsc911x: Driver version 2008-10-21
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
cdc_ncm: 01-June-2011
usbcore: registered new interface driver cdc_ncm
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 0.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: OMAP-EHCI Host Controller
usb usb2: Manufacturer: Linux 3.0.0 ehci_hcd
usb usb2: SerialNumber: ehci-omap.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 0 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
twl_rtc twl_rtc: Power up reset detected.
i2c /dev entries driver
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: HCILL protocol initialized
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
overo SoC init
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SD card at address 4567
mmcblk0: mmc0:4567 QEMU! 1.00 GiB
mmcblk0: p1 p2
asoc: twl4030-hifi <-> omap-mcbsp-dai.1 mapping ok
ALSA device list:
#0: overo
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2
ThumbEE CPU extension supported.
omap_vp_forceupdate_scale: vdd_mpu_iva TRANXDONE timeout exceeded while tryingto clear the TRANXDONE status
omap_vp_forceupdate_scale: vdd_core TRANXDONE timeout exceeded while tryingto clear the TRANXDONE status
sr_init: No PMIC hook to init smartreflex
smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
clock: disabling unused clocks to save power
fbcvt: 1024x768@60: CVT Name - .786M3-R
Console: switching to colour frame buffer device 128x48
regulator_init_complete: VDAC: incomplete constraints, leaving on
regulator_init_complete: vads7846: incomplete constraints, leaving on
twl_rtc twl_rtc: setting system clock to 2011-11-22 16:31:42 UTC (1321979502)
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 204K
Starting logging: OK
Initializing random number generator... done.
Starting network...

Welcome to Buildroot
buildroot login:
</pre>

Overo emulation in qemu

2011-11-22T17:06:01Z

Trevor Woerner: update to include general purpose qemu image generating script

__TOC__
[[Category:How to - qemu]]

Ash Charles has been working with Riku from the Qemu-linaro team to get support for the Overo hardware working in Qemu!

==Pre-Compiled Images==

Here are Ash's steps for working with pre-compiled images:

* binary executable for qemu available here (for x86_64):
::http://dl.dropbox.com/u/211887/qemu-system-arm
::MD5:c375b7d0338e3e8cd7009e69f3aaae74

* overo angstrom image with a kernel, MLO, u-boot packed:
::http://dl.dropbox.com/u/211887/overo.img.gz
::MD5:3545dbd2e7ffac3d352a7bc9e92373bf

* download, gunzip the overo.img.gz and run with:
::<code># ./qemu-system-arm -M overo -m 256 -sd ./overo.img -clock unix -serial stdio</code>
::(mouse & keyboard don't work currently but the console session is usable)

==From Sources==

* build your overo image using bitbake/OE as usual:
::<code>$ cd $OVEROTOP</code>
::<code>$ bitbake omap3-console-image</code>

* build the MLO program:
::<code>$ bitbake x-load</code>

* get the sources for and build qemu with overo support:
::<code>$ cd $OVEROTOP</code>
::<code>$ git clone git://git.linaro.org/qemu/qemu-linaro.git</code>
::<code>$ cd qemu</code>
::<code>$ ./configure --prefix=$OVEROTOP/local --target-list=arm-softmmu</code>
::<code>$ make install</code>
::<code>$ export PATH=$OVEROTOP/local/bin:$PATH</code>

* there are numerous ways to generate the qemu image file:
::<code># export OEDONE=$OETMP/deploy/glibc/images/overo</code>
** Ash Charles [[Overo_qemu_script|wrote a script]] specifically for generating Overo qemu images:
::<code># assemble-image.sh $OVEROTOP/overo.img $OEDONE/MLO-overo $OEDONE/u-boot-overo.bin $OEDONE/uImage-overo.bin $OEDONE/omap3-console-image-overo.tar.bz2</code>
** or using a more [https://github.com/twoerner/qemu-image-builder general-purpose script] for generating qemu images which includes support for Overo:
::<code># mkqemuimg.sh --partpercents 5 --format ",mkfs.ext3" --bootarm "$OEDONE/MLO-overo,$OEDONE/u-boot-overo.bin,$OEDONE/uImage-overo.bin" 1073741824 $OVEROTOP/overo.img ",$OEDONE/omap3-console-image-overo.tar.bz2"

* then run the image under qemu:
::<code># qemu-system-arm -M overo -m 256 -sd $OVEROTOP/overo.img -clock unix -serial stdio -net user -device usb-kbd -device usb-mouse</code>

Main Page

2011-11-22T16:47:12Z

Trevor Woerner: Add overo buildroot page, move 1-wire link to top of sort

<big>''Welcome to the Gumstix User Wiki''</big>

This site is provided so that users of the Gumstix OpenEmbedded build system can share their knowledge, showcase their Gumstix-based projects, and pass on links to other sources of information and materials. This information is entirely user generated and supported. Please contribute your know-how to help your fellow developers.

'''Customer additions and edits are encouraged, but please read the help page before you make any major edits.'''
''Note: you will need to create a new user account if you would like to contribute or edit content on this site.''

Go to the [http://gumstix.org Gumstix Developer's website] for official Gumstix supported documentation on OpenEmbedded and other information of interest to developers:

{|
| valign="top" |
{|cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5fffa;border:1px solid #bcc"
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's - Focus]]
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's]]
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's]]
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's]]
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:How-tos |User how to's]]

|-
| valign="top" |
* [[:Category:how to - Android|Android]]
* [[:Category:how to - eclipse|Eclipse]]
* [[:Category:How_to_-_Migrate_to_Gumstix|Migrate to Gumstix]]
* [[Linaro]]
* [[:Category:how to - Ubuntu|Ubuntu]]
| valign="top" |
* [[1-wire|1-wire]]
* [[:Category:how to - audio|Audio]]
* [[:Category:how to - adc|ADC]]
* [[AutoLogin|Automatic Logins]]
* [[:Category:how to - batteries|Batteries]]
* [[:Category:how to - bluetooth|Bluetooth]]
* [[:Category:how to - Buildroot overo|Buildroot (overo)]]
* [[:Category:Connect_hardware|Connect Hardware]]
* [[Caspa_camera_boards|Caspa camera boards]]
* [[:Category:how to - displays|Displays]]
* [[:Category:how to - DSP|DSP]]
* [[:Category:how_to_-_ethernet|Ethernet]]
* [[:Category:how_to_-_expansion_boards|Expansion Boards]]
* [[:Category:how to - fedora|Fedora]]
* [[:Category:how to - Fast Boot|Fast Boot]]
* [[:Category:how to - Fortran|Fortran]]

| valign="top" |
* [[Gaining Console Connection via Terminal]]
* [[:Category:how to - git|Git]]
* [[GPIO|GPIO]]
* [[GPS|GPS]]
* [[:Category:how to - gui|GUI]]
* [[:Category:how to - general|General]]
* [[:Category:how to - Build helloworld|HelloWorld]]
* [[HelloWorld|HelloWorld in Python, C, C++]]
* [[HelloWorld in Java|HelloWorld in Java]]
* [[:Category:how to - i2c|I2C]]
* [[:Category:how to - IMU|IMU]]
* [[:Category:how to - JAVA|JAVA]]
* [[Kernel Reconfiguration|Kernel Reconfiguration]]
* [[:Category:how to - Known Issues|Known Issues]]
* [[:Category:how to - LCD|LCD]]
* [[:Category:how to - Low Power|Low Power]]
| valign="top" |
* [[:Category:how to - linux|Linux]]
* [[AudioIn | Use a microphone]]
* [[MicroSd |MicroSD Duplication]]
* [[:Category:how to - Network_Boot|Network Boot]]
* [[:Category:how to - OpenEmbedded|OpenEmbedded]]
* [[:Category:how to - player|Player]]
* [[:Category:How to - PWM|PWM]]
* [[:Category:How_to_-_qemu|Qemu]]
* [[:Category:How_to_-_Qt|Qt]]
* [[:Category:how to - robotics|Robotics]]
* [[ROS|ROS]]
* [[RoboVero|RoboVero]]
* [[:Category:how to - security|Security]]
* [[:Category:SPI|SPI]]
| valign="top" |
* [[:Category:SUSE|SUSE]]
* [[Remote Debugging with GDB|Remote Debugging with GDB]]
* [[U-Boot|UBoot]]
* [[:Category:how to - usb|USB]]
* [[Verdex Git Repository]]
* [[Verdex JTAG]]
* [[VerdexPro U-Boot Flashing Fix]]
* [[:Category:how to - virtual machine|Virtual Machine]]
* [[:Category:how to - webcams|Webcams]]
* [[:Category:how to - wifi|Wifi]]

|}

{|
| valign="top" |
{|cellpadding="2" cellspacing="5" style="vertical-align:top;background-color:#f5fffa;border:1px solid #bcc"
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:projects|User projects]]
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:User_pics_videos|User Pics & Videos]]
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:resources|Resources]]
! style="margin:0;background:#cef2e0;font-size:120%;font-weight:bold;border:1px solid #a3b0bf;text-align:left;color:#000;padding:0.2em 0.4em;" | [[:Category:faqs|Questions and Answers]]

|-
| valign="top" |
* [[:Category:projects - audio|Audio]]
* [[:Category:projects - competitions|Competitions]]
* [[:Category:projects - displays|Displays]]
* [[:Category:projects - pdas|PDA's]]
* [[:Category:Projects_-Research_and_Education|Research & Education]]
* [[:Category:projects - monitoring and control|Monitoring and Control]]
* [[:Category:projects - robotics|Robotics & UAV's]]
| valign="top" |
* [http://www.youtube.com/results?uploaded=m&search_query=gumstix&search_type=videos&suggested_categories=28&uni=3&search_sort=video_date_uploaded Gumstix on Youtube]
* [http://www.flickr.com/search/?q=gumstix&s=rec Gumstix in Flickr]
* [http://www.cs.umd.edu/alandaluz/nchen/ebook/dualdisp-chi.mov Dual Display device at UMD]
| valign="top" |
* [[Windows CE solution|Solutions for Windows CE]]
* [[Qt solution|Solutions for Qt]]
* [[Manufacturer's specifications|Specifications for Processors & Components]]
* [[Software information]]
* [[Supported hardware]]
* [[Third Party Boards]]
| valign="top" |
Gumstix Community Mailing List (no cost)
* [https://lists.sourceforge.net/lists/listinfo/gumstix-users Sign-up]
* [http://old.nabble.com/Gumstix-f22543.html Archives]
|}

For information and support for the legacy gumstix buildroot build system:
[http://docwiki.gumstix.com/Main_Page docwiki.gumstix.com]
.

Category:How to - Buildroot overo

2011-11-22T16:42:00Z

Trevor Woerner: instructions for building a root filesystem for Overo using Buildroot

Officially Gumstix only supports building images for Overo devices using OpenEmbedded. But there are other ways of producing a root filesystem for an Overo device, for example [http://buildroot.uclibc.org/ Buildroot]. Since OE is the only official build system, it remains the best, most up-to-date place to get your cross-development toolchain, kernel, bootloader, and MLO for Overo development.

For the remainder of this document I'm going to assume <tt>${OEBASE}</tt> is where you have checked out OE and <tt>${BRBASE}</tt> is the directory into which you have unpacked Buildroot.

* Start off by following the official instructions for preparing your build system and checking out the OE code at [http://www.gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html Using the Open Embedded Build System for Overo Series]. Follow those instructions right until the end but do not perform the last step (i.e. "<tt>$ bitbake omap3-console-image</tt>")

* Replace the last instruction ("<tt>$ bitbake omap3-console-image</tt>") with the following:
$ bitbake virtual/kernel
$ bitbake x-load
$ bitbake u-boot

With these commands OE has built a cross-development toolchain for you as well as a kernel, MLO, and u-boot bootloader. For the root filesystem we now make use of Buildroot.

* Go to the location where you have unpacked Buildroot and issue:
$ make menuconfig

(If you prefer you can use '<tt>$ make nconfig</tt>', '<tt>$ make xconfig</tt>', or '<tt>$ make gconfig</tt>' instead)

* Under 'Target Architecture'
* select 'arm'

* Under 'Target Architecture Variant'
select 'generic_arm'
further down there is a '<tt>cortex_a8</tt>' option but Buildroot says the <tt>cortex_a8</tt> and <tt>cortex_a9</tt> options require gcc > 4.4.x. Currently the OE toolchain is 4.3.x. '<tt>generic_arm</tt>' seems to work fine

* Under 'Toolchain'
** Toolchain Type
select 'External toolchain'
** Toolchain
'Custom toolchain'
** Toolchain path
enter '${OEBASE}/tmp/sysroots/x86_64-linux/usr/armv7a'
(obviously if your build system is not x86 64-bit this path won't exist, look around and find your equivalent)
** Toolchain prefix
enter 'arm-angstrom-linux-gnueabi'

You can leave everything else as-is, or browse around and find other things to tweak.

* Exit the Buildroot configuration system and
$ make

Now when you assemble your Qemu image or SD card you will find your bootloader, MLO, and x-boot as usual in <tt>${OEBASE}/tmp/deploy/glibc/images/overo</tt> but your root filesystem will be found in <tt>${BRBASE}/images</tt>.

By way of comparison a Qemu image created for the Overo converted to VDI format uses:
* 27MB for a buildroot-based image
* 272MB for a completely OE-based image

<pre style="background:black;color:white">
# qemu-system-arm.linaro -M overo -m 256 -clock unix -serial stdio -sd br.HDD

Texas Instruments X-Loader 1.5.1 (Nov 22 2011 - 09:58:25)
OMAP35XX-GP ES3.1
Board revision: 0
Reading boot sector
Loading u-boot.bin from mmc

U-Boot 2011.09 (Nov 22 2011 - 10:10:50)

OMAP35XX-GP ES3.1, CPU-OPP2, L3-165MHz, Max CPU Clock 600 mHz
Gumstix Overo board + LPDDR/NAND
I2C: ready
DRAM: 256 MiB
NAND: 256 MiB
MMC: OMAP SD/MMC: 0
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Board revision: 0
Direct connection on mmc2
No EEPROM on expansion board
Die ID #51454d5551454d555400000051454d55
Net: smc911x-0
Hit any key to stop autoboot: 0
reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **
reading uImage

3091316 bytes read
Booting from mmc ...
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Angstrom/3.0/overo
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3091252 Bytes = 2.9 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
omap2_inth_read: Bad register 0x00000020
Linux version 3.0.0 (trevor@codei7) (gcc version 4.3.3 (GCC) ) #1 Mon Nov 21 17:37:48 EST 2011
CPU: ARMv7 Processor [412fc083] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: Gumstix Overo
Reserving 12582912 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP3430/3530 ES3.1 (iva sgx neon isp 720mhz )
SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x10000
Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
Reprogramming SDRC clock to 332000000 Hz
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 61952
Kernel command line: console=ttyO2,115200n8 mpurate=500 vram=12M omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 244MB = 244MB total
Memory: 240900k/240900k available, 21244k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xd0800000 - 0xf8000000 ( 632 MB)
lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc003b000 ( 204 kB)
.text : 0xc003b000 - 0xc05ce764 (5710 kB)
.data : 0xc05d0000 - 0xc061ea10 ( 315 kB)
.bss : 0xc061ea34 - 0xc068291c ( 400 kB)
NR_IRQS:410
IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts
Total of 96 interrupts on 1 active controller
OMAP clockevent source: GPTIMER1 at 32768 Hz
sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms
Console: colour dummy device 80x30
Calibrating delay loop... 435.38 BogoMIPS (lpj=1701888)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_hwmod: gpt12_fck: missing clockdomain for gpt12_fck.
omap_hwmod: am35x_otg_hs: cannot be enabled (3)
print_constraints: dummy:
NET: Registered protocol family 16
GPMC revision 5.0
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
OMAP GPIO hardware version 2.5
omap_mux_init: Add partition: #1: core, flags: 0
Found NAND on CS0
Registering NAND on CS0
platform iva.0: Enabled OPP corresponding to 720MHz
hw-breakpoint: debug architecture 0x0 unsupported.
omap_device: omap-mcbsp.2: alias fck already exists
omap_device: omap-mcbsp.3: alias fck already exists
Switched to new clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz
OMAP DMA hardware revision 4.0
bio: create slab <bio-0> at 0
print_constraints: vads7846: 3300 mV
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
omap_i2c omap_i2c.1: bus 1 rev3.12 at 2600 kHz
twl4030: PIH (irq 7) chaining IRQs 368..375
twl4030: power (irq 373) chaining IRQs 376..383
twl4030: gpio (irq 368) chaining IRQs 384..401
print_constraints: VUSB1V5: 1500 mV normal standby
print_constraints: VUSB1V8: 1800 mV normal standby
print_constraints: VUSB3V1: 3100 mV normal standby
twl4030_usb twl4030_usb: Initialized TWL4030 USB module
print_constraints: VMMC1: 1850 <--> 3150 mV at 3150 mV normal standby
print_constraints: VDAC: 1800 mV normal standby
print_constraints: VDVI: 1800 mV normal standby
omap_i2c omap_i2c.3: bus 3 rev3.12 at 400 kHz
Advanced Linux Sound Architecture Driver Version 1.0.24.
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
Switching to clocksource 32k_counter
Switched to NOHz mode on CPU #0
musb-hdrc: version 6.0, musb-dma, host
musb-hdrc musb-hdrc: MUSB HDRC host driver
musb-hdrc musb-hdrc: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 3.0.0 musb-hcd
usb usb1: SerialNumber: musb-hdrc
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc: USB Host mode controller at fa0ab000 using DMA, IRQ 92
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
platform iva.0: Enabled OPP corresponding to 720MHz
omap-iommu omap-iommu.0: isp registered
VFS: Disk quotas dquot_6.5.2
Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Registering unionfs 2.5.9.2 (for 3.0.0-rc4)
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 470
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
OMAP DSS rev 2.0
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP UART0
omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP UART2
console [ttyO2] enabled
brd: module loaded
loop: module loaded
omap2-nand driver initializing
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xba (Micron NAND 256MiB 1,8V 16-bit)
Creating 5 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000080000 : "xloader"
0x000000080000-0x000000240000 : "uboot"
0x000000240000-0x000000280000 : "uboot environment"
0x000000280000-0x000000680000 : "linux"
0x000000680000-0x000010000000 : "rootfs"
smsc911x: Driver version 2008-10-21
smsc911x-mdio: probed
smsc911x smsc911x.0: eth0: attached PHY driver [Generic PHY] (mii_bus:phy_addr=0:01, irq=-1)
smsc911x smsc911x.0: eth0: MAC Address: 52:54:00:12:34:56
smsc911x: Driver version 2008-10-21
usbcore: registered new interface driver asix
usbcore: registered new interface driver cdc_ether
cdc_ncm: 01-June-2011
usbcore: registered new interface driver cdc_ncm
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
ehci-omap ehci-omap.0: new USB bus registered, assigned bus number 2
ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
ehci-omap ehci-omap.0: USB 2.0 started, EHCI 0.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: OMAP-EHCI Host Controller
usb usb2: Manufacturer: Linux 3.0.0 ehci_hcd
usb usb2: SerialNumber: ehci-omap.0
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 0 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0
twl_rtc twl_rtc: Power up reset detected.
i2c /dev entries driver
OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
Bluetooth: HCILL protocol initialized
cpuidle: using governor ladder
cpuidle: using governor menu
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
usbcore: registered new interface driver snd-usb-audio
overo SoC init
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SD card at address 4567
mmcblk0: mmc0:4567 QEMU! 1.00 GiB
mmcblk0: p1 p2
asoc: twl4030-hifi <-> omap-mcbsp-dai.1 mapping ok
ALSA device list:
#0: overo
oprofile: hardware counters not available
oprofile: using timer interrupt.
TCP cubic registered
NET: Registered protocol family 17
NET: Registered protocol family 15
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 2
ThumbEE CPU extension supported.
omap_vp_forceupdate_scale: vdd_mpu_iva TRANXDONE timeout exceeded while tryingto clear the TRANXDONE status
omap_vp_forceupdate_scale: vdd_core TRANXDONE timeout exceeded while tryingto clear the TRANXDONE status
sr_init: No PMIC hook to init smartreflex
smartreflex smartreflex.0: omap_sr_probe: SmartReflex driver initialized
smartreflex smartreflex.1: omap_sr_probe: SmartReflex driver initialized
clock: disabling unused clocks to save power
fbcvt: 1024x768@60: CVT Name - .786M3-R
Console: switching to colour frame buffer device 128x48
regulator_init_complete: VDAC: incomplete constraints, leaving on
regulator_init_complete: vads7846: incomplete constraints, leaving on
twl_rtc twl_rtc: setting system clock to 2011-11-22 16:31:42 UTC (1321979502)
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 204K
Starting logging: OK
Initializing random number generator... done.
Starting network...

Welcome to Buildroot
buildroot login:
</pre>

Category:How to - Buildroot overo

2011-11-22T16:20:13Z

Trevor Woerner: instructions for how to build a root filesystem for Overo using Buildroot

Overo emulation in qemu

2011-11-22T15:28:51Z

Trevor Woerner: Undo revision 5707, '$' indicates commands which can be performed with regular privileges, '#' requires elevated privileges

__TOC__
[[Category:How to - qemu]]

Ash Charles has been working with Riku from the Qemu-linaro team to get support for the Overo hardware working in Qemu!

==Pre-Compiled Images==

Here are Ash's steps for working with pre-compiled images:

* binary executable for qemu available here (for x86_64):
::http://dl.dropbox.com/u/211887/qemu-system-arm
::MD5:c375b7d0338e3e8cd7009e69f3aaae74

* overo angstrom image with a kernel, MLO, u-boot packed:
::http://dl.dropbox.com/u/211887/overo.img.gz
::MD5:3545dbd2e7ffac3d352a7bc9e92373bf

* download, gunzip the overo.img.gz and run with:
::<code># ./qemu-system-arm -M overo -m 256 -sd ./overo.img -clock unix -serial stdio</code>
::(mouse & keyboard don't work currently but the console session is usable)

==From Sources==

* build your overo image using bitbake/OE as usual:
::<code>$ cd $OVEROTOP</code>
::<code>$ bitbake omap3-console-image</code>

* build the MLO program:
::<code>$ bitbake x-load</code>

* get the sources for and build qemu with overo support:
::<code>$ cd $OVEROTOP</code>
::<code>$ git clone git://git.linaro.org/qemu/qemu-linaro.git</code>
::<code>$ cd qemu</code>
::<code>$ ./configure --prefix=$OVEROTOP/local --target-list=arm-softmmu</code>
::<code>$ make install</code>
::<code>$ export PATH=$OVEROTOP/local/bin:$PATH</code>

* use [[Overo_qemu_script|Ash's supplied script]] to generate a qemu image:
::<code># export OEDONE=$OETMP/deploy/glibc/images/overo</code>
::<code># assemble-image.sh $OVEROTOP/overo.img $OEDONE/MLO-overo $OEDONE/u-boot-overo.bin $OEDONE/uImage-overo.bin $OEDONE/omap3-console-image-overo.tar.bz2</code>

* then run the image under qemu:
::<code># qemu-system-arm -M overo -m 256 -sd $OVEROTOP/overo.img -clock unix -serial stdio -net user -device usb-kbd -device usb-mouse</code>

Category:How to - OpenEmbedded

2011-07-07T17:48:42Z

Trevor Woerner: fix link - it pointed to a "getting started" page instead of the OE instructions for overo

Gumstix uses the OpenEmbedded build environment so developers can create a complete Linux Distribution for embedded systems.

== Overo ==
Instructions for setting up an OE build environment for the Overo series have been posted on www.gumstix.org [http://gumstix.org/software-development/open-embedded/61-using-the-open-embedded-build-system.html here].

== Verdex Pro ==
Instructions for setting up an OE build environment for the Verdex Pro series have been posted in various places at various times. As of Oct2010, the current instructions are [http://www.gumstix.net/wiki/index.php?title=Verdex_Git_Repository here] <font color=red>(Broken Link)</font>. They tell you how to build a filesystem image out of your own Git repository with the current kernel (2.6.32 in Oct2010).
Cautions: the build tree can take up over 30 GB unless you add 'INHERIT += rm_work' to your local.conf; by default, the generated filesystem is bigger than Verdex Flash and can be loaded on a specially partitioned MMC card (instructions linked from the page).

Instructions for building a 2.6.21 kernel and appropriate filesystem, from OE and SVN, are [http://www.gumstix.net/Setup-and-Programming/cat/Build-system-overview/111.html here] <font color=red>(Broken Link)</font>. As of Oct2010, some of the download URLs are stale, but you should be able to fix all problems by Googling for the error messages.

The old Buildroot documentation for 2.6.21gum kernels is still [http://docwiki.gumstix.org/Buildroot here]. As of Oct2010, many of the download links are stale, but individual packages are available [http://www.daimi.au.dk/~spider/gumstix/gumstix-buildroot/dl/ here] or by Googling the individual package names as they come up in error messages.

'''Kernel'''
There are numerous methods of kernel development; some consider Buildroot the most straightforward. Those using OE may find these links offer useful workflows for kernel development:
* http://ao2.it/en/blog/2010/05/27/neat-compilerun-cycle-git-and-openembedded
* http://bec-systems.com/site/521/best-practices-for-kernel-development-with-openembedded
* http://blogs.elphel.com/2009/12/openembeddedangstrom-kernel-workflow/

To directly cross-compile the 2.6.21 kernel from the OE/SVN tree try these commands:
source ${GUMSTIX_TOP}/extras/profile
cd ${GUMSTIX_TOP}/tmp/work/gumstix-custom-verdex-angstrom-linux-gnueabi/gumstix-kernel-2.6.21-r1/linux-2.6.21
make ARCH=arm CROSS_COMPILE=${GUMSTIX_TOP}/tmp/cross/bin/arm-angstrom-linux-gnueabi-

Overo emulation in qemu

2011-07-07T17:15:46Z

Trevor Woerner:

__TOC__
[[Category:How to - qemu]]

Ash Charles has been working with Riku from the Qemu-linaro team to get support for the Overo hardware working in Qemu!

==Pre-Compiled Images==

Here are Ash's steps for working with pre-compiled images:

* binary executable for qemu available here (for x86_64):
::http://dl.dropbox.com/u/211887/qemu-system-arm
::MD5:c375b7d0338e3e8cd7009e69f3aaae74

* overo angstrom image with a kernel, MLO, u-boot packed:
::http://dl.dropbox.com/u/211887/overo.img.gz
::MD5:3545dbd2e7ffac3d352a7bc9e92373bf

* download, gunzip the overo.img.gz and run with:
::<code># ./qemu-system-arm -M overo -m 256 -sd ./overo.img -clock unix -serial stdio</code>
::(mouse & keyboard don't work currently but the console session is usable)

==From Sources==

* build your overo image using bitbake/OE as usual:
::<code>$ cd $OVEROTOP</code>
::<code>$ bitbake omap3-console-image</code>

* build the MLO program:
::<code>$ bitbake x-load</code>

* get the sources for and build qemu with overo support:
::<code>$ cd $OVEROTOP</code>
::<code>$ git clone git://git.linaro.org/people/rikuvoipio/qemu.git</code>
::<code>$ cd qemu</code>
::<code>$ git checkout overo</code>
::<code>$ ./configure --prefix=$OVEROTOP/local --target-list=arm-softmmu</code>
::<code>$ make install</code>
::<code>$ export PATH=$OVEROTOP/local/bin:$PATH</code>

* use [[Overo_qemu_script|Ash's supplied script]] to generate a qemu image:
::<code># export OEDONE=$OETMP/deploy/glibc/images/overo</code>
::<code># assemble-image.sh $OVEROTOP/overo.img $OEDONE/MLO-overo $OEDONE/u-boot-overo.bin $OEDONE/uImage-overo.bin $OEDONE/omap3-console-image-overo.tar.bz2</code>

* then run the image under qemu:
::<code># qemu-system-arm -M overo -m 256 -sd $OVEROTOP/overo.img -clock unix -serial stdio</code>

Overo qemu script

2011-07-07T17:15:30Z

Trevor Woerner:

[[Category:How to - qemu]]
<pre>
#!/bin/bash
# This script generates SD card disk images suitable for use with QEMU.
#
# Copyright (C) 2011 Ash Charles
# Based on:
# Narcissus - Online image builder for the angstrom distribution
# Copyright (C) 2008 - 2011 Koen Kooi
# Copyright (C) 2010 Denys Dmytriyenko
# and
# Linaro Images Tools.
# Author: Guilherme Salgado <guilherme.salgado@linaro.org>
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License version 2 as
# published by the Free Software Foundation.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License along
# with this program; if not, write to the Free Software Foundation, Inc.,
# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

LC_ALL=C
set -e

function usage()
{
echo "This utility generates SD card images suitable for use with QEMU."
echo "Usage:"
echo " $0 <output name> <mlo> <u-boot> <kernel> <rootfs>"
echo "Example:"
echo " $0 sd.img ~/MLO ~/u-boot.bin ~/uImage ~/rootfs.tar.bz2"
}

function check_args()
{
echo $#
if [ $# -ne 5 ]; then
usage
exit 1
fi
OUTFILE=$1
MLO=$2
UBOOT=$3
KERNEL=$4
ROOTFS=$5

if ! [[ -e ${MLO} ]]; then
echo "MLO not found at ${MLO}! Quitting..."
exit 1
fi
if ! [[ -e ${UBOOT} ]]; then
echo "U-boot not found at ${UBOOT}! Quitting..."
exit 1
fi
if ! [[ -e ${KERNEL} ]]; then
echo "Kernel not found at ${KERNEL}! Quitting..."
exit 1
fi
if ! [[ -e ${ROOTFS} ]]; then
echo "Rootfs not found at ${ROOTFS}! Quitting..."
exit 1
fi
}

SIZE=1073741824 # 1G by default

function make_image()
{
qemu-img create -f raw ${OUTFILE} ${SIZE}

CYLINDERS=`echo ${SIZE}/255/63/512 | bc`
{
echo ,9,0x0C,*
echo ,,,-
} | sfdisk -D -H 255 -S 63 -C ${CYLINDERS} ${OUTFILE} &> /dev/null

# Reverse-engineer the partition setup
BYTES_PER_SECTOR="$(/sbin/fdisk -l -u ${OUTFILE} | grep Units | awk '{print $9}')"
VFAT_SECTOR_OFFSET="$(/sbin/fdisk -l -u ${OUTFILE} | grep img1 | awk '{print $3}')"
EXT3_SECTOR_OFFSET="$(/sbin/fdisk -l -u ${OUTFILE} | grep img2 | awk '{print $2}')"
}

function populate_image()
{
LOOP_DEV="/dev/loop1"
LOOP_DEV_FS="/dev/loop2"

echo "[ Format vfat partition ]"
/sbin/losetup -v -o $(expr ${BYTES_PER_SECTOR} "*" ${VFAT_SECTOR_OFFSET}) ${LOOP_DEV} ${OUTFILE}
mkfs.vfat -F 32 -n "boot" ${LOOP_DEV}

echo "[ Format ext3 partition ]"
/sbin/losetup -v -o $(expr ${BYTES_PER_SECTOR} "*" ${EXT3_SECTOR_OFFSET}) ${LOOP_DEV_FS} ${OUTFILE}
/sbin/mkfs.ext3 -L rootfs ${LOOP_DEV_FS}

echo "[ Copying files to vfat ]"
mount ${LOOP_DEV} /mnt
cp -v ${MLO} /mnt/MLO
cp -v ${UBOOT} /mnt/u-boot.bin
cp -v ${KERNEL} /mnt/uImage
umount ${LOOP_DEV}

echo "[ Copying file system ]"
mount ${LOOP_DEV_FS} /mnt
tar xaf ${ROOTFS} -C /mnt
umount ${LOOP_DEV_FS}

echo "[ Clean up ]"
/sbin/losetup -d ${LOOP_DEV}
/sbin/losetup -d ${LOOP_DEV_FS}
}

ARGS=$*
check_args $ARGS
make_image
populate_image
</pre>

Overo qemu script

2011-07-07T17:13:12Z

Trevor Woerner: Script for generating an Overo Qemu image

<pre>
#!/bin/bash
# This script generates SD card disk images suitable for use with QEMU.
#
# Copyright (C) 2011 Ash Charles
# Based on:
# Narcissus - Online image builder for the angstrom distribution
# Copyright (C) 2008 - 2011 Koen Kooi
# Copyright (C) 2010 Denys Dmytriyenko
# and
# Linaro Images Tools.
# Author: Guilherme Salgado <guilherme.salgado@linaro.org>
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License version 2 as
# published by the Free Software Foundation.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License along
# with this program; if not, write to the Free Software Foundation, Inc.,
# 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

LC_ALL=C
set -e

function usage()
{
echo "This utility generates SD card images suitable for use with QEMU."
echo "Usage:"
echo " $0 <output name> <mlo> <u-boot> <kernel> <rootfs>"
echo "Example:"
echo " $0 sd.img ~/MLO ~/u-boot.bin ~/uImage ~/rootfs.tar.bz2"
}

function check_args()
{
echo $#
if [ $# -ne 5 ]; then
usage
exit 1
fi
OUTFILE=$1
MLO=$2
UBOOT=$3
KERNEL=$4
ROOTFS=$5

if ! [[ -e ${MLO} ]]; then
echo "MLO not found at ${MLO}! Quitting..."
exit 1
fi
if ! [[ -e ${UBOOT} ]]; then
echo "U-boot not found at ${UBOOT}! Quitting..."
exit 1
fi
if ! [[ -e ${KERNEL} ]]; then
echo "Kernel not found at ${KERNEL}! Quitting..."
exit 1
fi
if ! [[ -e ${ROOTFS} ]]; then
echo "Rootfs not found at ${ROOTFS}! Quitting..."
exit 1
fi
}

SIZE=1073741824 # 1G by default

function make_image()
{
qemu-img create -f raw ${OUTFILE} ${SIZE}

CYLINDERS=`echo ${SIZE}/255/63/512 | bc`
{
echo ,9,0x0C,*
echo ,,,-
} | sfdisk -D -H 255 -S 63 -C ${CYLINDERS} ${OUTFILE} &> /dev/null

# Reverse-engineer the partition setup
BYTES_PER_SECTOR="$(/sbin/fdisk -l -u ${OUTFILE} | grep Units | awk '{print $9}')"
VFAT_SECTOR_OFFSET="$(/sbin/fdisk -l -u ${OUTFILE} | grep img1 | awk '{print $3}')"
EXT3_SECTOR_OFFSET="$(/sbin/fdisk -l -u ${OUTFILE} | grep img2 | awk '{print $2}')"
}

function populate_image()
{
LOOP_DEV="/dev/loop1"
LOOP_DEV_FS="/dev/loop2"

echo "[ Format vfat partition ]"
/sbin/losetup -v -o $(expr ${BYTES_PER_SECTOR} "*" ${VFAT_SECTOR_OFFSET}) ${LOOP_DEV} ${OUTFILE}
mkfs.vfat -F 32 -n "boot" ${LOOP_DEV}

echo "[ Format ext3 partition ]"
/sbin/losetup -v -o $(expr ${BYTES_PER_SECTOR} "*" ${EXT3_SECTOR_OFFSET}) ${LOOP_DEV_FS} ${OUTFILE}
/sbin/mkfs.ext3 -L rootfs ${LOOP_DEV_FS}

echo "[ Copying files to vfat ]"
mount ${LOOP_DEV} /mnt
cp -v ${MLO} /mnt/MLO
cp -v ${UBOOT} /mnt/u-boot.bin
cp -v ${KERNEL} /mnt/uImage
umount ${LOOP_DEV}

echo "[ Copying file system ]"
mount ${LOOP_DEV_FS} /mnt
tar xaf ${ROOTFS} -C /mnt
umount ${LOOP_DEV_FS}

echo "[ Clean up ]"
/sbin/losetup -d ${LOOP_DEV}
/sbin/losetup -d ${LOOP_DEV_FS}
}

ARGS=$*
check_args $ARGS
make_image
populate_image
</pre>

Overo emulation in qemu

2011-07-07T17:08:33Z

Trevor Woerner:

__TOC__
[[Category:How to - qemu]]

Ash Charles has been working with Riku from the Qemu-linaro team to get support for the Overo hardware working in Qemu!

==Pre-Compiled Images==

Here are Ash's steps for working with pre-compiled images:

* binary executable for qemu available here (for x86_64):
::http://dl.dropbox.com/u/211887/qemu-system-arm
::MD5:c375b7d0338e3e8cd7009e69f3aaae74

* overo angstrom image with a kernel, MLO, u-boot packed:
::http://dl.dropbox.com/u/211887/overo.img.gz
::MD5:3545dbd2e7ffac3d352a7bc9e92373bf

* download, gunzip the overo.img.gz and run with:
::<code># ./qemu-system-arm -M overo -m 256 -sd ./overo.img -clock unix -serial stdio</code>
::(mouse & keyboard don't work currently but the console session is usable)

==From Sources==

* build your overo image using bitbake/OE as usual:
::<code>$ cd $OVEROTOP</code>
::<code>$ bitbake omap3-console-image</code>

* build the MLO program:
::<code>$ bitbake x-load</code>

* get the sources for and build qemu with overo support:
::<code>$ cd $OVEROTOP</code>
::<code>$ git clone git://git.linaro.org/people/rikuvoipio/qemu.git</code>
::<code>$ cd qemu</code>
::<code>$ git checkout overo</code>
::<code>$ ./configure --prefix=$OVEROTOP/local --target-list=arm-softmmu</code>
::<code>$ make install</code>
::<code>$ export PATH=$OVEROTOP/local/bin:$PATH</code>

* use Ash's supplied script to generate a qemu image:
::<code># export OEDONE=$OETMP/deploy/glibc/images/overo</code>
::<code># assemble-image.sh $OVEROTOP/overo.img $OEDONE/MLO-overo $OEDONE/u-boot-overo.bin $OEDONE/uImage-overo.bin $OEDONE/omap3-console-image-overo.tar.bz2</code>

* then run the image under qemu:
::<code># qemu-system-arm -M overo -m 256 -sd $OVEROTOP/overo.img -clock unix -serial stdio</code>

Overo emulation in qemu

2011-07-07T17:07:37Z

Trevor Woerner:

__TOC__
[[Category:Qemu]]

Ash Charles has been working with Riku from the Qemu-linaro team to get support for the Overo hardware working in Qemu!

==Pre-Compiled Images==

Here are Ash's steps for working with pre-compiled images:

* binary executable for qemu available here (for x86_64):
::http://dl.dropbox.com/u/211887/qemu-system-arm
::MD5:c375b7d0338e3e8cd7009e69f3aaae74

* overo angstrom image with a kernel, MLO, u-boot packed:
::http://dl.dropbox.com/u/211887/overo.img.gz
::MD5:3545dbd2e7ffac3d352a7bc9e92373bf

* download, gunzip the overo.img.gz and run with:
::<code># ./qemu-system-arm -M overo -m 256 -sd ./overo.img -clock unix -serial stdio</code>
::(mouse & keyboard don't work currently but the console session is usable)

==From Sources==

* build your overo image using bitbake/OE as usual:
::<code>$ cd $OVEROTOP</code>
::<code>$ bitbake omap3-console-image</code>

* build the MLO program:
::<code>$ bitbake x-load</code>

* get the sources for and build qemu with overo support:
::<code>$ cd $OVEROTOP</code>
::<code>$ git clone git://git.linaro.org/people/rikuvoipio/qemu.git</code>
::<code>$ cd qemu</code>
::<code>$ git checkout overo</code>
::<code>$ ./configure --prefix=$OVEROTOP/local --target-list=arm-softmmu</code>
::<code>$ make install</code>
::<code>$ export PATH=$OVEROTOP/local/bin:$PATH</code>

* use Ash's supplied script to generate a qemu image:
::<code># export OEDONE=$OETMP/deploy/glibc/images/overo</code>
::<code># assemble-image.sh $OVEROTOP/overo.img $OEDONE/MLO-overo $OEDONE/u-boot-overo.bin $OEDONE/uImage-overo.bin $OEDONE/omap3-console-image-overo.tar.bz2</code>

* then run the image under qemu:
::<code># qemu-system-arm -M overo -m 256 -sd $OVEROTOP/overo.img -clock unix -serial stdio</code>

Overo emulation in qemu

2011-07-07T17:04:07Z

Trevor Woerner: Running Overo images under Qemu

__TOC__

Ash Charles has been working with Riku from the Qemu-linaro team to get support for the Overo hardware working in Qemu!

==Pre-Compiled Images==

Here are Ash's steps for working with pre-compiled images:

* binary executable for qemu available here (for x86_64):
::http://dl.dropbox.com/u/211887/qemu-system-arm
::MD5:c375b7d0338e3e8cd7009e69f3aaae74

* overo angstrom image with a kernel, MLO, u-boot packed:
::http://dl.dropbox.com/u/211887/overo.img.gz
::MD5:3545dbd2e7ffac3d352a7bc9e92373bf

* download, gunzip the overo.img.gz and run with:
::<code># ./qemu-system-arm -M overo -m 256 -sd ./overo.img -clock unix -serial stdio</code>
::(mouse & keyboard don't work currently but the console session is usable)

==From Sources==

* build your overo image using bitbake/OE as usual:
::<code>$ cd $OVEROTOP</code>
::<code>$ bitbake omap3-console-image</code>

* build the MLO program:
::<code>$ bitbake x-load</code>

* get the sources for and build qemu with overo support:
::<code>$ cd $OVEROTOP</code>
::<code>$ git clone git://git.linaro.org/people/rikuvoipio/qemu.git</code>
::<code>$ cd qemu</code>
::<code>$ git checkout overo</code>
::<code>$ ./configure --prefix=$OVEROTOP/local --target-list=arm-softmmu</code>
::<code>$ make install</code>
::<code>$ export PATH=$OVEROTOP/local/bin:$PATH</code>

* use Ash's supplied script to generate a qemu image:
::<code># export OEDONE=$OETMP/deploy/glibc/images/overo</code>
::<code># assemble-image.sh $OVEROTOP/overo.img $OEDONE/MLO-overo $OEDONE/u-boot-overo.bin $OEDONE/uImage-overo.bin $OEDONE/omap3-console-image-overo.tar.bz2</code>

* then run the image under qemu:
::<code># qemu-system-arm -M overo -m 256 -sd $OVEROTOP/overo.img -clock unix -serial stdio</code>