With high hopes I then attempted the 4.x series. Is there a
different way to load code onto the micro? I resorted to the 3.2.3
branch's msp430-jtag and msp430-gdbproxy (with the 4.x series
version of msp430-gdb). Neither seemed to actually convince the
processor to run the code.
I think I posted a similar question this list, but never got an
answer. I have the same setup -- msp430-gdbproxy from the 3.2.3
branch and 4.x compiler/gdb. FWIW, I'm using msp430-gdb 7.0.1 and
msp430-gdb 4.4.3, both from the sourceforge repository and built on my
mac. But the binary packages I worked on my windows machine, too.
The only thing that got me was needing to erase the flash before
uploading new code. So I have the following in my .gdbinit:
define connect
set remoteaddresssize 64
set remotetimeout 999999
target remote 192.168.3.9:2000
end
connect
define hook-load
monitor erase main
end
After that it's just 'msp430-gdb something.elf' and then 'load'. At
that point backtrace gives me:
(gdb) bt
#0 0x00001100 in _reset_vector__ ()
'continue' should then run the code..
While I'm at it, here's what I do for debug info:
-ggdb -g3 -femit-class-debug-always -femit-struct-debug-detailed=any
As a final random thought, you might try increasing the alignment to
like 4 or 8 bytes in the hope of shaking something loose in gcc, but
it's just a shot in the dark.
Good luck!
Tyler
