Hi Igor,
> JB> However, I'd really like something which would allow custom RSP
> JB> commands (which can write back to the socket) to be handled.
> JB> The problems I see are that, even though the gdb_put_packet() function
> JB> is declared and could be used by target code, I can't, for the life o
On 21 July 2011 11:18, Igor Skochinsky wrote:
> Hello Julius,
>
> Thursday, July 21, 2011, 11:48:17 AM, you wrote:
>
> JB> I'm looking at adding OpenRISC 1000 support to OpenOCD.
> [skip]
> JB> One solution is we make our GDB port not use these remote query
> JB> commands and instead rely on the r
Hello Julius,
Thursday, July 21, 2011, 11:48:17 AM, you wrote:
JB> I'm looking at adding OpenRISC 1000 support to OpenOCD.
[skip]
JB> One solution is we make our GDB port not use these remote query
JB> commands and instead rely on the register cache fetched with the "g"
JB> RSP command.
You can
Hi all,
I'm looking at adding OpenRISC 1000 support to OpenOCD.
At present, the OpenRISC GDB port implements reading and writing to
individual CPU registers by an "spr" command within GDB. This sends
out CPU register access requests as remote commands, and they are
handled in by the RSP server as
