Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: leonp@plris.com
To: IGOR LURI <iluri@fagorautomation.es>
Cc: gdb@sourceware.cygnus.com
Subject: Re: Failed to connect to OCD.
Date: Tue, 05 Jun 2001 08:45:00 -0000	[thread overview]
Message-ID: <5.0.2.1.0.20010605184036.00af1e68@plris.com> (raw)
In-Reply-To: <CA78D1B723D8D411AF0300508BDCF74F3F6C9C@NTCORREO>

At 16:32 05/06/01 +0200, you wrote:
> > I am using Insight-5.0 with wiggler for mpc823 on a win 2000 hosted
>system.
> > I am using Cygwin and cross compiler for powerpc-eabi target.
> >
> > I am not able to connect to the target. When I write this command on the
> > gdb console apears the following error:
> >
> >       (gdb) target ocd wiggler lpt1
> >       Remote target wiggler connected to wiggler lpt1
> >
> >       Error: OCD_INIT: Couldn't establish connection to remote target
> >       Unknown error code 24
> >       Failed to connect to OCD.
> >
> > If you are using wiggler to connect your target, please say me how you
>done.
0. Your problem looks like the problem of contacts. Check that your wiggler 
is working properly by using the Macraigor's OCD debugger.
1. There is some bug/problem with mpc860/823 CPU's in gdb - you need to 
define the CPU type and thus the registers will become accessible, but this 
not happens. I just now simply use an old version of gdb 4.18, which is 
free of this bug.
2. Another problem, that you must be aware is that you must perform several 
initializing commands, such as define chip selects, IMMR, etc. to make the 
system capable of downloading the code.



Leon Pollak
leonp@plris.com


      reply	other threads:[~2001-06-05  8:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-05  7:37 IGOR LURI
2001-06-05  8:45 ` leonp [this message]

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=5.0.2.1.0.20010605184036.00af1e68@plris.com \
    --to=leonp@plris.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=iluri@fagorautomation.es \
    /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