public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Richard Rauch" <rrauch@itrgmbh.de>
To: "'Eduardo Fernandes de Conto'" <eduardoconto@gmail.com>,
	<ecos-discuss@ecos.sourceware.org>
Subject: AW: [ECOS] eCos in virtual environment (eCos run on QEMU ARM?)
Date: Fri, 12 Sep 2014 17:24:00 -0000	[thread overview]
Message-ID: <017201cfceae$6826ac30$38740490$@itrgmbh.de> (raw)
In-Reply-To: <CAKNGs9hNJg4BE_JuqoMemsBst-CjxCFhzFsHJMDOgwgbB4Hvgg@mail.gmail.com>

Hello everyone,

this post is a bit old, but anyway...maybe this issue is still interesting:

we created a very convenient way to run und debug within QEMU target
simulation.
We have described in detail here:
http://tiprom.itrgmbh.com/projects/itr-products-ecos-toolchain/wiki/DebugTar
getConfiguration#Working-with-QEMU-target-simulation

Richard Rauch/ITR GmbH

> Von: ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
> owner@ecos.sourceware.org] Im Auftrag von Eduardo Fernandes de Conto
> Gesendet: Dienstag, 17. Juli 2012 15:57
> An: ecos-discuss@ecos.sourceware.org
> Betreff: [ECOS] eCos in virtual environment (eCos run on QEMU ARM?)
> 
> Hello everyone,
> 
> For my internship, we are trying to port/run eCos on a virtual environment
> (RABBITS) we used here that is based on QEMU and simulates an MPSoC with
> the ARM architecture (You may find for information here:
> http://tima-sls.imag.fr/www/research/rabbits/). I have I couple of
questions
> that I would be pleased if someone is able to answer to:
> 
> - Has someone successfully ran eCos with QEMU simulating the ARM
> architecture? If not, does anyone have any tips or ideas for doing it?
> I have seen that Grant Edwards has been able to execute eCos using QEMU
> with the i386 architecture. I've tried to boot using the ARM architecture
with
> no success until now though.
> 
> - One of the platforms of your environment simulates an ARM11 chip. Is
there
> is an ARM11 port for eCos?
> 
> - Is the ARM architecture compatible with MPSoC?
> 
> 
> Thanks for your attention!
> --
> Eduardo Fernandes de Conto
>  - Étudiant en Double Diplôme:
>         Grenoble INP - ENSIMAG (France) et UFRGS (Brésil)
> - Stagiaire Laboratoire TIMA - SLS (http://tima-sls.imag.fr/www)
> 
> --
> Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
> and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



--
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:[~2014-09-12 17:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKNGs9jC-YudRqEVBhh4dbSKyUrk767gb=mS727V6P_KtaC0hg@mail.gmail.com>
2012-07-17 13:57 ` Eduardo Fernandes de Conto
2012-07-18 15:09   ` [ECOS] " Grant Edwards
2012-07-18 20:25   ` Eduardo Fernandes de Conto
2014-09-12 17:24   ` Richard Rauch [this message]
2014-09-12 17:32     ` AW: [ECOS] " Richard Rauch

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='017201cfceae$6826ac30$38740490$@itrgmbh.de' \
    --to=rrauch@itrgmbh.de \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=eduardoconto@gmail.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 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).