Re: Jeeni & ARM720T with GDB

Re: Jeeni & ARM720T with GDB

[danish iftikhar]

>From: Fernando Nasser <fnasser@cygnus.com>
>To: danish iftikhar <d_iftikhar@hotmail.com>
>CC: grante@visi.com
>Subject: Re: Jeeni & ARM720T with GDB
>Date: Wed, 22 Nov 2000 07:30:20 +0000
>
>Danish,
>
>I believe we need mode information.  The log seems normal to me.
>
>What is the value of the PC  (P/x $pc) after the load?
>
>Can you do a "x/30i $pc" so we see the startup code?
>
>When you do "break main", what is printed?
>
>And, maybe before all that, what was the exact command you've used to 
>compile?
>
>What is the output when you add "-v" to your gcc command?
>
>Fernando
>
***************************************************
  Hi

   i am enclosing all the information that u have asked for :

  arm-elf-gcc -v
Reading specs from 
/proj/danish/ECOS_EP7211/tools/H-i686-pc-linux-gnu/lib/gcc-lib/arm-elf/2.95.2/specs
gcc version 2.95.2 19991024 (release)

the command i am using to compile is :
CXX = arm-elf-gcc -mcpu=arm7tdmi -D__EDB7211


arm-elf-gdb -v
GNU gdb 5.0
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-elf".


After load Pc shows the address : 0x8060

