Quantcast

Re: Debugging msp430 with mspdebug and ccsv6

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Debugging msp430 with mspdebug and ccsv6

Olivier Girard
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 <[hidden email]>
> Subject: [Mspgcc-users] Debugging msp430 with mspdebug and ccsv6
>         (beta) gdb
> To: [hidden email]
> Message-ID:
>         <CAP1=f4zqX=gTMkQriz6v5CzkLDex=
> [hidden email]>
> 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.

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Debugging msp430 with mspdebug and ccsv6

Wylder Keane-2
Hey Olivier,

Thanks for the response. I just tried this modification to mspdebug and it
seems to connect now (no digit 59 error), though it segfaults when I go to
set a breakpoint. No idea quite why this is happening yet but I'll keep
digging. Let me know if you find anything.

Also, here is the output from mspdebug with the last command sent:

Interrupted by gdb

$T0500:1e600000;01:26f90000;02:03000000;03:00000000;04:ffff0000;05:ffff0000;06:ffff0000;07:74c10000;08:1ad20000;09:00000000;0a:b4c80000;0b:00000000;0c:00000000;0d:6c120100;0e:7c010000;0f:9cc00000;#78

Connection closed

Thanks,
-Wylder


On Tue, Jan 7, 2014 at 3:30 PM, Olivier Girard <[hidden email]> wrote:

> 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 <[hidden email]>
> > Subject: [Mspgcc-users] Debugging msp430 with mspdebug and ccsv6
> >         (beta) gdb
> > To: [hidden email]
> > Message-ID:
> >         <CAP1=f4zqX=gTMkQriz6v5CzkLDex=
> > [hidden email]>
> > 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.
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> Mspgcc-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/mspgcc-users
>
>

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Loading...