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

Thank you so much for your help!! But I still not very clear about
some problems.

1. If "Redboot does not use the kernel" , does that mean if I want to
see the result of my modification, redboot is no help. But if without
the redboot, can I still use the VMware to run the ecos? Because I
only see the examples about how to run the redboot on VMware.

2. After these steps:
        " ecosconfig new pc_rltk8139
          edit ecos.ecc and change CYG_HAL_STARTUP to floppy
          ecosconfig tree
          make -s tests "
    and compilation of ecos, I also need to run some applications to
verify my   modification( like get some calculation results). How I
can run the applications and see the results?

Thank you!!!


> > 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?
>
>
> > 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

  reply	other threads:[~2007-06-14 16:11 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 [this message]
2007-06-14 23:11     ` Andrew Lunn
2007-06-27  1:52   ` xiaolu zhao
2007-06-27  9:48   ` xiaolu zhao

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=b48951870706140911j55c8eb8dqec2e9dd4a5bb058@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).