Re: [Mspgcc-users] Debugging msp430 with mspdebug and ccsv6

[Olivier G. <olg...@gm...>]

Hi Keane,

I have the exact same problem using the gdb beta together with the
openmsp430-gdbproxy (this is the mspdebug equivalent for the openMSP430
core: http://opencores.org/project,openmsp430).

Apparently, it seems to me that the error is generated when an expedited
response ("T") message is sent by the proxy to GDB to the new GDB beta.
In the openmsp430-gdbproxy, such a response is currently formatted as
following: "$T0500:f8c0;04:0000;".

Basically, together with the "T05" response, the proxy also returns the PC
value (00:f8c0) as well as the R4 value (04:0000)... now, as GDB complains
about the semicolon (i.e. digit 59) in the middle of this command because I
think it expects 32 bit register values instead of 16 bit previously (i.e.
it sees a semicolon while it expects two more bytes).
In fact, if I modify the openmsp430-gdbproxy to return such a response,
everything works fine again: "$T0500:f8c00000;04:00000000;"

Personally I have no idea if this is a bug or if this was implemented on
purpose (maybe a hint to an upcoming architecture)... however, it would be
really interested to know which one it is so that I can update my tool...
or not.

Cheers,
Olivier



> Date: Mon, 23 Dec 2013 10:36:05 -0800
> From: Wylder Keane <wyl...@gm...>
> Subject: [Mspgcc-users] Debugging msp430 with mspdebug and ccsv6
>         (beta) gdb
> To: msp...@li...
> Message-ID:
>         <CAP1=f4zqX=gTMkQriz6v5CzkLDex=
> 16k...@ma...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I'm having trouble debugging an msp430fr5969 using the new ccsv6 gcc
> toolchain. I'm trying to debug on the command line using mspdebug-0.22 as a
> proxy for the new msp430-elf-gdb that came with the ccsv6 beta and I keep
> getting the following error while trying to connect to mspdebug:
>
> (gdb) target remote localhost:2000
> Remote debugging using localhost:2000
> Reply contains invalid hex digit 59
>
> Is this because gdb was configured differently than mspdebug? Is there any
> way around this?
>
> I would very much like to debug my msp430's via GDB on the command line
> instead of through the CCS IDE.
>
> Thanks.