For some reason newer versions of the JTAG library from TI are slower
than the old ones. The main thing affecting speed, however, is the
download block size. I forget the gdb commands you need, but you can
force gdb to send bigger blocks. gsb 5.1.1 sometimes sends big blocks,
but keeps going into a mode were it sends on 30 something bytes each
time. gdb 6.0 doesn't have this problem, and loads much faster.
Loading with another tool, and then debugging with msp430-gdbproxy is OK.
Regards,
Steve
dkorov...@luxoft.com wrote:
Colleagues, Steve,
First question, the old version of msp430-gdbproxy loaded program to
flash relatively faster than msp430-jtag. The newer version loads
program to flash much slower. Even slower that I thought it hanged. If
it’s necessary, I may measure the time.
Second question. On msp430x149 I did the following thing. I downloaded
the code to flash using msp430-jtag, next I started msp430-gdbproxy,
and debugged my code. Was this right? Because I can’t do this thing on
1611. Is there something that should be done to make this way possible
(specifically in case that msp430-gdbproxy can’t be forced to work
faster).
Thnks in advance,
Dmitriy Korovkin
