Support for Xilinx MicroBlaze architecture (1 of 3)
Michael Eager
eager@eagercon.com
Sat Sep 12 18:35:00 GMT 2009
Eli Zaretskii wrote:
>> By default
>> +@code{xmd} uses port @code{1234}.
>
> Is there a way to change this default, and if so, should we let the
> user know how to do that?
There's documentation in the Xilinx EDK/SDK or running "xmd --help"
lists the options. I believe that there is an option to set the port.
Do you think that xmd should be described in the gdb info? Or
only this option?
>
>> +@item target remote XMD-HOST:1234
>> +@kindex target remote xmd-host>:1234
>> +Use this command to connect to the target if you are running @value{GDBN}
>> +on a different system @code{xmd}, which is running on @code{XMD-HOST}.
>
> I understand that XMD-HOST stands for the real name of the host. If
> so, we use the @var markup in Texinfo for this:
>
> +@item target remote @var{xmd-host}:1234
> +Use this command to connect to the target if you are running @value{GDBN}
> +on a different system @code{xmd}, which is running on @var{xmd-host}.
Sure.
> Finally, the index entries you have are not useful: they all are for
> commands that are not specific to the XMD target, and already have
> index entries elsewhere in the manual, where the general form of these
> commands is described. What is needed in this section is @cindex
> entries about the XMD itself, so that the reader could easily find
> this section. So I suggest these entries immediately after the
> @subsection line:
>
> @cindex Xilinx MicroBlaze
> @cindex XMD, Xilinx Microprocessor Debugger
I'll pull the generic index entries and add these.
> Okay with these changes.
Thanks.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
More information about the Gdb-patches
mailing list