public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@cygnus.co.uk>
To: "Ling Su" <lingsu@palmmicro.com>
Cc: "Jonathan Larmour" <jlarmour@redhat.com>,
	<ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] How to access PCI memory(HELP)....
Date: Wed, 13 Sep 2000 03:09:00 -0000	[thread overview]
Message-ID: <pou2bkmwrk.fsf@balti.cygnus.co.uk> (raw)
In-Reply-To: <002801c01ce4$4a3f7d90$0201a8c0@raccoon>

"Ling Su" <lingsu@palmmicro.com> writes:

> >
> > I responded to your previous message before I saw this one. As I said
> > there, I think that adjusting HAL_PHYSICAL_MEMORY_BASE so that the CPU
> > addr ends up at 0xD000_0000 will fix your problem.
> >
> > I guess HAL_PHYSICAL_MEMORY_BASE is probably misnamed, it should
> > really be HAL_PHYSICAL_MEMORY_OFFSET. It only works as a base when the
> > PCI memory allocation starts at zero.
> >
> Hi, Nick,
> 
> Yeah, I think I can understand your suggestion, unfortuantely I still met
> segment fault. I append my log message in the end, please take a look, I
> don't exactly the memory mapping for eCos in vrc4373 board. I guess there is
> something wrong on the PCI space and memory space. Could you let me know how
> can I trace the SIGSEGV and the segment fault, so that I can figure out
> which part is wrong. I don't quiet understand why I can not access
> 0xD000_0000 at all.
> 
If you take a look at the registers and the specific instruction that
the exception occured on you should be able to work out exactly what
address it was trying to access, and the value in the cause register
should tell you what exception it actually was. If it's a TLB
exception then maybe the MMU setup needs changing, if its
a bus exception then the problem lies in the hardware setup.


-- 
Nick Garnett, eCos Kernel Architect
Red Hat, Cambridge, UK

  reply	other threads:[~2000-09-13  3:09 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-11 21:05 [ECOS] Fw: " Ling Su
2000-09-12  2:56 ` [ECOS] " Nick Garnett
2000-09-12 11:07   ` Ling Su
2000-09-13  3:09     ` Nick Garnett [this message]
2000-09-12 15:52 ` [ECOS] Anyway to access the 7 segment display on NEC vrc4373 board? Ling Su
2000-09-13 11:58   ` [ECOS] " Jonathan Larmour
2000-09-12 18:31 ` [ECOS] Problem on allocate PCI memory space Ling Su
2000-09-13  3:19   ` [ECOS] " Nick Garnett
2000-09-13 12:40     ` Ling Su
2000-09-13 17:41       ` Ling Su
2000-09-14  3:32         ` Nick Garnett
2000-09-14  3:43           ` Andrew Lunn
2000-09-14 14:46           ` Ling Su
2000-09-14 14:51             ` Jonathan Larmour
2000-09-14 17:53               ` Ling Su
2000-09-14  3:08       ` Nick Garnett
  -- strict thread matches above, loose matches on Subject: below --
2002-06-13  4:59 [ECOS] How to access PCI memory(HELP) namita  chawla
2002-06-13  9:20 ` David N. Welton
2002-06-13  9:28   ` Stephen Polkowski
2000-09-08 11:43 Ling Su
2000-09-10 19:44 ` Jonathan Larmour
2000-09-10 19:48   ` Jonathan Larmour
2000-09-10 20:39     ` Ling Su
2000-09-10 21:29       ` Jonathan Larmour
2000-09-11  3:59         ` Nick Garnett
2000-09-11 11:47           ` Ling Su
2000-09-12  2:33             ` Nick Garnett
2000-09-12 12:10             ` Ling Su
2000-09-12 16:56               ` Ling Su
2000-09-13  3:04                 ` Nick Garnett
2000-09-11 11:34         ` Ling Su
2000-09-11 11:38           ` Jonathan Larmour
2000-09-11 11:39         ` Ling Su

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=pou2bkmwrk.fsf@balti.cygnus.co.uk \
    --to=nickg@cygnus.co.uk \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=jlarmour@redhat.com \
    --cc=lingsu@palmmicro.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).