public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Noah Aklilu <naklilu@ualberta.ca>
Cc: gdb@sourceware.cygnus.com
Subject: Re: Using GDB with M32R MSA2000 Board
Date: Tue, 09 Jan 2001 18:32:00 -0000	[thread overview]
Message-ID: <3A5BC95E.FD5A2934@redhat.com> (raw)
In-Reply-To: <3A5B6464.1385.3278E0@localhost>

Just to get a clearer error message, use GDB in command mode:

gdb -x -nw <your program>
...
(gdb) set remotebaud 9600
(gdb) target mon2000 /dev/com1

I don't know much about the mon2000 target.  If it has a log
facility you may try setting it on.

Fernando




Noah Aklilu wrote:
> 
> Hi
>         I trying to get gdb (really insight 5.0)
> to talk to a Mitusbishi MSA2000G01 (the m32r
> evaluation board).  I switched the board to monitor/
> self-debugging mode (instead of the default db32r ethernet
> mode) and  get the Mon2000> prompt
> using a terminal emulator.  When I tell gdb to
> connect to the same com port using mon2000 as the
> target (target mon2000 /dev/com1) it comes back with the error
> listed below.
>         I tried other target modes such as target m32r /dev/com1
> but it simply times out.  I am running gdb/insight under cygwin
> 1.1.7 on an NT 4 host (and compiled it there as well).  Any
> comments/tips will be appreciated.
> 
> Noah.
> 
> -- start here
> monitor_supply_register (21):  bad value from monitor: 7FFFFFF0
> psw =
> 000000C0 (BSM=0, BIE=0,
> BC=0, SM=1, IE=1, C=0)
>  bpc = 00000000
>  r0  = 00000000    r1  = 00000000    r2  = 00000000    r3  = 00000000
>  r4  = 00000000    r5  = 00000000    r6  = 00000000    r7  = 00000000
>  r8  = 00000000    r9  = 00000000    r10 = 00000000    r11 = 00000000
>  r12 = 00000000    r13 = 00000000    r14 = 00000000
>  spu = 009E3200    spi = 009E4200    acc = 00000000:00000000
> >.
> 
>     while executing
> "gdb_cmd "set remotebaud $baud""
>     (object "::.targetselection0.targetselection" method
> "::TargetSelection::change_baud" body line 4)
>     invoked from within
> "::.targetselection0.targetselection change_baud
> .targetselection0.targetselection.f.lab.lf.childsite.cb 9600"
>     (in namespace inscope "::TargetSelection" script line 1)
>     invoked from within
> "namespace inscope ::TargetSelection
> {::.targetselection0.targetselection
> change_baud}
> .targetselection0.targetselection.f.lab.lf.childsite.cb 9600"
>     ("after" script)errorCode is NONE
> --end here
> 
> ------------------------------------------
> Noah Aklilu
> http://www.ee.ualberta.ca/~aklilu/
> naklilu@ualberta.ca

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

  reply	other threads:[~2001-01-09 18:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-09 18:20 Noah Aklilu
2001-01-09 18:32 ` Fernando Nasser [this message]
2001-01-10 20:20   ` Noah Aklilu
2001-01-11  7:26     ` Fernando Nasser
2001-01-12 20:50       ` Noah Aklilu
2001-01-12 21:00       ` Noah Aklilu

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=3A5BC95E.FD5A2934@redhat.com \
    --to=fnasser@redhat.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=naklilu@ualberta.ca \
    /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).