Here is my small statistics:
On target MSP430F1611 with Self-made Parallel FET msp430-size gives me:
text data bss dec hex filename
39744 72 1086 40902 9fc6 ./dio.elf
latest msp430-gdbproxy with md5sum b4ced0208b029b4a25dc79930477656e
loads the elf for 2 min and 52 sec
older msp430-gdbproxy with md5sum 133779c83f80cd180822024264f63195
loads the same elf for 3 min and 12 sec
maybe compared with an older msp430-gdbproxy is slower, but maybe not.
for comparison here is statistic from my current msp430-jtag tool
(not latest in the cvs). is 21 seconds, which includes a few seconds
for compilations, erase and erase check...
I have the same problem with not recognized device before a year,
when I started to work with MSP430F1611 (I have used F169 before using
F1611). This kind of problems always are very nasty. I want to ask all
msp430-gdbproxy developers if is possible to provide some extra
functionality of this closed source tool. I mean to add external
configuration text or xml file, which contain IDs, device names,
programming algo and etc, so each user can add latest devices if the
programming is possible due to hardware limitations and programming
sequences limitations... The msp430-gdbproxy developers can make new
version for bugfixes, new features, new default configuration file and
etc. Also to change tool version. If some one ask me which is your
msp430-gdbproxy version I'll tell him - 0.7.1. :))) a little bit
confusing...
regards,
Petar Petkoff
