On 2009-11-17, Daniel Beer <[email protected]> wrote:
>> 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.
Yup, there are some parts that gdbproxy just doesn't support.
The last part I used wasn't support by gdbproxy under either
Linux or Windows. :/
> * 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"
To be honest, one doesn't use gdb for that. One typically uses
msp430-jtag:
msp430-jtag -e foo.hex
Unfortunately, there are also parts that msp430-jtag doesn't
support (for those I had to use the Elprotronic programmer
under Windows).
> * gdbproxy is proprietary (and thus not portable).
Are there CPU/JTAG features under NDA that gdbproxy supports
that MSPDebug doesn't? If not, one wonders why gdbproxy is
subject to an NDA.
All in all, the JTAG/debug/flash-programming support situation
for the MSP430 family is in rather sad shape, so it certainly
won't hurt to have another option.
--
Grant Edwards grante Yow! I brought my BOWLING
at BALL -- and some DRUGS!!
visi.com
