[ECOS] GDB question

[ECOS] GDB question

[kah.yin.ng]

Dear all,
     I am trying to use GDB to read the contents of some register such as the
PRCMD, PSC, and the SYC registers on the V850/SB1 micro. Besides using the
printf statements and reading the memory addresses of these register, is there
any other way that I can read the contents of these registers? I am avoiding the
printf statement because I hope to see the changes inside the register all the
time. The value I read from the memory address is different from what I print
out, so I hope there will be a more reliable way to read the registers.

     Thanks!

--Kah

Re: [ECOS] GDB question.

[Ottawa Guy]

Hi Gary,
Thanks for your response, I am writing the STUB code
for SPARC simulator. It turns out that the Uart I/O
function was returning "char" and ECOS converts the
"char" to a int. Since the coversion process failed,
ECOS GDB stub keeps on sending the same response over
and over again. Once I realized that, it fixed some of
my problems.
       Hadi 
       
--- Gary Thomas <gary@mlbassoc.com> wrote:
> On Fri, 2004-02-06 at 23:15, Ottawa Guy wrote:
> > Hello,
> > I am very new at implementing GDB stuff. I have
> > simulator which can a talk to a GDB host software
> > throught a serial port. I loaded GDB stubs in my
> > simulator and called "breakpoint()". 
> 
> What kind of simulator is this?  Who wrote the GDB
> stubs that
> run on the simulator?
> 
> > 
> > I start my gdb host program, and type the
> following
> > 
> > (gdb) target extended-remote /dev/ttyS0
> > Remote debugging using /dev/ttyS0
> > Couldn't establish connection to remote target
> > Malformed response to offset query,
> > T0544:00000000;0e:00000000;
> > (gdb) 
> > 
> > 
> > I found the GDB host was sending "+$Hc-1#09" to my
> > target.
> > 
> > It seems my GDB stub program keep on sending
> > "T0544:00000000;0e:00000000" string I have no idea
> > why.
> 
> This is an indication from the remote system that it
> has stopped, 
> probably abnormally.  It most likely means that your
> stubs are not
> working properly.  The fact that the values are 0
> also implies that
> there is something wrong at the other end.
> 
> > 
> > 
> > Can someone let me know what are the sequence of
> > events suppose to happen at the target when  the
> GDB
> > host request for a connection. By that I mean when
> the
> > GDB host type "target extended-remote /dev/ttyS0"
> what
> > should be the sequence of response expected from
> the
> > target.
> 
> The actual request/reply script will differ from
> platform to platform
> and architecture to architecture.  To understand
> this completely, you'll
> need to read about the GDB remote protocol.  If you
> are running Linux,
> you can get a very complete description from "info
> gdb"
> 
> Gary Thomas <gary@mlbassoc.com>
> MLB Associates
> 


__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] GDB question.

[Gary Thomas]

On Fri, 2004-02-06 at 23:15, Ottawa Guy wrote:
> Hello,
> I am very new at implementing GDB stuff. I have
> simulator which can a talk to a GDB host software
> throught a serial port. I loaded GDB stubs in my
> simulator and called "breakpoint()". 

What kind of simulator is this?  Who wrote the GDB stubs that
run on the simulator?

> 
> I start my gdb host program, and type the following
> 
> (gdb) target extended-remote /dev/ttyS0
> Remote debugging using /dev/ttyS0
> Couldn't establish connection to remote target
> Malformed response to offset query,
> T0544:00000000;0e:00000000;
> (gdb) 
> 
> 
> I found the GDB host was sending "+$Hc-1#09" to my
> target.
> 
> It seems my GDB stub program keep on sending
> "T0544:00000000;0e:00000000" string I have no idea
> why.

This is an indication from the remote system that it has stopped, 
probably abnormally.  It most likely means that your stubs are not
working properly.  The fact that the values are 0 also implies that
there is something wrong at the other end.

> 
> 
> Can someone let me know what are the sequence of
> events suppose to happen at the target when  the GDB
> host request for a connection. By that I mean when the
> GDB host type "target extended-remote /dev/ttyS0" what
> should be the sequence of response expected from the
> target.

The actual request/reply script will differ from platform to platform
and architecture to architecture.  To understand this completely, you'll
need to read about the GDB remote protocol.  If you are running Linux,
you can get a very complete description from "info gdb"

Gary Thomas <gary@mlbassoc.com>
MLB Associates


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

[ECOS] GDB question.

[Ottawa Guy]

Hello,
I am very new at implementing GDB stuff. I have
simulator which can a talk to a GDB host software
throught a serial port. I loaded GDB stubs in my
simulator and called "breakpoint()". 

I start my gdb host program, and type the following

(gdb) target extended-remote /dev/ttyS0
Remote debugging using /dev/ttyS0
Couldn't establish connection to remote target
Malformed response to offset query,
T0544:00000000;0e:00000000;
(gdb) 


I found the GDB host was sending "+$Hc-1#09" to my
target.

It seems my GDB stub program keep on sending
"T0544:00000000;0e:00000000" string I have no idea
why.


Can someone let me know what are the sequence of
events suppose to happen at the target when  the GDB
host request for a connection. By that I mean when the
GDB host type "target extended-remote /dev/ttyS0" what
should be the sequence of response expected from the
target.

           Thank you in advance.
                       Ottawa




__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss