On Wed, Nov 18, 2009 at 10:43:35AM +1300, Bernard Mentink wrote:
> On Tue, Nov 17, 2009 at 3:53 PM, Daniel Beer <[email protected]> wrote:
>
> > Hi all,
> >
> > MSPDebug now supports the eZ430-F2013 and FET430UIF devices (though
> > it could probably do with a bit more testing).
> >
> > Source code and details here:
> >
> > http://homepages.xnet.co.nz/~dlbeer/
> >
> > Regards,
> > Daniel
> >
> > -
> >
>
> Thanks for the contribution.
> Forgive me for asking though, why do we need another debugger? What is wrong
> with gdb and gdbproxy?
> (Both of these integrate quite nice into an Eclipse IDE)
There are three things I don't like about gdb/gdbproxy:
* They don't support the eZ430-RF2500.
* They're quite cumbersome to use from the command line if you're
just trying to do something simple like reflash a chip (this was
kind of a pain at my last job). In MSPDebug you can just do:
./mspdebug -u /dev/ttyUSB0 "prog foo.hex"
* gdbproxy is proprietary (and thus not portable).
Of course, I understand that these won't be problems for everyone. They
were problems for me though, which is why I wrote MSPDebug :).
- Daniel
