RE: [Patch, microblaze]: Fix for remote G Packet message too long error for baremetal.

Ajit Kumar Agarwal
2014-07-02T10:40:26Z

-----Original Message-----
From: Michael Eager [mailto:eager@eagercon.com]
Sent: Tuesday, July 01, 2014 10:16 PM
To: Ajit Kumar Agarwal; Pedro Alves
Cc: gdb-patches@sourceware.org; Vinod Kathail; Vidhumouli Hunsigida; Nagaraju Mekala
Subject: Re: [Patch, microblaze]: Fix for remote G Packet message too long error for baremetal.

On 07/01/14 09:06, Ajit Kumar Agarwal wrote:
>
>
> -----Original Message-----
> From: Michael Eager [mailto:eager@eagercon.com]
> Sent: Monday, June 30, 2014 8:18 PM
> To: Ajit Kumar Agarwal; Pedro Alves
> Cc: gdb-patches@sourceware.org; Vinod Kathail; Vidhumouli Hunsigida;
> Nagaraju Mekala
> Subject: Re: [Patch, microblaze]: Fix for remote G Packet message too long error for baremetal.
>
> On 06/30/14 03:32, Ajit Kumar Agarwal wrote:
>> Based on the feedback, updated the patch with the review comments.
>
>>> How has this been tested? Please be specific.
>
> The patch has been tested with in-house applications with the older and newer designs for tar remote localhost:1234( 1234 port number) command.

When I said "be specific" I meant to give me *all* of the details of the environment.

Saying "older" and "newer" is much less than specific.
Saying "target remote ..." tells me absolutely nothing.

>>What target running which configurations built with which versions of EDK?

Target is microblaze-xilinx-elf New version is EDK 13.3 and New Microblaze version is 8.30.a( This supports the stack protect registers).

Target is microblaze-xilinx-elf old EDK version 12.4 and old microblaze version is 8.00b(This doesn't support the stack protect registers).

>>Which versions of XMD were tested?

Xilinx EDK 14.7 is used for testing. The designs with different configuration as mentioned above are downloaded and tested using this XMD.

Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077