The start uo code is :
(gdb) x/30i $pc
0x8060 <warm_reset>:    mrs     r7, cpsr
0x8064 <warm_reset+4>:  and     r7, r7, #31     ; 0x1f
0x8068 <warm_reset+8>:  cmp     r7, #19 ; 0x13
0x806c <warm_reset+12>: beq     0x80a0 <start>
0x8070 <warm_reset+16>: mov     r0, #0  ; 0x0
0x8074 <warm_reset+20>: str     r0, [r0, #64]
0x8078 <warm_reset+24>: ldr     r1, [pc, #4c0]  ; 0x8540 <_eCos_id+20>
0x807c <warm_reset+28>: ldr     r2, [r1, #4]
0x8080 <warm_reset+32>: str     r2, [r0, #4]
0x8084 <warm_reset+36>: ldr     r2, [r1, #36]
0x8088 <warm_reset+40>: str     r2, [r0, #36]
0x808c <warm_reset+44>: ldr     r2, [r1, #8]
0x8090 <warm_reset+48>: str     r2, [r0, #8]
0x8094 <warm_reset+52>: ldr     r2, [r1, #64]
0x8098 <warm_reset+56>: str     r2, [r0, #40]
0x809c <warm_reset+60>: swi     0x00000000
0x80a0 <start>: ldr     r0, [pc, #474]  ; 0x851c <.init_flag>
0x80a4 <start+4>:       ldr     r1, [r0]
0x80a8 <start+8>:       cmp     r1, #0  ; 0x0
0x80ac <start+12>:      bne     0x80a8 <start+8>
0x80b0 <start+16>:      ldr     r1, [pc, #c8]   ; 0x8180 <init_done>
0x80b4 <start+20>:      str     r1, [r0]
0x80b8 <start+24>:      mov     r0, #0  ; 0x0
0x80bc <start+28>:      ldr     r1, [pc, #454]  ; 0x8518 
<.__exception_handlers>
0x80c0 <start+32>:      cmp     r7, #19 ; 0x13
0x80c4 <start+36>:      beq     0x80d0 <start+48>
0x80c8 <start+40>:      ldr     r2, [r1, #40]
0x80cc <start+44>:      str     r2, [r0, #40]
0x80d0 <start+48>:      ldr     r2, [r1, #24]
0x80d4 <start+52>:      str     r2, [r0, #24]

  i am not able to do step or cont but using stepi i went through this 
startup function . It seems to loop around between 0x815c & 0x8164 and is 
not going ahead of that .
the code at this address is as follows :

0x8154  <start+180>:            cmp     r1, r2
-       0x8158  <start+184>:            beq     0x8168 <start+200>
-       0x815c  <start+188>:            str     r0, [r1], #4
-       0x8160  <start+192>:            cmp     r1, r2
-       0x8164  <start+196>:            bne     0x815c <start+188>
-       0x8168  <start+200>:            bl      0x1f194 <hal_hardware_init>
-       0x816c  <start+204>:            bl      0x1ee10 
<cyg_hal_invoke_constructors>
-       0x8170  <start+208>:            bl      0x1f358 <cyg_start>


umm when i do a break main , the reply is :

gdb) break main
Breakpoint 1 at 0x8558: file App.c

  Hoping to get an early reply from your side

thanks
danish.


_____________________________________________________________________________________
Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com

Re: Jeeni & ARM720T with GDB

[Grant Edwards]

On Wed, Nov 22, 2000 at 10:35:04AM -0000, danish iftikhar wrote:

> After load Pc shows the address : 0x8060
> 
> The start uo code is :
> (gdb) x/30i $pc
> 0x8060 <warm_reset>:    mrs     r7, cpsr
> 0x8064 <warm_reset+4>:  and     r7, r7, #31     ; 0x1f
> 0x8068 <warm_reset+8>:  cmp     r7, #19 ; 0x13
> 0x806c <warm_reset+12>: beq     0x80a0 <start>

That looks right.

>   i am not able to do step or cont but using stepi i went through this 
> startup function . It seems to loop around between 0x815c & 0x8164 and is 
> not going ahead of that .
> the code at this address is as follows :
> 
> 0x8154  <start+180>:            cmp     r1, r2
> -       0x8158  <start+184>:            beq     0x8168 <start+200>
> -       0x815c  <start+188>:            str     r0, [r1], #4
> -       0x8160  <start+192>:            cmp     r1, r2
> -       0x8164  <start+196>:            bne     0x815c <start+188>
> -       0x8168  <start+200>:            bl      0x1f194 <hal_hardware_init>
> -       0x816c  <start+204>:            bl      0x1ee10 
> <cyg_hal_invoke_constructors>
> -       0x8170  <start+208>:            bl      0x1f358 <cyg_start>

It looks to me like the debugger and emulator are working fine.
The loop you're looking at is zeroing out the bss section.  R2
should contain the address of the end of bss, and R1 should
start at the beginning of bss and increment through the whole
section.  This loop will probably execute tens of thousands of
times, so you can get pretty bored doing a stepi...

Do the addresses in R1 and R2 correspond to your bss section?

Can you set a breakpoint immediately following the loop and do
a cont?

-- 
Grant Edwards
grante@visi.com

Re: Jeeni & ARM720T with GDB

[danish iftikhar]

  Hi
     i went through the code and checked the addresses of bss as well as 
other sections and they are perfectly o.k.
  ya , grant , it's zeroing the bss address only and i was able to come out 
of that loop .
where it stucks is in <cyg_hal_invoke_constructors> : take a look at code 
below :


> > 0x8154  <start+180>:            cmp     r1, r2
> > -       0x8158  <start+184>:            beq     0x8168 <start+200>
> > -       0x815c  <start+188>:            str     r0, [r1], #4
> > -       0x8160  <start+192>:            cmp     r1, r2
> > -       0x8164  <start+196>:            bne     0x815c <start+188>
> > -       0x8168  <start+200>:            bl      0x1f194 
><hal_hardware_init>
> > -       0x816c  <start+204>:            bl      0x1ee10
<cyg_hal_invoke_constructors>
> > > > -       0x8170  <start+208>:            bl      0x1f358 <cyg_start>


  things seem to work perfectly fine for h/w initialisation .
  i wonder whether some special options have to be configured in ecos build 
to make it work. i have a basic doubt ..how the diagnostic output is handled 
.
i don't think that jeeni will be able to send it back to console ..
or will connecting through the serial port work .
is the diag printf 's are the one causing it to hang.

thanks
danish.



>From: Grant Edwards <grante@visi.com>
>To: danish iftikhar <d_iftikhar@hotmail.com>
>CC: fnasser@cygnus.com, gdb@sourceware.cygnus.com
>Subject: Re: Jeeni & ARM720T with GDB
>Date: Wed, 22 Nov 2000 08:39:21 -0600
>
>On Wed, Nov 22, 2000 at 10:35:04AM -0000, danish iftikhar wrote:
>
> > After load Pc shows the address : 0x8060
> >
> > The start uo code is :
> > (gdb) x/30i $pc
> > 0x8060 <warm_reset>:    mrs     r7, cpsr
> > 0x8064 <warm_reset+4>:  and     r7, r7, #31     ; 0x1f
> > 0x8068 <warm_reset+8>:  cmp     r7, #19 ; 0x13
> > 0x806c <warm_reset+12>: beq     0x80a0 <start>
>
>That looks right.
>
> >   i am not able to do step or cont but using stepi i went through this
> > startup function . It seems to loop around between 0x815c & 0x8164 and 
>is
> > not going ahead of that .
> > the code at this address is as follows :
> >
> > 0x8154  <start+180>:            cmp     r1, r2
> > -       0x8158  <start+184>:            beq     0x8168 <start+200>
> > -       0x815c  <start+188>:            str     r0, [r1], #4
> > -       0x8160  <start+192>:            cmp     r1, r2
> > -       0x8164  <start+196>:            bne     0x815c <start+188>
> > -       0x8168  <start+200>:            bl      0x1f194 
><hal_hardware_init>
> > -       0x816c  <start+204>:            bl      0x1ee10
> > <cyg_hal_invoke_constructors>
> > -       0x8170  <start+208>:            bl      0x1f358 <cyg_start>
>
>It looks to me like the debugger and emulator are working fine.
>The loop you're looking at is zeroing out the bss section.  R2
>should contain the address of the end of bss, and R1 should
>start at the beginning of bss and increment through the whole
>section.  This loop will probably execute tens of thousands of
>times, so you can get pretty bored doing a stepi...
>
>Do the addresses in R1 and R2 correspond to your bss section?
>
>Can you set a breakpoint immediately following the loop and do
>a cont?
>
>--
>Grant Edwards
>grante@visi.com

_____________________________________________________________________________________
Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com

Re: Jeeni & ARM720T with GDB

[Grant Edwards]

>   i went through the code and checked the addresses of bss as well as other
> sections and they are perfectly o.k. ya , grant , it's zeroing the bss
> address only and i was able to come out of that loop . where it stucks is
> in <cyg_hal_invoke_constructors> : take a look at code below :

I don't think you have any problems with gdb or the Jeeni.

>   things seem to work perfectly fine for h/w initialisation . i wonder
> whether some special options have to be configured in ecos build to make it
> work. i have a basic doubt ..how the diagnostic output is handled . i don't
> think that jeeni will be able to send it back to console .. or will
> connecting through the serial port work . is the diag printf 's are the one
> causing it to hang.

You probably have eCos configured incorrectly.  Diag_printf calls
hal_diag_write_char (or something like that) to write diagnostic output. The
platform (and therefore the HAL package) you selected when you configured
eCos must provide diagnostic output routines that work with your board.

There are two ways to handle diagnostic output:

1) Use a UART or other output device and have hal_diag_xxx write to that
   device.

2) Send diagnostic output to the debugger.

I don't think you can use option 2 with the Jeeni.  While the RDI protocol
does allow for a debug channel, there is no way to write debug data to the
Jeeni using the JTAG interface.  If you were debugging via GDB stubs or via
the Angel ROM monitor, I think you could use option 2.

If you want to use option 1, you have to have an extra UART or some other
type of comm port available for use by the hal_diag_xxx routines.  Having an
extra UART available for use during debugging can be _extremely_ handy.

In any case, it looks like gdb and Jeeni are working fine.  Perhaps the eCos
documentation and mailing list would be a good place to look for advice on
getting the hal_diag_write_char() routine to work for your hardware.

-- 
Grant Edwards
grante@visi.com

Re: Jeeni & ARM720T with GDB

[danish iftikhar]

>From: Michael Leibowitz <mleibowi@crystal.cirrus.com>
>Reply-To: mleibowi@crystal.cirrus.com
>To: Fernando Nasser <fnasser@cygnus.com>
>CC: danish iftikhar <d_iftikhar@hotmail.com>, gdb@sourceware.cygnus.com
>Subject: Re: Jeeni & ARM720T with GDB
>Date: Mon, 20 Nov 2000 11:04:14 -0600
>
>When I try that, I get an error message:
>
>Continuing.
>RDI_execute: a miscellaneous type of error
>
>Program received signal SIGTERM, Terminated.
>?? () at setup.S:4
>4		B	Reset_Handler
>Current language:  auto; currently asm
>
>using gdb 5.0 (insight w/ -nw) and 7211 eval board.
>
>Any ideas?
>
>On Mon, 20 Nov 2000 10:48:14 Fernando Nasser wrote:
> > The sequence of commands you should use is:
> >
> > file <exec>
> > target rdi e=....
> > load
> > break <somewhere>
> > cont
> >
> >
> > Don't use the load command argument.
>
******************

   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 .

regards
danish.


_____________________________________________________________________________________
Get more from the Web.  FREE MSN Explorer download : http://explorer.msn.com

Re: Jeeni & ARM720T with GDB

[Fernando Nasser]

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

Jeeni & ARM720T with GDB

[danish iftikhar]

Hi
   I am trying to use Jeeni EMbedded Ice to connect from my linux host 
running GDB to Cirrus Logic EP7211 board .
The board uses ARM720T processor , due to which i have set the same 
configuration in Jeeni .
Then i tried to connect to target by using target rdi e=IP_ADDR ;
( as i tried using ethernet interface ) . It then said connected to target 
..something..something .
But when i give the load (filename) , it does'nt do anything ..
once it said "you can't do that when your target is exec" , i gave the 
target rdi command again and tried to download & then it hanged .

Can anybody explain what is happening...do i need to do anything else for 
downloading the program .

PS: i have set the appropriate endianness also .

regards
danish.


_________________________________________________________________________
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com .

Share information about yourself, create your own public profile at 
http://profiles.msn.com .

Re: Jeeni & ARM720T with GDB

[Fernando Nasser]

The sequence of commands you should use is:

file <exec>
target rdi e=....
load
break <somewhere>
cont


Don't use the load command argument.

Fernando


danish iftikhar wrote:
> 
> Hi
>    I am trying to use Jeeni EMbedded Ice to connect from my linux host
> running GDB to Cirrus Logic EP7211 board .
> The board uses ARM720T processor , due to which i have set the same
> configuration in Jeeni .
> Then i tried to connect to target by using target rdi e=IP_ADDR ;
> ( as i tried using ethernet interface ) . It then said connected to target
> ..something..something .
> But when i give the load (filename) , it does'nt do anything ..
> once it said "you can't do that when your target is exec" , i gave the
> target rdi command again and tried to download & then it hanged .
> 
> Can anybody explain what is happening...do i need to do anything else for
> downloading the program .
> 
> PS: i have set the appropriate endianness also .
> 
> regards
> danish.
> 
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com .
> 
> Share information about yourself, create your own public profile at
> http://profiles.msn.com .

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

Re: Jeeni & ARM720T with GDB

[Michael Leibowitz]

When I try that, I get an error message:

Continuing.
RDI_execute: a miscellaneous type of error

Program received signal SIGTERM, Terminated.
?? () at setup.S:4
4		B	Reset_Handler
Current language:  auto; currently asm

using gdb 5.0 (insight w/ -nw) and 7211 eval board.

Any ideas?

On Mon, 20 Nov 2000 10:48:14 Fernando Nasser wrote:
> The sequence of commands you should use is:
> 
> file <exec>
> target rdi e=....
> load
> break <somewhere>
> cont
> 
> 
> Don't use the load command argument.

Re: Jeeni & ARM720T with GDB

[Fernando Nasser]

Michael Leibowitz wrote:
> 
> When I try that, I get an error message:
> 
> Continuing.
> RDI_execute: a miscellaneous type of error
> 
> Program received signal SIGTERM, Terminated.
> ?? () at setup.S:4
> 4               B       Reset_Handler
> Current language:  auto; currently asm
> 
> using gdb 5.0 (insight w/ -nw) and 7211 eval board.
> 
> Any ideas?
> 

It can be the way you compiled/linked your program or a series of
other reasons.  There is not much information above.
Maybe you should post pieces of console output with the relevant 
information (the output of "gcc -v", your compilation command and 
any messages printed by gcc, etc).

BTW, which host are you running gdb on? Which OS version, libraries...

If I am not mistaken, there were a series of fixes and improvements
to GDB RDI after 5.0 came out.  I am not sure that they can make any
difference to your case, but maybe you should consider switching to
more recent sources.

Fernando



> On Mon, 20 Nov 2000 10:48:14 Fernando Nasser wrote:
> > The sequence of commands you should use is:
> >
> > file <exec>
> > target rdi e=....
> > load
> > break <somewhere>
> > cont
> >
> >
> > Don't use the load command argument.

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

Re: Jeeni & ARM720T with GDB

[Grant Edwards]

On Mon, Nov 20, 2000 at 05:17:30PM +0000, Fernando Nasser wrote:

> It can be the way you compiled/linked your program or a series of
> other reasons.  There is not much information above.
> Maybe you should post pieces of console output with the relevant 
> information (the output of "gcc -v", your compilation command and 
> any messages printed by gcc, etc).
> 
> BTW, which host are you running gdb on? Which OS version, libraries...
> 
> If I am not mistaken, there were a series of fixes and improvements
> to GDB RDI after 5.0 came out.  I am not sure that they can make any
> difference to your case, but maybe you should consider switching to
> more recent sources.

Most of the changes had to do with Insight GUI issues, but it
couldn't hurt to use a recent snapshot.

-- 
Grant Edwards
grante@visi.com

Re: Jeeni & ARM720T with GDB

[Grant Edwards]

On Mon, Nov 20, 2000 at 11:04:14AM -0600, Michael Leibowitz wrote:

> When I try that, I get an error message:
> 
> Continuing.
> RDI_execute: a miscellaneous type of error
> 
> Program received signal SIGTERM, Terminated.
> ?? () at setup.S:4
> 4		B	Reset_Handler
> Current language:  auto; currently asm
> 
> using gdb 5.0 (insight w/ -nw) and 7211 eval board.
> 
> Any ideas?

The "load" works OK?

-- 
Grant Edwards
grante@visi.com

Re: Jeeni & ARM720T with GDB

[Michael Leibowitz]

On Mon, 20 Nov 2000 16:29:25 Grant Edwards wrote:
> On Mon, Nov 20, 2000 at 11:04:14AM -0600, Michael Leibowitz wrote:

> The "load" works OK?

Yeah

Re: Jeeni & ARM720T with GDB

[Grant Edwards]

On Mon, Nov 20, 2000 at 05:38:21PM -0600, Michael Leibowitz wrote:

> > The "load" works OK?
> 
> Yeah

Do the load addresses and start addresses printed by the "load"
command look right?

-- 
Grant Edwards
grante@visi.com

Re: Jeeni & ARM720T with GDB

[Grant Edwards]

On Mon, Nov 20, 2000 at 04:48:14PM +0000, Fernando Nasser wrote:
> The sequence of commands you should use is:
> 
> file <exec>
> target rdi e=....
> load
> break <somewhere>
> cont
> 
> Don't use the load command argument.

Why not?  

It works fine for me.  The macro I use to load an ELF object
file is:

define reload
  resetcpu
  delete
  symbol-file 
  symbol-file $arg0
  load $arg0
  break *0x00
  break *0x04
  break *0x08
  break *0x0c
  break *0x10
  break *0x14
  # IRQ at 0x18 is used
  break *0x1c
end

After a "reload" then I do "cont" after optionally setting more
breakpoints.

The "resetcpu" command at the top is another macro that resets
a bunch of peripheral chips and puts them into a known state.

-- 
Grant Edwards
grante@visi.com