Hi Daniel, Really happy with the '247 support :) However... (uh oh ;-)) now they've given me 2272's to work with, which mspdebug recognizes as a 2234:
$ ./mspdebug uif -j -d /dev/ttyUSB0 'prog blink.hex' MSPDebug version 0.13 - debugging tool for MSP430 MCUs Copyright (C) 2009, 2010 Daniel Beer <[email protected]> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Trying to open UIF on /dev/ttyUSB0... Initializing FET... FET protocol version is 20401004 Configured for JTAG (2) Set Vcc: 3000 mV Device ID: 0xf227 Device: MSP430F2234 Code memory starts at 0xe000 Number of breakpoints: 2 Erasing... Programming... Writing 128 bytes to 8000... fet: FET returned error code 7 (Could not write device memory) fet: failed to write to 0x8000 ihex: error on line 9 It works if I use --fet-force-id MSP430F2274 (which has the same memory layout), but I figured you might be able to correct the identification. Here's the msg28 bytes: $ ./mspdebug uif -j -d /dev/ttyUSB0 --fet-force-id foo 'prog blink.hex' MSPDebug version 0.13 - debugging tool for MSP430 MCUs Copyright (C) 2009, 2010 Daniel Beer <[email protected]> This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Trying to open UIF on /dev/ttyUSB0... Initializing FET... FET protocol version is 20401004 Configured for JTAG (2) Set Vcc: 3000 mV Device ID: 0xf227 fet: unknown device msg28_data: [0x1a bytes] f2 27 50 40 00 00 00 00 00 00 02 02 01 04 a1 61 84 00 89 00 00 00 00 00 00 00 fet: identify failed Trying again... Initializing FET... FET protocol version is 20401004 Configured for JTAG (2) Sending reset... Set Vcc: 3000 mV Device ID: 0xf227 fet: unknown device msg28_data: [0x1a bytes] f2 27 50 40 00 00 00 00 00 00 02 02 01 04 a1 61 84 00 89 00 00 00 00 00 00 00 fet: identify failed Having it work by default would be nice, but the workaround has been fine so far. Kind regards, Michiel > -----Original Message----- > From: Daniel Beer [mailto:[email protected]] > Sent: maandag 8 november 2010 22:48 > To: GCC for MSP430 - http://mspgcc.sf.net > Subject: [Mspgcc-users] MSPDebug version 0.13 > > MSPDebug version 0.13 is now available from mspdebug.sourceforge.net. > Changes in this release are: > > * Bug fix: incorrect handling of Intel HEX segment offsets. > * Support for new chips: MSP430F1121, MSP430F2131, MSP430F2617, > MSP430F247, MSP430F4270, MSP430G2231, CC430F5133. > * Support for Olimex MSP430-JTAG-ISO. > * FET driver retries with a reset if the first attempt to > connect fails. This should fix the problem which requires > devices to be replugged after each session. > * Notify the user when programming in quiet mode, and display > version banner unless starting in quiet mode. > > As always, let me know if you have any questions or comments. > > Regards, > Daniel > > -- > D.L. Beer Engineering > www.dlbeer.co.nz > > ----------------------------------------------------------------------- > ------- > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users ------------------------------------------------------------------------------ The Next 800 Companies to Lead America's Growth: New Video Whitepaper David G. Thomson, author of the best-selling book "Blueprint to a Billion" shares his insights and actions to help propel your business during the next growth cycle. Listen Now! http://p.sf.net/sfu/SAP-dev2dev _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
