public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Cristiano Ligieri Pereira <cpereira@ics.uci.edu>
To: Gary Thomas <gthomas@redhat.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Port problem
Date: Fri, 17 Aug 2001 11:07:00 -0000	[thread overview]
Message-ID: <Pine.SOL.4.20.0108171100370.7982-100000@washoe.ics.uci.edu> (raw)
In-Reply-To: <XFMail.20010817063716.gthomas@redhat.com>

> You built this CygMon yourself?  If so, what was the source code base?
> 
> Note: we really only support RedBoot on the XScale, not CygMon.

I didn't build it but I have the sources from Intel. The addressesare the
following (file elf-lrh-rom.specs):

*link:
-T bsp.ld%s -Ttext 0x00000000 -Tdata 0xc0000000 %(old_link)

> This tells me that you may have a memory mapping problem.
> 
> eCos programs expect the memory map to be somewhat different than the hardware
> map.  Most particularly, DRAM gets moved to 0x00000000 and the FLASH at 0
> gets moved around as well.  On some XScale platforms, this is even trickier,
> but the basic idea is the same.

That's why I'm forcing to execute PLATFORM_SETUP1 and remapping the memory
there according to what you've just said. But it looks like I'm missing
something then.

> > how should I do about the serial communication with the host? Can I reuse
> > the communication already established with CygMon? Do I need to break it
> > and restart a new connection?
> > 
> 
> No.

The No refers to which question? :-)

> I think you should look into getting RedBoot working as your base debug 
> environment.

Ok. I'll do that. 

Cristiano.

  reply	other threads:[~2001-08-17 11:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-16 11:00 Cristiano Ligieri Pereira
2001-08-16 22:47 ` Cristiano Ligieri Pereira
2001-08-17  2:50   ` Jesper Skov
2001-08-17  5:10     ` Mark Salter
2001-08-17  7:56       ` Cristiano Ligieri Pereira
2001-08-17  5:36   ` Gary Thomas
2001-08-17 11:07     ` Cristiano Ligieri Pereira [this message]
2001-08-17 11:14       ` Gary Thomas

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=Pine.SOL.4.20.0108171100370.7982-100000@washoe.ics.uci.edu \
    --to=cpereira@ics.uci.edu \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=gthomas@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).