Hi,

I appear to be having the same difficulty with gdb-proxy and the FG439
chip as John is.

A F1121 chip with gdb/gdb-proxy works on Linux; and the FG439 works with
C-SPY on Windows.
Both using the same JTAG interface hardware.

However, with the FG439 (specifically the "retro watch") and gdb-proxy; I
receive the same response as John:
debug:     msp430: msp430_open()
info:      msp430: Target device is a 'Device unknown' (type 0)
notice:    msp430-gdbproxy: waiting on TCP port 2000

I am using the gdb-proxy version from ftp.opencall.org

Regards,
Jamie Lawson

On Sun, 30 May 2004, Steve Underwood wrote:

> Hi John,
>
> I don't understand what you mean. I said the latest gdbproxy supports
> everything released to date, so a new variant is no problem at all. The
> FG43x parts work OK with gdbproxy. If you got the result shown below,
> you didn't get the latest gdbproxy from ftp.opencall.org
>
> Regards,
> Steve
>
>
> John Griessen wrote:
>
> >I'm a new user.
> >
> >I got this far using my TI FET kit and the mspgcc pages and
> >http://www.mikrocontroller.net/mspgcc.en.htm
> >
> >The mikrocontroller.net page is essential for beginners, please point to
> >it from all other beginner howto fragments.
> >
> >Does this mean my choice of a new variant stopped me?
> >
> >Is the pyjtag open method such that we can add new types by templating
> >from existing ones?
> >How does it compare to gdbproxy?
> >
> >debug:     msp430: msp430_open()
> >info:      msp430: Target device is a 'Device unknown' (type 0)
> >notice:    msp430-gdbproxy: waiting on TCP port 2000
> >

Reply via email to