All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Andreas Glatz <andi.glatz@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Debug/trace tools for xenomai applications.
Date: Wed, 17 Nov 2010 09:43:46 +0100	[thread overview]
Message-ID: <1289983426.1933.406.camel@domain.hid> (raw)
In-Reply-To: <E1C5E37E-623F-41B8-892C-5101FD132E4A@gmail.com>

On Tue, 2010-11-16 at 11:46 +0000, Andreas Glatz wrote: 
> > 
> > 
> > On Mon, 2010-11-15 at 21:26 +0100, ronny meeus wrote: 
> > > Hello 
> > > 
> > > 
> > > Thanks for the information. 
> > > I was testing on QEMU but I have seen that there are issue with
> > > the 
> > > timing anyhow. 
> > > I'm currently changing to a target environment. Once this is 
> > > completed, I will re-run my tests and get back with the result. 
> > > 
> > > 
> > > I do not really understand what you mean with the simulator. 
> > > Where can I find more information about it? 
> > 
> > 
> > http://git.xenomai.org/?p=xenosim.git;a=blob;f=doc/mvm-manual.txt;h=1c6767ea2890d68e1c1c5cfe1420e189b3cc5328;hb=06919eb3a6b6baf7880ea3ade1ecc5f610c35794 
> > 
> > 
> 
> 
> So in other words the simulator is a good debugging tool if your
> application doesn't (i) directly access hardware (mmap aso...)
> (ii) doesn't used assembly code written for another platform and (iii)
> can be compiled with the gcc 2.95.3. 
> 
> 
> For the first two restrictions this means in other words that
> the application should follow the golden design standard which
> proposes to put all hardware depended code into rtdm drivers and
> everything else into the application. 

Exactly. The hardware-dependent code should be either:
- stubbed or replaced with some C/C++ code providing limited feedback,
enough to have the application running.
- left in, but connected internally to a software component partially or
fully modeling the hardware. Such component would run within the
simulator directly, which is actually an extensible event-driven
simulation engine, with a C++ interface to build add-ons/models.

> 
> 
> Could one (partly) work around the first two restrictions by letting
> the simulator run inside of qemu which emulates the
> target architecture?

Maybe for the inline assembly code which is not directly device-related.
Running RTDM drivers in simulation mode would require to simulate the
devices with a model though.

> 
> Andreas
> _______________________________________________
> Xenomai-help mailing list
> Xenomai-help@domain.hid
> https://mail.gna.org/listinfo/xenomai-help

-- 
Philippe.





  reply	other threads:[~2010-11-17  8:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.45.1289905237.25153.xenomai@xenomai.org>
2010-11-16 11:46 ` [Xenomai-help] Debug/trace tools for xenomai applications Andreas Glatz
2010-11-17  8:43   ` Philippe Gerum [this message]
2010-11-17  9:42     ` Jan Kiszka
2010-11-14 11:27 Andreas Glatz
2010-11-14 15:36 ` Gilles Chanteperdrix
  -- strict thread matches above, loose matches on Subject: below --
2010-11-14  0:24 ronny meeus
2010-11-15  9:30 ` Philippe Gerum
2010-11-15 13:10   ` Gilles Chanteperdrix
2010-11-15 15:07     ` Philippe Gerum
2010-11-15 20:26       ` ronny meeus
2010-11-15 20:56         ` Philippe Gerum
2010-11-17 13:49   ` ronny meeus
2010-11-17 14:01     ` Philippe Gerum
2010-11-17 15:00       ` ronny meeus

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=1289983426.1933.406.camel@domain.hid \
    --to=rpm@xenomai.org \
    --cc=andi.glatz@domain.hid \
    --cc=xenomai@xenomai.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 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.