I’m trying to boot the Yocto 3.5 console image I downloaded from the Gumstix Developer site on a Overo Water Storm. I had this board setup to run an eCon Systems camera and it worked fine, but the kernel was old and didn’t have power management. When I try to boot the Yocto image from a 32 GB SDHC card, it hangs at this point:


[    3.409118] Stack: (0xdec2bdf8 to 0xdec2c000)

[    3.413665] bde0:                                                       dec1ca40 c0261198

[    3.422210] be00: 00000000 0000003c 00000500 000002d0 ffffffff ded96694 deedf780 c04612d4

[    3.430755] be20: 22222222 22222222 22222222 22222222 ded96694 c06ad008 dec2be90 ded96694

[    3.439270] be40: c06ad008 dec2be90 00000010 c026ea1c def7e800 c06ad7a8 c06ad008 c0679564

[    3.447814] be60: 0000003d c048cae0 00000018 dec2be7c 00000000 00000004 def7e800 deefc800

[    3.456359] be80: dec2be8c deef92c0 dec1ca40 00000000 02d00500 0000fa00 00300020 00050050

[    3.464904] bea0: 0003000d c0054110 00000000 00000003 dec98248 00000000 c06cea84 c06aeec8

[    3.473449] bec0: c06cea84 c06cea84 c02989ec 00000000 00000000 c067906c 00000000 c0299ae8

[    3.481964] bee0: c0299ad4 c02987e0 c06cea84 c06aeec8 c06aeec8 c06aeefc c06cea84 c0298a54

[    3.490509] bf00: 00000000 dec2bf10 c06cea84 c0296d3c dec077d8 dec93770 c06cea84 c06cea84

[    3.499053] bf20: deefbbc0 c06d47f8 c06fb2c0 c0297dcc c059b8e8 c059b8e8 dec2bf40 c06cea84

[    3.507598] bf40: 00000001 c0690ba0 c06fb2c0 0000009e c067906c c0298f78 00000000 c06cea70

[    3.516113] bf60: 00000001 c0690ba0 c06fb2c0 0000009e c067906c c0299d5c 00000007 c06867d8

[    3.524658] bf80: c0690ba0 c0679094 dec2a000 c000867c c067906c 57904696 c0690bc8 00000008

[    3.533203] bfa0: 00000007 c06867d8 c0690ba0 c06fb2c0 0000009e c0659160 c06867e0 c06598ec

[    3.541748] bfc0: 00000007 00000007 c0659160 00000013 00000000 00000000 00000000 c06597b4

[    3.550262] bfe0: c000eec8 00000013 00000000 00000000 00000000 c000eec8 5c80818a 194008c8

[    3.558837] [<c025e600>] (dss_mgr_check_timings+0x4/0x30) from [<c0261198>] (dpi_check_timings+0x18/0xc8)

[    3.568817] [<c0261198>] (dpi_check_timings+0x18/0xc8) from [<c026ea1c>] (tfp410_check_timings+0x28/0x3c)

[    3.578826] [<c026ea1c>] (tfp410_check_timings+0x28/0x3c) from [<c0679564>] (omapfb_probe+0x4a4/0x9bc)

[    3.588531] [<c0679564>] (omapfb_probe+0x4a4/0x9bc) from [<c0299ae8>] (platform_drv_probe+0x14/0x18)

[    3.598083] [<c0299ae8>] (platform_drv_probe+0x14/0x18) from [<c02987e0>] (driver_probe_device+0x134/0x340)

[    3.608276] [<c02987e0>] (driver_probe_device+0x134/0x340) from [<c0298a54>] (__driver_attach+0x68/0x8c)

[    3.618164] [<c0298a54>] (__driver_attach+0x68/0x8c) from [<c0296d3c>] (bus_for_each_dev+0x48/0x80)

[    3.627624] [<c0296d3c>] (bus_for_each_dev+0x48/0x80) from [<c0297dcc>] (bus_add_driver+0xf0/0x25c)

[    3.637054] [<c0297dcc>] (bus_add_driver+0xf0/0x25c) from [<c0298f78>] (driver_register+0x9c/0x120)

[    3.646514] [<c0298f78>] (driver_register+0x9c/0x120) from [<c0299d5c>] (platform_driver_probe+0x18/0x9c)

[    3.656524] [<c0299d5c>] (platform_driver_probe+0x18/0x9c) from [<c0679094>] (omapfb_init+0x28/0x54)

[    3.666046] [<c0679094>] (omapfb_init+0x28/0x54) from [<c000867c>] (do_one_initcall+0x90/0x160)

[    3.675140] [<c000867c>] (do_one_initcall+0x90/0x160) from [<c06598ec>] (kernel_init+0x138/0x1f8)

[    3.684417] [<c06598ec>] (kernel_init+0x138/0x1f8) from [<c000eec8>] (kernel_thread_exit+0x0/0x8)

[    3.693695] Code: e3e00015 e8bd8010 c05caaf5 e92d4008 (e5900028)

[    3.701049] ---[ end trace 9cfa2e61e9ba1615 ]---

[    3.706115]  mmcblk0: p1 p2

[    3.709350] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b


I also found I had to use the MLO and u-boot files from the eCon Systems SD card shipped with the camera (MLO must be updated version). The ones from the Gumstix website won’t work. I’m getting suspicious of the environment variables in NAND. Here’s what I have now:

Overo # printenv


bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run nandboot; fi









mmcroot=/dev/mmcblk0p2 rw

mmcrootfstype=ext3 rootwait

nandroot=/dev/mtdblock4 rw


nandargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay} root=${nandroot} rootfstype=${nandrootfstype}

loadbootscript=fatload mmc 0 ${loadaddr} boot.scr

bootscript=echo Running bootscript from mmc ...; source ${loadaddr}

loaduimage=fatload mmc 0 ${loadaddr} uImage

mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}

nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; bootm ${loadaddr}



bootargs=mem=87M@0x80000000 mem=128M@0x88000000 console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR-16@60 omapfb.debug=y

mmcargs=setenv bootargs console= ttyO2,115200n8 vram=12M omapfb.mode=dvi:1280x720MR-16@60 omapfb.debug=y omapdss.def_disp=lcd43 root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait mem=224M@0x80000000 mem=256M@0x90000000





Environment size: 1374/131068 bytes


I did get an image from the archives that was factory installed to boot, so I know I’m not too far away from getting this to work. Can someone suggest the correct environment variables I need to get the Yocto 3.5 console image to work with the MLO and u-boot files from the same directory? I looked around on the web and couldn’t find much about the environment variables for the Overo Water Storm. Most of the variables look pretty generic, but I’m sure some of the memory settings are special.


Eventually, I’d like to compile my own kernel to reduce power and boot time and possibly take advantage of the some of the video processing hardware. Even though this board is connected to a camera, it only will process an image and store it rather than display it.

Thanks,  Rob


Robert Glatts

Senior Development Engineer

Scripps Institution of Oceanography

University of California, San Diego