Remote monitor 'qCmd' command response

Remote monitor 'qCmd' command response

[Mitchell Fang]

Hi,

  I was wondering if someone could clarify this part from the GDB manual:

" Before the final result packet, the target may also respond with a
number of intermediate 'Ooutput' console output packets."

I'm trying to implement this intermediate response functionality and
not having much success.  I plan to use it to where I have a response
like

(gdb) monitor load
<response from stub>  Loading....
<response from stub>  Loading....
<response from stub>  load successful
(gdb)

Is this even possible?

What happens right now is that I send 'OLoading...' and then gdb
doesn't accept the other responses cause it thinks its the final
result packet.

Here's what is shows on the console:

(gdb) monitor load
0Loading...
(gdb)

Here is the log:

w $qRcmd,6c6f61642062696e203838382e62696e#a9
r +<Timeout: 2 seconds>
w -
r <Timeout: 2 seconds>
w -
r $4f4c6f6164696e672e2e2e0a#6b
w +

I'm not really sure whats going on and some help would be nice.

Thanks
Mitchell

Re: Remote monitor 'qCmd' command response

[Daniel Jacobowitz]

On Wed, Jun 07, 2006 at 12:01:41PM -0700, Mitchell Fang wrote:
> What happens right now is that I send 'OLoading...' and then gdb
> doesn't accept the other responses cause it thinks its the final
> result packet.
> 
> Here's what is shows on the console:
> 
> (gdb) monitor load
> 0Loading...
> (gdb)
> 
> Here is the log:
> 
> w $qRcmd,6c6f61642062696e203838382e62696e#a9
> r +<Timeout: 2 seconds>
> w -
> r <Timeout: 2 seconds>
> w -
> r $4f4c6f6164696e672e2e2e0a#6b
> w +

That's not "OLoading...".  The _data_ for the packet is supposed to be
hex escaped, not the packet itself.  It should start with an "O".

-- 
Daniel Jacobowitz
CodeSourcery

Re: Remote monitor 'qCmd' command response

[Mitchell Fang]

Aye...silly me.  I don't know why I was so so intent on encoding the
O.  Thanks for the help Daniel.

For future reference here's the correct response:

View for log:
c monitor load bin 888.bin
w $qRcmd,6c6f61642062696e203838382e62696e#a9
r +$O4c6f6164696e672e2e2e0a#20

now it responds "Loading..."

On 6/7/06, Daniel Jacobowitz <drow@false.org> wrote:
> On Wed, Jun 07, 2006 at 12:01:41PM -0700, Mitchell Fang wrote:
> > What happens right now is that I send 'OLoading...' and then gdb
> > doesn't accept the other responses cause it thinks its the final
> > result packet.
> >
> > Here's what is shows on the console:
> >
> > (gdb) monitor load
> > 0Loading...
> > (gdb)
> >
> > Here is the log:
> >
> > w $qRcmd,6c6f61642062696e203838382e62696e#a9
> > r +<Timeout: 2 seconds>
> > w -
> > r <Timeout: 2 seconds>
> > w -
> > r $4f4c6f6164696e672e2e2e0a#6b
> > w +
>
> That's not "OLoading...".  The _data_ for the packet is supposed to be
> hex escaped, not the packet itself.  It should start with an "O".
>
> --
> Daniel Jacobowitz
> CodeSourcery
>