From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Cc: saleh usman <salehusman@hotmail.com>
Subject: Re: Problem using output of console-image
Date: Wed, 06 Jan 2010 08:34:35 -0700 [thread overview]
Message-ID: <4B44AD8B.7060902@mlbassoc.com> (raw)
In-Reply-To: <BAY127-W279A13B86B227AAF2D8080D8720@phx.gbl>
On 01/06/2010 08:25 AM, saleh usman wrote:
>
> Hi
> I've built console-image for omap5912osk machine but I am facing problem in using output.There are four folders named all, armv5te, i686, omap5912osk in /temp/deploy/glibc/ipk.and so many ipk files in these folders.
> Which files exactly I should use to run the output on my target platform and how to run these files.
> Wheather to install these files, any other package or directly run them just by typing their names.
> Since
> linux is running on ARM9 GPP of machine ,should I take care of u-boot, kernel version or
> anything else to run generated output on my target platform
>
Start with the files in tmp/deploy/glibc/images/<platform>
There you should find the kernel (uImage) and file system. Depending
on your configuration, there may be multiple choices for the file
system ranging from a raw tar file to JFFS2 or UBI images. Which
you choose and how you deploy them are up to you (and are target
platform dependent)
For example, when running an image on the BeagleBoard (OMAP3530),
I put the kernel (uImage) and unpack the tar.bz2 file system to
an SD card and boot from that.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-01-06 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 15:25 Problem using output of console-image saleh usman
2010-01-06 15:34 ` Gary Thomas [this message]
2010-01-06 16:26 ` Philip Balister
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B44AD8B.7060902@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=salehusman@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.