I’ve been struggling to generate a bootable SD card. I’m running ubuntu 12.04 LTS. mkcard fails when trying to make the file systems. I can dd a downloaded demo 2012.02.14 image file to the sd card and boot from it. When I tried erasing the files from that working sd card and replacing it with the build I created using open embedded that boot fails. It starts but then dies within a few seconds.
A couple of questions:
Which recipe(s) should I use to build a bootable sd card like the demo?
How can I generate an image file, like the demo image file, that I can then dd to the sd card?
Is there a problem with booting 3.2.14?
I've been struggling to generate a bootable SD card. I'm running ubuntu
12.04 LTS. mkcard fails when trying to make the file systems. I can dd
a downloaded demo 2012.02.14 image file to the sd card and boot from it.
When I tried erasing the files from that working sd card and replacing it
with the build I created using open embedded that boot fails. It starts but
then dies within a few seconds.
A couple of questions:
Which recipe(s) should I use to build a bootable sd card like the demo?
Is it [1] that you are using? Erasing MLO and writing a new one won't
work. You may be able to 'cat MLO.new > MLO' successfully, but it is
likely to fail on the OMAP35x/DM37x ROM boot if the directory table
changes or if you add fragmentation to the FAT tables.
The class used to build an SD card image with OE is [2].
If you are looking for a set of tools to build images, you might take
a look at linaro-media-create [3].
Unpatched, it won’t run, but are you talking about a specifically
patched version?
Specifically patch version? No. I’m just trying to get a working build that will let me create my own kernel modules. I’ll take any version that can do that.
I started out with [5] which gave me a kernel. Knowing which recipe to use to create the rootfs such as [4] wasn’t clear at first but I eventually created a one (i.e. console-image) and then ran into the problems creating a SD image. If I do [2] will the build I have run or is there something within it that needs a patch?
Unpatched, it won't run, but are you talking about a specifically
patched version?
Specifically patch version? No. I'm just trying to get a working build that
will let me create my own kernel modules. I'll take any version that can do
that.
I started out with [5] which gave me a kernel. Knowing which recipe to use
to create the rootfs such as [4] wasn't clear at first but I eventually
created a one (i.e. console-image) and then ran into the problems creating a
SD image. If I do [2] will the build I have run or is there something within
it that needs a patch?
[2] isn't a recipe, it is a class that needs to be inherited by a
recipe. [4] uses that class, so you can:
MACHINE=beaglebone bitbake cloud9-gnome-image
As long as the permissions used by [2] are setup such that the
loopback device can access the image file that gets created and
partition/format/write to it.