public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Shu Higashiyama <higashi@jiyu-sha.co.jp>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Plese Help me
Date: Thu, 24 Dec 2009 16:50:00 -0000	[thread overview]
Message-ID: <20091224165007.GA2173@sg-laptop> (raw)
In-Reply-To: <20091224235608.F46C.A1A37DDB@jiyu-sha.co.jp>

On Thu, Dec 24, 2009 at 11:56:39PM +0900, Shu Higashiyama wrote:
> Hello ALL

Hello Shu,

> Ecos is developed in the environment of Ferora7.

That's great.

> Redboot is operating as for HAL now at the time of change based on
> Lpcmt of ARM (confirmed operation). 

AFAIK `lpcmt' target is based on LPC2106 CPU which has 64K of RAM, so,
it looks like that RedBoot won't be very useful for your development,
thus it will be possible to run a couple of the eCos tests in RAM with
it.

> The kernel binary cannot be vomited though the kernel is compiled
> with configtool.  Please advise there is no description that vomits
> the final kernel image also in contents of makefile and the
> embarrassment. 

If you expected that you will get something like `zImage' you won't
get the same thing with `configtool' (CT), but, you can build a set of
the eCos tests. If your HAL is the same as `lpcmt' HAL, you will get
the set of ROMable ELF images, if you select 'Build Tests' in CT. Use
JTAG to burn them into ROM. If your FLASH programmer does not support
ELFs convert got images to .bin or .hex formats with objcopy utility.
By other hand you can try to build a few set of the RAM images if you
select RAM startup in CT and rebuild the libraries and tests. The
built RAM images can be loaded into RAM with your RedBoot (I hope).
One thing: the build process in CT will be stopped on the first error:

    .bss is not within region ram

If you familiar with CLI you can build more the RAMAble tests making
`make' do not stop on the first error:

    make -k -C kernel/current tests

It's possible to build 36 RAMable kernel tests for `lpcmt':

    $ find install/tests -type f | wc -l
    36

But, IMO it seems for me that' better to use JTAG and work with
ROMable images on your target.

Hope that helps.

Sergei

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2009-12-24 16:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24 14:56 Shu Higashiyama
2009-12-24 16:50 ` Sergei Gavrikov [this message]
2010-02-02  4:34 Shu Higashiyama

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=20091224165007.GA2173@sg-laptop \
    --to=sergei.gavrikov@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=higashi@jiyu-sha.co.jp \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).