Tom Russell wrote:
I am having trouble with the load function in insight (gdb):
I start msp430-gdbproxy and then insight.
I use File->Open and open test1.elf
I use Run->Connect to connect to the JTAG.
I open the Console and issue
commands:
monitor erase all
load test1.elf
That looks OK. If the "monitor erase all" command works, you should be
communicating OK with msp430-gdbproxy and the MCU.
If I just type "load", I get the error
Error: Invalid download offset: Files/mspgcc/demo/test1.elf
Strange. That doesn't normally happen. I have no idea what "load
test1.elf" will do, as "load" is usually used without parameters.
However, you indicate you have tried without parameters and had trouble,
The same thing happens if I use the download function in the Run menu.
The download function is just the same as using "load" from a console
window, and you would expect it to do the same thing.
My makefile (adopted from CVS archives) is:
NAME = test1
CPU = msp430x147
ASMOPT = -mmcu=${CPU}
COPT = -mmcu=${CPU} -O1 -Wall -g
${NAME}.elf: test1.o
msp430-gcc -mmcu=${CPU} -o $@ $^
msp430-objcopy -O ihex $@ ${NAME}.a43
msp430-objdump -DS ${NAME}.elf >${NAME}.lst
test1.o: test1.c
msp430-gcc ${COPT} -c $<
Those options look OK, wlthough msp430-objcopy and msp430-objdump are
needed if you are usign gdb. It only requires the elf file. "-O2" is the
more useful optimisation level, but "-O1" shouldn't give any trouble.
Did I do something wrong in the compilation?
You didn't say what platform you are using. Did you build the tools
yourself, or use an installer?
Regards,
Steve
