Hi Steve, Don't mean to be a pest, but is there any chance you can make the new version of GDBProxy available soon?
Cheers, Rich :-) ----- Original Message ----- From: "Steve Underwood" <[email protected]> To: <[email protected]> Sent: Saturday, March 06, 2004 10:37 AM Subject: Re: [Mspgcc-users] GDBProxy support for 427 chip Hi Richard, This appears to mean Chris has not put the latest gdbproxy in that installer. gdbproxy needs updating for each new part that is launched, since it has to detect the signature of the device, and know its capabilities (e.g. number of breakpoints, if it has the enhanced emulation module, etc.). I actually need to publish a newer version of gdbproxy right now, which has support for the 415, 417, 1610, 1611, and 1612. I will try to get this out in a day or two. Regards, Steve Richard Willis wrote: >Hi, >I've just got a sample of the FE427 chip and am having trouble getting it to >work with the latest Windows installation, mspgcc-20040224.exe. > >Running GDBProxy give this: >======================== >C:\mspgcc\bin>msp430-gdbproxy --port=2000 msp430 > >Remote proxy for GDB, v0.7.1, Copyright (C) 1999 Quality Quorum Inc. >MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood > >GDBproxy comes with ABSOLUTELY NO WARRANTY; for details >use `--warranty' option. This is Open Source software. You are >welcome to redistribute it under certain conditions. Use the >'--copying' option for details. > >debug: MSP430_Initialize() >debug: MSP430_VCC(3000) >debug: MSP430_Identify() >info: msp430: Target device is a 'Device unknown' (type 0) >debug: MSP430_Configure() >notice: msp430-gdbproxy: waiting on TCP port 2000 >======================== > >So, it's saying 'Device unknown'. Is this a problem? Running >msp430-gdb.exe (GNU gdb 6.0) then gives: >======================== >(gdb) monitor identify >Current target device is a 'Device unknown' (type 0), so: > Main memory is from 0x0 to 0xFFFF (65536 bytes) > Info memory is from 0x0 to 0xFF (256 bytes) > RAM is from 0x200 to 0x0 (-511 bytes) > Up to 2 breakpoints are supported > Emulation level is 0 > Clock control level is 0 > VCC is from 1.800V to 3.600V > Has a test Vpp pin > >(gdb) erase all >Erasing all flash memory >Erasing target flash - all...MSP430 error: Invalid parameter(s) (3) >Protocol error with Rcmd >======================== > >So I can't even erase the chip... Help ! > >Cheers, >Rich. > > > >------------------------------------------------------- >This SF.Net email is sponsored by: IBM Linux Tutorials >Free Linux tutorial presented by Daniel Robbins, President and CEO of >GenToo technologies. Learn everything from fundamentals to system >administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click >_______________________________________________ >Mspgcc-users mailing list >[email protected] >https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > > ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
