public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andreas.Karlsson@combitechsystems.com
To: ecos-discuss@sourceware.cygnus.com
Cc: jlarmour@cygnus.co.uk
Subject: [ECOS] Building stub to AEB1-revC fails
Date: Thu, 09 Nov 2000 05:03:00 -0000	[thread overview]
Message-ID: <2253171AF143D21185A60000F8FA748B0229AAB3@pluto.combitech.se> (raw)

Hi,

I had some problem while building a new stub to my AEB-board with expanded
RAM-memory.

So I thought that I firstly had to build a clean stub just see that it
works, it didn't. The funny thing is that it works if I don't change the
options to revC. But when running the stub as revB (128KB RAM instead of
256KB) of course the download fails when passing the 128 KB limit. (I link
with eCos configured for revC)



Jifl asked me if I had tried this with clean code. Ok, I have been playing a
little bit with the sources so:

I installed Linux on a computer (since there is no uuencoder in the cygwin
library, just to eliminate one more possible error source), downloaded and
installed eCos and the tools. Then I followed the manual to create a new
stub:

1. $ ecosconfig new aeb stubs. There where five resolved conflicts.

2. Editing ecos.ecc setting CYGHWR_HAL_ARM_AEB_REVISION to C

3. $ ecosconfig tree

4. $ make 

5. Downloaded the stub to the board as described in the documentation

6. When downloading the program gdb just hangs. Not a single byte is
downloaded.

As when doing this with cygwin tools it all works when I change
CYGHWR_HAL_ARM_AEB_REVISION back to B.

Is this a bug? Is there anyone that have succeeded creating a stub to
AEB1-revC? Any hints?

/Andreas



 

             reply	other threads:[~2000-11-09  5:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-09  5:03 Andreas.Karlsson [this message]
2000-11-09  5:46 ` Jesper Skov
2000-11-09  5:52 Andreas.Karlsson
2000-11-09  6:29 ` Jesper Skov
2000-11-09  6:29 Andreas.Karlsson
2000-11-12 23:54 Andreas.Karlsson
2000-11-13  0:02 ` Jesper Skov

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=2253171AF143D21185A60000F8FA748B0229AAB3@pluto.combitech.se \
    --to=andreas.karlsson@combitechsystems.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jlarmour@cygnus.co.uk \
    /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).