public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Olaf Peters" <olaf.peters@technolution.nl>
To: <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] GDB stubs on EDB7211
Date: Thu, 08 Feb 2001 03:08:00 -0000	[thread overview]
Message-ID: <JGEEJKHHJODGMOKKPBENKENLCAAA.olaf.peters@technolution.nl> (raw)
In-Reply-To: <4.3.2.7.2.20010207084920.00b187e0@larwe.com>

Lewin,

Thanks for your help so far.

> >an eCos snapshot from 26 januari 2001 and created the edb7xxx
> gdbrom stubs.
> >Than I programmed the gdb_module.bin file into the EDB7211 flash.
>
> You might find it easier, as I did, to start with the "official
> release" of
> eCos, 1.3.1 rather than a snapshot. The 1.3.1 release comes with a
> pre-compiled binary ready to flash.

The pre-compiled binary seems to work fine on my EDB7211 board.
But now comes the real problem: I have an EDB7211 alike
custom board, build around the EP7211 (flash, ram and ethernet controller
are the same). For this board I need to do some
additional hardware initialisations at start-up, so I need to be able to
compile
the EDB7211 GDB rom stub.
I tried to built the EDB7211 gdb stubs with eCos 1.3.1, but it
doesn't work (I followed the guidelines in the ecos-tutorial-arm.pdf file).
Any suggestions why the EDB7211 GDB stubs I built myself with eCos 1.3.1
don't work and the shipped images do work?

Tia,
Olaf.

  reply	other threads:[~2001-02-08  3:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07  5:54 Olaf Peters
2001-02-07  6:01 ` Lewin A.R.W. Edwards
2001-02-08  3:08   ` Olaf Peters [this message]
     [not found]   ` <JGEEJKHHJODGMOKKPBENOENLCAAA.olaf.peters@technolution.nl>
2001-02-08  6:55     ` Lewin A.R.W. Edwards
2001-02-07  8:20 ` Wilson Kwan

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=JGEEJKHHJODGMOKKPBENKENLCAAA.olaf.peters@technolution.nl \
    --to=olaf.peters@technolution.nl \
    --cc=ecos-discuss@sources.redhat.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).