Re: Jeeni & ARM720T with GDB

Fernando Nasser
2000-11-21T09:36:00Z

danish iftikhar wrote:
>
> Well , i tried to use the above commands and was able to download
> successfully . But after i set break point and do continue , everything
> seems to hang .
> Any guesses what is going wrong now .
> the rdiromatzero command for EP7211 board should be set at 0 or 1 ??
> i am using insight 5.0 .
>
> do we need to specifically download some program for reset and all those
> things which Grant has told .
>

I don't have a Jeeni target, so Grant is the person who can help you with that.

I would try "set rdiromatzero true" as it is a quick test.

Another thing you can do is to turn on Grant's RDI trace facility:

Something like

maintenance rdilogfile /dev/tty
maintenance rdilogenable on

Would print the message exchange between GDB and the target.

Do this after the load or you will have too many messages!

BTW, your program may have been linked with the wrong load address.
What is the value of the PC (P/x $pc) after the load?

--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
From taylor@cygnus.com Tue Nov 21 12:38:00 2000
From: David Taylor <taylor@cygnus.com>
To: gdb@sourceware.cygnus.com
Cc: gdb-patches@sourceware.cygnus.com
Subject: pathmap (again)
Date: Tue, 21 Nov 2000 12:38:00 -0000
Message-id: <200011212037.PAA22391@texas.cygnus.com>
X-SW-Source: 2000-11/msg00222.html
Content-length: 1370

Okay, I don't think there was complete agreement on the syntax and the
semantics, but here's a stab at what I think was agreeable to most...

Proposed Interface:

pathmap add <from> <to>

append a mapping from directory <from> to directory <to>
to the current list of mappings.

pathmap delete <optional-list>

delete the mappings indexed by <optional-list> from the
list of known mappings. All subsequent mappings move up
the list. (For example, if you delete mapping 2, then mapping
3 becomes mapping 2, mapping 4 becomes mapping 3, and so on.)

pathmap list <optional-list>

list the specified mappings. If no list is given, all
mappings are listed.

and potentially:

pathmap insert <index> <from> <to>

As for 'pathmap add', but insert the mapping immediately after
mapping <index>. All subsequent mappings move down the list.
If <index> is zero, then the mapping is inserted before the
first mapping.

Where:

<from> and <to> are directory path prefixes

<optional-list> is a list in the same format as for the
breakpoint commands

<index> is a non negative integer

And the mappings are not regular expressions -- that is left as a
potential enhancement for the future. Also, I'm unconvinced of the
need for the "pathmap insert" functionality.

Comments?

David
--
David Taylor
taylor@redhat.com, taylor@cygnus.com
From fnasser@cygnus.com Tue Nov 21 13:39:00 2000
From: Fernando Nasser <fnasser@cygnus.com>
To: David Taylor <taylor@cygnus.com>
Cc: gdb@sourceware.cygnus.com, gdb-patches@sourceware.cygnus.com
Subject: Re: pathmap (again)
Date: Tue, 21 Nov 2000 13:39:00 -0000
Message-id: <3A1AEBA8.5EA780AF@cygnus.com>
References: <200011212037.PAA22391@texas.cygnus.com>
X-SW-Source: 2000-11/msg00223.html
Content-length: 2492

Well, I like it this way. It does not hurt the CLI language at all
so if you are looking for an "approval in principle" or something like that
consider it given. I will not pest you with requests to change the command
interface anymore :-)

I can only answer for the CLI aspects though. But I understood that people
liked the idea of having this around, so if I did not misunderstood I believe
everybody is sort of waiting for the patch already.

The "insert" operation is interesting. I think J.T. gave a good example of
a situation where it can be useful. But I guess it is a simple thing to add
at any time, so we may test the concept by initially not providing it and
seeing if someone asks for it (out of a personal need) or even send a patch.

IMO you should go ahead with this and submit a patch.

Fernando

