Stephen Glow schrieb:
Does anyone know exactly what the development status of gdbproxy is at
the moment? It seems like lots of people are having problems getting
the Linux version of this program to work with newer devices. The files
on source forge haven't been updated for well over a year. Has this
program been abandoned by it's developers?
not actively abandoned, no.
the build of msp430-gdbroxy involves some code to interface with the
MSP430.dll. that interface is under an NDA.
number of persons that can currently build msp430-gdbproxy:
1
(not me)
msp430-gdbproxy itself doesn't need to know the CPU type as far as i
know. that knowledge is in MSP430.dll. however it seems that the
interface to MSP430.dll has undergone some minor changes, so that not
all DLLs work.
Why exactly is this software closed source anyway? I realize there's
some sort of NDA involved, but does anyone know what that covers? The
well, the management at TI seems to be convinced that this situation is
the best for their company.
as user of many open source software i can not share this view, but i
can understand it.
JTAG interface seems to be fairly well documented by TI.
only the basics. the application note describes the electrical signals
and how the JTAG state machine works. it gives you access to the address
and data bus and some sort of single stepping of instructions.
this enables to use the built in flash controller to program the Flash
memory and some more nifty things.
however this is far away from debugging with breakpoints. that is part
where the NDA begins.
How can we fix this problem?
we can't. someone could reverse engineer at the dll level or at the JTAG
level but i don't think that will lead to a well functioning debugger ;-)
the best part would be if TI would open its JTAG description with the
debugging part. then we could implement a msp430-gdb that works without
the gdbproxy.
chris
