public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "xiaolu zhao" <deerxiaolu@gmail.com>
To: ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] how to check my modifications to the kernel without a board?
Date: Wed, 27 Jun 2007 09:48:00 -0000	[thread overview]
Message-ID: <b48951870706260414v4db6474i636a284eaf63d741@mail.gmail.com> (raw)
In-Reply-To: <20070614154512.GB1594@lunn.ch>

Because my command-line ecosconfig does not work, I tried to use
graphic configtool to try the tests suggested by andrew.

But I met some problems:
1. If I want to run the eCos on the vmware, I think I need a .bin file
to generate the floppy image and load to the vmware. When I use
redboot, I know there is a option in the config file to choose
("Redboot ROM monitor/Redboot HAL options/Build RedBoot binary image")
and I can get a bin file in the generated install folder. But without
redbboot, I do not know how to generate the bin file?

2. I want to try the tests cases using configtool. but it seems the
hardware platform should be connected, does it? Does that mean if I
want to do the test, I should run the vmware at the same time?

Would you like to give me some advice about these problems? Thank you so much!



On 6/14/07, Andrew Lunn <andrew@lunn.ch> wrote:
> On Thu, Jun 14, 2007 at 05:14:18PM +0200, xiaolu zhao wrote:
> > Hi, I met a big problem, would you like to give me some advices?
> >
> > I did some modifications to the ecos Kernel code(like in sched.cxx,
> > thread.hxx etc.). But I have no a real hardware board. So I want to
> > use VMware as a virtual machine to see the results.Is it possible?
>
> Should be, but i have never done it myself. However, i would actually
> recommend using the synthetic target on Linux.
>
> > I tried the redbbot on the Vmware and the "hello.c" example works. But
> > after I modified the kernel code and rebuild the ecos using the
> > configtool, it did not give any compilation complaints. I know it is
> > impossible, there should be a lot of errors in the code. Does Redbbot
> > have nothing to do with the ecos kernel files?
>
> Redboot does not use the kernel.
>
> > If the redboot has nothing to do with the kernels, how can I check my
> > modificaiton to the kernel files with VMare?
>
> I would suggest you use the kernel test cases. These are good tests to
> see if your changes have broken anything.
>
> Try doing:
>
> ecosconfig new pc_rltk8139
> edit ecos.ecc and change CYG_HAL_STARTUP to floppy
> ecosconfig tree
> make -s tests
>
> Once you have fixed all the compiler error you can run the test cases
> in install/tests/kernel/current.
>
>   Andrew
>

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

      parent reply	other threads:[~2007-06-26 11:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14 15:48 [ECOS] how to check my modifications to the kernel without a board‎ xiaolu zhao
2007-06-14 16:16 ` [ECOS] how to check my modifications to the kernel without a board? Andrew Lunn
2007-06-14 22:02   ` xiaolu zhao
2007-06-14 23:11     ` Andrew Lunn
2007-06-27  1:52   ` xiaolu zhao
2007-06-27  9:48   ` xiaolu zhao [this message]

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=b48951870706260414v4db6474i636a284eaf63d741@mail.gmail.com \
    --to=deerxiaolu@gmail.com \
    --cc=ecos-discuss@ecos.sourceware.org \
    /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).