David Taylor wrote:
>
> Okay, I don't think there was complete agreement on the syntax and the
> semantics, but here's a stab at what I think was agreeable to most...
>
> Proposed Interface:
>
> pathmap add <from> <to>
>
> append a mapping from directory <from> to directory <to>
> to the current list of mappings.
>
> pathmap delete <optional-list>
>
> delete the mappings indexed by <optional-list> from the
> list of known mappings. All subsequent mappings move up
> the list. (For example, if you delete mapping 2, then mapping
> 3 becomes mapping 2, mapping 4 becomes mapping 3, and so on.)
>
> pathmap list <optional-list>
>
> list the specified mappings. If no list is given, all
> mappings are listed.
>
> and potentially:
>
> pathmap insert <index> <from> <to>
>
> As for 'pathmap add', but insert the mapping immediately after
> mapping <index>. All subsequent mappings move down the list.
> If <index> is zero, then the mapping is inserted before the
> first mapping.
>
> Where:
>
> <from> and <to> are directory path prefixes
>
> <optional-list> is a list in the same format as for the
> breakpoint commands
>
> <index> is a non negative integer
>
> And the mappings are not regular expressions -- that is left as a
> potential enhancement for the future. Also, I'm unconvinced of the
> need for the "pathmap insert" functionality.
>
> Comments?
>

--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario M4P 2C9
From jtc@redback.com Tue Nov 21 17:06:00 2000
From: jtc@redback.com (J.T. Conklin)
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb@sourceware.cygnus.com
Subject: Re: memory region documentation
Date: Tue, 21 Nov 2000 17:06:00 -0000
Message-id: <5mem04rf23.fsf@jtc.redback.com>
References: <5mg0ku2r9l.fsf@jtc.redback.com> <200011151126.GAA03721@indy.delorie.com> <5mpujvhh52.fsf@jtc.redback.com> <200011162001.PAA04807@indy.delorie.com>
X-SW-Source: 2000-11/msg00224.html
Content-length: 883

>>>>> "Eli" == Eli Zaretskii <eliz@delorie.com> writes:
>> However, this exercise has reminded me why I'm a programmer and not a
>> tech writer.

Eli> Actually, what you wrote was very good; the comments I had were pretty
Eli> much minor.

Thanks, but I stand by my comment --- You didn't see what went into
that draft. I spent a lot of time writing (and re-writing) it until
it reflected what I wanted to say.

>> Can you tell me where you'd like me to put this chapter? I assume
>> it's a chapter, since it doesn't seem to be a good fit into any of
>> the existing chapters --- especially if we start adding more varied
>> attributes.

Eli> It looks like between "Native Debugging" and "Support Libraries"
Eli> would be a good place.

Eh? Those chapters are in the internals document, this is intended to
be user documentation.

--jtc

--
J.T. Conklin
RedBack Networks
From d_iftikhar@hotmail.com Wed Nov 22 00:08:00 2000
From: "danish iftikhar" <d_iftikhar@hotmail.com>
To: gdb@sourceware.cygnus.com
Subject: GDB & Jeeni
Date: Wed, 22 Nov 2000 00:08:00 -0000
Message-id: <F2516byoxxSQWBLYu7A00001552@hotmail.com>
X-SW-Source: 2000-11/msg00225.html
Content-length: 4680

Hi
i am still not able to execute the program on the target boeard .
As soon as i give 'cont' , everything goes for a toss .
i am also not able to single step it ..when i give info target command , it
says "Target does not support single stepping " .
But , when i tried by using "stepi" instruction it at once moved into some
"warm-reset" assembly code ..& from there to "start" code and startted an
endless loop there .
i think that it is not able to initialise even ..
any guesses where the problem may be .
i enabled the rdilogfile , but i could'nt figure out anything from it ..
i am attaching the log file , hoping some of u may help me in this regard .

thanks
danish.

WITH rdiromatzero 1 :

ADP log file opened at Wed Nov 22 16:40:10 2000

