public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Nick Garnett <nickg@cygnus.co.uk>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] serial communication with i386 ( modified )
Date: Wed, 30 Aug 2000 04:01:00 -0000	[thread overview]
Message-ID: <pod7irf2dd.fsf@balti.cygnus.co.uk> (raw)
In-Reply-To: <930B10D665E74D115AF40005B8ACC2B0@pradeeppatel.indiatimes.com>

"pradeep patel" <pradeeppatel@indiatimes.com> writes:

> Hi,
> I made an eCos boot floppy for i386 PC target. I could successfully
> boot the pentium PC using this boot floppy. It shows some characters
> on monitor after booting.  Then i tried to connect my host which
> also pentium PC with Windows NT. I tried with serial port
> COM1. Initially i got an error " cannot connect to target " but then
> i could solve that problem.
> Now i am getting an following display:
> 
> Remote debugging COM1
> 0x3be0 in crc32 ( ptr=0x0, len=0, crc=0 )
>  at //c/progra~1/Redhat~1/eCos/packages/hal/common/v1_3_1/src/generic_stub.c :
> 
> 1580 __mem_fault=0;
> 
> can you help me to solve this problem? What is problem with generic_stub.c file ?
> 
> I tried shifting __mem_fault=0; one line upward i.e line 1580 in generic_stub.c to be blank.
> But still it is showing me error at line 1580 and it doesn't display __mem_fault=0;
> 

What exception are you getting? What program are you running?  Check
that you are buiding the application for RAM startup rather than
ROM. Try some of the test program to see if these work correctly.

GDB does not always get the exact line number correct, especially in
optimized code where instructions have been rescheduled. Take a look
instead at the actual assembly code and register contents to see what
is really going wrong.


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

  reply	other threads:[~2000-08-30  4:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-30  2:46 pradeep patel
2000-08-30  4:01 ` Nick Garnett [this message]
     [not found] <01C01385.5D272B00@PC-P3453>
2000-08-31  7:32 ` Nick Garnett

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=pod7irf2dd.fsf@balti.cygnus.co.uk \
    --to=nickg@cygnus.co.uk \
    --cc=ecos-discuss@sourceware.cygnus.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).