On 2007-12-15, Steve Underwood <[email protected]> wrote: >>>> Since the DLL files appear to work with the IAR debugger is it >>>> safe to assume that they're up-to-date enough?and that it's >>>> msp430-gdbproxy itself that needs to be udpated? >>>> >>>> What does it take to add a new device type to msp430-gdbproxy? >>>> >>>> Is there anything I can do to help? >>>> >>> Any available device should work with >>> >>> http://www.soft-switch.org/downloads/mspgcc/MSP430.dll >>> >> >> Using msp430.dll and msp430-gdbproxy.exe from the above link, I >> get the output shown above (same results with IAR's msp430.dll >> and soft-switch's msp430.dll).
[...] > I haven't actually tried the latest MSP430.dll at > www.soft-switch.org with an F2330, because I haven't yet seen > one of those devices. However, it is the latest TI DLL code, > and seems to work OK with other new devices, like the F2169. All I know is that msp430-gdbproxy on Windows doesn't recognize the part (it turns out it's actually a F2370 instead of a F2330) when using either the IAR msp430.dll or the soft-switch msp430.dll. I assume that msp430-gdbproxy will always use .dll files in the current directory (also the location of of msp430-gdbproxy) rather than pulling in a .dll from some other location? If that's not the case, then I don't know how to tell exactly what msp430.dll file is being used. The IAR msp430.dll file does work when I use it with IAR EW 4.0. I never tried using the soft-switch msp430.dll with IAR EW 4.0. -- Grant