tx: [T=0 L=25] 01 fd fc 01 05 00 01 00 00 00 00 00 ff ff ff ff ff ff ff ff
ff 00 00 02 00
R=00010005 H->T CI_HADP: ADP_CPUread ff 00020000
rx: [T=0 L=28] 01 fd fd 01 05 00 01 80 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00 d3 00 00 00
R=80010005 H<-T CI_HADP: ADP_CPUread 00000000 000000d3
tx: [T=0 L=25] 01 fe fd 01 05 00 01 00 00 00 00 00 ff ff ff ff ff ff ff ff
ff 00 08 00 00
R=00010005 H->T CI_HADP: ADP_CPUread ff 00000800
rx: [T=0 L=28] 01 fe fe 01 05 00 01 80 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00 60 18 00 00
R=80010005 H<-T CI_HADP: ADP_CPUread 00000000 00001860
tx: [T=0 L=28] 01 ff fe 01 03 00 01 00 00 00 00 00 ff ff ff ff ff ff ff ff
60 80 00 00 04 00 00 00
R=00010003 H->T CI_HADP: ADP_Read 00008060 00000004
rx: [T=0 L=32] 01 ff ff 01 03 00 01 80 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00 00 00 00 00 00 70 0f e1
R=80010003 H<-T CI_HADP: ADP_Read 00000000 00000000 e10f7000
tx: [T=0 L=25] 01 00 ff 01 05 00 01 00 00 00 00 00 ff ff ff ff ff ff ff ff
ff 00 20 00 00
R=00010005 H->T CI_HADP: ADP_CPUread ff 00002000
rx: [T=0 L=28] 01 00 00 01 05 00 01 80 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00 54 18 00 00
R=80010005 H<-T CI_HADP: ADP_CPUread 00000000 00001854
tx: [T=0 L=29] 01 01 00 01 09 00 01 00 00 00 00 00 ff ff ff ff ff ff ff ff
8c 85 00 00 00 00 00 00 00
R=00010009 H->T CI_HADP: ADP_SetBreak 0000858c 00000000 00000000
rx: [T=0 L=36] 01 01 01 01 09 00 01 80 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00 78 ec 03 00 74 fe 1e 00 dc 98 00 00
R=80010009 H<-T CI_HADP: ADP_SetBreak 00000000 0003ec78 001efe74 000098dc
tx: [T=0 L=24] 01 02 01 01 0d 00 01 00 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00
R=0001000d H->T CI_HADP: ADP_Execute 00000000
rx: [T=0 L=24] 01 02 02 01 0d 00 01 80 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00
R=8001000d H<-T CI_HADP: ADP_Execute 00000000

WITH rdiromatzero 0 :

ADP log file opened at Wed Nov 22 16:55:43 2000

tx: [T=0 L=25] 01 fd fc 01 05 00 01 00 00 00 00 00 ff ff ff ff ff ff ff ff
ff 00 00 02 00
R=00010005 H->T CI_HADP: ADP_CPUread ff 00020000
rx: [T=0 L=28] 01 fd fd 01 05 00 01 80 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00 d3 00 00 00
R=80010005 H<-T CI_HADP: ADP_CPUread 00000000 000000d3
tx: [T=0 L=25] 01 fe fd 01 05 00 01 00 00 00 00 00 ff ff ff ff ff ff ff ff
ff 00 08 00 00
R=00010005 H->T CI_HADP: ADP_CPUread ff 00000800
rx: [T=0 L=28] 01 fe fe 01 05 00 01 80 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00 60 18 00 00
R=80010005 H<-T CI_HADP: ADP_CPUread 00000000 00001860
tx: [T=0 L=28] 01 ff fe 01 03 00 01 00 00 00 00 00 ff ff ff ff ff ff ff ff
60 80 00 00 04 00 00 00
R=00010003 H->T CI_HADP: ADP_Read 00008060 00000004
rx: [T=0 L=32] 01 ff ff 01 03 00 01 80 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00 00 00 00 00 00 70 0f e1
R=80010003 H<-T CI_HADP: ADP_Read 00000000 00000000 e10f7000
tx: [T=0 L=25] 01 00 ff 01 05 00 01 00 00 00 00 00 ff ff ff ff ff ff ff ff
ff 00 20 00 00
R=00010005 H->T CI_HADP: ADP_CPUread ff 00002000
rx: [T=0 L=28] 01 00 00 01 05 00 01 80 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00 54 18 00 00
R=80010005 H<-T CI_HADP: ADP_CPUread 00000000 00001854
tx: [T=0 L=29] 01 01 00 01 09 00 01 00 00 00 00 00 ff ff ff ff ff ff ff ff
8c 85 00 00 00 00 00 00 00
R=00010009 H->T CI_HADP: ADP_SetBreak 0000858c 00000000 00000000
rx: [T=0 L=36] 01 01 01 01 09 00 01 80 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00 78 ec 03 00 74 fe 1e 00 dc 98 00 00
R=80010009 H<-T CI_HADP: ADP_SetBreak 00000000 0003ec78 001efe74 000098dc
tx: [T=0 L=24] 01 02 01 01 0d 00 01 00 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00
R=0001000d H->T CI_HADP: ADP_Execute 00000000
rx: [T=0 L=24] 01 02 02 01 0d 00 01 80 00 00 00 00 ff ff ff ff ff ff ff ff
00 00 00 00
R=8001000d H<-T CI_HADP: ADP_Execute 00000000