[linux-sh:03385] Re: Problem when using GDB stub for SH2

Hi Fabio,

Fabio Giovagnini wrote:
> Did you used sh-ipl+g as is for sh-2 only setting you serial line?

I used my own UART initialization routine, and it is working. In fact, 
the hardware initialization part is not the issue. The problem is more 
on how gdb stub handles breakpoint and continue commands from gdb.

 >>5. start the kernel:
 >>    (gdb) c
 >>    Continuing.
 >>    Sending packet: $Z0,1ba26,2#70...Ack
 >>    Packet received:
 >>    Packet Z0 (software-breakpoint) is NOT supported
 >>    Sending packet: $m1ba26,2#27...Ack
 >>    Packet received: d107
 >>    Sending packet: $M1ba26,2:c320#39...Ack
 >>    Packet received: OK
 >>    Sending packet: $Hc0#db...Ack
 >>    Packet received:
 >>    Sending packet: $c#63...Ack

For the above scenario (in my previous email), I have a few questions:
- why does gdb know to write "c320" which is the opcode for "trapa #32" 
for SH2?
- what are the possible reasons of why there is no response from stub 
after gdb sends the packet "$c#63"?

> It should be working with the job done by Paul Mundt.
> Is it rigth Paul?
> Anyway Min ZOU, we have a working version for sh4 7044.

Where is the source code available?

Thanks!

-- 
Best regards,
Min