public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jesper Skov <jskov@cygnus.co.uk>
To: Bernd Sprenger <sprenger@Robotics.Stanford.EDU>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Problems with the PowerPC simulator
Date: Fri, 05 Nov 1999 01:28:00 -0000	[thread overview]
Message-ID: <otg0yl8gjw.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <3821EEFF.57B6A468@robotics.stanford.edu>

>>>>> "Bernd" == Bernd Sprenger <sprenger@Robotics.Stanford.EDU> writes:

Bernd> Using this definition I was able to run the test program via
Bernd> the following command line:

>> powerpc-eabi-run -o '/#address-cells 1' \
Bernd>                     -o '/openprom/init/register/pc 0x100' \ -o
Bernd> '/iobus@0xf0000000/reg 0xf0000000 0x01000000' \ -o
Bernd> '/iobus/pal@0xf0001000/reg 0xf0001000 32' \
Bernd> install/tests/kernel/bin_sem0

This can be reduced to:

 -o '/iobus/pal@0xf0001000/reg 0xf0001000 32'

Bernd> The same is true for the gdb using these paramaters when
Bernd> selecting the target.

Bernd> Now my question:

Bernd> Is there a possibility to configure psim that it uses this
Bernd> device-tree by default?

I don't know, but it shouldn't really matter. In GDB you can make a
macro instead of typing in the runes by hand (as suggested in the
Getting Started Guide). For the stand-alone simulator you can create a
shell alias or a shell script with the necessary runes.

Bernd> Is there a better documentation of psim available than the
Bernd> files its source directory (Bugs, Install, Readme, Run and
Bernd> Psim.texinfo)?

There's sourceware.cygnus.com/psim, but I suspect it's the same
documentation as distributed with the sources.

Jesper

      reply	other threads:[~1999-11-05  1:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-04 12:39 Bernd Sprenger
1999-11-05  1:28 ` Jesper Skov [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=otg0yl8gjw.fsf@thinktwice.zoftcorp.dk \
    --to=jskov@cygnus.co.uk \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=sprenger@Robotics.Stanford.EDU \
    /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).