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 have the most used registers in the G/g packet and use P/p for the rest. If you make an XML description (not sure if OpenOCD supports it, but would be nice), you might even not need to rebuild GDB to make use of it. 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 of JB> me, figure out where I could get the right connection* to be putting JB> the data out at the right place. Also, the unconditional "OK" being JB> sent isn't great either - perhaps that could be conditional on a JB> return value from command_run_line() or something. I'm quite sure you can send a different response for qRcmd - that's how you can use the usual "telnet" interface from inside GDB. Otherwise have a look at the File-I/O Remote Protocol Extension or qXfer commands. -- WBR, Igor mailto:skochin...@mail.ru _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
